Layer 7 — AI Governance (BFT Council)
33-Agent Byzantine Fault Tolerant Decision Council
Every AI decision with operational impact passes through a 33-agent BFT council. Quorum of 23/33 required for execution. Any agent can veto. Council deliberations are SIGIL-logged. Prevents single-point-of-failure AI decisions and adversarial manipulation.
COUNCIL VOTE: deploy_drone_swarm_to_grid_S4
QUORUM: 23/33 required
VOTE: 29 FOR / 3 ABSTAIN / 1 AGAINST → APPROVED
SIGIL: f3a8b2c1...4e5f (Ed25519 signed)
Layer 6 — Audit Trail (SIGIL Chain)
Ed25519 Hash-Chained Execution Ledger
Every action — API call, AI inference, drone command, sensor reading — is logged to the SIGIL chain. Each entry is Ed25519-signed and hash-chained to the previous entry. Tampering breaks the chain. The full ledger is replayable for after-action review and regulatory audit.
SIGIL ENTRY:
ts: 2026-07-06T06:45:00Z
actor: jeeves-agent-001
action: mcp_federation_call
tool: sentinel-hub-mcp/get_satellite_imagery
params: {bbox: [53.8, -1.5, 53.9, -1.4], date: "2026-07-06"}
result_hash: sha256:a3f7e2...
prev_sig: 763521b2d0...
signature: cef92dd24c... (Ed25519)
Layer 5 — Compliance (JSP 936 Generator)
Automated AI Assurance Report Generation
Every deployed AI model gets an auto-generated JSP 936 compliance report. Covers: model provenance, training data, bias testing, adversarial robustness, human-in-the-loop requirements, edge cases, decommissioning plan. Maps to UK AI Bill 2025, EU AI Act, and ISO 42001.
Layer 4 — Cryptography (Quantum-Safe)
ML-DSA-65 (Dilithium) + ML-KEM-768 (Kyber) Ready
DEFONEOS implements NIST post-quantum cryptography standards. Digital signatures use ML-DSA-65 (CRYSTALS-Dilithium, security level 3). Key encapsulation uses ML-KEM-768 (CRYSTALS-Kyber). 90-day rotation cycle. Current deployment uses Ed25519 (classical) with PQC as dual-signing overlay — ready for the quantum threat.
| Algorithm | Type | NIST Standard | Security Level | Key Size |
|---|
| ML-DSA-65 (Dilithium) | Signature | FIPS 204 | 3 (192-bit) | 1952 bytes pub |
| ML-KEM-768 (Kyber) | Key Exchange | FIPS 203 | 3 (192-bit) | 1184 bytes pub |
| Ed25519 | Signature (current) | RFC 8032 | 128-bit classical | 32 bytes pub |
| SHA-256 | Hash | FIPS 180-4 | 128-bit | 32 bytes |
Layer 3 — Network (Zero-Trust)
mTLS + SPIFFE Identity + Microsegmentation
Every service-to-service connection uses mutual TLS. Each service has a cryptographic identity (SPIFFE/SPIRE). No implicit trust — every request is authenticated, authorised, and logged. Network is microsegmented: sensor MCPs cannot talk to each other directly, only through the fusion engine. C2 commands flow through a dedicated control plane.
| Component | Protocol | Port | Auth |
|---|
| Sensor MCP → Fusion Engine | gRPC + mTLS | 9090 | SPIFFE ID |
| Fusion Engine → Cesium COP | WebSocket + TLS | 443 | JWT (Ed25519) |
| C2 (FreeTAKServer) → Drones | CoT + DTLS | 8087/8089 | Pre-shared key + cert |
| SIGIL Ledger → Storage | gRPC + mTLS | 9091 | SPIFFE + Ed25519 |
| BFT Council → Agents | gRPC + mTLS | 9092 | SPIFFE + vote token |
| Admin / Dashboard | HTTPS + OAuth2 | 443 | OIDC + RBAC |
Layer 2 — Platform (Hardened Containers)
Distroless Containers + seccomp + Read-Only Rootfs
All DEFONEOS services run in distroless containers (no shell, no package manager, no attack surface). Root filesystem is read-only. seccomp profiles restrict syscalls to a minimal whitelist. Each container runs as non-root (UID 65534). AppArmor profiles enforce additional MAC constraints.
| Hardening Control | Implementation | Verified |
|---|
| Container base image | gcr.io/distroless/python3 (no shell) | ✅ |
| Root filesystem | Read-only (readOnlyRootFilesystem: true) | ✅ |
| User | nonroot (UID 65534) | ✅ |
| seccomp | RuntimeDefault + custom deny-list | ✅ |
| AppArmor | Custom profile per service | ✅ |
| Capabilities | All dropped (drop: ALL) | ✅ |
| Privileged mode | Never (privileged: false) | ✅ |
| Image scanning | Trivy + Grype on every build | ✅ |
| SBOM | CycloneDX generated per image | ✅ |
Layer 1 — Physical (Sovereign Cloud)
UK Sovereign Cloud (MOD Cloud / Crown Commercial)
DEFONEOS runs on UK sovereign cloud infrastructure. No foreign data centres. No foreign jurisdiction. Data residency guaranteed under UK GDPR + DPA 2018. Options: MOD Cloud (preferred), UK Crown Commercial Service approved cloud (AWS London, Azure UK South, GCP London), or on-premise at MOD establishment.
| Cloud Option | Region | Sovereignty | Classification |
|---|
| MOD Cloud | UK (Farnborough) | ✅ UK Sovereign | Up to SECRET |
| AWS London (eu-west-2) | UK (London) | ✅ UK Data Residency | Up to OFFICIAL |
| Azure UK South | UK (London) | ✅ UK Data Residency | Up to OFFICIAL |
| GCP London (europe-west2) | UK (London) | ✅ UK Data Residency | Up to OFFICIAL |
| On-Premise (MOD Est.) | UK (Site-specific) | ✅ Full Air-Gap | Up to TOP SECRET |