Skip to content

Distributed 2PC/3PC Transactional Mitigation Engine

Density:

A defensive transaction T is defined as an ordered sequence of heterogeneous actions across independent enforcement agents:

T = [ a_firewall, a_identity, a_edr, a_deception ]

Hermes enforces the ACID Defensive Invariant:

  • Atomicity: Either all mitigation actions succeed and are permanently committed, or none are applied and any partial changes are cleanly rolled back.
  • Consistency: The enterprise security posture transitions deterministically from safe state S0 to hardened state S1.
  • Isolation: Concurrent mitigation transactions targeting overlapping network segments or accounts are serialized.
  • Durability: Committed mitigation states survive agent crashes and network partitions via immutable Merkle logging.

Unlike classic Two-Phase Commit (2PC) which blocks indefinitely if the coordinator fails during the commit phase, Hermes implements Non-Blocking Three-Phase Commit (3PC):

Coordinator (Arbiter) Firewall Agent IAM Warden Agent EDR Agent
| | | |
| 1. CAN-COMMIT? | | |
|----------------------------->|-------------------->|------------------>|
| | | |
| 2. YES / VOTE-COMMIT | | |
|<-----------------------------|<--------------------|<------------------|
| | | |
| 3. PRE-COMMIT (Lock assets) | | |
|----------------------------->|-------------------->|------------------>|
| | | |
| 4. ACK-PRECOMMIT | | |
|<-----------------------------|<--------------------|<------------------|
| | | |
| 5. DO-COMMIT (Execute) | | |
|----------------------------->|-------------------->|------------------>|
| | | |
| === MITIGATION APPLIED ATOMICALLY ACROSS ALL TARGETS === |

Every defensive transaction is bound to a 60-second Canary Health Monitor:

  1. After DO-COMMIT, the swarm monitors health telemetry (BGP route flapping, legitimate authentication failure spikes, VIP reachability).
  2. If any monitored canary metric exceeds failure thresholds within 60 seconds, the coordinator immediately transitions the transaction from COMMITTED to ROLLED_BACK.
  3. Inverse compensation steps are executed in reverse order (a_edr_inv, a_identity_inv, a_firewall_inv) returning the infrastructure to pristine state S0.