Skip to content
Landfall
NIST PF · NIST-PF-PR-DS-P

NIST PF PR.DS-P - Data Security

Protect data at rest and in transit, manage removal and transfers, maintain availability, prevent leaks, check software and hardware integrity, and separate development/testing from production.

CRITICALRequirementData processingTechnical standardIn forceApplies from 16 January 2020

Where this comes from

Provision: PR.DS-P - Data Security

Instrument: NIST Privacy Framework Version 1.0

Citation: NIST Privacy Framework Version 1.0 (16 January 2020), Core, PR.DS-P1 through PR.DS-P8

Text version: NIST Privacy Framework 1.0 Core, 16 January 2020 (not PF 1.1)

Checked against the source: 6 September 2026

Read the official text ↗

Who it applies to

It applies when all of these are true:

  • NIST PF 1.0 Target Profile adopted: YES
  • PR.DS-P: Which outcomes are selected in this project's Target Profile? is PR.DS-P1, PR.DS-P2, PR.DS-P3, PR.DS-P4, PR.DS-P5, PR.DS-P6, PR.DS-P7 or PR.DS-P8

What engineering work it implies

Sample acceptance criteria Landfall generates for this obligation:

  • Personal data is encrypted in transit and at rest
  • Access to personal data is role-restricted and access is logged
  • A documented incident-response / breach-notification procedure exists and is tested
  • Third-party processors are bound by equivalent security obligations
  • Key rotation completes without loss of access to data encrypted under the prior key

Evidence an auditor expects

  • Technical controlTechnical audit

    Data protection measures

    Evidence for selected PR.DS-P safeguards: data at rest/in transit, lifecycle disposition, availability, leak prevention, integrity and environment separation. Test the assessed systems and data; no child-only restriction or universal technical method is prescribed by this category.

Questions people ask

Does NIST PF PR.DS-P - Data Security apply to my service?
It applies when NIST PF 1.0 Target Profile adopted: YES; PR.DS-P: Which outcomes are selected in this project's Target Profile? is PR.DS-P1, PR.DS-P2, PR.DS-P3, PR.DS-P4, PR.DS-P5, PR.DS-P6, PR.DS-P7 or PR.DS-P8.
From when does this apply?
NIST PF PR.DS-P - Data Security applies from 16 January 2020. Its current status is: in force.
What evidence does an auditor expect?
Data protection measures.

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.

Run the pre-scanAll NIST PF obligations

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