Blog
Compliance

ISO 27001 compliance: your essential guide

Jack McDonach
Author
Jack McDonach
Technical Solutions Specialist

Key Points

What is ISO 27001?

ISO 27001 is a compliance standard designed to manage information security. It provides a robust framework for creating and maintaining an Information Security Management System (ISMS).

Created and managed by the International Organization for Standardization (ISO), it is underpinned by three core principles: Confidentiality, Integrity, and Availability of information.  

It is internationally recognized and the go-to standard for information security (infosec), so obtaining ISO 27001 compliance sends a powerful message to your customers, clients, regulators, staff and other stakeholders that your organization is committed to upholding the highest security standards.

Who needs ISO 27001 certification?

According to ISO, over 70,000 ISO 27001 organizations are certified in over 150 countries – spanning all industries, but especially those in risk-averse sectors such as finance, healthcare, and defense.  

Although it’s a natural fit for these types of organizations, ISO 27001 can be beneficial to anyone that needs to prove that the sensitive information they store is safe, regardless of company size. The standard demands that controls, procedures and risk management is airtight, which can boost customer confidence and, in turn, open up more business opportunities.  

Why is ISO 27001 important?

Cyber threats are both amorphous and relentless, making cyber security a priority for all, but a daunting prospect for some. Fortunately, the holistic approach to information security provided by ISO 27001 makes it a good foundation for organizations keen to improve their security posture.  

By integrating information security principles at the core of your organization and reducing the burden on maintenance and removing the mystery often associated with it, ISO 27001 compliance can help ingrain security in all your processes and controls, so it’s not something that has to be introduced as a standalone consideration.

What are ISO 27001’s controls?

ISO 27001 consists of 114 security controls grouped into 14 areas:

  • Information security policies  
  • Organization of information security
  • Human resources security
  • Asset management
  • Access control
  • Cryptography
  • Physical and environmental security
  • Operations security
  • Communications security
  • Systems acquisition, development and maintenance
  • Supplier relationships
  • Information security incident management
  • Information security aspects of business continuity management
  • Compliance

These controls will help you understand the gaps present in your current operations and processes, and then close or mitigate the risks associated with these.

How can vulnerability management help with ISO 27001 compliance?

Vulnerability management is simply best practice for every modern business today, and continuous monitoring should be integrated into your ISO 27001 controls. Vulnerability management can help to identify risks before exploitation or compromises, as well as improve the overall security posture for ISO 27001 compliance and audits.

FAQs

Is vulnerability scanning required for ISO 27001 compliance?

Although not actually specified by ISO 27001, it is highly recommended to run regular vulnerability scans to maintain visibility of your attack surface and get ahead of potential risks introduced by new, emerging or recurring vulnerabilities.

Is penetration testing required for ISO 27001 compliance?

Similar to vulnerability scanning, penetration testing isn’t a specific requirement for ISO 27001, however, it is considered best practice to conduct regular pentests.

How Intruder can help you achieve ISO 27001 compliance

ISO certification doesn’t need to be difficult with Intruder. Get audit-ready reports, continuous monitoring, integrations with Drata, Vanta, and more. Intruder takes the pain out of ISO 27001 compliance by automating and streamlining the reporting process, reducing both the cost and time of compliance. Why not try it for free for 14 days or get in touch to find out more.

Get our free

Ultimate Guide to Vulnerability Scanning

Learn everything you need to get started with vulnerability scanning and how to get the most out of your chosen product with our free PDF guide.

Sign up for your free 14-day trial

7 days free trial
Find out all you need to know about achieving ISO 27001 compliance and how vulnerability management can help with our essential guide.
back to BLOG

ISO 27001 compliance: your essential guide

Jack McDonach

What is ISO 27001?

ISO 27001 is a compliance standard designed to manage information security. It provides a robust framework for creating and maintaining an Information Security Management System (ISMS).

Created and managed by the International Organization for Standardization (ISO), it is underpinned by three core principles: Confidentiality, Integrity, and Availability of information.  

It is internationally recognized and the go-to standard for information security (infosec), so obtaining ISO 27001 compliance sends a powerful message to your customers, clients, regulators, staff and other stakeholders that your organization is committed to upholding the highest security standards.

Who needs ISO 27001 certification?

According to ISO, over 70,000 ISO 27001 organizations are certified in over 150 countries – spanning all industries, but especially those in risk-averse sectors such as finance, healthcare, and defense.  

Although it’s a natural fit for these types of organizations, ISO 27001 can be beneficial to anyone that needs to prove that the sensitive information they store is safe, regardless of company size. The standard demands that controls, procedures and risk management is airtight, which can boost customer confidence and, in turn, open up more business opportunities.  

Why is ISO 27001 important?

Cyber threats are both amorphous and relentless, making cyber security a priority for all, but a daunting prospect for some. Fortunately, the holistic approach to information security provided by ISO 27001 makes it a good foundation for organizations keen to improve their security posture.  

By integrating information security principles at the core of your organization and reducing the burden on maintenance and removing the mystery often associated with it, ISO 27001 compliance can help ingrain security in all your processes and controls, so it’s not something that has to be introduced as a standalone consideration.

What are ISO 27001’s controls?

ISO 27001 consists of 114 security controls grouped into 14 areas:

  • Information security policies  
  • Organization of information security
  • Human resources security
  • Asset management
  • Access control
  • Cryptography
  • Physical and environmental security
  • Operations security
  • Communications security
  • Systems acquisition, development and maintenance
  • Supplier relationships
  • Information security incident management
  • Information security aspects of business continuity management
  • Compliance

These controls will help you understand the gaps present in your current operations and processes, and then close or mitigate the risks associated with these.

How can vulnerability management help with ISO 27001 compliance?

Vulnerability management is simply best practice for every modern business today, and continuous monitoring should be integrated into your ISO 27001 controls. Vulnerability management can help to identify risks before exploitation or compromises, as well as improve the overall security posture for ISO 27001 compliance and audits.

FAQs

Is vulnerability scanning required for ISO 27001 compliance?

Although not actually specified by ISO 27001, it is highly recommended to run regular vulnerability scans to maintain visibility of your attack surface and get ahead of potential risks introduced by new, emerging or recurring vulnerabilities.

Is penetration testing required for ISO 27001 compliance?

Similar to vulnerability scanning, penetration testing isn’t a specific requirement for ISO 27001, however, it is considered best practice to conduct regular pentests.

How Intruder can help you achieve ISO 27001 compliance

ISO certification doesn’t need to be difficult with Intruder. Get audit-ready reports, continuous monitoring, integrations with Drata, Vanta, and more. Intruder takes the pain out of ISO 27001 compliance by automating and streamlining the reporting process, reducing both the cost and time of compliance. Why not try it for free for 14 days or get in touch to find out more.

Release Date
Level of Ideal
Comments
Before CVE details are published
🥳
Limited public information is available about the vulnerability.

Red teamers, security researchers, detection engineers, threat actors have to actively research type of vulnerability, location in vulnerable software and build an associated exploit.

Tenable release checks for 47.43% of the CVEs they cover in this window, and Greenbone release 32.96%.
Day of CVE publish
😊
Vulnerability information is publicly accessible.

Red teamers, security researchers, detection engineers and threat actors now have access to some of the information they were previously having to hunt themselves, speeding up potential exploit creation.

Tenable release checks for 17.12% of the CVEs they cover in this window, and Greenbone release 17.69%.
First week since CVE publish
😐
Vulnerability information has been publicly available for up to 1 week.

The likelihood that exploitation in the wild is going to be happening is steadily increasing.

Tenable release checks for 10.9% of the CVEs they cover in this window, and Greenbone release 20.69%.
Between 1 week and 1 month since CVE publish
🥺
Vulnerability information has been publicly available for up to 1 month, and some very clever people have had time to craft an exploit.

We’re starting to lose some of the benefit of rapid, automated vulnerability detection.

Tenable release checks for 9.58% of the CVEs they cover in this window, and Greenbone release 12.43%.
After 1 month since CVE publish
😨
Information has been publicly available for more than 31 days.

Any detection released a month after the details are publicly available is decreasing in value for me.

Tenable release checks for 14.97% of the CVEs they cover over a month after the CVE details have been published, and Greenbone release 16.23%.

With this information in mind, I wanted to check what is the delay for both Tenable and Greenbone to release a detection for their scanners. The following section will focus on vulnerabilities which:

  • Have CVSSv2 rating of 10
  • Are exploitable over the network
  • Require no user interaction

These are the ones where an attacker can point their exploit code at your vulnerable system and gain unauthorised access.

We’ve seen previously that Tenable have remote checks for 643 critical vulnerabilities, and OpenVAS have remote checks for 450 critical vulnerabilities. Tenable release remote checks for critical vulnerabilities within 1 month of the details being made public 58.4% of the time, but Greenbone release their checks within 1 month 76.8% of the time. So, even though OpenVAS has fewer checks for those critical vulnerabilities, you are more likely to get them within 1 month of the details being made public. Let’s break that down further.

In Figure 10 we can see the absolute number of remote checks released on a given day after a CVE for a critical vulnerability has been published. What you can immediately see is that both Tenable and OpenVAS release the majority of their checks on or before the CVE details are made public; Tenable have released checks for 247 CVEs, and OpenVAS have released checks for 144 CVEs. Then since 2010 Tenable have remote released checks for 147 critical CVEs and OpenVAS 79 critical CVEs on the same day as the vulnerability details were published. The number of vulnerabilities then drops off across the first week and drops further after 1 week, as we would hope for in an efficient time-to-release scenario.

Figure 10: Absolute numbers of critical CVEs with a remote check release date from the date a CVE is published

While raw numbers are good, Tenable have a larger number of checks available so it could be unfair to go on raw numbers alone. It’s potentially more important to understand the likelihood that OpenVAS or Tenable will release a check of a vulnerability on any given day after a CVE for a critical vulnerability is released. In Figure 11 we can see that Tenable release 61% their checks on or before the date that a CVE is published, and OpenVAS release a shade under 50% of their checks on or before the day that a CVE is published.

Figure 11: Percentage chance of delay for critical vulnerabilities

So, since 2010 Tenable has more frequently released their checks before or on the same day as the CVE details have been published for critical vulnerabilities. While Tenable is leading at this point, Greenbone’s community feed still gets a considerable percentage of their checks out on or before day 0.

I thought I’d go another step further and try and see if I could identify any trend in each organisations release delay, are they getting better year-on-year or are their releases getting later? In Figure 12 I’ve taken the mean delay for critical vulnerabilities per year and plotted them. The mean as a metric is particularly influenced by outliers in a data set, so I expected some wackiness and limited the mean to only checks released 180 days prior to a CVE being published and 31 days after a CVE being published. These seem to me like reasonable limits, as anything greater than 6 months prior to CVE details being released is potentially a quirk of the check details and anything after a 1-month delay is less important for us.

What can we take away from Figure 12?

  • We can see that between 2011 and 2014 Greenbone’s release delay was better than that of Tenable, by between 5 and 10 days.
  • In 2015 things reverse and for 3 years Tenable is considerably ahead of Greenbone by a matter of weeks.
  • But, then in 2019 things get much closer and Greenbone seem to be releasing on average about a day earlier than Tenable.
  • For both the trendline over an 11-year period is very close, with Tenable marginally beating Greenbone.
  • We have yet to have any data for 2021 for OpenVAS checks for critical show-stopper CVEs.
Figure 12: Release delay year-on-year (lower is better)

With the larger number of checks, and still being able to release a greater percentage of their remote checks for critical vulnerabilities Tenable could win this category. However, the delay time from 2019 and 2020 going to OpenVAS, and the trend lines being so close, I am going to declare this one a tie. It’s a tie.

The takeaway from this is that both vendors are getting their checks out the majority of the time either before the CVE details are published or on the day the details are published. This is overwhelmingly positive for both scanning solutions. Over time both also appear to be releasing remote checks for critical vulnerabilities more quickly.

Written by

Jack McDonach

Recommended articles

Ready to get started with your 14-day trial?
try for free