ShieldCortex

No. ShieldCortex runs entirely on your machine with no cloud, no account, and no telemetry. An optional free cloud account adds replica sync for memories, graph data, and audit logs across devices, with 500 scans a month included. For fleets, always-on servers, and memory sync at scale, Enterprise adds SSO, dedicated support, and an SLA — contact us to discuss.

Every memory write passes through the defence layers: input sanitisation (strips control characters), pattern detection (regex-based prompt injection firewall), semantic analysis (embedding similarity to a curated attack corpus, on the async deep-scan path), structural validation (JSON integrity, format anomalies, fragmentation attempts), behavioural scoring (entropy analysis, anomaly detection, baseline deviation), and credential leak detection (25+ patterns across 11 providers).

ShieldCortex is strongest as a door on the native brain: scan what the agent stores, gate what it does, inspect and quarantine poison. It is not a second MemGPT and does not own OpenClaw or Hermes recall. v5.0.6 is the current patch on 5.0.0 (Node 22.14+ or Node 24). Action Guard and automatic memory inject stay off by default.

Iron Dome is the behavioural protection layer included free with ShieldCortex. It controls what your AI agent can do — not just what it remembers. It includes injection scanning, action gates, PII protection, emergency kill switch, and four built-in security profiles (personal, school, enterprise, paranoid).

Environment Firewall is the third defence layer (added in v4.10.0). The memory firewall protects what the agent stores; Iron Dome protects what the agent does; the Environment Firewall protects what the agent sees from the outside world. Run shieldcortex env scan <url> against any page and it returns a taint label (trusted, untrusted, suspicious, hostile) with CI-friendly exit codes. It scores provenance, detects hidden content tricks (display:none, visibility:hidden, bidi overrides, same-colour text, HTML comments, ARIA-hidden regions, meta refreshes), and runs injection patterns against visible and hidden text separately — a hit inside hidden content marks the page hostile regardless of the domain, because humans will never see it.

Yes. Enterprise engagements include done-for-you configuration: we analyse your codebase and agent stack, produce a hardened ShieldCortex config, and support rollout across your fleet. Contact sales@drakonsystems.com to discuss.

ShieldCortex works with OpenClaw (native hook), Claude Code (MCP memory server), VS Code and Cursor (MCP integration), and Codex (shared Codex config). It can also guard any memory backend via the universal memory bridge scan() API.

Cloud keys are scope-based. Teams can now edit an existing key instead of revoking and recreating it. Typical sync devices use scan and audit. Add verify when you want the Verify workspace to receive LLM verification jobs. Keep keys and admin scopes for humans rather than unattended devices.

Replay is an incident and event reconstruction surface, not a full chat-session movie. It focuses on audit, verify, sync ingest, and synced memory events that matter for investigation, then lets you export reports, scope by device or project, and jump into Review, Capture, or Graph.

v5.0.6 is the current patch on 5.0.0. OpenClaw native process (list, poll, inspect a running session) is a reviewed contract: inspect calls go through, stop or type-into still needs a yes, and the card says what Jarvis wants to do instead of invalid_tool_input. shieldcortex protect (root, once) pins the security-critical config so an agent cannot quietly turn Guard off. The breaking change is still 5.0.0: Node 20 is gone (Node 22.14+ or Node 24 only). Action Guard stays off by default. Stay on 4.x with npm install -g shieldcortex@4 if you cannot move Node yet. Read https://shieldcortex.ai/docs/upgrading-5 before you update.