NIST CSF 2.0 Framework

Protect (PR): Safeguards for Identity, Data and Platforms

Access control, training, data security, platform security and resilience

9 min read
CTO, Cloud Architect, IT Director
Updated 11/18/2026
Intermediate
NIST CSF 2.0ProtectAccess ControlData Security

TL;DR (for busy owners)

  • What it is: Protect (PR) covers the safeguards that reduce the chance and impact of an incident: who can access what, how people are trained, how data and platforms are secured, and how infrastructure stays resilient.
  • Why it matters: In cloud, most incidents begin with an identity — a leaked key, an over-permissioned role, an unscoped trust. PR.AA is where the biggest risk reduction usually is.
  • Quick action: Enforce MFA for every person with privileged access and remove long-lived access keys that nobody owns.

The five Protect categories

CodeCategoryIn plain English
PR.AAIdentity Management, Authentication, and Access ControlThe right identities have the right access, verified appropriately
PR.ATAwareness and TrainingPeople know their security responsibilities
PR.DSData SecurityData confidentiality, integrity and availability are protected
PR.PSPlatform SecurityHardware, software and services are configured and maintained securely
PR.IRTechnology Infrastructure ResilienceArchitecture and capacity support continued operation

How attackers get around weak protection

A developer's access key is committed to a repository. The key belongs to an IAM user with broad permissions, so whoever finds it can read data, create new credentials and in some cases make themselves an administrator. No vulnerability was exploited — the permissions did the work. The compromised access key scenario walks through each step and the controls that break it.

Fast checks (30 minutes)

Protect quick assessment

  • MFA is enforced for all privileged human access, including the root user (PR.AA)
  • Workloads use roles or federation rather than long-lived access keys (PR.AA)
  • Permissions to change IAM, logging and keys are limited to a small group (PR.AA)
  • S3 Block Public Access is enabled at account level (PR.DS)
  • Sensitive data is encrypted with keys whose use is restricted (PR.DS)
  • Backups are isolated from the accounts they protect and restores are tested (PR.DS, PR.IR)
  • Engineers with production access have had security training in the last year (PR.AT)

Evidence to keep

Evidence that protections are in place

IAM credential report showing MFA status and key age

Easy
10 minutes to export
IAM owner

Access review records for privileged roles

Medium
Quarterly
Security lead

Encryption and public-access settings for data stores

Medium
1 hour
Platform team

Most recent restore test result

Medium
Per test
Operations

Map to frameworks

NIST CSF 2.0 Protect categories

NIST CSF 2.0
PR.AA
Identity Management, Authentication, and Access Control
NIST CSF 2.0
PR.DS
Data Security
NIST CSF 2.0
PR.PS
Platform Security
NIST CSF 2.0
PR.IR
Technology Infrastructure Resilience
OWASP Top 10
A01
Broken Access Control

Where Securitain fits

Evidence for PR.AA and PR.DS in AWS

IAM Security

Effective permissions, privilege-escalation paths and risky trust across connected accounts.

  1. 1Review identities with sensitive permissions such as broad S3, KMS decrypt or Secrets Manager access
  2. 2Check supported privilege-escalation combinations such as iam:PassRole with compute services
  3. 3Use findings and their remediation guidance to reduce access

Data Security

Public and cross-account exposure on S3, KMS, SQS, SNS and Secrets Manager resource policies.

  1. 1Review resource-policy exposure findings
  2. 2Confirm each external grant has a business owner

Next steps

Identity first

MFA and removing unowned long-lived keys are the highest-value first moves. Then narrow the small number of permissions that matter most: IAM administration, logging, keys, secrets and sensitive data. The Cloud Control Explorer shows which controls address which attack techniques.

Sources & References

Read-only analysis of effective permissions, escalation paths and trust relationships.

Find over-permissioned AWS identities

Stay in the loop

Cloud security insights, early access & compliance updates

Weekly InsightsEarly AccessExpert Content
No spam, everUnsubscribe anytimeWeekly updates
Chat with Securitain