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
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19037
PUBLISHED: 2019-11-21
ext4_empty_dir in fs/ext4/namei.c in the Linux kernel through 5.3.12 allows a NULL pointer dereference because ext4_read_dirblock(inode,0,DIRENT_HTREE) can be zero.
CVE-2019-19036
PUBLISHED: 2019-11-21
btrfs_root_node in fs/btrfs/ctree.c in the Linux kernel through 5.3.12 allows a NULL pointer dereference because rcu_dereference(root->node) can be zero.
CVE-2019-19039
PUBLISHED: 2019-11-21
__btrfs_free_extent in fs/btrfs/extent-tree.c in the Linux kernel through 5.3.12 calls btrfs_print_leaf in a certain ENOENT case, which allows local users to obtain potentially sensitive information about register values via the dmesg program.
CVE-2019-6852
PUBLISHED: 2019-11-20
A CWE-200: Information Exposure vulnerability exists in Modicon Controllers (M340 CPUs, M340 communication modules, Premium CPUs, Premium communication modules, Quantum CPUs, Quantum communication modules - see security notification for specific versions), which could cause the disclosure of FTP har...
CVE-2019-6853
PUBLISHED: 2019-11-20
A CWE-79: Failure to Preserve Web Page Structure vulnerability exists in Andover Continuum (models 9680, 5740 and 5720, bCX4040, bCX9640, 9900, 9940, 9924 and 9702) , which could enable a successful Cross-site Scripting (XSS attack) when using the products web server.