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.

Cloud

2/25/2019
10:30 AM
John Carbo
John Carbo
Commentary
100%
0%

Secure the System, Help the User

The enterprise must do its part in deploying and maintaining secure systems so that end users stand a chance against attackers.

Relying on end users for security is difficult, but securing enterprise systems doesn't have to be. For a system to be valuable, it must be accessible and beneficial to end users. Organizations have improved security awareness training for employees, but the training has limited value until the underlying systems are secured. Securing a system removes an attack vector that funnels the attack up to the end user (such as phishing). This is when training shows its value.

Remove the Attack on the System + Train End Users on Most Likely Attacks = Thwart the Attacker
Secure life cycle management sounds difficult, but it isn't. The approach starts with identifying the systems that are running in the enterprise. If you have an inventory of these assets, great! If not, then start scanning your networks for hosts, look at Active Directory or LDAP, ask around, and create an inventory list. (Your last resort is pulling the plug to see who screams.) If you work in the cloud, check the invoice for systems.

Once you have an inventory, prioritize everything according to what's important to the enterprise. Anything hanging off the external network is a priority because it is accessible from the Internet. Internal systems with sensitive information are a high priority (personally identifiable information, financial info, customer, backups, etc.). Prioritizing is important because resources to secure the systems are always constrained.

Now it's time to find out how bad things are. It's impossible to manually check each system for patch levels or security settings, so don't even try. Use a benchmarking tool like the Center for Internet Security's CIS-CAT, Microsoft's Baseline Security Analyzer, or a vulnerability scanner. These tools will take your inventory list, compare items to known good security configurations, and provide a gap report for each system.

Review the recommendations and decide which ones make sense for your enterprise. Benchmarks have different levels of recommendations, and the highest-level security recommendations may not work for your enterprise (because they're too restrictive). If your enterprise has regulatory requirements, now is the time to align with them.

Come up with a strategy to get systems secured according to the recommendations. All new systems should receive the approved recommendations by default. Existing systems will need to be scheduled according to their priority. Now is a good time to decommission unnecessary or legacy systems (for example, the dusty machine under the desk), and don't forget about development systems. Even though a system may not be in production for end users, if it is on the network then it can be a weak link in the overall security of the enterprise.

The full life cycle of the system is from when it's turned on until it's turned off. It must be secure during the entire life, so deploy it based on the secure configuration and keep it maintained until it is powered off. Maintenance is critical because a lot of time and effort was spent getting the enterprise secured up to this point. Keep on top of the latest benchmark releases, and scan the enterprise environment with a vulnerability tool (such as OpenVas, Tenable Nessus, Rapid7 Nexpose, etc.). Benchmarking and vulnerability scanning should be integrated into the enterprise patch management program. This will ensure that a system is initially deployed securely and is kept up to date until it's powered off and securely disposed.

There is a great feeling in the secure life cycle when subsequent reports show how much progress has been made in securing systems. No enterprise can be made 100% secure; the goal is to reduce the risk to an acceptable level and give end users the best chance at thwarting attackers through the training they receive. Most breaches occur because of insecure configuration or lack of system patching. Ponemon Institute's 2018 State of Endpoint Security Risk states that the average time to patch is 102 days. This provides attackers with a large window to find weak points to exploit. Unless your enterprise is specifically targeted, keeping secure configurations and patches up to date is a great way to not end up in the news.

Related Content:

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry's most knowledgeable IT security experts. Check out the Interop agenda here.

John Carbo is the Director of Information Security at Abacus Group, an IT service provider for alternative investment firms. He oversees the security of the Abacus Cloud platform and advises clients on their security strategies. John has spent his entire career in the ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Edge-DRsplash-10-edge-articles
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
News
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Commentary
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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-32606
PUBLISHED: 2021-05-11
In the Linux kernel 5.11 through 5.12.2, isotp_setsockopt in net/can/isotp.c allows privilege escalation to root by leveraging a use-after-free. (This does not affect earlier versions that lack CAN ISOTP SF_BROADCAST support.)
CVE-2021-3504
PUBLISHED: 2021-05-11
A flaw was found in the hivex library in versions before 1.3.20. It is caused due to a lack of bounds check within the hivex_open function. An attacker could input a specially crafted Windows Registry (hive) file which would cause hivex to read memory beyond its normal bounds or cause the program to...
CVE-2021-20309
PUBLISHED: 2021-05-11
A flaw was found in ImageMagick in versions before 7.0.11 and before 6.9.12, where a division by zero in WaveImage() of MagickCore/visual-effects.c may trigger undefined behavior via a crafted image file submitted to an application using ImageMagick. The highest threat from this vulnerability is to ...
CVE-2021-20310
PUBLISHED: 2021-05-11
A flaw was found in ImageMagick in versions before 7.0.11, where a division by zero ConvertXYZToJzazbz() of MagickCore/colorspace.c may trigger undefined behavior via a crafted image file that is submitted by an attacker and processed by an application using ImageMagick. The highest threat from this...
CVE-2021-20311
PUBLISHED: 2021-05-11
A flaw was found in ImageMagick in versions before 7.0.11, where a division by zero in sRGBTransformImage() in the MagickCore/colorspace.c may trigger undefined behavior via a crafted image file that is submitted by an attacker processed by an application using ImageMagick. The highest threat from t...