INDRA: Formal Vulnerability Proof and Automatic Rule Synthesis Without Database Damage

1. Visual Explanation: Why Blind Scanners Break Databases While INDRA Proves Safety

To make the engineering mechanism clear at a glance to both non-technical decision-makers and principal security engineers, the diagram below compares conventional active scanning against the in-path wire filter of INDRA. A traditional tool transmits raw mutations directly to the server socket and relies on human analysts to sort through dozens of ambiguous error responses.

2. Interactive Five-Stage Pipeline (L1 through L5): Plain Meaning and Engineer's Proof

Every verification cycle moves through five deterministic stages without calling external cloud models or exposing internal traffic to third parties. Click any stage button below the schematic to inspect both the plain-language explanation and the exact technical proof recorded on the reference stand.

Module: ScopeGuard + ScopedRedirectHandler
Allowlist: localhost:8888, localhost:8890
HTTP 301/302/307/308 external hop -> ScopeViolationError
Gate A Verification: 1.140 s (PASS, rc=0)

3. Live Deterministic Wire-Filter & Immune Rule Simulator (What Language Models Cannot Do)

A conversational language model predicts words from training text and cannot execute an in-path AST wire check, compute a cryptographic Streebog-256 ledger receipt, or guarantee zero false positives on a 28-route testbed. Use the interactive simulator below to test any of the eight benchmark vulnerability classes or submit a custom request string against the live deterministic engine on this host.

{
  "status": "VERIFIED_DETERMINISTIC",
  "vector": "INJ-SQL",
  "scan_mode": "AUTO_SCAN",
  "wire_sandbox": {
    "decision": "BLOCKED_DESTRUCTIVE_MUTATION_BEFORE_SOCKET",
    "sandbox_rule": "SEC-ZD-SQL-01",
    "blocked_tokens": ["DROP TABLE", "TRUNCATE"],
    "packets_sent_to_live_db": 0
  },
  "formal_witness": {
    "witness_hash": "85de2412c34d4965",
    "stand_confusion_matrix": "TP=2, FP=0, TN=2, FN=0 (FPR=0.0%)"
  },
  "immune_compiler": {
    "compiled_rule_id": "IMMUNE-SQL-85DE2412",
    "synthesis_elapsed_sec": 0.00001,
    "mcp_sentinel_latency_ms": {
      "in_memory": 0.016,
      "disk_gost_ledger": 22.5
    }
  },
  "ledger_receipt": {
    "algorithm": "GOST R 34.11-2012 (Streebog-256)",
    "passport_digest": "12893d4741eac397918241743e88a613d6b1b1c6309ee77ebe6bb21fbccc9be3"
  }
}

4. Reference Matrix of 7 Active Auto-Scan Classes and 1 Isolated Lab Class

In the factory test passport (INDRA_AUDIT_PASSPORT.md), the eight vulnerability classes are divided into seven active probing classes (AUTO_SCAN, four scenarios each on the N = 28 stand) and one isolated laboratory class (LAB_ONLY, DOS-RSRC). Separating resource exhaustion into laboratory mode guarantees that routine automated scans never degrade production or staging targets.

5. Clean-Room Demarcation, Honest Boundaries, and Offline Reproducibility

Engineering trust requires explicit boundaries regarding what the platform measures and where its scope ends. Every deployment of INDRA adheres to four verifiable technical and legal boundaries:

• In-path software wire filter: The Zero-Damage Sandbox is a deterministic software interceptor in the request path (zero_damage_sandbox.py) that inspects candidate probes before network transmission. On the reference stand it blocked 26 of 26 destructive mutations in test_sandbox_integrity.py and 7 of 7 destructive probes in Gate B.
• Clean-Room separation from closed solver cores: The indra-core package and the open-source utilities (mcp-sentinel 1.1.2, iss-ledger-117 1.1.1, iss-agent-kit 0.1.1) operate on the Python standard library under the Apache-2.0 license without exposing proprietary Z3 satisfiability modulo theories (SMT) formulas.
• Dual Latency disclosure for mcp-sentinel: Contract checking inside mcp-sentinel 1.1.2 takes approximately 0.016 milliseconds in process memory and approximately 22.5 milliseconds when writing a synchronous GOST R 34.11-2012 receipt to disk.
• Factory test passport disclaimer: The generated document INDRA_AUDIT_PASSPORT.md is an internal developer factory test protocol structured around GOST R 56939-2024 and Order No. 117 of the Federal Service for Technical and Export Control of Russia (FSTEC of Russia) dated April 11, 2025 (clauses 60-61), and does not replace a state compliance certificate.