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 and has covered networking, security, and IT as a writer and editor since 1992. Steve is based in Columbia, Md. View Full Bio
 

Recommended Reading:

Previous
1 of 8
Next
Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest 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.
Commentary
What the FedEx Logo Taught Me About Cybersecurity
Matt Shea, Head of Federal @ MixMode,  6/4/2021
Edge-DRsplash-10-edge-articles
A View From Inside a Deception
Sara Peters, Senior Editor at Dark Reading,  6/2/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
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-23394
PUBLISHED: 2021-06-13
The package studio-42/elfinder before 2.1.58 are vulnerable to Remote Code Execution (RCE) via execution of PHP code in a .phar file. NOTE: This only applies if the server parses .phar files as PHP.
CVE-2021-34682
PUBLISHED: 2021-06-12
Receita Federal IRPF 2021 1.7 allows a man-in-the-middle attack against the update feature.
CVE-2021-31811
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-31812
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an infinite loop while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-32552
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-16 package apport hooks, it could expose private data to other local users.