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.

Endpoint

10/8/2019
11:30 AM
Steve Zurier
Steve Zurier
Slideshows
Connect Directly
Twitter
RSS
E-Mail
100%
0%

7 Considerations Before Adopting Security Standards

Here's what to think through as you prepare your organization for standards compliance.
Previous
1 of 8
Next

Image Source: Adobe Stock:  leowolfert

Image Source: Adobe Stock: leowolfert

ISO 27001. PCI DSS. GDPR. When it comes to business and security standards, it's easy to get lost in the alphabet soup of acronyms.

How can you discern which ones are right for your organization? Start by asking some high-level questions as to what you hope to accomplish by adopting them – and how adhering to standards can help your growth, says Khushbu Pratap, a senior principal analyst at Gartner who covers risk and compliance.

"The most important questions to ask [are]: Are your customers asking for it, and do your stakeholders think a particular standard is important?" says Pratap.

Assuming the answers are yes, there are additional factors to think through before moving ahead with a strategy for compliance. The seven practical tips outlined in this feature will help. Heavily regulated organizations typically have special teams that work on these standards, but even for them, use this list as a chance to take a step back and better target your standards compliance and certification teams.

 

Steve Zurier has more than 30 years of journalism and publishing experience, most of the last 24 of which were spent covering networking and security technology. Steve is based in Columbia, Md. View Full Bio

Previous
1 of 8
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
MarkL199
50%
50%
MarkL199,
User Rank: Apprentice
10/23/2019 | 4:59:45 AM
ISO 27001 used as a Framework
I agree with the article in that you really need to understand the business drivers, but I also think that a vast majority of business would be best served using ISO 27001 as their Information Security Management System. This gives the framework for their security program as a whole, from the creation of policies to performing compliance activities. I would not even consider certification, unless there is an overwhelming need. The next decision is whether to use the controls contained within ISO 27001, or take the opportunity to swap out more suitable controls (e.g. NIST, CIS20, ISF, PCI DSS etc.). The good thing about ISO 27001 is that it does give a wide coverage of controls across a security program, such as covering non IT-related area's most other controls don't (e.g. policies, people, physical etc.) However, ISO 27001 can be a bit high level and not detailed enough, even if using ISO 27002. This is where tailoring your controls either by using say NIST SP 800-53 across your enterprise, or specific requirements (e.g. PCI DSS). I personally like to use ISO27001 as the framework and also utilise the non-tech controls contained within. Then I would bring in more specific controls to cover the technical side, cloud specific, privacy, IoT etc. My concern about going straight to NIST is that although they are excellent controls, they are designed for information systems and therefore focus on the IT security side and not really a holistic information security program. Lack resources, time, or just need to get some technical controls in fast? I would go with CIS20 controls as they are very easy to follow and lead you through a three stage maturity process.
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5292
PUBLISHED: 2020-03-31
Leantime before versions 2.0.15 and 2.1-beta3 has a SQL Injection vulnerability. The impact is high. Malicious users/attackers can execute arbitrary SQL queries negatively affecting the confidentiality, integrity, and availability of the site. Attackers can exfiltrate data like the users' and admini...
CVE-2020-7009
PUBLISHED: 2020-03-31
Elasticsearch versions from 6.7.0 to 6.8.7 and 7.0.0 to 7.6.1 contain a privilege escalation flaw if an attacker is able to create API keys. An attacker who is able to generate an API key can perform a series of steps that result in an API key being generated with elevated privileges.
CVE-2019-13495
PUBLISHED: 2020-03-31
In firmware version 4.50 of Zyxel XGS2210-52HP, multiple stored cross-site scripting (XSS) issues allows remote authenticated users to inject arbitrary web script via an rpSys.html Name or Location field.
CVE-2020-5291
PUBLISHED: 2020-03-31
Bubblewrap (bwrap) before version 0.4.1, if installed in setuid mode and the kernel supports unprivileged user namespaces, then the `bwrap --userns2` option can be used to make the setuid process keep running as root while being traceable. This can in turn be used to gain root permissions. Note that...
CVE-2019-14905
PUBLISHED: 2020-03-31
A vulnerability was found in Ansible Engine versions 2.9.x before 2.9.3, 2.8.x before 2.8.8, 2.7.x before 2.7.16 and earlier, where in Ansible's nxos_file_copy module can be used to copy files to a flash or bootflash on NXOS devices. Malicious code could craft the filename parameter to perform OS co...