Core Role: core-vigilante • Autonomous SOC, SOAR & Deception

Vigilante Cyber Defense, Autonomous SOC & Active SOAR

The core-vigilante Core Role turns your Axonwall appliance into an autonomous Security Operations Center (SOC), kernel-enforced SOAR responder, deception honeynet, and forensic evidence vault. Configured declaratively in /etc/axonwall/vigilante.yaml (with automatic core-k3s dependency activation), Vigilante fuses network IDS/NSM sensors, eBPF runtime detection, multi-agent AI triage, and cryptographic chain-of-custody storage.

1. Vigilante Battlestation & 12 Modular K3s Packages

Vigilante operates across three global enforcement postures (monitoring, hybrid, and enforcing) and orchestrates 12 modular Kubernetes security packages inside the isolated vigilante-soc namespace—backed by OpenEBS axonwall-zfs-local or synchronous 2-node axonwall-replicated-ha PersistentVolumeClaims:

Module IDDefault PVCCyber-Defense Capability
vigil-soc / vigil-local20 GiB / 5 GiBAutonomous multi-agent AI SOC War Room orchestrator paired with air-gapped on-appliance local SLM triage (vigil-local).
opensearch / wazuh50 GiB / 30 GiBDistributed SIEM log analytics index (opensearch) and unified XDR, FIM, and compliance correlation (wazuh).
suricata / zeek / falco10 / 10 / 5 GiBDeep packet IDS/IPS alerts (suricata), L7 protocol transaction logs & file carving (zeek), and eBPF syscall anomaly detection (falco).
bloodhound / openvas / zap15 / 30 / 5 GiBActive Directory & IAM privilege-escalation attack-path graphing (bloodhound), network CVE scanning (openvas), and web DAST (zap).
flamingo / kctf5 GiB / 20 GiBCloud-native deception & canary listener pods (flamingo) and isolated Kubernetes CTF / Purple-Team exploit range (kctf).

2. Kernel-Level SOAR Active Containment & Ransomware Freeze

Unlike cloud SIEMs that merely emit ticket notifications minutes after data exfiltration completes, VigilanteManager (engine/vigilante.go) executes deterministic kernel and K3s containment in milliseconds governed by VigilanteSoarPolicySchema:

Priority -10 nftables C2 Blocklists

Vigilante hooks table inet axonwall input and forward chains at priority -10 (pre-empting standard priority 0 pass rules). When autoBlockC2Ips triggers, validated IPs/CIDRs (checked against ValidateTargetSafety so appliance, gateway, and HA IPs are strictly immune) are injected into timeout-backed kernel sets (@vigilante_soar_block_v4 / @vigilante_soar_block_v6, implemented as vigilante_soar_blocklist_v4/v6).

Shannon-Entropy Ransomware Pod Freeze

eBPF write-stream monitors compute sliding-window Shannon entropy deltas across NAS shares and PVC mounts. When a process spikes write entropy above ransomwareEntropyDeltaThreshold (default 2.0 bits/byte), autoFreezeRansomwarePods immediately halts encryption in place via cgroup freezer / SIGSTOP while autoIsolateCompromisedPods applies a zero-egress NetworkPolicy quarantine.

Multi-Agent War Room Quorum Governance
High-impact autonomous containment actions generated by AI analysts require consensus across independent detection models meeting warRoomQuorumThreshold (default 0.75, configurable from 0.50 to 1.00) before transitioning from advisory staging to kernel enforcement.

3. Deception Mesh, Honeytokens & Canary Directories

Zero-false-positive intrusion detection is achieved by seeding synthetic credentials, decoy listeners, and filesystem tripwires across the cluster (VigilanteDeceptionConfigSchema):

Canary ServiceAccounts

Deploys high-value bait K8s identities (e.g. cluster-admin-backup, vault-sync-sa) watched by audit hooks; any API token use triggers instant pod isolation.

Credential Honeytokens

Generates tracked aws-sts, github-pat, slack-webhook, and decoy kubeconfig lure files that alert the SOC the moment an intruder attempts enumeration.

Decoy Network Services

Spins up instrumented smb, ssh, redis, and mssql traps—allowing MCP DNAT redirection to steer live attackers into sandboxes.

Ransomware Canary Dirs

Places hidden canary bait files in NAS shares (ransomwareCanaryDirs, e.g. /mnt/tank/shares) to detect SMB/NFS lateral encryption on the very first file rename or overwrite.

4. Tamper-Evident ZFS Forensic Evidence Vault & Sigma Data Lake

ProvisionEvidenceVault provisions a dedicated zstd-compressed OpenZFS dataset (<zfsPool>/vigilante-evidence) and strictly verifies that the dataset is mounted before writing forensic artifacts—refusing to silently spill sensitive captures onto the root filesystem:

  • SHA-256 Merkle Chain-of-Custody Ledger & GPG Signing (merkleLedgerEnabled: true)Every captured PCAP ring segment, carved Zeek payload (carved/), memory/process lineage snapshot, and SOAR action is hashed into an append-only SHA-256 Merkle tree under ledger/, optionally signed with an offline-escrowed GPG key (gpgEnabled / gpgKeyId), and packaged as RFC 3161 timestamped court-ready evidence bundles or replicated to Axonwall Vault WORM S3 object lock.
  • Embedded SQLite / DuckDB Security Data Lake (dataLakeBackend)Select lightweight transactional sqlite or vectorized columnar duckdb under datalake/ for high-speed Sigma rule hunting across millions of normalized Suricata EVE, Zeek, Falco, K3s audit, and OpenLDAP authentication events.

5. Multi-Node Federation, LDAP RBAC & Vigilante MCP Server

Vigilante integrates natively with Axonwall's multi-site fleet mesh, embedded OpenLDAP directory, and autonomous AI tooling:

Peer SOC Threat Federation

Enable federation.enabled to exchange signed IOCs and active C2 blocklists across peer Axonwall SOC nodes (autoIngestPeerBlocks: true) so a compromise detected at one branch immunizes the entire enterprise fleet.

Zero-Touch OpenLDAP RBAC

Automatically provisions service account svc-vigilante and POSIX groups vigilante-admin (10230), vigilante-operator (10231), and vigilante-readonly (10232), propagating SSO bindings into OpenSearch, Wazuh, and Vigil-SOC (Identity Docs).

106-Tool Vigilante MCP Server

Exposes 18 static resources, 5 URI templates, and 106 specialized cyber-ops tools covering Sigma hunting, MITRE ATT&CK Purple Team atomic simulations, kCTF range scoring, BloodHound path queries, and forensic evidence sealing.

/etc/axonwall/vigilante.yaml
yaml
vigilante:
  enabled: true
  posture: "hybrid"
  domain: "soc.axonwall.local"

  modules:
    - id: "vigil-soc"
      enabled: true
      namespace: "vigilante-soc"
      storageClass: "axonwall-replicated-ha"
      storageSizeGb: 20
    - id: "vigil-local"
      enabled: true
      namespace: "vigilante-soc"
      storageClass: "axonwall-zfs-local"
      storageSizeGb: 10
    - id: "opensearch"
      enabled: true
      namespace: "vigilante-soc"
      storageClass: "axonwall-zfs-local"
      storageSizeGb: 80
    - id: "wazuh"
      enabled: true
      namespace: "vigilante-soc"
      storageClass: "axonwall-replicated-ha"
      storageSizeGb: 40
    - id: "falco"
      enabled: true
      namespace: "vigilante-soc"
      storageClass: "axonwall-zfs-local"
      storageSizeGb: 5
    - id: "suricata"
      enabled: true
      namespace: "vigilante-soc"
      storageClass: "axonwall-zfs-local"
      storageSizeGb: 15
    - id: "zeek"
      enabled: true
      namespace: "vigilante-soc"
      storageClass: "axonwall-zfs-local"
      storageSizeGb: 20
    - id: "bloodhound"
      enabled: true
      namespace: "vigilante-soc"
      storageClass: "axonwall-zfs-local"
      storageSizeGb: 15
    - id: "flamingo"
      enabled: true
      namespace: "vigilante-soc"
      storageClass: "axonwall-zfs-local"
      storageSizeGb: 5
    - id: "zap"
      enabled: false
      namespace: "vigilante-soc"
      storageClass: "axonwall-zfs-local"
      storageSizeGb: 5
    - id: "kctf"
      enabled: false
      namespace: "vigilante-soc"
      storageClass: "axonwall-zfs-local"
      storageSizeGb: 20
    - id: "openvas"
      enabled: false
      namespace: "vigilante-soc"
      storageClass: "axonwall-zfs-local"
      storageSizeGb: 30

  soar:
    autoBlockC2Ips: true
    autoIsolateCompromisedPods: true
    autoFreezeRansomwarePods: true
    ransomwareEntropyDeltaThreshold: 2.0
    warRoomQuorumThreshold: 0.75
    blocklistTimeoutSeconds: 86400

  deception:
    enabled: true
    canaryServiceAccounts:
      - "cluster-admin-backup"
      - "vault-sync-sa"
    honeytokens:
      - "aws-sts"
      - "github-pat"
      - "kubeconfig"
    decoyServices:
      - "ssh"
      - "smb"
      - "redis"
    ransomwareCanaryDirs:
      - "/mnt/tank/shares"

  evidenceVault:
    zfsPool: "tank"
    datasetName: "vigilante-evidence"
    dataLakeBackend: "duckdb"
    gpgEnabled: true
    gpgKeyId: "0x9F4B8C2E1A7D3041"
    merkleLedgerEnabled: true

  federation:
    enabled: true
    nodeName: "axonwall-soc-hq"
    peers:
      - "https://10.255.0.2:2966"
    autoIngestPeerBlocks: true

  ldapAuth:
    enabled: true
    autoProvisionPrincipals: true
    allowLocalBreakGlass: true
    defaultRole: "viewer"
    syncModuleSso: true
Access Vigilante Workspaces in Web Console, TUI & CLI
Open the live Attack Graph, SOAR Playbook Queue, Deception Mesh, Purple-Team Range, and Forensic Evidence Vault at /vigilante/battlestation, in the Neovim Super Configurator via axonwall-config vigilante, or on Tab [7] Compute & SOC of axonwall-tui.