Overview
On Wednesday, December 16, 2015, the Commodity Futures Trading Commission (CFTC or Commission) approved for publication two proposed rules to amend existing regulations addressing cybersecurity. The proposed rules would establish testing obligations and safeguards for the automated systems used by designated contract markets (DCMs), swap execution facilities (SEFs), swap data repositories (SDRs) (the Exchange Proposal), and derivatives clearing organizations (DCOs) (the Clearing Proposal and, together, the Proposals).1
The Commission’s Proposals grant regulated entities with significant deference with respect to the development and implementation of policies and procedures reasonably designed to demonstrate compliance with the new cybersecurity provisions. However, these new regulatory burdens will come with significant operational, technology, and other resource burdens, including ongoing testing and engagement with third-party service providers. Furthermore, the scope of the Proposals for testing may extend further than similar cybersecurity standards established by other federal agencies.
The Commission unanimously approved the Proposals. They were published in the Federal Register on December 23, 2015 and are subject to a 60-day public comment period ending on February 22, 2016.
The Proposals
CFTC staff, in presenting the Proposals for Commission action, stated that the Proposals address cybersecurity and system safeguard requirements for DCMs, SEFs, SDRs, and DCOs. Specifically, the Proposals would enhance and clarify existing rule provisions related to cybersecurity testing and system safeguard risk analysis and oversight by specifying and defining the types of cybersecurity testing that these entities would be required to conduct in order to fulfill their regulatory system safeguard testing obligations. Cybersecurity testing by these entities can strengthen their cyber defenses, mitigate risks to their operations, and maintain their cyber resilience and ability to detect, contain, respond to, and recover from cyberattacks.
The Proposals would require DCMs, SEFs, SDRs, and DCOs to conduct five essential types of cyber testing: (1) vulnerability testing; (2) penetration testing; (3) controls testing; (4) security incident response testing; and (5) enterprise technological risk assessment. The Proposals also would establish minimum testing frequencies and independent contractor testing requirements for DCOs, SDRs, and covered DCMs (i.e., those whose total annual trading volume is five percent or more of the total annual trading volume of DCMs regulated by the CFTC for the year in question). The Exchange Proposal includes an Advance Notice of Proposed Rulemaking, through which the Commission is considering whether, in a future proposal, to apply minimum testing frequency and independent contractor testing requirements to certain SEFs to be defined as “covered SEFs.”
Below is an overview of the five types of systems safeguards and cybersecurity testing proposed by the CFTC:
1 Further detailed information on the Proposals, including fact sheets and statements by Chairman Massad, Commissioner Bowen, and Commissioner Giancarlo, is available at http://www.cftc.gov/PressRoom/PressReleases/pr7293-15.
- Vulnerability testing is the process of scanning a system for weaknesses. CFTC staff explained that vulnerability testing is covered by generally accepted practices and standards, e.g. developed by the National Institute of Standards and Technology. The Proposals would require vulnerability testing by DCMs, SEFs, SDRs, and DCOs at a frequency determined by an appropriate risk analysis. In addition, under the Proposals, DCOs, SDRs, and covered DCMs would be required to use independent contractors for testing during at least two of the quarterly tests each year.
- Penetration testing is the process (external or internal) of simulating an attack on a system to discover and exploit its weaknesses. CFTC staff stated that the Proposals call for DCMs, SEFs, SDRs, and DCOs to conduct penetration testing at a frequency determined by an appropriate risk analysis, and at least annually by DCOs, SDRs, covered DCMs. The annual external penetration test of DCOs, SDRs, and covered DCMs would need to be performed by an independent contractor.
- Controls testing relates to the safeguard or countermeasures used by an entity to protect its automated systems or the confidentiality and integrity of its data and information. CFTC staff stated that, under the Proposals, DCOs, SDRs, and covered DCMs would be required to conduct controls testing no less frequently than every two years. DCOs, SDRs, and covered DCMs would be required to use independent contractors to test each of the defined key controls no less frequently than every two years.
- Security incident response plan testing would mean testing of a registrant’s security incident response plan to determine the plan’s effectiveness, identify its potential weaknesses or deficiencies, enable regular plan updating and improvement, and maintain organizational preparedness and resiliency with respect to security incidents. CFTC staff stated that, at minimum, the Proposals call for DCOs, SDRs, and covered DCMs to have testing performed no less than annually.
- Enterprise technology risk assessment would mean a written assessment that includes an identification and analysis of threats and vulnerability. CFTC staff stated that, at minimum, the Proposals would require DCOs, SDRs, and covered DCMs to perform this function no less frequently than annually.
1 Further detailed information on the Proposals, including fact sheets and statements by Chairman Massad, Commissioner Bowen, and Commissioner Giancarlo, is available at http://www.cftc.gov/PressRoom/PressReleases/pr7293-15.