# NIST SP 800-53 Rev. 5 PT-8 — Computer Matching Requirements - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pt-8-computer-matching-requirements - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › PT — PII Processing and Transparency - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `PT-8`·critical·Component: **Computer Matching Program** ## What this control requires > When a system or organization conducts a matching program, they must obtain approval from the Data Integrity Board, develop a matching agreement, publish a matching notice in the Federal Register, verify the information produced before taking adverse actions, and provide individuals with notice and an opportunity to contest findings before any adverse action is taken. > > — NIST SP 800-53 Rev. 5, Control PT-8 ### In plain English When a system or organization conducts a matching program, they must obtain approval from the Data Integrity Board, develop a matching agreement, publish a matching notice in the Federal Register, verify the information produced before taking adverse actions, and provide individuals with notice and an opportunity to contest findings before any adverse action is taken. In practice, this means you can prove you information management-level controls on a defined cadence. ## Why it matters SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed. This control is rated **critical** in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping. ## What an auditor looks for A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan. Within **Computer Matching Program**, the assessor will trace your implementation back to the catalogue reference (Control PT-8) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Incident Response **Runbook.** Maintain a runbook keyed by incident type with named roles (IC, comms, scribe), an out-of-band comms channel, and a 72-hour timeline for external notification. **Tabletop.** Run a quarterly tabletop exercise (ransomware, insider, supply-chain) and feed gaps back into the runbook. ### Operational checklist - **Information.** Document the trigger, the owner and the cadence. - **Data.** Document the trigger, the owner and the cadence. - **Response.** Document the trigger, the owner and the cadence. - **System.** Document the trigger, the owner and the cadence. - **Change.** Document the trigger, the owner and the cadence. - **Scope:** management, actions, information, organization, system, integrity, integrity board, requirements. ## Evidence to collect - **Ticketing Workflow.** `ticketing_workflow` evidence Workflow metrics (ServiceNow, Jira) show approvals and remediation. Focus: Computer Matching Requirements. ## Common pitfalls - Runbooks that name a role but no person, or list a paging channel that no longer exists. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**ISO/IEC 27001:2022 A.5.8** — Information security in project management](https://support.icompaas.com/compliance/iso-27001-2022/a-5-8-information-security-in-project-management) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control SI-7(5)** — Automated Response To Integrity Violations](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-7-5-automated-response-to-integrity-violations) - [**Control SA-9(1)** — Risk Assessments And Organizational Approvals](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-9-1-risk-assessments-and-organizational-approvals) - [**Control AU-9(5)** — Dual Authorization](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/au-9-5-dual-authorization) - [**Control SI-4(7)** — Automated Response To Suspicious Events](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-4-7-automated-response-to-suspicious-events) - [**Control SI-7(7)** — Integration Of Detection And Response](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-7-7-integration-of-detection-and-response) - [**Control SI-2(3)** — Time To Remediate Flaws And Benchmarks For Corrective Actions](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-2-3-time-to-remediate-flaws-and-benchmarks-for-corrective-actions) ## References - [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls) - Catalogue identifier: `Control PT-8` Topics: governance riskchange managementincident response ## Related compliance guidance - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs. - [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.