# Checklist: running a Regulation SCI program at an SCI entity

Fourteen steps under 17 CFR 242.1000 to 242.1007: defining SCI systems, writing the required policies, notifying the SEC and members of SCI events, filing quarterly change reports, completing the annual SCI review, testing continuity plans with members, and keeping the records.

Checklist · Financial Services · Security & Resilience. Published November 14, 2026. Last reviewed November 14, 2026.

## Who the regulation binds

Regulation SCI applies to SCI entities: SCI self-regulatory organizations (national securities exchanges, registered securities associations, registered clearing agencies and the Municipal Securities Rulemaking Board, with two exclusions for notice-registered exchanges and limited purpose associations), SCI alternative trading systems that cross the volume thresholds in the definition, plan processors, exempt clearing agencies subject to ARP and SCI competing consolidators (section 242.1000) [1]. Broker-dealers that are none of these are outside it.

The SEC proposed amendments on April 14, 2023 that would have widened the definition of SCI entity. In a notice published June 17, 2025, the Commission withdrew that proposal and said it does not intend to issue final rules on it; any future action would start with a new proposal [2]. The steps below follow the rule text in force, as shown in the eCFR and checked on November 14, 2026 [1].

## Reading the steps

Each step gives the work, a typical owner and the section behind it. The owner under each step is a typical role, not one the rule names, unless the step says the rule names it. Where a step is our suggestion rather than a requirement, it says so. This checklist explains the regulation; it is not legal advice, and counsel should confirm how it applies to a given entity.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## The checklist

1. **Classify the entity’s systems as SCI systems, critical SCI systems and indirect SCI systems, and keep the classification current.** (Chief Technology Officer with the Chief Compliance Officer) The duties attach to these defined terms in section 242.1000: SCI systems directly support trading, clearance and settlement, order routing, market data, market regulation or market surveillance; critical SCI systems include clearance and settlement systems of clearing agencies and openings, reopenings and closings on the primary listing market; indirect SCI systems are those that, if breached, would be reasonably likely to pose a security threat to SCI systems [1]. A maintained written classification is our suggestion.
2. **Adopt written policies and procedures for capacity, integrity, resiliency, availability and security that contain the seven minimum elements.** (Chief Technology Officer) Section 242.1001(a)(1) and (2) require capacity planning estimates, periodic capacity stress tests, a program to keep development and testing methodology current, regular reviews and testing including of backup systems, business continuity and disaster recovery plans, market data standards, and monitoring to identify potential SCI events. Under section 242.1001(a)(4), policies consistent with current SCI industry standards are deemed reasonably designed, though those standards are not the only way to comply [1].
3. **Check that the business continuity and disaster recovery plans can meet the two recovery targets the rule sets after a wide-scale disruption.** (Head of resilience) Section 242.1001(a)(2)(v) requires backup and recovery capabilities that are sufficiently resilient and geographically diverse and reasonably designed to achieve next business day resumption of trading and two-hour resumption of critical SCI systems following a wide-scale disruption [1].
4. **Adopt systems compliance policies covering pre-implementation testing, change controls, functional assessments and coordination between regulatory and technology staff.** (Chief Compliance Officer with engineering leads) Section 242.1001(b)(1) and (2) list testing of all SCI systems and changes before implementation, internal controls over changes, a plan for assessments designed to detect systems compliance issues, and a plan of coordination and communication between regulatory and other personnel. Section 242.1001(b)(4) gives individuals a safe harbor when they have reasonably discharged their duties under these policies [1].
5. **Set the criteria for identifying responsible SCI personnel, designate and document them for each system, and write the escalation procedure that reaches them quickly.** (Chief Compliance Officer) Section 242.1001(c)(1) requires all three. Section 242.1000 defines responsible SCI personnel as the senior managers with responsibility for the affected system and their designees, and the event clocks in section 242.1002 start when any of them has a reasonable basis to conclude that an SCI event has occurred [1].
6. **Put a recurring review of each set of policies on the compliance calendar and record the fixes made.** (Chief Compliance Officer) Sections 242.1001(a)(3), (b)(3) and (c)(2) each require periodic review of the policies’ effectiveness and prompt action to remedy deficiencies [1]. The rule does not fix a frequency; a calendar entry and a remediation log are our suggestion.
7. **When responsible SCI personnel have a reasonable basis to conclude an SCI event has occurred, start corrective action and notify the SEC immediately.** (Incident commander, with regulatory affairs) Section 242.1002(a) requires corrective action that at a minimum mitigates potential harm to investors and market integrity and devotes adequate resources to remedy the event. Section 242.1002(b)(1) requires immediate notice to the Commission. An SCI event is a systems disruption, a systems compliance issue or a systems intrusion (section 242.1000) [1].
8. **File the written notifications on Form SCI on the rule’s clock: within 24 hours, then updates, an interim notice within 30 calendar days after the event occurred if it is not resolved or the investigation is not closed, and a final notice within five business days after resolution and closure of the investigation.** (Regulatory affairs) Section 242.1002(b)(2) to (4) set the 24-hour written notice made on a good faith, best efforts basis, the regular updates, the interim notice and the final notice, and list their contents, including an analysis of parties that may have experienced a loss. Section 242.1006 requires filings on Form SCI with an electronic signature, except the immediate notice and the updates [1].
9. **Log de minimis SCI events and file the quarterly summary of de minimis systems disruptions and systems intrusions within 30 calendar days after each quarter ends.** (Regulatory affairs) Section 242.1002(b)(5) removes the immediate and written notice duties for events with no or a de minimis impact on operations or market participants, and replaces them with records and the quarterly report [1].
10. **Tell affected members or participants about SCI events promptly, and all members or participants for major SCI events.** (Member communications, with the incident commander) Section 242.1002(c) requires prompt dissemination of the systems affected and a summary for disruptions and compliance issues, then more detail and progress updates; for intrusions, a summary unless dissemination would likely compromise security or an investigation and the entity documents why. Market regulation and surveillance systems and de minimis events are excepted. A major SCI event is one with any impact on a critical SCI system or a significant impact on operations or market participants (section 242.1000) [1].
11. **Write the criteria for a material systems change, and file the quarterly report of completed, ongoing and planned material changes within 30 calendar days after each quarter ends.** (Change management lead) Section 242.1003(a)(1) requires the report, covering SCI systems and the security of indirect SCI systems, and reasonable written criteria for materiality. Section 242.1003(a)(2) requires a prompt supplemental report for a material error or omission [1].
12. **Complete an SCI review at least once each calendar year, and send the report to senior management within 30 calendar days and then to the SEC and the board within 60 calendar days after that.** (Internal audit or the objective reviewers; the rule names the senior management recipients) Section 242.1003(b) sets the annual review, with penetration test reviews at least once every three years and assessments of market regulation and surveillance systems on a risk-based frequency of at least once every three years. Section 242.1000 requires the review to be done by objective personnel with appropriate experience and defines senior management for this purpose as the CEO, CTO, CIO, General Counsel and Chief Compliance Officer, or their equivalents [1].
13. **Set standards for designating the members or participants needed to keep markets fair and orderly if the continuity plans are activated, designate them, and test with them at least once every 12 months.** (Head of resilience with market operations) Section 242.1004(a) and (b) require the standards, the designation and mandatory participation in scheduled functional and performance testing of the plans, including backup systems. Section 242.1004(c) requires coordinating the testing on an industry- or sector-wide basis with other SCI entities [1].
14. **Keep Regulation SCI records for the required period, and get a written undertaking from any service bureau that holds them.** (Records management with legal) Section 242.1005(a) applies Rule 17a-1 to SCI SROs; section 242.1005(b) requires other SCI entities to keep the records for at least five years, the first two readily accessible to the SEC. Section 242.1007 requires a written undertaking from a service bureau or other recordkeeping service that prepares or keeps the records [1].

## Sources

1. Electronic Code of Federal Regulations. 17 CFR 242.1000 to 242.1007, Regulation SCI (current text, checked November 14, 2026). <https://www.ecfr.gov/current/title-17/chapter-II/part-242> Checked November 14, 2026.
2. Securities and Exchange Commission, Federal Register (via GovInfo). Withdrawal of Proposed Regulatory Actions (90 FR 25531, June 17, 2025), including the proposed amendments to Regulation SCI published April 14, 2023. <https://www.govinfo.gov/content/pkg/FR-2025-06-17/html/2025-11110.htm> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-sec-regulation-sci-entity-policies-notices-reviews-bcdr-testing>
Publisher: Moraph Insights
