Control Traceability Matrix

August 24, 2026 · View on GitHub

Version: 0.1.0 | Impact Level: FIPS Moderate

Disclaimer: This matrix is informational only. Each agency must verify control implementation against their specific ATO requirements.

This document provides bidirectional traceability between:

  • NIST SP 800-53 Rev 5.2 controls (the compliance framework)
  • OWASP risks (the threat model)
  • Guidance documents (the implementation guidance)
  • Checklist items (the verification steps)

Use this matrix to:

  • Auditors: Trace from a control → find all documents and checklist items that address it
  • Developers: Trace from a checklist failure → find the playbook that explains how to fix it
  • ISSOs: Trace from an OWASP risk → find controls, guidance, and verification methods

1. NIST 800-53 Control → Document Mapping

For each control referenced in this playbook, this table shows where implementation guidance and verification steps can be found.

ControlNameAGENTS.mddocs/CODING_PRACTICES.mdSECURITY-CONTROLS.mdAGENT-IDENTITY.mdChecklist
AC-2Account Management§2.1—§3.1§2, §3—
AC-3Access Enforcement§3.1§3.2§3.1§44.1, 4.2
AC-4Information Flow Enforcement—————
AC-5Separation of Duties——§3.1—1.1
AC-6Least Privilege§3.1, §10—§3.1§44.3
AC-12Session Termination§2.3—§3.1§3—
AC-17Remote Access§6.1—§3.1——
AU-2Event Logging§2.2§6.2§3.2§66.4
AU-3Content of Audit Records§2.2§6.2§3.2§66.5
AU-6Audit Record Review, Analysis, and Reporting§2.2—§3.2§6—
AU-12Audit Record Generation§2.2, §14.3—§3.2§6—
CA-2Control Assessments—————
CA-7Continuous Monitoring—————
CM-2Baseline Configuration§12.1, §15.3—§3.3—10.1
CM-3Configuration Change Control§3.2, §13, §14.1, §14.2—§3.3—1.3, 1.4
CM-5Access Restrictions for Change§3.2, §14.2—§3.3—10.6
CM-6Configuration Settings§12.1, §15.3—§3.3—10.2
CM-7Least Functionality§3.1, §10—§3.3——
CM-8System Component Inventory—————
CM-10Software Usage Restrictions—————
CP-10System Recovery and Reconstitution—————
IA-2Identification and Authentication (Organizational Users)§2.1§3.1§3.4§2, §34.1
IA-5Authenticator Management—§4§3.4§32.1, 2.6
IA-8Identification and Authentication (Non-organizational Users)§2.1—§3.4§2—
IR-4Incident Handling§9.1—§3.5——
IR-6Incident Reporting§9.2, §14.5—§3.5——
MP-4Media Storage—————
MP-6Media Sanitization—————
PL-4Rules of Behavior—————
RA-3Risk Assessment§1—§3.6——
RA-5Vulnerability Monitoring and Scanning§9.2§5.2§3.6—9.4, 9.5
SA-4Acquisition Process—§5.1§3.7——
SA-5System Documentation§15.4————
SA-8Security and Privacy Engineering Principles§15.1, §15.2—§3.7——
SA-11Developer Testing and Evaluation§8, §14.3, §14.4§1.1§3.7—9.1, 9.2, 9.3
SA-15Development Process, Standards, and Tools§15.1, §15.2§1.1§3.7——
SA-17Developer Security and Privacy Architecture and Design§15.1————
SC-3Security Function Isolation—————
SC-7Boundary Protection§6.1§8§3.8—8.3
SC-8Transmission Confidentiality and Integrity§6.1§8.1§3.8—7.1, 7.2
SC-13Cryptographic Protection§5.4§7§3.8—7.3, 7.4
SC-18Mobile Code—————
SC-23Session Authenticity—————
SC-28Protection of Information at Rest§4§4, §7§3.8—7.5
SI-2Flaw Remediation§9§5.2§3.9——
SI-3Malicious Code Protection§10, §11—§3.9——
SI-4System Monitoring—————
SI-7Software, Firmware, and Information Integrity—————
SI-10Information Input Validation§5.1, §11§2§3.9—3.1-3.6
SI-11Error Handling—§6.1§3.9—6.1, 6.2
SI-12Information Management and Retention—————
SI-15Information Output Filtering—————
SI-17Fail-safe Procedures§14.5, §14.6————
SR-3Supply Chain Controls and Processes§7§5.2§3.10—5.1-5.7
SR-11Component Authenticity§7§5.2§3.10—5.5

Control and Name columns are generated (make generate) — Control from the union of nist_controls: frontmatter across the mapped documents, Name from NIST SP 800-53 Rev 5 (via the derived data/nist-800-53-control-names.json, refreshed from NIST OSCAL by make refresh-oscal). The per-document section anchors and checklist numbers are maintained by hand.

2. OWASP Risk → Control and Guidance Mapping

OWASP Top 10 for LLM Applications 2025

OWASP IDRiskPrimary ControlsAGENTS.mddocs/CODING_PRACTICES.mdChecklist
LLM01Prompt InjectionSI-10, SI-3§11§2.13.1
LLM02Sensitive Information DisclosureSC-28, SI-12§4§4, §6.22.1-2.6, 6.3
LLM03Supply Chain VulnerabilitiesSR-3§7§55.1-5.7
LLM04Data and Model PoisoningSI-10§11——
LLM05Improper Output HandlingSI-10, SI-15—§2.23.1-3.6
LLM06Excessive AgencyAC-6, CM-7§3, §10—4.3
LLM07System Prompt LeakageSC-28§4—2.1
LLM08Vector and Embedding Weaknesses————
LLM09MisinformationSA-11§8.2§1.29.6
LLM10Unbounded Consumption——§8.18.2

OWASP Top 10 for Agentic Applications 2026

OWASP IDRiskPrimary ControlsAGENTS.mddocs/CODING_PRACTICES.mdChecklist
Agentic-01Agent Goal HijackSI-10§11§2.13.1
Agentic-02Identity and Privilege AbuseAC-2, AC-6, IA-2§2, §3§34.1-4.5
Agentic-03Unexpected Code ExecutionCM-7, SI-3§10——
Agentic-04Insecure Inter-Agent Communication—Out of scope (MVP)——
Agentic-05Human Agent Trust ExploitationAC-6§3.2, §8.2§1.21.1, 1.5
Agentic-06Tool Misuse and ExploitationAC-6, CM-7§3, §10—4.3
Agentic-07Agentic Supply Chain VulnerabilitiesSR-3§7§55.1-5.7
Agentic-08Memory and Context PoisoningSI-10§11——
Agentic-09Cascading FailuresIR-4§9§6.1—
Agentic-10Rogue AgentsCM-7, AU-2§10——

3. Checklist Item → Control and Guidance Mapping

This reverse mapping lets reviewers trace from a failed checklist item back to the control it satisfies and the playbook for remediation.

Checklist #Checklist ItemNIST ControlGuidance Location
1.1Human review of AI-generated codeSA-11, AC-5AGENTS.md §8.2
1.2AI attribution in commitsSA-15AGENTS.md §2.1
1.3Standard PR/review process followedCM-3AGENTS.md §3.2
1.4No direct commits to protected branchesCM-3, CM-5AGENTS.md §3.2
1.5Reviewer understands the codeSA-11AGENTS.md §8.2
2.1No secrets in source codeIA-5, SC-28docs/CODING_PRACTICES.md §4
2.2No secrets in committed configIA-5docs/CODING_PRACTICES.md §4
2.3No secrets in CI/CD definitionsIA-5docs/CODING_PRACTICES.md §4.2
2.4No internal network info exposedSC-7AGENTS.md §6.1
2.5Secrets scanning hook activeIA-5GETTING-STARTED.md §4
2.6Credentials from approved secrets mgmtIA-5, SC-28docs/CODING_PRACTICES.md §4.1
3.1External input validatedSI-10docs/CODING_PRACTICES.md §2.1
3.2Parameterized SQL queriesSI-10docs/CODING_PRACTICES.md §2.1
3.3Context-appropriate output encodingSI-10, SI-15docs/CODING_PRACTICES.md §2.2
3.4Path traversal preventionSI-10docs/CODING_PRACTICES.md §2.1
3.5No unsafe APIs with untrusted dataSI-10, SC-18docs/CODING_PRACTICES.md §9
3.6Redirect URL allowlistingSI-10docs/CODING_PRACTICES.md §9
4.1All protected endpoints authenticatedIA-2, AC-3docs/CODING_PRACTICES.md §3.1
4.2Server-side authorization enforcementAC-3docs/CODING_PRACTICES.md §3.2
4.3Least privilege appliedAC-6AGENTS.md §3.1
4.4Secure session managementSC-23docs/CODING_PRACTICES.md §3.3
4.5No hardcoded auth bypassesAC-3docs/CODING_PRACTICES.md §3.2
5.1Dependencies pinned to exact versionsSR-3docs/CODING_PRACTICES.md §5.2
5.2Lock file committedSR-3docs/CODING_PRACTICES.md §5.2
5.3No critical/high dependency CVEsRA-5, SR-3docs/CODING_PRACTICES.md §5.2
5.4Dependency licenses reviewedSA-4docs/CODING_PRACTICES.md §5.1
5.5Package names verified (typosquatting)SR-11docs/CODING_PRACTICES.md §5.1, AGENTS.md §7.1
5.6Dependency scanning in CI/CDRA-5docs/CODING_PRACTICES.md §5.2
5.7SBOM generated/updatedSR-3docs/CODING_PRACTICES.md §5.2
6.1Explicit error handlingSI-11docs/CODING_PRACTICES.md §6.1
6.2No internal details in error messagesSI-11docs/CODING_PRACTICES.md §6.1
6.3No sensitive data in logsAU-3docs/CODING_PRACTICES.md §6.2
6.4Audit logging for security eventsAU-2docs/CODING_PRACTICES.md §6.2
6.5Structured log formatAU-3docs/CODING_PRACTICES.md §6.2
7.1TLS 1.2+ for all network commsSC-8AGENTS.md §6.1
7.2TLS certificate validation enabledSC-8AGENTS.md §6.1
7.3Current FIPS-validated cryptoSC-13AGENTS.md §5.4
7.4No custom cryptographic implementationsSC-13AGENTS.md §5.4
7.5Sensitive data encrypted at restSC-28docs/CODING_PRACTICES.md §7
7.6No hardcoded crypto keysSC-13, IA-5AGENTS.md §5.4
8.1Authenticated API endpointsIA-2, AC-3docs/CODING_PRACTICES.md §8.1
8.2Rate limiting on public endpointsSC-7docs/CODING_PRACTICES.md §8.1
8.3CORS with explicit origin allowlistSC-7docs/CODING_PRACTICES.md §8.2
8.4Security headers configuredSC-7docs/CODING_PRACTICES.md §8.2
8.5No sensitive data in URL paramsSC-8docs/CODING_PRACTICES.md §8.1
8.6Request/response schema validationSI-10docs/CODING_PRACTICES.md §8.1
9.1Unit tests for new functionalitySA-11AGENTS.md §8.1
9.2All existing tests passSA-11AGENTS.md §8.1
9.3Error paths and edge cases testedSA-11AGENTS.md §8.1
9.4SAST scan passedRA-5, SA-11docs/CODING_PRACTICES.md §10.2
9.5SCA scan passedRA-5, SR-3docs/CODING_PRACTICES.md §5.2
9.6AI code reviewed for hallucinated APIsSA-11docs/CODING_PRACTICES.md §1.2
10.1Infrastructure changes version-controlledCM-2, SA-10docs/CODING_PRACTICES.md §10.1
10.2No default credentialsCM-6, IA-5docs/CODING_PRACTICES.md §10.1
10.3Least-privilege IAM rolesAC-6docs/CODING_PRACTICES.md §10.1
10.4Logging/monitoring enabledAU-2, AU-12docs/CODING_PRACTICES.md §10.1
10.5Container images scannedRA-5docs/CODING_PRACTICES.md §5.3
10.6Human approval gate for productionCM-5AGENTS.md §3.2

4. AI RMF Function → Document Mapping

AI RMF FunctionSub-FunctionPrimary Documents
GOVERNGOVERN 1 — PoliciesAGENTS.md §1, §10, §12, §13, §14, §15
GOVERN 6 — AccountabilityAGENTS.md §2, AGENT-IDENTITY.md §2, §5, §6
MAPMAP 1 — ContextGETTING-STARTED.md, risk-assessment template
MAP 3 — Supply ChainAGENTS.md §7, docs/CODING_PRACTICES.md §5
MAP 5 — DataAGENTS.md §4, docs/CODING_PRACTICES.md §4
MEASUREMEASURE 1 — MetricsAGENTS.md §8, pre-deployment checklist
MEASURE 2 — TestingAGENTS.md §8, §15, docs/CODING_PRACTICES.md §1, SECURITY-CONTROLS.md §3.6
MANAGEMANAGE 1 — Risk TreatmentAGENTS.md §14, SECURITY-CONTROLS.md §5, risk-assessment template §6
MANAGE 2 — Ongoing MonitoringAGENTS.md §6, §11, SECURITY-CONTROLS.md §3.6
MANAGE 4 — Incident ResponseAGENTS.md §9, SECURITY-CONTROLS.md §3.5

Version History

DateVersionChange
2026-02-250.1.0Initial release