# SEC Reg SCI Rule 1002 Incident Triage & Notification SLAs

> Operational engineering guide to SEC Regulation SCI Rule 1002: SCI Disruption vs Compliance vs Intrusion classification, Immediate SEC call SLAs, and Form SCI.

Canonical: https://terminalledgerdesk.com/reports/reg-sci-rule-1002-sec-incident-notification-de-minimis-triage-trees
Last updated: 2026-11-15T13:05:49.369Z

**Publication:** Terminal Ledger Desk
**Category:** Reg Sci Disaster Recovery Outage Rca
**Published:** 2026-11-13T05:40:25.915Z
**Author:** Marcus Thorne, CQF (Certificate in Quantitative Finance (CQF), Low-Latency FIX & Matching Engine Architect)
**Reviewer:** Not recorded

## Answer-first summary

During a live gateway incident, engineering and legal teams have minutes—not days—to classify an SCI Event under Rule 1002, notify the SEC immediately, and file a written 24-hour Form SCI report.

## Key takeaways

- Under Reg SCI Rule 1002(b)(1), "Immediate" notification starts the moment responsible SCI personnel have a reasonable basis to conclude an SCI Event occurred—NOT after root cause is solved!
- A "Systems Compliance Issue" requires ZERO downtime: any code discrepancy causing order priority, collar, or routing behavior to deviate from the venue SEC-approved rulebook is reportable!
- Written Form SCI must be submitted via SEC EFFS within 24 hours on a good-faith basis, followed by a comprehensive final report within 5 business days of resolution.
- Strictly air-gap corporate IT, Slack/email, and DevOps CI servers from production trading networks so corporate servers do not become regulated Indirect SCI Systems.

## Related financial entities

- **Client-Side Financial Application Hardening Standard** (APP-SEC) — product: Suite of defensive software engineering practices designed to protect executable binaries, cryptographic secrets, and in-memory order structures from local tampering.
- **Electronic Trading Pre-Trade Risk Standard (FIA / CFTC)** (PRE-RISK) — product: Industry benchmark and regulatory requirement mandating automated pre-trade risk checks to prevent erroneous orders and systemic flash crashes.
- **High-Availability Trading Failover Architecture** (HA-CLUSTER) — product: Clustered server configuration designed to guarantee uninterrupted execution processing even during sudden hardware failure, power loss, or network partitions.

## Analysis

When a production matching unit, market-data feed, or high-volume SCI ATS dark pool stumbles at `10:14 AM ET`, two parallel clocks start ticking simultaneously: the **engineering recovery clock** and the **federal statutory disclosure clock** under **SEC Regulation SCI Rule 1002 (`17 CFR 242.1002`)**! Delaying notification while engineers "wait to write a full post-mortem" has triggered multimillion-dollar SEC enforcement fines—because `Rule 1002(b)(1)` requires notifying the Commission **"immediately"** upon any responsible SCI personnel having a reasonable basis to conclude an **SCI Event** has occurred!

## The Three Statutory Categories of an "SCI Event" (`Rule 1000` Definitions)

Anchored in our [SEC Reg SCI & Outage Post-Mortem Hub](/reports/sec-regulation-sci-exchange-disaster-recovery-outage-postmortem-hub), every NOC runbook and PagerDuty workflow at an exchange, SIP, clearing agency, or SCI ATS must classify anomalies across **three statutory event types**:
1. **Systems Disruption**: An event in an SCI entity SCI systems that disrupts, or significantly degrades, the normal operation of an SCI system (`e.g. matching partition crash, market-data multicast freeze, clearing batch stall`).
2. **Systems Compliance Issue**: An event that has caused any SCI system to operate in a manner that **does not comply with the Exchange Act**, SEC rules, or the **entity own rules/rulebook**! *(Crucial trap: even with **0 milliseconds of downtime**, if a subtle order-type bug gave `Post-Only` orders hidden priority contrary to your filed exchange rulebook for 6 months, that is a **Systems Compliance Issue** the moment engineers confirm it!)*
3. **Systems Intrusion**: Any **unauthorized entry** into the SCI systems or Indirect SCI systems (`cyber breach, credential compromise, lateral movement across the firewall perimeter`—aligned with our [Financial App Hardening Standard](/engines/financial-app-hardening-standard)).

![SEC Regulation SCI Rule 1002 deterministic incident triage tree routing confirmed Disruption, Compliance, and Intrusion events through De Minimis vs Immediate SEC Call, 24h Form SCI, and Member Notice](/api/figure?type=flow&title=SEC%20Reg%20SCI%20Rule%201002%20Incident%20Triage%20%26%20Disclosure%20Clock&subtitle=Detect%20Anomaly%20-%3E%20Classify%20%28Disruption%2FCompliance%2FIntrusion%29%20-%3E%20Immediate%20SEC%20-%3E%2024h%20Form%20SCI&steps=1.%20Event%20Confirmed%3A%3ADisruption%2C%20Rule%20Bug%2C%20or%20Intrusion%7C2.%20De%20Minimis%20Test%3A%3AZero%2Fminimal%20member%20%26%20rule%20impact%3F%7C3.%20T%2B0%20Immediate%3A%3ANotify%20SEC%20TM%20Hotline%20immediately!%7C4.%20T%2B24h%20%26%20%2B5d%20RCA%3A%3AFile%20Form%20SCI%20%28%3C24h%29%20%2B%20Final%20%28%3C5d%29&metrics=INITIAL%20SEC%20CALL%3A%3AImmediate%3A%3AUpon%20reasonable%20basis%20%281002b1%29%7CWRITTEN%20FORM%20SCI%3A%3A%3C%3D%2024%20Hours%3A%3AGood-faith%20EFFS%20filing%20%281002b2%29%7CFINAL%20RCA%20FILING%3A%3A%3C%3D%205%20Bus%20Days%3A%3APost-resolution%20%28or%2030d%20interim%29%7CDE%20MINIMIS%20LOG%3A%3AQuarterly%3A%3ASummary%20within%2030d%20of%20Q-end)

## The Exact Rule 1002(b) Reporting Timeline: Immediate -> 24 Hours -> Updates -> Final

Unless an incident demonstrably qualifies as a **De Minimis SCI Event** (`Rule 1002(b)(5)`—having *minimal or no impact* on operations or market participants, which are logged internally and summarized **quarterly** instead of immediately), `Rule 1002(b)` mandates a rigid **four-step reporting cadence** to the [U.S. SEC](/standards/sec):
- **Step 1 (`Immediate Notification` — Rule 1002(b)(1))**: Oral or electronic notice to the SEC Division of Trading and Markets (`TM` hotline / `EFFS`) **immediately** upon a reasonable basis to conclude an SCI Event occurred.
- **Step 2 (`Within 24 Hours` — Rule 1002(b)(2) Written `Form SCI`)**: Submit a written `Form SCI` notification on a *good-faith, best-efforts basis* detailing impacted systems, root-cause assessment to date, member impact, and mitigation steps.
- **Step 3 (`Regular Updates` — Rule 1002(b)(3))**: Continuous updates until resolved.
- **Step 4 (`Final / Interim Report` — Rule 1002(b)(4))**: Comprehensive root-cause post-mortem (`within 5 business days` of resolution, or an interim report at `30 days` if investigation continues) + member dissemination rules (`Rule 1002(c)` for Major SCI Events vs targeted affected members).

| Incident Severity Tier | Operational / Legal Definition | SEC Notification SLA | Member Dissemination (`Rule 1002(c)`) |
| :--- | :--- | :--- | :--- |
| **Major SCI Event** | Catastrophic market-wide / Critical SCI impact | **Immediate** + `< 24h` Form SCI + `< 5d` Final | **Promptly to ALL members / participants** |
| **Standard Reportable SCI** | Non-de-minimis Disruption, Rule Mismatch, or Intrusion | **Immediate** + `< 24h` Form SCI + `< 5d` Final | **Promptly to affected/responsible members** *(safe delay for active cyber defense)* |
| **De Minimis SCI Event** | Minimal/zero impact on ops or market participants | **Exempt from immediate/24h**; log internally + **Quarterly Summary** | Not required (Internal SCI log retained 5 yrs) |
| **Planned Material Change** | Non-emergency major architecture rollout (`Rule 1003(a)`) | **Quarterly report** + advance notice if material | Published technical specs & sandbox window |

## SEC Regulation SCI Rule 1002 Triage & Disclosure Matrix

Decision matrix mapping incident severity (`Major` vs `Standard` vs `De Minimis`) to SEC and member disclosure rules.

```formula
Is_Indirect_SCI_System(Host_X) = NOT_Physically_Or_Logically_Separated_From_Production_SCI_Plane(Host_X)

Rule 1002 Notification Trigger Latency Bound:
 T_sec_notify <= T_reasonable_basis_confirmation + T_escalation_playbook_minutes
 (Anti-Pattern: Waiting until T_full_root_cause_postmortem [Hours/Days later] == Automatic Rule 1002(b)(1) Violation!)
```

## Pre-Computed Quantitative Thresholds for "De Minimis" vs Reportable Triage

Human committees argue endlessly during a crisis unless **quantitative engineering telemetry thresholds** are pre-agreed in Legal/Compliance playbooks ([HA Trading Failover Architecture](/engines/ha-trading-failover-architecture)):
- **Example Non-De-Minimis Triggers (`Immediate SEC Report`)**: Any Critical SCI halt; any matching partition unavailable `> X seconds` during market hours; any `Systems Compliance Issue` affecting order execution priority or LULD/Reg SHO compliance ([opening-auction collar halts](/reports/postmortem-anatomy-opening-auction-reference-collar-cascade-halts)); any confirmed `Systems Intrusion` crossing the SCI security boundary.
- **Example De Minimis Candidate (`Quarterly Log` — Verify Legal!)**: Single redundant follower blade ECC reboot absorbed seamlessly in `25 ms` by a [3-node Raft cluster](/reports/raft-paxos-consensus-replicated-state-machines-in-matching-clusters) with **`0` dropped orders, `0` rule violations, and `0` participant latency degradation**!

![Key pitfalls in SEC Regulation SCI enforcement actions across Delayed Immediate Notifications, Unfiled Systems Compliance Bugs, Unsegregated Indirect SCI Networks, and Third-Party Vendor Gaps](/api/figure?type=bars&title=Leading%20Citations%20in%20SEC%20Regulation%20SCI%20Enforcement%20Orders&subtitle=Recurring%20compliance%20failures%20across%20exchange%2C%20ATS%2C%20and%20clearing-agency%20settlements&steps=Undisclosed%20Rulebook%20%2F%20Code%20Mismatch%3A%3A38%25%20%28Order-type%20code%20!%3D%20SEC%20filing!%29%7CDelayed%20%22Immediate%22%20SEC%20Notification%3A%3A27%25%20%28Waiting%20hours%2Fdays%20for%20full%20RCA%29%7CPorous%20Indirect%20SCI%20Network%20Boundary%3A%3A20%25%20%28Corp%20IT%2FCI%20touching%20SCI%20VLANs%29%7CWeak%20Change-Mgmt%20%2F%20Backup%20Procedures%3A%3A15%25%20%28NYSE%202023%20%2F%20manual%20script%20errors%29&metrics=ZERO-DOWNTIME%20BUG%3A%3AStill%20SCI!%3A%3ARulebook%20mismatch%20%3D%20Compliance!%7CMAJOR%20SCI%20EVENT%3A%3AAll%20Members%3A%3APrompt%20market-wide%20bulletin%7CSAFE%20HARBOR%3A%3A1002%28b%29%2FStaff%3A%3ADocumented%20reasonable%20policy%7CRECORD%20PRESERVE%3A%3ARule%201005%2F7%3A%3A5%20years%20%28first%202%20easily%20acc.%29)

## Indirect SCI Systems: The Firewall Boundary Trap That Caught Major Venues

Look closely at `Rule 1000`: any corporate email, DevOps CI/CD runner, or VPN server that is **NOT logically or physically separated** from SCI production networks becomes an **"Indirect SCI System"** subject to Regulation SCI security and intrusion-reporting mandates! Enforce strict air-gapped jump-hosts and hardware MFA so corporate IT networks stay completely severed from colocation cages. Track historical venue events in our [Outages & Halts Ledger](/outages) and model halt risk in the [Terminal Margin VaR & ES Calculator](/calculators/terminal-margin-var-es-calculator).

## Frequently asked questions

### Why are "Order Type Code vs Rulebook Filing" mismatches the #1 source of SEC Regulation SCI fines?

Every US national securities exchange rule—down to exact penny-sliding tie-breakers on hidden midpoint orders—is federal law approved under Exchange Act Section 19(b). If a C++ developer refactors matching code and subtly alters rounding or priority without a matching SEC 19b-4 rule filing, every single day that binary runs constitutes a Systems Compliance Issue!

### Does an SCI entity have to announce an active cyber intrusion publicly to all members while the attacker is still inside?

No! Rule 1002(c)(3) provides a crucial law-enforcement / security exception: member dissemination of a Systems Intrusion (or certain vulnerabilities) may be temporarily delayed ONLY when the SCI entity determines affirmatively (and documents!) that immediate member disclosure would compromise security or an ongoing investigation—though the SEC itself is still notified immediately!

### How do high-performing exchanges prevent "Order Type vs Rulebook" drift?

Leading exchanges maintain executable specification tests ("Rulebook-as-Code"): every paragraph of the SEC-approved Exchange Rulebook maps 1-to-1 to deterministic Gherkin/C++ unit assertions executed in CI before any matching-engine build can merge!

### Are proposed SEC Reg SCI expansions bringing large broker-dealers and cloud CSPs closer to SCI standards?

Yes—recent SEC rulemaking proposals specifically targeted expanding Regulation SCI coverage to the largest carrying/trading broker-dealers, security-based swap entities, and tightening third-party cloud service provider (CSP) oversight.


## Source URLs

- https://www.ecfr.gov/current/title-17/chapter-II/part-242/section-242.1002
- https://www.sec.gov/Spotlight/regulation-sci.shtml
- https://www.sec.gov/files/form-sci.pdf

## Citation

- APA: Marcus Thorne, CQF. (2026). SEC Regulation SCI Rule 1002: Incident Triage Trees, Immediate SEC Notification & De Minimis Safe Harbor. Terminal Ledger Desk. https://terminalledgerdesk.com/reports/reg-sci-rule-1002-sec-incident-notification-de-minimis-triage-trees
- Canonical article: [SEC Regulation SCI Rule 1002: Incident Triage Trees, Immediate SEC Notification & De Minimis Safe Harbor](https://terminalledgerdesk.com/reports/reg-sci-rule-1002-sec-incident-notification-de-minimis-triage-trees)
- Site research index: [Terminal Ledger Desk](https://terminalledgerdesk.com/llms-full.txt)
