NIST CSF 2.0
The US framework of outcomes: Govern, Identify, Protect, Detect, Respond, Recover.
Updated
The Cybersecurity Framework is outcome-based and maps to the detailed controls in NIST SP 800-53. It is the reference most US procurement teams and insurers use, and the common language between security and the board.
Version 2.0, published in February 2024, added the Govern function and applies to organisations of any size and sector, not only critical infrastructure. Each subcategory states what should be true, and informative references map it to detailed controls such as SP 800-53 and the CIS Benchmarks.
Official text: Cybersecurity Framework at NIST.
Who needs it
Organisations that need a common language for cyber risk with executives, insurers, US customers and federal supply chains. It is the default reference in the United States and increasingly used in Europe as a structure above frameworks like ISO 27001 and CIS.
Outcomes, not settings
The CSF tells you what a secure organisation looks like, for example that identities are managed and access is least privilege, and leaves the how to you. In the cloud, the Protect and Detect functions resolve into concrete configuration: identity and access settings, data protection, platform security and continuous monitoring. The informative references point to the CIS Benchmarks and SP 800-53 controls that implement each outcome.
Profiles and tiers
A Current Profile records where you are, a Target Profile where you want to be, and tiers describe how mature your risk management is. A continuous cloud review gives you a Current Profile for the technical outcomes that keeps itself up to date, and a record of progress towards the target.
What NIST CSF asks of your cloud
The control areas that map onto infrastructure configuration in AWS, Google Cloud and Azure.
PR.AA · Identity management, authentication and access control
Identities and credentials managed, users and services authenticated with MFA, and access permissions limited to least privilege.
PR.DS · Data security
Data at rest and in transit protected, and backups maintained and tested.
PR.PS · Platform security
Configuration management, software and hardware maintained securely, and log records generated and available.
PR.IR · Technology infrastructure resilience
Networks and environments protected from unauthorised logical access and usage, with segmentation.
DE.CM · Continuous monitoring
Networks, computing resources and services monitored to find anomalies and potential compromise.
ID.AM · Asset management
An inventory of hardware, software, services and data flows, which in the cloud is your accounts, resources and trust relationships.
How AKRIBOS checks NIST CSF
Mapped to your resources
Every NIST CSF control is evaluated against the actual accounts, roles, networks and storage in your estate, with the setting behind each result.
Findings come with the fix
A failing control is shown with the exact change as CLI commands or Terraform. You review and approve; nothing is applied on its own.
Evidence over time
Scheduled reviews and a full audit trail give you a dated record of each control for the whole audit period, not just the day of the audit.
Common issues under NIST CSF
Misconfigurations that fail NIST CSF controls, with the control reference for each.
Storage bucket open to the internet
CriticalObject storage that anyone can list or read, usually from a permissive ACL, bucket policy or account-wide setting that was never switched on.PR.AA-05 (least-privilege access), PR.DS-01 (data at rest protected).
Read moreRoot or owner account without MFA
CriticalThe most privileged identity in the account protected by a password alone.PR.AA-03 (users authenticated), PR.AA-05 (privileged access).
Read moreDatabase reachable from the internet
CriticalA managed database with a public address and a firewall that lets the world in.PR.IR-01 (segmentation), PR.DS-01 (data at rest).
Read moreSnapshots or machine images shared publicly
CriticalDisk snapshots, database snapshots or machine images that anyone with a cloud account can copy.PR.DS-01 (data at rest), PR.AA-05 (access).
Read moreOver-permissive IAM policies
HighIdentities, often service accounts, that can do anything in the account because a wildcard or a basic role was easier than a scoped policy.PR.AA-05 (access permissions managed on least privilege).
Read moreSSH or RDP open to 0.0.0.0/0
HighManagement ports reachable from any address on the internet.PR.IR-01 (networks protected from unauthorised access).
Read moreAudit logging incomplete
HighGaps in the record of who did what: missing regions, missing data-access events, or logs that can be altered.PR.PS-04 (log records generated), DE.CM-01 and DE.CM-09 (monitoring).
Read moreLong-lived or unused credentials
HighAccess keys, service account keys and client secrets that never rotate and are no longer needed.PR.AA-01 (identities and credentials managed).
Read moreInstance metadata without session tokens
HighCompute instances that answer metadata requests, including their temporary credentials, to any process that can reach the local metadata address.PR.PS-01 (configuration management), PR.PS-02 (software maintained).
Read moreTrust policies open to any account
HighRoles or bindings that let identities outside your organisation assume access, often for a vendor integration that was set up too generously.PR.AA-05 (access), GV.SC (supply chain risk management).
Read moreData at rest without the encryption you intended
MediumVolumes, snapshots or databases created without encryption, or without the customer-managed keys your policy requires.PR.DS-01 (data at rest protected).
Read moreTransport encryption not enforced
MediumEndpoints that still accept plaintext or outdated TLS, even though an encrypted path exists.PR.DS-02 (data in transit protected).
Read moreNetwork flow logs off
MediumNo record of which addresses talked to which, so traffic to and from a compromised host cannot be reconstructed.DE.CM-01 (networks monitored).
Read moreDefault network with permissive rules
MediumWorkloads running in the cloud-created default network, which ships with rules nobody would write deliberately.PR.IR-01 (segmentation).
Read moreNIST CSF questions
Is NIST CSF a certification?
No. There is no certificate. Organisations self-assess against it and use it to structure their programme and communicate risk; auditors and customers may ask for your profile.
How does CSF 2.0 relate to SP 800-53?
The CSF describes outcomes; SP 800-53 is the catalogue of controls that achieve them. Each CSF subcategory lists informative references into 800-53, CIS and ISO 27001, so a cloud review mapped to those also maps to the CSF.
Which functions does a cloud review cover?
Mainly Protect and Detect, plus the asset inventory under Identify. Govern, Respond and Recover are organisational and procedural, though the audit trail helps with Respond and Recover evidence.
Other frameworks
CIS Benchmarks
The baseline configuration standard for AWS, Google Cloud and Azure.
Read moreSOC 2
Evidence that your cloud controls work, not just that they exist.
Read moreISO/IEC 27001
The international standard for an information security management system, applied to your cloud.
Read moreDORA
The EU Digital Operational Resilience Act, applied to the cloud behind your financial services.
Read moreNIS2
EU-wide cyber risk-management obligations for essential and important entities.
Read morePCI DSS v4
Requirements for every environment that stores, processes or transmits cardholder data.
Read moreBSI C5
Germany's cloud computing compliance criteria catalogue.
Read moreDNB Good Practice Information Security
What De Nederlandsche Bank expects of the financial institutions it supervises.
Read moreAttackers don't wait for your next audit. Neither does AKRIBOS.
Connect AWS, Google Cloud or Azure and get your first review today.
