Governed Agentic Security Operations Architecture
An implementation-oriented governance and adoption kit for MSSP, MDR, and DFIR teams designing agent-assisted security workflows with explicit scope, policy, approval, evidence, audit, and replay boundaries.
Independent project: This is an independent personal reference architecture and adoption kit. It is not affiliated with, sponsored by, endorsed by, reviewed by, approved by, or maintained by Microsoft or any other employer. See
DISCLAIMER.md.
Agentic systems may assist security operations, but they do not authorize themselves.
At a Glance
- 36-control normative governance catalog
- MSSP, MDR, and DFIR implementation profiles
- Deterministic
gasooffline conformance CLI - Schema-governed requests, approvals, decisions, evidence, and audit records
- AI Assurance and Agent Judge patterns for evidence support, unsupported claims, tenant boundaries, HITL compliance, output quality, and ATT&CK/ATLAS mapping
- Request-digest-bound approvals
- Tenant, customer, case, and target-scope validation
- Hash-chained audit-record verification and deterministic replay
- 56 automated tests
- Three end-to-end walkthroughs
What This Demonstrates
- Governed agentic security architecture
- Translation of governance requirements into machine-readable contracts
- Deterministic policy and approval validation
- Tenant-scope-aware MSSP, MDR, and DFIR operating models
- Evidence lineage, auditability, and replay
- Separation of Agent Judge assurance from PDP authorization, PEP enforcement, and human approval
- Clear separation between offline conformance validation and external production enforcement
Scope Boundary
This repository is not a SOC product, autonomous response platform, production control plane, SIEM/SOAR replacement, legally sufficient DFIR evidence system, or customer-ready managed security service.
The gaso CLI validates local, synthetic artifacts and reconstructs recorded audit timelines. It does not invoke agents or models, contact security platforms, or execute external actions. Production identity, authorization, policy enforcement, approval authority, tenant isolation, tool mediation, evidence preservation, audit storage, deployment, and response execution remain external implementation responsibilities.
Passing repository validation establishes conformance of supplied artifacts to the checks implemented by this offline kit. It does not establish production enforcement, security, compliance, factual correctness, evidentiary validity, or operational safety. See TRACEABILITY.md for the implemented-versus-external boundary.
60-Second Technical Review
Architecture Views
The diagrams remain available through their supporting architecture documents:
- Executive view
- Engineering view
- Shared operating model
- Runtime control loop
- Agentic fleet operations
Quick Start
Choose the path closest to your objective:
Local Validation
The gaso CLI requires Python 3.11 or later and operates on local synthetic artifacts only.
python -m venv .venv
. .venv/bin/activate
python -m pip install -e ".[dev]"
gaso validate controls/control-catalog.yaml profiles/mssp.yaml
gaso verify-tenant-scope \
templates/governed-action-request.yaml \
templates/human-approval-record.yaml \
templates/customer-approval-record.yaml
gaso evaluate-policy templates/governed-action-request.yaml \
--policy policies/endpoint-response-policy.yaml \
--approvals templates/human-approval-record.yaml templates/customer-approval-record.yaml
gaso verify-evidence-manifest templates/evidence-manifest.yaml \
--lineage templates/derived-artifact-lineage.yaml
gaso verify-audit-chain tests/fixtures/audit-valid.jsonl
gaso replay tests/fixtures/audit-valid.jsonl
pytest
An ALLOW result means only that the synthetic request satisfied the selected reference policy. The CLI never invokes the requested action.
End-to-End Walkthroughs
Repository Navigation
License and Attribution
Copyright 2026 Anthony Fuller.
This repository is licensed under the Apache License, Version 2.0. The license permits use, modification, and redistribution subject to its terms. Attribution information is provided in NOTICE consistent with Section 4(d) of the license; the NOTICE file does not modify the license.
Publication under Apache License 2.0 is a license grant and does not transfer copyright ownership. Existing copies and prior releases remain governed by the Apache 2.0 terms under which they were distributed.
The canonical source for this project is:
https://github.com/anthfuller/governed-agentic-security-operations
Architecture, machine-readable contracts, synthetic examples, offline checks, and external production responsibilities remain deliberately separated throughout the repository.