Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
7 Ways to Better Secure Electronic Health Records
Newest First  |  Oldest First  |  Threaded View
tdsan
100%
0%
tdsan,
User Rank: Ninja
7/26/2018 | 3:06:35 PM
Re: The BEST way to secure electronic health records
I agree with the first person who commented on the article (patch fanatic) but there is something flawing with out thinking because the hacks are still occuring, even though the numbers are down, it is still happening. I do think there are a few things that we need to follow that most organizations don't do:

→ Training needs to be put at the forftont, we need to evaluate the talent we have on staff on a consistent basis

→ Firewalls, routers, switches and other network gear needs to be follow the NSA security guidelines and framework - https://www.vmguru.com/2017/04/sizing-your-vmware-infrastructure/ (we need to add to this guideline and continue to test so we can push the envelope (or at least get close)

→ We really need to remove IPv4 from the mix of solutions and move to an IPv6 (pure) environment

→ We need to have a moc setup where we pay someone to hack the environment and we test the people there by putting them into a scenario

→ Application programming methodologies need to be reviewed by qualified hackers who have a deveopment background

→ We need to employ machine learning in the mix of products where the technology is always checking to see who is accessing what and reporting or even thwarting it

→ We need to automate the pentesting process but tailor it to our needs, get it to the point that the vulnerabilities can be mitigating by a autonomic programming change

→ We need to prioritize the threats or vulnerabilities, schedule weekend schedule patch and system updates to ensure the systems meet a certain severity level (sev1-5) and if the sev level is reviewed by outside vendor (reputable)

→ Implement next generation firewalls, endpoint monitoring, NMS, HIDS, NIDS, Zone/Layering and application integration without our existing security tools

→ We need a protocol monitoring device that identifies and baselines relationships between systems and applications, if there is an outside presence, then the system needs to tell us

→ Move pertinent data to zone 0, do not install DB on Web applications (separation of duties) and only allow data to write after a cleansing or holding area (similar to ACH) to ensure the data has not been compromised

→ If multiple records have been extracted by an outside source (Database), there needs to be a warning and action to go along with this potential threat, or at least after 10 records, then something needs to stop the data extraction (notification or autonomic stoppage)

→ If we are not doing business with a specific country, then block those countries that are not in our purvey using ACLs, NGFW with Country blocking capability

→ DNS needs to be configured with DNSSEC using specific keys that are stored in a safe place and only allow queries (recursive) to be done by systems that are internal, anything from the outside trying to access and perform lookups internally with outside IP addresses need to be thwarted

There are other things but this all I can think of right now.

Todd
paul.dittrich
50%
50%
paul.dittrich,
User Rank: Strategist
7/24/2018 | 3:36:35 PM
The BEST way to secure electronic health records
My #1 suggestion:

Be an absolutely merciless fanatic about patching and updating your software.  All of it.  Every day.  On every device you own.

The suggestions in the column are certainly valid but some of them require external experts and/or a higher level of technical skill than simply updating existing software.  IMO, keeping all software 100% up-to-date is the single most important security measure for just about every organization.


Commentary
How SolarWinds Busted Up Our Assumptions About Code Signing
Dr. Jethro Beekman, Technical Director,  3/3/2021
News
'ObliqueRAT' Now Hides Behind Images on Compromised Websites
Jai Vijayan, Contributing Writer,  3/2/2021
News
Attackers Turn Struggling Software Projects Into Trojan Horses
Robert Lemos, Contributing Writer,  2/26/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: George has not accepted that the technology age has come to an end.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-26814
PUBLISHED: 2021-03-06
Wazuh API in Wazuh from 4.0.0 to 4.0.3 allows authenticated users to execute arbitrary code with administrative privileges via /manager/files URI. An authenticated user to the service may exploit incomplete input validation on the /manager/files API to inject arbitrary code within the API service sc...
CVE-2021-27581
PUBLISHED: 2021-03-05
The Blog module in Kentico CMS 5.5 R2 build 5.5.3996 allows SQL injection via the tagname parameter.
CVE-2021-28042
PUBLISHED: 2021-03-05
Deutsche Post Mailoptimizer 4.3 before 2020-11-09 allows Directory Traversal via a crafted ZIP archive to the Upload feature or the MO Connect component. This can lead to remote code execution.
CVE-2021-28041
PUBLISHED: 2021-03-05
ssh-agent in OpenSSH before 8.5 has a double free that may be relevant in a few less-common scenarios, such as unconstrained agent-socket access on a legacy operating system, or the forwarding of an agent to an attacker-controlled host.
CVE-2021-3377
PUBLISHED: 2021-03-05
The npm package ansi_up converts ANSI escape codes into HTML. In ansi_up v4, ANSI escape codes can be used to create HTML hyperlinks. Due to insufficient URL sanitization, this feature is affected by a cross-site scripting (XSS) vulnerability. This issue is fixed in v5.0.0.