CFTC system safeguards rules for exchanges, SEFs, clearing houses and swap data repositories, explained
Four CFTC rules set how derivatives exchanges, swap execution facilities, clearing organizations and swap data repositories test their systems and recover from disruption. Some entities have fixed minimum testing frequencies; others test on their own risk analysis.
The Commodity Futures Trading Commission (CFTC) sets system safeguards rules for four kinds of registered entity: derivatives clearing organizations under 17 CFR 39.18 [1], designated contract markets under 17 CFR 38.1051 [2], swap execution facilities under 17 CFR 37.1401 [3] and swap data repositories under 17 CFR 49.24 [4]. Each requires a program of risk analysis and oversight for the entity's operations and automated systems, business continuity and disaster recovery resources, and regular testing of both [1][2][3][4]. Futures commission merchants, swap dealers and major swap participants were the subject of a separate operational resilience proposal, which the Commission later withdrew [6][7].
This explainer covers four parts: what the risk program must address, the testing duties, the recovery targets, and the notice and record duties, followed by the rules' status as checked on November 14, 2026. The figures for each entity type sit side by side in our comparison of CFTC system safeguards testing rules.
What the risk program must cover
For a clearing organization, the program must address six elements: information security, business continuity and disaster recovery, capacity and performance planning, systems operations, systems development and quality assurance, and physical security and environmental controls [1]. The information security element names controls including least privilege, separation of duties, user and device identification and authentication, security awareness training, audit log monitoring, encryption, malware defenses, vulnerability management, penetration testing and incident response [1]. The clearing organization must follow generally accepted standards and industry best practices for the development, operation, reliability, security and capacity of its automated systems [1].
Outsourcing does not move the duty [1]. A clearing organization that contracts out resources keeps complete responsibility for meeting the program and continuity requirements, and must employ people with the expertise to supervise the service provider [1]. Required testing applies to both its own and its outsourced resources and must verify that they work together [1]. The contract market rule groups its program into categories of risk analysis and oversight, beginning with enterprise risk management and governance, which includes board and management oversight of technology and security [2].
Six kinds of testing, and who must do them
The clearing organization rule defines and requires vulnerability testing, external penetration testing, internal penetration testing, controls testing, security incident response plan testing and an enterprise technology risk assessment [1]. Its minimum frequencies are:
- Vulnerability testing: no less frequently than quarterly, including automated vulnerability scanning [1].
- Penetration testing: external and internal tests each no less frequently than annually, with independent contractors conducting the required annual external test [1].
- Controls testing: every control at a frequency set by risk analysis, and key controls no less frequently than every three years, assessed by independent contractors and allowed on a rolling basis [1].
- Incident response plan testing and the enterprise technology risk assessment: each no less frequently than annually [1].
Swap data repositories carry the same floors: quarterly vulnerability testing, annual penetration and incident response plan testing, an annual enterprise technology risk assessment, and independent testing of key controls at least every three years [4].
Contract markets split in two [2]. A covered designated contract market is one whose annual total trading volume in 2015, or in any later calendar year, is five percent or more of the combined volume of all contract markets the Commission regulates [2]. Covered contract markets meet the same minimum frequencies and must use independent contractors for the annual external penetration test and the key controls assessment [2]. Other contract markets, and all swap execution facilities, test at a frequency set by an appropriate risk analysis, and may use independent contractors or employees who do not develop or operate the systems being tested [2][3].
The scope of a clearing organization's testing must be broad enough to find risks that could let an intruder, unauthorized user or insider interfere with operations, degrade its systems, or add to, delete, modify or exfiltrate regulated data [1]. Where a clearing organization must use an independent contractor, that contractor must be independent of both the clearing organization and any outside provider that designs, develops or maintains the resources under test [1]. Senior management and the board receive and review reports of the results at clearing organizations, contract markets and swap execution facilities [1][2][3]. Each of those entities must document the vulnerabilities and deficiencies found, analyze the risk of each, and decide whether to remediate it or accept the risk, remediating in a timely manner when it chooses to fix [1][3].
Recovery targets
A clearing organization's continuity plan, and the resources behind it, must meet a recovery time objective of no later than the next business day after a disruption [1]. Systemically important clearing organizations, and those that have elected subpart C, must be able to resume daily processing, clearing and settlement no later than two hours after any disruption, including a wide-scale disruption [5]. For those entities, the secondary site and the staff needed to meet that target must be outside the relevant area of the resources and people they normally rely on [5].
Contract markets and swap execution facilities have plans and resources that generally should allow trading to resume during the next business day, while those the Commission has determined to be critical financial markets must meet a same-day recovery time objective after a wide-scale disruption [2][3]. Swap data repositories follow the same pattern: the next business day for most, and the same day for one the Commission determines is critical [4]. Contract markets and swap execution facilities must update their continuity plans no less frequently than annually [2][3].
Notices and records
A clearing organization must promptly notify Division of Clearing and Risk staff of any hardware or software malfunction, security incident or targeted threat that materially impairs, or creates a significant likelihood of materially impairing, its automated systems, and of any activation of its continuity plan [1]. It must give timely advance notice of material planned changes to its automated systems and to its risk program [1]. A swap execution facility must promptly report electronic trading halts, material system malfunctions, cyber security incidents or targeted threats, and continuity plan activations, and give advance notice of material planned changes [3].
Clearing organizations keep current copies of their continuity plan, updated at least annually, along with all operational risk assessments and all testing and assessment reports, whether contractors or employees did the work, and provide them to staff promptly on request [1].
Status as checked on November 14, 2026
The eCFR text of 17 CFR 39.18 cites 81 FR 64336, September 19, 2016, as its source [1], and the contract market rule's history ends with an amendment at 82 FR 45434, September 29, 2017 [2]. A proposal published January 24, 2024 at 89 FR 4706 would have required futures commission merchants, swap dealers and major swap participants to maintain an operational resilience framework covering information and technology security, third-party relationships and business continuity [6]. The Commission withdrew that proposal and said it does not intend to issue final rules on it [7]. The withdrawal notice was published at 90 FR 43949 on September 11, 2025, and its dates statement says the proposed rules are withdrawn as of September 8, 2025 [7]. The Unified Agenda entry for the same rulemaking lists the withdrawal under 09/08/2025 with the same citation [8].
On October 13, 2026 the Commission published an advance notice of proposed rulemaking on crypto asset transactions and markets, with comments due December 14, 2026 [9]. Its section on operational risk and system safeguards notes that Core Principle 20 requires a contract market to maintain a program of risk analysis and oversight, and asks what operational risks and related system safeguards requirements may be specific to crypto asset markets and to technologies such as blockchain [9]. The notice seeks comment on the Commission's intent to develop rules; it does not amend the system safeguards sections described above [9].
Where these rules land for technology teams
In our view, the rules turn three routine engineering activities into regulated records: the test calendar, the choice of testers, and the remediation log. The independence test for contractors reaches the firm's own providers, so the same group that builds or runs a clearing organization's systems cannot also be its required independent tester. And because outsourced resources are inside the testing scope, cloud and hosting arrangements belong in the test plan from the start rather than as an exception.
This explainer describes the regulations; it is not legal advice, and registered entities should confirm with counsel how the rules apply to them.
Moraph’s teams help organizations with work like this. See our solutions.
Spotted an error? Tell us and we will check it and correct the explainer where needed.