mi-23 · version 0.2
SDLC Common Controls Catalog logo

Agentic Processes Provenance

Summary

Produce signed and immutable provenance evidence for any agentic process that significantly affects a high-risk system’s SDLC pipeline—including processes that produce, approve, scan, or test software, or perform release operations—so that all agentic steps can be monitored and gated throughout the pipeline and after release.

Description

Agentic process provenance answers the questions “which agent acted, using which policies and guidelines, with which tools, who were the involved humans, and what was the result?” for any agentic step that materially affects a high-risk system release. Provenance records are created when the agentic process runs and are linked to the released software so they support in-pipeline control and gating as well as post-market monitoring and post-release audits.

These records are immutable once written and stored in a tamper-evident system that prevents retroactive modification. By binding agentic session evidence to release artefacts (alongside software artefact provenance), agentic process provenance ensures that only software created, checked, and released by approved agentic components operating under corporate policies and guidelines reaches production.

This control complements MI-3 Software Artifact Provenance, which establishes chain of custody from source commit through build. MI-23 extends that chain to the agentic actors, contexts, and human oversight that shaped the change before and during release.

Requirements

  • A provenance record MUST be created for every agentic process that significantly affects the content of a high-risk system release (including produce, approve, scan, test, and release operations)
  • Provenance records MUST be signed, immutable once written, and stored in a tamper-evident system that prevents retroactive modification
  • Provenance MUST be linked to the released software identity in a way that supports both in-pipeline gating and post-market monitoring / post-release audit
  • Pipeline and release gates MUST be able to verify that required agentic provenance exists and that the recorded agentic components were approved under corporate policy before promotion to production
  • Provenance records MUST answer, at minimum:
    • Which agentic process operated, identifying the agent, harness, and models involved
    • Which context resources (guidelines, policies, or prompts) were used throughout the agentic session(s)
    • Which agentic tools were involved (e.g. skills, MCP tools, and equivalent tool integrations)
    • How to access the agentic session logs
    • Task details handled by the process (e.g. commit, Jira issue, released version, artifact)
    • Result of the agentic process
    • Human accountable for the process
    • Humans that acted as reviewers or co-producers in the agentic process
    • Agentic session start and end timestamps (as required by the EU AI Act)

Examples & Commentary

  • No high-risk system release should proceed to production without provenance for every significant agentic produce, approve, scan, test, or release step that significantly affected that release
  • Use a dedicated provenance store or attestation service so agentic records remain independent of any single agent harness or CI/CD system
  • Implement deployment and version-approval gates (MI-12, MI-19) that verify agentic provenance is present, signed, and bound to approved agent/harness/model identities before release
  • Link agentic provenance to artefact digests and version identifiers so post-market monitoring can reconstruct which agent sessions contributed to a released build
  • Retain session log references with retention aligned to EU AI Act record-keeping and deployer monitoring obligations
  • Periodically audit production releases against agentic provenance to confirm that agent-influenced changes have known, approved origins and named human accountability

Version History

v0.2 current
v0.1 2026-10-12

Cite This Version

This link always shows v0.2 exactly as published, even after the card changes.

SDLC-PREV-023 v0.2, Agentic Processes Provenance. FINOS SDLC Common Controls Catalog. https://sdlc-common-controls.finos.org/versions/mi-23-v0.2.html
How to cite controls

Snapshot Details

Card
mi-23
Version
0.2
Status
First-Reading-Approved
Sliced
2026-10-12
Commit
17a3054