Compliance Matrix: FSTEC Order No. 117, GOST R 56939-2024, Federal Law No. 152-FZ, and Civil Code Article 1079
Operating autonomous software agents inside regulated financial, legal, and public-sector environments requires verifiable engineering controls rather than declarative policy statements. Effective March 1, 2026, Order No. 117 of the Federal Service for Technical and Export Control of Russia (FSTEC of Russia) dated April 11, 2025 mandates strict application-interface filtering and tamper-evident event logging across protected information systems (clauses 60 and 61).
Simultaneously, civil liability doctrine treats autonomous agent deployments analogously to sources of heightened danger under Article 1079 of the Civil Code of the Russian Federation. The only mathematically sound way to attribute liability between the model vendor, the system operator, and the end user is an immutable, hash-chained cryptographic receipt for every permitted and blocked tool call.
1. Regulatory Requirements Mapped to MITR Engineering Controls
The table below maps each statutory requirement to its concrete implementation module, engineering decision record, and live verification artifact.
| Regulation & Clause | Protected Legal & Security Invariant | Implementation in MITR Sentinel & Z3 Gate |
Verification Artifact & Flag |
|---|---|---|---|
FSTEC Order No. 117 (clauses 60–61) & GOST R 56939-2024 |
Application programming interface boundary protection and tamper-evident security event logging | In-path contract filter mcp-sentinel 1.1.2, formal Z3 prover on tiers R4–R5, and append-only iss-ledger-117 1.1.1 with Streebog-256 hash chaining |
DECISION_LEDGER=on, verifier iss_verifier.py |
| Civil Code Article 1079 (Heightened Danger Liability) | Evidentiary proof of safety enforcement and fault delineation across multi-party agent workflows | Cryptographic receipt for every UNSAT allowance and SAT block, externally anchored to the Bitcoin blockchain via OpenTimestamps |
gate_actions.jsonl, kit /console/verify/ |
| Federal Law No. 152-FZ (Personal Data Protection) | Prevention of unauthorized outbound transmission of payment card numbers and personal identifiers | Deterministic pre-dispatch payload inspection and token redaction prior to external webhook or interface transmission (ADR-0073) |
PII_CARD_GUARD=on, tier R4 outbound block |
| Direct & Indirect Prompt-Injection Defense | Blocking malicious instructions embedded inside untrusted external documents or retrieval corpora | Structural command-data separation, red-line invariant hardening, and retrieval provenance checks (ADR-0068, ADR-0069, ADR-0072) |
RED_LINES_HARDENING=on, RAG_INJECTION_GUARD=on |
| Sovereign Air-Gapped Isolation | Zero reliance on external content delivery networks, third-party trackers, or foreign cloud verifiers | Self-contained static assets with strict cross-origin headers (COOP: same-origin, COEP: require-corp) and self-hosted /vendor/z3/ |
asi5.ru.nginx.conf, MITR Opora bundle |
2. Legal Demarcation of the Developer Factory Test Protocol
All telemetry figures published on asi5.ru and inside the /console/verify/ bundle are generated automatically from daily testbed runs as an internal factory test protocol by Autonomous Non-Profit Organization Research Institute of System Synthesis (OGRN 1267700083617, INN 9731161602). This protocol demonstrates deterministic engineering performance under the stated methodology and does not replace a state compliance certificate issued by FSTEC of Russia where certified means of protection are statutorily required.