NIST SP 800-171 Rev 3ISO 27701:2019

NIST SP 800-171 Rev 3 covers 29.6% of ISO 27701:2019

32 of the 108 controls in ISO 27701:2019 are already satisfied by evidence you collected for NIST SP 800-171 Rev 3. 76 are genuine gaps. Every claim below was judged against both control sets and then argued against; the ones that did not survive are published further down with the reason each failed.

29.6%
of the target already covered
32
controls evidenced
76
genuine gaps
0
claims rejected in review

This number is directional. It says how much of ISO 27701:2019 your NIST SP 800-171 Rev 3 evidence satisfies. The reverse pair is a different number, often very different, because a security standard has enormous depth for access control and almost none for lawful basis or data subject rights.

56 candidate mappings were examined and 0 were removed. Signed off 2026-08-19, review level machine verified. Mappings were judged by Claude Code rather than read line by line by a practitioner. Every claim shows its reasoning so you can check it. Ask and a practitioner will review this pair.

Where the gaps are

Coverage is never evenly spread. A source standard usually satisfies one part of a target almost completely and barely touches another, and which part is which is the thing worth knowing before you plan the work.

PIMS-specific guidance related to ISO/IEC 27002, ISO 27701:201924 of 36 evidenced, 12 to do
PIMS-specific requirements related to ISO/IEC 27001, ISO 27701:20197 of 23 evidenced, 16 to do
Additional ISO/IEC 27002 guidance for PII controllers, ISO 27701:20191 of 31 evidenced, 30 to do
Additional ISO/IEC 27002 guidance for PII processors, ISO 27701:20190 of 18 evidenced, 18 to do

Theme level, not control level, deliberately. The per-control list of what is evidenced and what is a gap is the report itself, so publishing it here would be publishing the thing being sold.

Claims that held

A sample. Each one names the control whose evidence does the work, the control it satisfies, and why.

03.15.015.3.2argued against and upheld
Policy

Organization-level policy is developed, disseminated and reviewed for every requirement family.

03.02.015.5.3argued against and upheld
Awareness

Literacy training makes users aware of policy, their contribution and consequences.

03.11.015.6.2argued against and upheld
Information security risk assessment

Risk assessments are updated at defined frequency and on significant change.

03.11.045.6.3argued against and upheld
Information security risk treatment

Findings are treated by acceptance, transfer, mitigation or avoidance and implemented.

03.12.035.7.1argued against and upheld
Monitoring, measurement, analysis and evaluation

Continuous monitoring strategy defines ongoing measurement and security status reporting.

03.12.015.7.2argued against and upheld
Internal audit

Assessment at defined frequency tests whether controls operate as intended.

03.12.025.8.1argued against and upheld
Nonconformity and corrective action

The plan of action and milestones documents corrective action and tracks it to closure.

03.13.066.10.1argued against and upheld
Network security management

Deny by default and allow by exception is the network segregation rule required.

Claims that did not hold

Nothing proposed for this pair was rejected in review. That is unusual and worth knowing rather than hiding: it means the candidate set was small and every candidate held.

The full report

Everything above is a sample. The report is every evidenced control and every gap, with the reasoning and the source document behind each one, in a form you can hand to an assessor. $299, emailed immediately.

Buy this crosswalk