Skip to content
NIST CSF · NIST-CSF-PR-DS-02

NIST CSF PR.DS-01 - Protection of data at rest (legacy record alias)

Assess the selected CSF 2.0 data-at-rest protection outcome for the documented project and data scope

HIGHRecommendationGovernanceTechnical standardIn forceApplies from 26 February 2024

Where this comes from

Provision: PR.DS-01 - Protection of data at rest (legacy record alias)

Instrument: NIST Cybersecurity Framework 2.0 (February 2024)

Citation: NIST CSWP 29, NIST Cybersecurity Framework 2.0, 26 February 2024, Appendix A, PR.DS-01; section 3 Organizational Profiles. The stable database ID is a legacy alias and does not change the official identifier.

Text version: CSF 2.0

Checked against the source: 6 September 2026

Read the official text ↗

Who it applies to

It applies when all of these are true:

  • NIST CSF 2.0 Target Profile adopted: YES
  • PR.DS: Which outcomes are selected in this project's Target Profile? is PR.DS-01

What engineering work it implies

Sample acceptance criteria Landfall generates for this obligation:

  • Confirm selected PR.DS-01 in the documented CSF 2.0 Target Profile, including stored-data boundaries, organizational roles, profile owner/version and tailoring; PR.DS-02 is the distinct data-in-transit outcome.
  • Identify the assessed stored-data confidentiality, integrity and availability risks and choose proportionate safeguards, with measurable acceptance criteria and accountable owners.
  • Verify confidentiality against unauthorized access, integrity against unauthorized change and availability under the assessed failure scenarios; record remaining gaps with scoped evidence.
  • Where encryption is chosen, test the assessed key access, protection, lifecycle and recovery controls using synthetic keys and data. PR.DS-01 does not itself prescribe an algorithm, product, encryption layer or rotation period.
  • Keep data-in-transit, data-in-use and backup outcomes separate unless explicitly selected and assessed; do not treat a storage-decision document or a checked task as proof of all security outcomes.

Evidence an auditor expects

  • Assessment documentDocument review

    Selected PR.DS-01 stored-data protection assessment

    Confirm selected PR.DS-01 in the documented CSF 2.0 Target Profile, including stored-data boundaries, organizational roles, profile owner/version and tailoring; PR.DS-02 is the distinct data-in-transit outcome. Identify the assessed stored-data confidentiality, integrity and availability risks and choose proportionate safeguards, with measurable acceptance criteria and accountable owners. Verify confidentiality against unauthorized access, integrity against unauthorized change and availability under the assessed failure scenarios; record remaining gaps with scoped evidence. Where encryption is chosen, test the assessed key access, protection, lifecycle and recovery controls using synthetic keys and data. PR.DS-01 does not itself prescribe an algorithm, product, encryption layer or rotation period. Keep data-in-transit, data-in-use and backup outcomes separate unless explicitly selected and assessed; do not treat a storage-decision document or a checked task as proof of all security outcomes.

Questions people ask

Does NIST CSF PR.DS-01 - Protection of data at rest (legacy record alias) apply to my service?
It applies when NIST CSF 2.0 Target Profile adopted: YES; PR.DS: Which outcomes are selected in this project's Target Profile? is PR.DS-01.
From when does this apply?
NIST CSF PR.DS-01 - Protection of data at rest (legacy record alias) applies from 26 February 2024. Its current status is: in force.
What evidence does an auditor expect?
Selected PR.DS-01 stored-data protection assessment.

Find out whether this one lands on you

Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.

Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.

What Landfall Is NOT

Critical Boundaries

Understanding these boundaries is essential before using this product. Misuse of this tool for purposes outside its scope may create legal, regulatory, or commercial risk for your organization.

NOT Legal Advice

This product does not provide legal advice and does not create an attorney-client relationship.

Interpretations are informational analysis, not legal counsel. Always consult qualified legal professionals for compliance decisions.

NOT a Risk Score

We do not quantify, calculate, or certify your compliance risk level.

No numerical risk rating, compliance percentage, or safety score. Risk assessment requires human judgment about your specific context.

NOT Runtime Enforcement

This is a planning and mapping tool, not a runtime enforcement system.

Does not integrate with your production systems. Does not block, filter, or enforce compliance in real-time. Implementation is your responsibility.

NOT Regulatory Approval

Using this tool does not mean you are compliant with any regulation.

No certification, seal of approval, or compliance guarantee. Regulators will evaluate your actual implementation, not your use of this tool.

NOT Authoritative Interpretation

Our interpretations are not binding and may differ from regulatory guidance.

Only regulators and courts provide authoritative interpretation. Our analysis reflects our reading of requirements, which may be incomplete or incorrect.

NOT a Safe Harbor

This tool does not shield you from enforcement actions or liability.

Documentation of your process is valuable, but does not constitute a legal defense. Compliance is ultimately your organization's responsibility.

NOT an AI Compliance Agent

AI features assist analysis but do not make compliance decisions for you.

AI-generated interpretations require human review and approval. Automated suggestions are starting points, not final answers.

NOT Complete Coverage

We do not cover all regulations, all obligations, or all jurisdictions.

Regulatory landscape is vast and evolving. Gaps in our coverage do not mean those requirements don't apply to you.

What This Tool IS:

  • A structured workflow for mapping regulatory requirements to implementation tasks
  • A documentation system for compliance decisions (audit trail)
  • A collaboration platform for compliance, legal, and engineering teams
  • An informational resource for understanding regulatory obligations