Seeded demo · auth off · no application database · GitLab SoT / GitHub twin · not an ATO
CC9.2 — Vendor and business partner risk management
NIST SP 800-53 Revision 5 · assessed by internal audit
Data as of23 Aug 2026
What this requires
In plain language: the outcome this security requirement is meant to achieve.
The entity assesses and manages risks associated with vendors and business partners.
How we check it
Confirm a current security review exists for every vendor processing customer data.
Source mappings
Traceability from this Rev. 5 control to DAAG, organizational guidance, and DCSA supplemental guidance.
DAAG reference
Not supplied in uploaded sources
Organization document
Not supplied in uploaded sources
Implementation narrative
Not supplied in uploaded SSP
DCSA supplemental guidance
Not supplied in uploaded sources
Proof
Documents and records that show this requirement is met.
| Artifact | Kind | Status | Collected | Expires | Source | Digest |
|---|---|---|---|---|---|---|
| Vendor security review register Manual140 KB | Policy document | Expired | 14 Feb 2026 | 14 Aug 2026 | Vanta Priya Raghunathan | a50b61c72d83… |
| Sub-processor DPA inventory Manual148 KB | Policy document | Valid | 14 May 2026 | 14 May 2027 | Ironclad Tomas Lindqvist | 1c72d83e94fa… |
Problems
Open issues tied to this requirement. 1 total.
FND-1029HighOpen
Four active vendors processing customer data without current security review
The vendor register lists four vendors with expired security reviews that continue to process customer personal data under active contracts.
Remediation Complete refreshed security reviews and suspend data flows for any vendor not cleared within 30 days.
Manual testvendor-registeropened 14 May 2026due 30 Jun 2026
Test record
- Framework
- NIST 800-53 5.1.1
- Domain
- Third Party
- Test method
- Manual
- Last tested
- 14 May 2026
- Next due
- 14 Jul 2026
- Retest window
- 40d overdue
Accountable owner
Audit period
NIST SP 800-53 Revision 5
- Window
- — – —
- Authority
- NIST
- Assessor
- Internal audit