ABS Core v4.1.0
Security and Compliance

NIST AI RMF 1:1 Mapping

Complete mapping of NIST AI Risk Management Framework controls to ABS Core SovereignAuditRecord fields. 19 controls, 12 fully covered.

NIST AI RMF 1:1 Mapping

ABS Core maps 19 NIST AI Risk Management Framework controls to specific fields in the SovereignAuditRecord (SAR). An auditor can verify compliance by inspecting the SAR field referenced by each control.


Coverage Summary

CategoryFullPartialPlannedTotal
GOVERN4105
MAP3104
MEASURE3115
MANAGE2215
Total125219

GOVERN Function

ControlTitleSAR Evidence FieldCoverage
GOVERN-1.1Policies for AI risk managementpolicy_referenceFULL
GOVERN-1.2Accountability structuresagent_id, agent_oid_pubkeyFULL
GOVERN-1.3Risk management integrationdecision, reasonFULL
GOVERN-1.4Organizational commitmentcompliance_tagsFULL
GOVERN-1.5Ongoing monitoringengine_latency_ms, total_latency_msPARTIAL

How to verify GOVERN-1.1: Open any SovereignAuditRecord. The policy_reference field contains the identifier of the policy that produced the decision. Cross-reference with the policy file to confirm the rule exists and is current.


MAP Function

ControlTitleSAR Evidence FieldCoverage
MAP-1.1AI system purpose and contextrequest_hash, decision_stageFULL
MAP-1.2Interdependency analysisagent_id, oid_verifiedFULL
MAP-1.5Impact assessmentdecision, reasonFULL
MAP-1.6Data requirementsrequest_hashPARTIAL

How to verify MAP-1.1: The request_hash provides the SHA-256 fingerprint of the exact request that was evaluated. The decision_stage shows which pipeline component made the decision. Together, they prove the context of each governance action.


MEASURE Function

ControlTitleSAR Evidence FieldCoverage
MEASURE-1.1Metrics for risk measurementengine_latency_ms, total_latency_msFULL
MEASURE-2.1AI system evaluationoid_verified, oid_signatureFULL
MEASURE-2.3Independent evaluationrfc3161_token, rfc3161_authorityFULL
MEASURE-2.5Bias assessmentcompliance_tagsPARTIAL
MEASURE-4.1Feedback mechanismstemporal_drift_msPLANNED

How to verify MEASURE-2.3: The rfc3161_token contains a Base64-encoded DER timestamp token from an independent Time Stamping Authority (rfc3161_authority). This proves the record existed at the stated time without relying on the system's own clock.


MANAGE Function

ControlTitleSAR Evidence FieldCoverage
MANAGE-1.1Risk response prioritiesdecision (ALLOW/DENY/ESCALATE)FULL
MANAGE-1.3Risk tolerance alignmentlicense_statusFULL
MANAGE-2.1Incident responseledger_block_hash, prev_block_hashPARTIAL
MANAGE-2.3Root cause analysiscrypto_receipt, engine_fingerprintPARTIAL
MANAGE-4.1Regular updatesengine_fingerprintPLANNED

How to verify MANAGE-1.3: The license_status field indicates whether governance was in FULL enforcement, GRACE_PERIOD, or AUDIT_ONLY mode. If any record shows AUDIT_ONLY, the organization's risk tolerance policy should document whether that gap was accepted.


SovereignAuditRecord v4.1.0 Field Reference

SAR FieldTypeNIST Controls Served
versionstringSchema versioning
record_idstring (UUIDv7)Record correlation
timestampstring (ISO 8601)Temporal evidence
agent_idstringGOVERN-1.2, MAP-1.2
agent_oid_pubkeystring (hex)GOVERN-1.2
oid_signaturestring (hex)MEASURE-2.1
oid_verifiedbooleanMAP-1.2, MEASURE-2.1
request_hashstring (SHA-256)MAP-1.1, MAP-1.6
policy_referencestringGOVERN-1.1
decisionALLOW/DENY/ESCALATEGOVERN-1.3, MAP-1.5, MANAGE-1.1
reasonstringGOVERN-1.3, MAP-1.5
ledger_block_hashstring (SHA-256)MANAGE-2.1
prev_block_hashstring (SHA-256)MANAGE-2.1
crypto_receiptstringMANAGE-2.3
rfc3161_tokenstring (Base64 DER)MEASURE-2.3
rfc3161_authoritystringMEASURE-2.3
compliance_tagsstring[]GOVERN-1.4, MEASURE-2.5
license_statusFULL/AUDIT_ONLY/GRACE_PERIODMANAGE-1.3
temporal_drift_msnumberMEASURE-4.1
engine_fingerprintstring (SHA-256)MANAGE-2.3, MANAGE-4.1
engine_latency_msnumberGOVERN-1.5, MEASURE-1.1
total_latency_msnumberGOVERN-1.5, MEASURE-1.1
decision_stagestringMAP-1.1

On this page