United States

NIST SP 800-122

8 controls. 132 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

8 controls 132 frameworks share controls with it United States verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

NIST SP 800-122 Protecting PII Confidentiality Evidence & Implementation Kit

8 controls is the documentation set somebody has to write. This is that set, already written: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
NISTSP122-1Scope, PII Definition, and PII Confidentiality Impact Analysis0
NISTSP122-2PII Privacy Notice, Consent, and Lawful Processing0
NISTSP122-3PII Data Subject Rights and Automated Decision-Making22
NISTSP122-4PII Minimisation, Purpose Limitation, and Pseudonymisation47
NISTSP122-5PII Security Controls - Encryption, Access Control, Storage, Audit90
NISTSP122-6PII Breach Response and Incident Handling79
NISTSP122-7PII Sharing, Cross-Border Transfers, and Third-Party Agreements26
NISTSP122-8Continuous Monitoring, Training, and Privacy Programme Governance84

Tell me when NIST SP 800-122 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • System security plans
  • Standard operating procedures
  • Current-as-at dates and approval records
  • Revenue analysis
  • Exemption documentation
  • Annual applicability review
  • Encryption + pseudonymisation evidence
  • Incident response playbook
  • Affected data subject notification
  • Data subject breach notification when high-risk

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for NIST SP 800-122, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition