NIST SP 800-161 Rev 1ISO 27701:2019

NIST SP 800-161 Rev 1 covers 30.6% of ISO 27701:2019

33 of the 108 controls in ISO 27701:2019 are already satisfied by evidence you collected for NIST SP 800-161 Rev 1. 75 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.

30.6%
of the target already covered
33
controls evidenced
75
genuine gaps
0
claims rejected in review

This number is directional. It says how much of ISO 27701:2019 your NIST SP 800-161 Rev 1 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.

114 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.

Additional ISO/IEC 27002 guidance for PII processors, ISO 27701:20198 of 18 evidenced, 10 to do
PIMS-specific guidance related to ISO/IEC 27002, ISO 27701:201915 of 36 evidenced, 21 to do
Additional ISO/IEC 27002 guidance for PII controllers, ISO 27701:201910 of 31 evidenced, 21 to do
PIMS-specific requirements related to ISO/IEC 27001, ISO 27701:20190 of 23 evidenced, 23 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.

PS-66.10.2argued against and upheld
Information transfer

Access agreements bind the individuals with access, which is the confidentiality obligation required.

AC-46.10.2argued against and upheld
Information transfer

Information flow enforcement controls where data moves, including outside the system to suppliers.

SC-86.11.1argued against and upheld
Security requirements of information systems

Requires protection of information in transit between the organization and external parties.

PM-256.11.3argued against and upheld
Test data

Directly prevents real personal data being used for testing, training or research.

SR-56.12.1argued against and upheld
Information security in supplier relationships

Acquisition strategies and contract tools impose supply chain requirements before engagement.

SA-96.12.1argued against and upheld
Information security in supplier relationships

Governs external service providers and allocates the security roles each party holds.

SA-46.12.1argued against and upheld
Information security in supplier relationships

Puts the security and privacy requirements and required evidence into the supplier contract.

SR-66.12.2argued against and upheld
Supplier service delivery management

Supplier assessments and reviews are conducted at a depth matched to what is supplied.

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