Global control library.

63 controls. 18 frameworks. Find the evidence your team can record.

See a demo

Reference mappings for pre-production work. You confirm applicability. Customer validation and independent review remain required.

63 controls

ISO 42001

ISO/IEC 42001:2023 — Artificial intelligence management system

International · Source: official ISO 42001 source (opens in a new tab)

Agent risk review

Agent views calculate risk signals from recorded activity and approval history. This is not a compliance score.

ISO42001.RSK-01: reference and evidence

AI management: risk assessment

Review agent risk signals within the management system scope.

Evidence
Agent trust / Developer report
Mapping
Review signal
Link to this control

Control ownership

The control-ownership matrix records customer-attested owners and review evidence.

ISO42001.OWN-02: reference and evidence

AI management: accountability

Identify the owner who reviews each selected control.

Evidence
Control-ownership matrix
Mapping
Owner review
Link to this control

Management review evidence

Evidence exports collect recorded sessions, decisions, and governance references.

ISO42001.REV-03: reference and evidence

AI management: review and improvement

Provide recorded evidence for management review.

Evidence
Evidence package / Verifier result
Mapping
Verifiable artifact
Link to this control

Customer validation: Customers must define the management system scope, assess impacts, and complete independent certification if required.

ISO 27001

ISO/IEC 27001:2022 — Information security management systems

International · Source: official ISO 27001 source (opens in a new tab)

Evidence access

Portal access checks apply team scope and role permissions to evidence.

ISO27001.ACC-01: reference and evidence

Information security management: access control

Restrict access to agent evidence by role and team.

Evidence
Portal access checks
Mapping
Evidence mapping
Link to this control

Credential exposure

Redaction detects supported credential patterns before the client sends event content.

ISO27001.DAT-02: reference and evidence

Information security management: information protection

Reduce sensitive credentials in development telemetry.

Evidence
Redaction summary
Mapping
Evidence mapping
Link to this control

Evidence integrity

Package verification checks manifest hashes and export-chain metadata.

ISO27001.INT-03: reference and evidence

Information security management: record integrity

Detect changes to exported development evidence.

Evidence
Evidence package / Verifier result
Mapping
Verifiable artifact
Link to this control

Customer validation: Customers must select controls from their risk assessment and validate the full management system against the licensed standard.

SOC 2

SOC 2 — Trust Services Criteria (2017, revised points of focus 2022)

International · Source: official SOC 2 source (opens in a new tab)

Access and ingest identity

Signed ingest authenticates submissions. Portal access checks restrict team data.

SOC2.CC6-02: reference and evidence

Trust Services Criteria CC6: logical access

Restrict evidence access and authenticate event submissions.

Evidence
Signed ingest / Scoped access
Mapping
Evidence mapping
Link to this control

Change evidence integrity

Evidence manifests bind exported records to hashes that local verification checks.

SOC2.CC8-03: reference and evidence

Trust Services Criteria CC8: change management

Preserve evidence for review of a proposed change.

Evidence
Evidence package / Verifier result
Mapping
Verifiable artifact
Link to this control

Activity review

The portal groups available blocked actions and denied approvals for review.

SOC2.CC7-04: reference and evidence

Trust Services Criteria CC7: system operations

Review recorded policy blocks and approval decisions.

Evidence
Agent trust / Developer report
Mapping
Review signal
Link to this control

Customer validation: A qualified auditor must assess the selected criteria, system scope, and review period. Product evidence is not an attestation.

EU AI Act

Artificial Intelligence Act — Regulation (EU) 2024/1689

European Union · Source: official EU AI Act source (opens in a new tab)

Technical documentation

Capability records describe declared permissions, event families, and trust levels.

EUAI.ART11-01: reference and evidence

Article 11: technical documentation

Record capabilities and permissions for system review.

Evidence
Capability provenance
Mapping
Evidence mapping
Link to this control

Agent event records

Signed ingest stores events from configured connectors in the activity ledger.

EUAI.ART12-02: reference and evidence

Article 12: record-keeping

Keep available agent actions and outcomes for review.

Evidence
Agent activity ledger
Mapping
Evidence mapping
Link to this control

Human approval

Configured runtime gates hold actions for reviewers and record their decisions.

EUAI.ART14-03: reference and evidence

Article 14: human oversight

Require human review for configured sensitive actions.

Evidence
Approval decision records
Mapping
Evidence mapping
Link to this control

Credential redaction

The client removes detected credentials before emission and records a redaction summary.

EUAI.ART15-04: reference and evidence

Article 15: cybersecurity

Reduce credential exposure in emitted telemetry.

Evidence
Redaction summary
Mapping
Evidence mapping
Link to this control

Risk review record

Threshold receipts bind policy settings to a named reviewer and review date.

EUAI.ART9-05: reference and evidence

Article 9: risk management

Review available risk signals and document threshold decisions.

Evidence
Model-risk threshold signoff receipt
Mapping
Owner review
Link to this control

Customer validation: Customers must determine system classification, their legal role, applicable dates, and required assessments. Coding agents are not automatically high-risk systems.

DORA

Digital Operational Resilience Act — Regulation (EU) 2022/2554

European Union · Source: official DORA source (opens in a new tab)

Change impact

Blast Radius Snapshot identifies recorded routes, symbols, commands, and caller dependencies.

DORA.ICT-01: reference and evidence

Article 9: protection and prevention

Assess dependencies before a code change proceeds.

Evidence
Blast Radius Snapshot
Mapping
Verifiable artifact
Link to this control

Supplier boundary evidence

Readiness checks supplied boundary evidence. It does not deploy or validate a customer environment.

DORA.TPRM-02: reference and evidence

Article 28: technology third-party risk

Review evidence for the declared customer-cloud boundary.

Evidence
BYOC deployment-readiness report
Mapping
Verifiable artifact
Link to this control

Approval outage handling

The runtime approval provider blocks configured actions on timeout or transport failure.

DORA.RES-03: reference and evidence

Article 9: protection and prevention

Stop configured gated actions when approval is unavailable.

Evidence
Approval decision records
Mapping
Evidence mapping
Link to this control

Change approval record

Pull request evidence links recorded sessions, decisions, commits, and verification results.

DORA.CHG-04: reference and evidence

Article 9(4)(e): change management

Keep review decisions with the proposed change.

Evidence
PR evidence / Check Run
Mapping
Verifiable artifact
Link to this control

Customer validation: Customers must validate service scope, supplier contracts, resilience testing, and incident processes outside this pre-production evidence.

PRA SS1/23

PRA SS1/23 — Model risk management principles for banks

United Kingdom · Source: official PRA SS1/23 source (opens in a new tab)

Model identification

Session provenance records available model, agent, developer, and repository identifiers.

PRA.INV-01: reference and evidence

Principle 1: model identification and classification

Identify recorded models and their development context.

Evidence
Session provenance
Mapping
Evidence mapping
Link to this control

Accountable risk owner

Threshold signoff receipts record the reviewer, policy hash, and review date.

PRA.GOV-02: reference and evidence

Principle 2: governance

Record the owner responsible for threshold review.

Evidence
Model-risk threshold signoff receipt
Mapping
Owner review
Link to this control

Validation evidence

Evidence packages preserve recorded decisions and session references for external review.

PRA.VAL-03: reference and evidence

Principle 4: independent model validation

Supply development records for independent model review.

Evidence
Evidence package / Verifier result
Mapping
Verifiable artifact
Link to this control

Risk limits

Runtime policy can request approval before a configured sensitive action proceeds.

PRA.MIT-04: reference and evidence

Principle 5: model risk mitigants

Record human decisions for configured sensitive actions.

Evidence
Approval decision records
Mapping
Evidence mapping
Link to this control

Customer validation: Customers must confirm institution and model scope under the current statement. Agent records do not replace independent model validation.

MAS TRM

MAS Guidelines on Risk Management Practices — Technology Risk

Singapore · Source: official MAS TRM source (opens in a new tab)

Change approval

Pull request evidence links commits to recorded decisions and verification results.

MAS.CHG-01: reference and evidence

Section 7.5: change management

Review recorded change impact and approval evidence.

Evidence
PR evidence / Check Run
Mapping
Verifiable artifact
Link to this control

Independent release review

Portal roles restrict approval actions and support independent reviewer decisions.

MAS.SOD-02: reference and evidence

Section 7.6: software release management

Separate development and review permissions before release.

Evidence
Portal access checks
Mapping
Evidence mapping
Link to this control

Security test evidence

Pull request evidence includes available verification summaries and Check Run results.

MAS.TEST-03: reference and evidence

Section 6.1: source review and security testing

Keep available verification results with the proposed code change.

Evidence
PR evidence / Check Run
Mapping
Verifiable artifact
Link to this control

Change activity records

Configured connectors emit session, tool, and result events to signed ingest.

MAS.LOG-04: reference and evidence

Section 7.5.7: change activity logging

Record available agent activity during a code change.

Evidence
Agent activity ledger
Mapping
Evidence mapping
Link to this control

Customer validation: Customers must validate release controls, testing, and rollback procedures. The catalog maps guideline themes, not every applicable MAS notice.

APRA CPS 234

APRA CPS 234 — Information Security

Australia · Source: official APRA CPS 234 source (opens in a new tab)

Security ownership

Customer-attested ownership matrices name control owners and their review evidence.

APRA.OWN-01: reference and evidence

CPS 234: roles and responsibilities

Record who owns selected information security controls.

Evidence
Control-ownership matrix
Mapping
Owner review
Link to this control

Sensitive action review

Runtime sensitivity rules can hold configured actions for human approval.

APRA.SENS-02: reference and evidence

CPS 234: controls matched to asset sensitivity

Review sensitive agent actions under the selected policy.

Evidence
Approval decision records
Mapping
Evidence mapping
Link to this control

Control test evidence

Connector proof receipts bind supplied capture, approval, and portal read-back evidence.

APRA.TEST-03: reference and evidence

CPS 234: testing control effectiveness

Collect evidence for independent testing of configured controls.

Evidence
Connector proof receipt
Mapping
Verifiable artifact
Link to this control

Customer validation: Customers must validate asset classification, independent control testing, and reporting obligations. A verifier result does not prove control effectiveness.

OSFI B-13

OSFI Guideline B-13 — Technology and Cyber Risk Management

Canada · Source: official OSFI B-13 source (opens in a new tab)

Separate change duties

Portal roles restrict approval actions and record reviewer identity.

OSFI.SOD-01: reference and evidence

Section 2.5.2: segregation of duties

Separate code authorship from approval permissions.

Evidence
Portal access checks
Mapping
Evidence mapping
Link to this control

Change traceability

Pull request evidence binds recorded sessions, commits, and review decisions.

OSFI.TRACE-02: reference and evidence

Section 2.5.3: traceable changes

Link available agent activity to the reviewed change.

Evidence
PR evidence / Check Run
Mapping
Verifiable artifact
Link to this control

Development security checks

Evidence exports include available review results and verification references.

OSFI.SEC-03: reference and evidence

Section 2.4.2: security throughout development

Keep available security checks with development records.

Evidence
Evidence package / Verifier result
Mapping
Verifiable artifact
Link to this control

Customer validation: Customers must validate controls across the full technology lifecycle. These mappings cover evidence before production.

RBI IT Directions

RBI Information Technology Governance, Risk, Controls and Assurance Practices Directions, 2023

India · Source: official RBI IT Directions source (opens in a new tab)

Change approvals

Pull request evidence joins recorded commits, approval decisions, and verification results.

RBI.CHG-01: reference and evidence

Section 13: change and patch management

Document review and approval before a change proceeds.

Evidence
PR evidence / Check Run
Mapping
Verifiable artifact
Link to this control

Agent audit trails

The activity ledger records submitted session, tool, policy, and outcome events.

RBI.AUD-02: reference and evidence

Section 15: audit trails

Keep available agent actions and decisions for review.

Evidence
Agent activity ledger
Mapping
Evidence mapping
Link to this control

Scoped access

Portal guards apply role permissions and team scope to recorded evidence.

RBI.ACC-03: reference and evidence

Section 19: access controls

Restrict development evidence to authorized roles and teams.

Evidence
Portal access checks
Mapping
Evidence mapping
Link to this control

Risk review evidence

Developer reports show recorded trends and evidence counts for customer review.

RBI.RISK-04: reference and evidence

Section 22: periodic review of technology risks

Review recorded risk signals with accountable owners.

Evidence
Agent trust / Developer report
Mapping
Review signal
Link to this control

Customer validation: Customers must confirm entity scope and validate retention, access review, and information systems audit requirements.

Japan FSA

Japan FSA — Principles for Model Risk Management

Japan · Source: official Japan FSA source (opens in a new tab)

Model inventory

Session provenance records available models, agents, and repositories.

JFSA.INV-01: reference and evidence

Principle 2: inventory and model risk rating

Identify recorded models and associated development sessions.

Evidence
Session provenance
Mapping
Evidence mapping
Link to this control

Model review record

Signoff receipts record policy hashes and named reviewers for customer review.

JFSA.APR-02: reference and evidence

Principle 4: model approval

Retain the owner review of selected model-risk thresholds.

Evidence
Model-risk threshold signoff receipt
Mapping
Owner review
Link to this control

Ongoing review

Developer reports summarize available weekly signals and approval history.

JFSA.MON-03: reference and evidence

Principle 5: ongoing monitoring

Review recorded outcomes and evidence gaps over time.

Evidence
Agent trust / Developer report
Mapping
Review signal
Link to this control

Customer validation: Customers must determine model scope and risk ratings. Agent evidence supports review but does not establish model validity.

NIST AI RMF

NIST AI Risk Management Framework 1.0

United States · Source: official NIST AI RMF source (opens in a new tab)

Named risk owners

Customer-attested matrices identify control owners and supporting review evidence.

NIST.GOV-01: reference and evidence

GOVERN: accountability

Assign review responsibility for selected agent controls.

Evidence
Control-ownership matrix
Mapping
Owner review
Link to this control

Agent context

Session provenance and intent records show available agent context and stated work.

NIST.MAP-02: reference and evidence

MAP: context and intended use

Describe the agent, repository, and intended development work.

Evidence
Intent Registry / Spec Trace
Mapping
Review signal
Link to this control

Risk signal review

Agent reports show available scores, evidence counts, and missing evidence.

NIST.MEASURE-03: reference and evidence

MEASURE: risk assessment

Review measured signals with their evidence limits.

Evidence
Agent trust / Developer report
Mapping
Review signal
Link to this control

Risk decisions

Runtime approval records show reviewer decisions for configured sensitive actions.

NIST.MANAGE-04: reference and evidence

MANAGE: risk treatment

Record decisions on configured actions that require review.

Evidence
Approval decision records
Mapping
Evidence mapping
Link to this control

Customer validation: This voluntary framework requires use-case assessment and stakeholder review. Agent metrics do not measure every AI risk.

FFIEC

FFIEC Information Technology Examination Handbook

United States · Source: official FFIEC source (opens in a new tab)

Separate review duties

Portal role checks restrict approval actions and support independent review.

FFIEC.SOD-01: reference and evidence

Information Security booklet: separation of duties

Separate development permissions from approval permissions.

Evidence
Portal access checks
Mapping
Evidence mapping
Link to this control

Change attribution

Pull request evidence links available agent sessions, commit hashes, and policy decisions.

FFIEC.SDLC-02: reference and evidence

Development, Acquisition, and Maintenance booklet: change management

Link recorded development work to a reviewed change.

Evidence
PR evidence / Check Run
Mapping
Verifiable artifact
Link to this control

Reviewable change records

Evidence exports include manifests and hashes for local verification.

FFIEC.LOG-03: reference and evidence

Development, Acquisition, and Maintenance booklet: audit evidence

Keep evidence that reviewers can inspect after a change.

Evidence
Evidence package / Verifier result
Mapping
Verifiable artifact
Link to this control

Customer validation: Customers must test control operation across their development process. Recorded agent activity covers only configured sources.

SR 11-7 (legacy)

SR 11-7 — Supervisory Guidance on Model Risk Management (superseded)

United States · Source: official SR 11-7 (legacy) source (opens in a new tab)

Model inventory

Recorded sessions can include model, agent, connector, and repository identifiers.

SR11-7.INV-01: reference and evidence

Legacy SR 11-7: model inventory

Identify models and agents used in development.

Evidence
Session provenance
Mapping
Evidence mapping
Link to this control

Intent trace

Intent Registry links recorded intent bundles to sessions and specification evidence.

SR11-7.SND-02: reference and evidence

Legacy SR 11-7: conceptual soundness

Compare recorded work with the stated development intent.

Evidence
Intent Registry / Spec Trace
Mapping
Review signal
Link to this control

Outcome review

Developer reports show recorded risk signals, evidence counts, and weekly trends.

SR11-7.MON-03: reference and evidence

Legacy SR 11-7: outcomes analysis

Review agent outcomes and evidence limits over time.

Evidence
Agent trust / Developer report
Mapping
Review signal
Link to this control

Threshold signoff

Signoff receipts bind reviewer identity, policy hash, and review cadence.

SR11-7.GOV-04: reference and evidence

Legacy SR 11-7: governance

Assign an owner to review agent risk thresholds.

Evidence
Model-risk threshold signoff receipt
Mapping
Owner review
Link to this control

Independent review evidence

Evidence packages bind recorded sessions and decisions to a verifiable manifest.

SR11-7.VAL-05: reference and evidence

Legacy SR 11-7: validation

Give reviewers a stable record of the development evidence.

Evidence
Evidence package / Verifier result
Mapping
Verifiable artifact
Link to this control

Customer validation: SR 26-2 replaced SR 11-7 and excludes generative and agentic AI. These mappings are governance analogies.

HIPAA Security Rule

HIPAA Security and Privacy Rules — 45 CFR Parts 160 and 164

United States · Source: official HIPAA Security Rule source (opens in a new tab)

Activity records

Agent sessions, tool calls, and approvals on ePHI repositories are recorded in the portal activity ledger; runtime governance decisions are also written to the hash-chained audit log.

HIPAA.AUD-01: reference and evidence

45 CFR 164.312(b): audit controls

Record agent activity on systems that create, receive, or maintain ePHI.

Evidence
Session provenance / Audit export
Mapping
Evidence mapping
Link to this control

Activity review

The obligation register lists open, unverified, prevented, and controlled findings for each review window.

HIPAA.REV-02: reference and evidence

45 CFR 164.308(a)(1)(ii)(D): information system activity review

Review agent activity on ePHI systems on a regular cadence.

Evidence
Obligation register
Mapping
Review signal
Link to this control

Covered model providers

Data-class obligations flag PHI-tagged activity that reached a provider outside the BAA list.

HIPAA.BA-03: reference and evidence

45 CFR 164.308(b)(1): business associate contracts and other arrangements

Keep PHI in agent context on providers covered by a business associate agreement.

Evidence
Obligation register / Liability register
Mapping
Review signal
Link to this control

Customer validation: Covered entities and business associates must run their own risk analysis and confirm which repositories touch ePHI. Product evidence does not make a system HIPAA compliant.

PCI DSS

Payment Card Industry Data Security Standard v4.0.1

International · Source: official PCI DSS source (opens in a new tab)

Independent code review

Approval records name requester and reviewer; the obligation register opens a finding when they match or cannot be shown.

PCI.REV-01: reference and evidence

Requirements 6.2.3 and 6.2.3.1: review before release

Review agent-written changes to in-scope code before release. Manual reviews need someone other than the author.

Evidence
Approval decision records / Obligation register
Mapping
Evidence mapping
Link to this control

Change records

Intent bundles record the reason for a change; approval records hold the authorization.

PCI.CHG-02: reference and evidence

Requirement 6.5.1: production change procedures

Record the reason, description, and approval for agent-run production changes.

Evidence
Intent Registry / Approval decision records
Mapping
Evidence mapping
Link to this control

Service provider boundary

Sessions record model provider and model; obligations flag account data tagged in agent activity.

PCI.TPSP-03: reference and evidence

Requirement 12.8: third-party service providers

Know which model providers received agent context from in-scope work.

Evidence
Session provenance / Obligation register
Mapping
Review signal
Link to this control

Customer validation: A QSA or internal assessor must confirm cardholder data environment scope and test each requirement. Agent records are inputs to that assessment.

NAIC AI Bulletin

NAIC Model Bulletin — Use of Artificial Intelligence Systems by Insurers (2023)

United States · Source: official NAIC AI Bulletin source (opens in a new tab)

AIS program records

Threshold signoff receipts bind reviewer identity, policy hash, and review cadence.

NAIC.GOV-01: reference and evidence

AIS Program: governance and accountability

Name owners and review cadence for AI used in insurance development work.

Evidence
Model-risk threshold signoff receipt
Mapping
Owner review
Link to this control

Pricing change review

Path-scoped obligations require an independent approver for agent changes to pricing and underwriting code.

NAIC.CTRL-02: reference and evidence

AIS Program: risk management and internal controls

Review agent changes to rating, underwriting, and claims decision code.

Evidence
Approval decision records / Obligation register
Mapping
Evidence mapping
Link to this control

Third-party AI inventory

Sessions record the agent, connector, model provider, and model behind each change.

NAIC.TP-03: reference and evidence

AIS Program: third-party AI systems

Identify the third-party agents and models used to build insurance systems.

Evidence
Session provenance
Mapping
Evidence mapping
Link to this control

Customer validation: The bulletin is guidance with force only where a state adopts it, and wording varies. Insurers must confirm which version applies and whether coding agents fall inside their AIS program scope.

NYDFS Part 500

23 NYCRR Part 500 — Cybersecurity Requirements for Financial Services Companies

United States · Source: official NYDFS Part 500 source (opens in a new tab)

Secure development evidence

Approval and obligation records show which agent changes reached release branches and who approved them.

NYDFS.APP-01: reference and evidence

Section 500.8: application security

Show secure development practice for agent-written changes to in-house applications.

Evidence
Approval decision records / Obligation register
Mapping
Evidence mapping
Link to this control

Audit trail

Hash-chained audit records and verifiable evidence packages preserve the agent activity record.

NYDFS.AUD-02: reference and evidence

Section 500.6: audit trail

Keep records that let the entity reconstruct agent activity.

Evidence
Evidence package / Verifier result
Mapping
Verifiable artifact
Link to this control

Third-party providers

Provider allowlist obligations flag sessions that used a model provider outside the approved list.

NYDFS.TPSP-03: reference and evidence

Section 500.11: third-party service provider security policy

Know which model providers received agent context and flag those outside policy.

Evidence
Obligation register
Mapping
Review signal
Link to this control

Customer validation: Covered entities must confirm their class, exemptions, and certification duties. Agent records support, but do not replace, the written cybersecurity program.

Track a control with your agents.

See a recorded session, approval, and evidence export.