Image without description
  • Jacco Meijer
  • |
  • Jul 11, 2025

Cyber security risk frameworks

Managing cyber security risk with ISO 27001 and NIST CSF

Managing risk

Risk is a broad area and in the context of risk management, risk relates to threats, vulnerabilities and assets.

Image without description

For an organization to manage risk, risk need to be identified. Once identified, risk can be analyzed and treated.

Larger organizations manage risk by identifying as much risk at the same time while small and medium sized businesses usually start with the first risk identified.

Risk analysis is analyzing threats, vulnerabilities and assets. Threat modeling being part of threat analysis.

From risk analysis, risk is evaluated by looking at likelihood and impact of the risk. Likelihood is the probability that a threat exploits a vulnerability and impact is the possible asset value loss. In a quantitative way when measured in currency and in a qualitative way when evaluating importance.

Once inherent risk is evaluated, it is treated and residual risk remains. The table below gives a high level overview.

EvaluationTreatmentHow
Risk exceeds a thresholdAvoidStop using a specific technology or behavior
Likelihood or impact can be reduced with cost effective measuresMitigateImplement controls
Mitigation is not cost effectiveTransferShift risk onto a 3rd party by e.g. insurance or cloud services
Mitigation and transfer are not cost effectiveAcceptBe aware

Frameworks for managing risk

The ISO 31000 family is a guideline for managing risk that details a process, principles and a framework. It is a framework that fits all types of industry and is regulation independent. Many other frameworks like e.g. ISO 14971 for medical devices address specific industry types and align with industry specific regulations.

Specifically for cyber security, NIST SP 800-37 is a well known risk framework. Two other notable cyber security specific risk standards are not frameworks but do provide useful guidance.

  • ISO 27005, provides guidance on managing information security risks
  • NIST 800-30, a guide for conducting information security risk assessments

NIST CSF

NIST CSF, with cyber security in it's name is specific for the field. It is an outcome oriented roadmap that does not mandate the how. What does NIST CSF have on the roadmap for risk management?

NIST CSF risk management

The first NIST CSF core function IDENTIFY is about the organization's current cyber security risks. Asset management and risk management are on the roadmap here.

The core function PROTECT is about treating the risk. Based on the results of IDENTIFY, controls are added where needed instead of the one-size-fits-all approach.

As expected for a cyber security framework, NIST CSF clearly has managing risk on the roadmap. But NIST CSF has a broader scope than only managing cyber security risk and the framework does not contain specifics on how to manage risk.

ISO 27001

ISO 27001 is a management system for cyber security and like NIST CSF, there is no 'how'. What does it say on risk management requirements?

ISO 27001 risk management

ISO 27001 requires 'Actions to address risks and opportunities' in clause 6 which details to:

  • 6.1.2 Information security risk assessment
  • 6.1.3 Information security risk treatment

Appendix A contains the recommended Information security controls and states that the controls shall be used in context with information security risk treatment (6.1.3) as mentioned above.

Two specific controls on risk management are:

  • 5.7 Threat intelligence
  • 5.9 Inventory of information and other associated assets

As you may expect from a cyber security management framework, ISO 27001 makes risk management mandatory. Similar to NIST CSF the standard is more broad than only managing cyber security risk. Another similarity is that is does not contain specifics on how to manage risk.

Conclusion

The post below on NIST CSF and ISO 27001 states that the standards have a different purpose, but their goals align and the standards strengthen each other. This is in line with risk management being part of both standards.

Image without description
  • Jacco Meijer
  • |
  • Jun 6, 2025

Combining ISO 27001 and NIST CSF

How to use ISO 27001 and NIST Cyber Security Framework together

How to manage risk

Both standards do not mandate how to manage risk. Threat modeling is a way to achieve this. This fits on the NIST CSF roadmap and answers to the ISO 27001 requirements. More on that in the post below.

Image without description
  • Jacco Meijer
  • |
  • Jul 18, 2025

Threat modeling as part of a risk framework

Threat modeling in the context of ISO 27001 and NIST CSF


Other posts

Image without description
  • Jacco Meijer
  • |
  • Jul 25, 2025

Threat modeling, security frameworks and Enterprise Architecture

Combining ISO 27001, NIST CSF and threat modeling with Enterprise Architecture strengthens all elements

Image without description
  • Jacco Meijer
  • |
  • Jul 18, 2025

Threat modeling as part of a risk framework

Threat modeling in the context of ISO 27001 and NIST CSF

Image without description
  • Jacco Meijer
  • |
  • Jun 27, 2025

NIST CSF Tiers for cyber security risk governance and management

NIST CSF 2.0 contains useful tiers for Capability Maturity Modeling in Enterprise Architecture

Image without description
  • Jacco Meijer
  • |
  • Jun 20, 2025

Archimate risk assessment elements

A few simple specializations for working with risk assessments in Archimate

Image without description
  • Jacco Meijer
  • |
  • Jun 13, 2025

Security principles in Enterprise Architecture

Adding security principles to Enterprise Architecture for NIST CSF and ISO 27001

Image without description
  • Jacco Meijer
  • |
  • Jun 6, 2025

Combining ISO 27001 and NIST CSF

How to use ISO 27001 and NIST Cyber Security Framework together

Image without description
  • Jacco Meijer
  • |
  • May 1, 2025

CISSP certification and Enterprise Architecture

How do the CISSP certification domains relate to Enterprise Architecture and the ArchiMate layers?

Image without description
  • Jacco Meijer
  • |
  • Apr 23, 2025

Architect roles in the ArchiMate context

An ArchiMate model that maps architect roles to the ArchiMate framework layers.

Image without description
  • Jacco Meijer
  • |
  • Mar 18, 2025

Visualizing IT Architecture in three languages, UML, C4 and ArchiMate

What are the differences and what are these languages most used for?

Image without description
  • Jacco Meijer
  • |
  • Feb 18, 2025

OAuth 2.0 and OpenID Connect Sequence Diagrams

Technical specs can be hard to read. While still highly technical, the UML Sequence Diagrams provided in this blog are a lot easier to understand.

Image without description
  • Jacco Meijer
  • |
  • Jan 9, 2025

OWASP and CISSP

OWASP recommendations from the independent information security certification CISSP.

Image without description
  • Jacco Meijer
  • |
  • Mar 21, 2024

UI Library with MDX documentation

Using the simple Render JSX plugin for Esbuild this post shows how to setup a simple UI library.

Image without description
  • Jacco Meijer
  • |
  • Mar 20, 2024

Render JSX plugin for Esbuild

Transform Esbuild generated JSX bundles to HTML pages.

Image without description
  • Jacco Meijer
  • |
  • Mar 19, 2024

Esbuild as a static site generator for MDX

Static site generators gain popularity. This blog is about using Esbuild as a static site generator for MDX.

Image without description
  • Jacco Meijer
  • |
  • Mar 18, 2024

11ty and Github pages

Simplifying the Contentful-Gatsby-Netlfy trio.

Image without description
  • Jacco Meijer
  • |
  • Jun 30, 2022

NPM7 and @npmcli/arborist

@npmcli/arborist is a powerful library that handles the new NPM 7 workspaces. This blog is about a simple make tool that uses the library.

Image without description
  • Jacco Meijer
  • |
  • May 12, 2022

Comparing React app, Nextjs and Gatsby

A new React project starts with a React toolchain. Main tools in the chains are SSR, React server components and GraphQL.

Image without description
  • Jacco Meijer
  • |
  • May 10, 2022

Versioning strategy for NPM modules

It is important to be able to bump the version of a NPM package without side effects.

Image without description
  • Jacco Meijer
  • |
  • Apr 12, 2022

React component themes and CSS variables

Creating React components with flexible themes by using CSS variables.

Image without description
  • Jacco Meijer
  • |
  • Mar 21, 2022

Content modeling with variants

The efficiency of a variant field in a content model.

Image without description
  • Jacco Meijer
  • |
  • Mar 12, 2022

Documentation

Documenting a software project is challenging. Here's a few simple guidelines that help a team writing clear documentation.

Image without description
  • Jacco Meijer
  • |
  • Mar 11, 2022

Javascript history

In 1986 David Ungar and Randall B. Smith developed Self at Xerox PARC. Inspired by Java, Scheme and Self Brendan Eich created Javascript in 1995.

Image without description
  • Jacco Meijer
  • |
  • Mar 10, 2022

On Javascript transpilers, bundlers and modules

There's Javascript transpilers, modules, bundles and bundlers. This is a brief overview of all of these.

Image without description
  • Jacco Meijer
  • |
  • Feb 11, 2022

Agile Scrum

The Agile Scrum framework is flexible enough to be used in many different ways. Here's one way of working.

Image without description
  • Jacco Meijer
  • |
  • Jan 20, 2022

What happened to Wheelroom?

Founded in 2018. Started to fly in 2020 and abandoned in 2021. What happened?

Image without description
  • Jacco Meijer
  • |
  • Jan 19, 2022

Contentful, Netlify and Gatsby four years later

What did we learn from using Contentful for four years?

Image without description
  • Jacco Meijer
  • |
  • Jan 18, 2022

Typescript interface for React UI components

How to define an interface for React UI components that prevents breaking changes.

Image without description
  • Jacco Meijer
  • |
  • Jan 17, 2022

Naming React components

What's in a name? A clear naming strategy helps developers communicate. Most devs rather spend time writing component code than wasting time on a good component name.