EvidenceSheet
NIST SP 800-53 Rev 5 · PT - PII Processing and Transparency

PT-8 Computer Matching Requirements

When a system or organization processes information for the purpose of conducting a matching program: a. Obtain approval from the Data Integrity Board to conduct the matching program; b. Develop and enter into a computer matching agreement; c. Publish a matching notice in the Federal Register; d. Independently verify the information produced by the matching program before taking adverse action against an individual, if required; and e. Provide individuals with notice and an opportunity to contest the findings before taking adverse action against an individual.

Source: NIST SP 800-53 Rev 5, PT-8. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST SP 800-53 Rev 5 in the compliance library.

Base controls and their enhancements. Which apply follows the baseline you are assessed against (for example FedRAMP Moderate or High, or the low, moderate and high baselines of SP 800-53B). Text in square brackets is a parameter your organisation sets.

10
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Privacy Act system of records · Data governance / DLP tooling
  • Test of Organizational processes for supporting and/or implementing personally identifiable information processing; matching program · Document repository

governing documentDocuments that govern the control

  • Personally identifiable information processing and transparency policy and procedures · Policy repository / GRC workspace
  • Privacy notice · Policy repository / GRC workspace
  • Federal Register notices · Policy repository / GRC workspace
  • Data Integrity Board determinations · Policy repository / GRC workspace
  • Contracts · Vendor register / contract repository
  • Information sharing agreements · Vendor register / contract repository
  • Memoranda of understanding · Document repository
  • Governing requirements · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

PT-7(2) Specific Categories of Personally Identifiable Information | First Amendment Information · RA-1 Policy and Procedures