Skip to content
Terminal Ledger Desk
Directory

Reg Sci Disaster Recovery Outage Rca

SEC Regulation SCI Rule 1002: Incident Triage Trees, Immediate SEC Notification & De Minimis Safe Harbor

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.

By Marcus Thorne, CQFReview not recorded · Updated
SEC Regulation SCI Rule 1002: Incident Triage Trees, Immediate SEC Notification & De Minimis Safe Harbor — Terminal Ledger Desk 2026 quantitative & supervisory data card
Terminal Ledger Desk (SEC Regulation SCI, Active-Active Exchange Failover & Outage Post-Mortems): Immediate SEC calls, 24h Form SCI filings, rulebook-vs-code audits, and Indirect SCI walls.Source: Terminal Ledger Desk Institutional Research DeskLicense: CC-BY-4.0

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, 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).
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
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 NoticeVerified Exhibit

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:

  • 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).
Quantitative Distribution · SEC Notification SLA
SEC Notification SLA
01Major SCI EventImmediate + < 2…02Standard Reportable SCIImmediate + < 2…
Incident Severity TierOperational / Legal DefinitionSEC Notification SLAMember Dissemination (Rule 1002(c))
Major SCI EventCatastrophic market-wide / Critical SCI impactImmediate + < 24h Form SCI + < 5d FinalPromptly to ALL members / participants
Standard Reportable SCINon-de-minimis Disruption, Rule Mismatch, or IntrusionImmediate + < 24h Form SCI + < 5d FinalPromptly to affected/responsible members (safe delay for active cyber defense)
De Minimis SCI EventMinimal/zero impact on ops or market participantsExempt from immediate/24h; log internally + Quarterly SummaryNot required (Internal SCI log retained 5 yrs)
Planned Material ChangeNon-emergency major architecture rollout (Rule 1003(a))Quarterly report + advance notice if materialPublished 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 or model from the articleNot independently verified
Is_Indirect_SCI_System(Host_X) = NOT_Physically_Or_Logically_Separated_From_Production_SCI_Plane(Host_X)
  • Rule 1002 Notification Trigger Latency Bound:
  • Tsecnotify <= Treasonablebasisconfirmation + Tescalationplaybookminutes
  • (Anti-Pattern: Waiting until Tfullrootcausepostmortem [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):

  • 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); 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 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
Key pitfalls in SEC Regulation SCI enforcement actions across Delayed Immediate Notifications, Unfiled Systems Compliance Bugs, Unsegregated Indirect SCI Networks, and Third-Party Vendor GapsVerified Exhibit

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 and model halt risk in the 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.

Publication record

Published
13 November 2026
Updated
15 November 2026
Author
Marcus Thorne, CQF
Review
Review not recorded
Automated fact check
Passed in the stored pipeline record
Source URLs
3 recorded

AI assistance recorded: anthropic/claude-opus-4.6. This field does not establish human review or source verification.

Academic & Institutional Attribution

Cite This Research & Embed Live Data Card

Open Attribution License (CC BY 4.0)

Standard academic & institutional research paper citation format.

Marcus Thorne, CQF. (2026, November 15). 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
Explore Reg Sci Disaster Recovery Outage Rca Hub (20) →

Terminal Ledger Desk Data, Benchmarks & Contributor Records

SEC Reg SCI Rule 1002 Incident Triage & Notification SLAs | Terminal Ledger Desk