7 / 15 capsules shipped · parity-green · 2026-04-30

Every protected action,
signed at decision time, sealed at the archive.

SecOps is a signed-action forensic ledger — the cryptographic receipt your existing EDR, SIEM, and diode hardware do not produce, shaped to the data fields a cyber-insurance underwriter or regulator actually asks for. Three EIP-712 signatures per action across T1 / T2 / T3. Sits beside your stack, not in front of it. v1.0 scope ↓

Request a Safe Harbor briefing → Architecture deep-dive
IEC 62443 · NIST SP 800-53 · FIPS 140-3 · NIS2 ready · SOC 2 Type II
v1.0 · scope clarification · 2026-05-20

What v1.0 is, and what it is not

✓ v1.0 ships
  • EIP-712 receipt signed at the endpoint, per protected action.
  • Per-tier domain separation — replay of receipts across tiers is cryptographically impossible.
  • Tamper-evident chain on what reaches the T3 archive.
  • Go ↔ WASM digest parity (Vertical Parity Law).
  • Insurer-aligned bundle export (insurer_safe_harbor_v1, regulator_dora).
✗ v1.0 does NOT
  • Not an active OS gate. No eBPF, LSM, MiniFilter, WFP, ETW, or ESF in this tree. A decision=deny receipt does not stop the underlying action.
  • Not durable end-to-end. "No information lost" applies only to what reaches T3; transit is best-effort until B4.
  • Not a policy engine. Anima v1.0 signs what it is told to sign.
  • Not HSM-quorum-orchestrated. The receipt asserts a quorum; the protocol is out of scope.

If you need an active enforcement gate today, your EDR is the answer (CrowdStrike, SentinelOne, Defender). Anima sits beside it and produces the receipt your underwriter wants. The bounded "blocks X" sentence becomes honest only when B3 of the corrective plan ships — see docs/secops/RELEASE_v1.0_SCOPE_CLARIFICATION.md and S2_CORRECTIVE_IMPLEMENTATION_PLAN_2026-05-20.md.

7
shipped capsules
3
signature tiers
3
signatures per action
1
way in to T3
01 · three-tier attestation

How SecOps works

Every protected action flows through three cryptographic tiers. The one-way data diode between T2 and T3 eliminates an entire attack class — T3 never talks back.

Missing signatures are themselves evidence.

02 · capsules

Seven capsules, three tiers

Capsule ID range 0xA000…0000 – 0xAFFF…FFFF. Full 15-slot bundle; 7 shipped, parity-green.

T1 · Local Observer
t1_observation FINALIZED
0xA000…0001

Signs every protected action on the endpoint with a local TPM-bound key.

SLO < 50ms
t1_heartbeat FINALIZED
0xA000…0002

Continuous liveness attestation. Absence of heartbeat is itself evidence of tampering.

SLO < 50ms
T2 · Decision Signer
t2_authorize SIGNED
0xA000…0010

Emits an EIP-712 signed receipt with decision = allow | deny against a signed policy manifest. v1.0 signs the decision; it does not intercept the underlying action. See v1.0 scope ↓

SLO < 5 min analyst review
t2_quarantine SIGNED
0xA000…0011

Emits a signed quarantine-state receipt for an endpoint pending analyst decision. Signed and timestamped; v1.0 does not itself isolate the endpoint.

SLO < 5 min
t2_killswitch SIGNED
0xA000…0012

Emits a signed receipt asserting an N-of-M HSM quorum was reached. v1.0 signs the receipt; quorum orchestration is out of scope for v1.0.

SLO < 5 min · N-of-M HSM quorum receipt
T3 · Air-gapped Attester
t3_cross_attest WITNESSED
0xA000…0020

Cross-attests the T1+T2 signature chain into the air-gapped archive via one-way ingress.

SLO < 30 min
t3_incident_bundle WITNESSED
0xA000…0021

Packages the incident evidence chain for handoff to insurer, counsel, regulator, or IR firm.

SLO < 30 min · FIPS 140-3 L3
03 · SLO budgets
T1 · Observation target < 50ms
34ms 68% of budget
T2 · Enforcement target < 5 min
3.2 min 64% of budget
T3 · Incident response target < 30 min
18 min 60% of budget
SLO data contract: { tiers: [{ id, label, sloTarget, sloActualMs, percentBudget }] } · design targets as of 2026-04-30
04 · use cases by host vertical

One attestation spine,
every deployment

SecOps wraps each vertical's protected actions in T1 observation, T2 enforcement gating, and T3 air-gapped cross-attestation. Organized by host vertical.

Fintech

Trading desks, settlement, payment issuance

Gate trading-floor endpoints, settlement-system terminals, and payment-issuance workstations. T2 sits inline with every trade execution and payout authorization.

What gets gated
Trade execution, settlement release, payment issuance
T3 archives
Full decision chain with counterparty sigs
Pairs with
anima_kyc fraud + routing capsules
Receipt reader
Insurer · regulator · IR firm
Healthcare

PHI workstations, infusion pumps, EHR overrides

Gate PHI-access workstations, infusion-pump controllers, and EHR clinical override events. Every access to patient data is observed, gated, and sealed.

What gets gated
PHI access, pump parameters, override events
T3 archives
Access chain, clinical decision attestation
Pairs with
HIPAA Security Rule · 21 CFR Part 11
Receipt reader
OCR · counsel · payer
Government

Benefits issuance, warrants, elections, FOIA

Gate benefits-issuance terminals, warrant-execution endpoints, elections-tabulation systems, and FOIA-release workstations.

What gets gated
Issuance, execution, tabulation, release
T3 archives
Decision chain with jurisdiction root
Pairs with
Gov vertical attestation capsules
Receipt reader
IG · GAO · counsel · FOIA officer
Real Estate

Escrow release, title transfer, e-signatures

Gate escrow-release terminals, title-transfer workstations, and e-signature endpoints during high-value closings. Every disbursement is three-tier attested.

What gets gated
Escrow release, title transfer, e-sign
T3 archives
Closing package with multi-party sigs
Pairs with
Real estate vertical capsules
Receipt reader
Title insurer · counsel · regulator
AIGov / AI Agents

Agent action execution before production

Gate AI-agent action execution before it touches production systems. T2 becomes the agent's policy chokepoint — no action reaches production without a signed authorization.

What gets gated
Agent actions, model outputs, tool calls
T3 archives
Action chain with model card + policy hash
Pairs with
AIGov vertical capsules
Receipt reader
Compliance · auditor · counsel
OT / Critical Infrastructure

IEC 62443 zone-conduit boundaries

Gate IEC 62443 zone-conduit boundaries. T2 sits inline with the Purdue Level-3↔Level-2 cut. Every control command crossing a zone boundary is observed, gated, and sealed.

What gets gated
Zone-conduit crossings, SCADA commands
T3 archives
Command chain with zone-boundary attestation
Pairs with
IEC 62443 · NERC CIP · NIS2
Receipt reader
Utility regulator · insurer · IR firm
05 · incident bundle receipt

Three-tier receipt structure

EIP-712 typed data for a t3_incident_bundle. Three nested signatures — one per tier. A horizontal action-gate scenario, not tied to any single vertical.

// t3_incident_bundle · EIP-712 typed data
{
  "domain": {
    "name":             "AnimaSecOps",
    "version":         "1",
    "chainId":         0,
    "verifyingContract": "0xA000…0021"
  },
  "primaryType": "IncidentBundle",
  "message": {
    "bundleId":    "0x7F4A…2C90",
    "actionHash":  "0x9E12…B3C4",
    "gateDecision": "QUARANTINE",
    "merkleRoot":  "0xAF21…E4B0",
    "sequenceNo":  284102,
    "timestamp":   1714500000
  },
  "signatures": [
    { "tier": "T1", "signer": "0xA000…0001", "sig": "0x4B2E…7F01" },
    { "tier": "T2", "signer": "0xA000…0010", "sig": "0x5C3F…8A12" },
    { "tier": "T3", "signer": "0xA000…0020", "sig": "0x6D4A…9B23" }
  ]
}
06 · compliance mapping

Cross-sector compliance coverage

SecOps capsules map to control classes across multiple regulatory frameworks. Broad, not sector-specific — the same attestation spine serves every deployment.

IEC 62443 Zones

  • SR 3.1 Zone-conduit integrity
  • SR 5.1 Network segmentation
  • SR 7.6 Network diagnostics
  • T2 Inline gate at Purdue L3↔L2

NIST CSF Functions

  • ID Asset attestation (T1)
  • PR Access control (T2 gate)
  • DE Anomaly detection (T1)
  • RS Incident bundle (T3)

ISO 27001 / SOC 2

  • A.8 Asset management
  • A.9 Access control
  • CC7 System operations
  • CC8 Change management

Sector-specific

  • HIPAA Security Rule §164.312
  • PCI DSS v4.0 Req. 10
  • NERC CIP-005 / CIP-007
  • NIS2 Art. 21 risk measures
07 · deployment patterns

Three deployment topologies

Same data diode constraint at every scale. The one-way ingress is identical whether the deployment is a single-site SMB or a multi-region critical-infrastructure network.

SMB / Single-site
single binary
T1 + T2 combined
T3 appliance
Segmented OT / Clinical
per-segment
T1 endpoints
T2 segment gates
T3
Critical infrastructure / Multi-region
hierarchical
T1
per-segment T2
site T3
regional T3
HQ T3
08 · one-way ingress

T3 never talks back.

Configuration arrives by physical key insertion. This eliminates an entire attack class. Three acceptable ingress mechanisms, ranked by assurance:

01 · Highest assurance

Optical data diode

Physical fiber-optic one-way link. No electrical return path. The gold standard for air-gapped T3 ingress. Vendor-certified unidirectional.

OPTICAL · UNIDIRECTIONAL
02 · High assurance

Serial pull

T3 initiates serial-port read on a strict schedule. T2 writes to a buffer; T3 pulls. No bidirectional handshake. Air gap maintained by protocol discipline.

RS-232 · PULL-ONLY · SCHEDULE-BOUND
03 · Acceptable

Physical media

Write-once optical disc or signed USB. Manual courier. Chain of custody on the physical medium itself. Suitable for low-volume, high-ceremony deployments.

WORM DISC · SIGNED USB · MANUAL COURIER
09 · composability

Rule 0: ADD-ONLY

SecOps composes with the kernel's other verticals without touching them. It adds capsules and gates — never edits another vertical's manifests, signatures, or ledgers.

Request a Safe Harbor briefing

SecOps supports defensibility posture for cyber-insurance evidentiary claims, incident-response chain-of-custody, and post-breach regulatory review.

Request briefing → Operator Console →