6 U.S.C. § 651 Definition
In this part, the term “Cybersecurity Advisory Committee” means the advisory committee established under section 665e(a) of this title.
USC Subchapter XVIII
USC Subchapter XVIII
in effect6 U.S.C. § 652 Cybersecurity and Infrastructure Security Agency
(a) Redesignation(1) In generalThe National Protection and Programs Directorate of the Department shall, on and after November 16, 2018, be known as the “Cybersecurity and Infrastructure Security Agency”. (2) ReferencesAny reference to the National Protection and Programs Directorate of the Department in any law, regulation, map, document, record, or other paper of the United States shall be deemed to be a reference to the Cybersecurity and Infrastructure Security Agency of the Department.
(b) Director(1) In generalThe Agency shall be headed by the Director, who shall report to the Secretary. (2) Qualifications(A) In generalThe Director shall be appointed from among individuals who have—(i) extensive knowledge in at least two of the areas specified in subparagraph (B); and (ii) not fewer than five years of demonstrated experience in efforts to foster coordination and collaboration between the Federal Government, the private sector, and other entities on issues related to cybersecurity, infrastructure security, or security risk management. (B) Specified areasThe areas specified in this subparagraph are the following:(i) Cybersecurity. (ii) Infrastructure security. (iii) Security risk management. (3) ReferenceAny reference to an Under Secretary responsible for overseeing critical infrastructure protection, cybersecurity, and any other related program of the Department as described in section 113(a)(1)(H) of this title as in effect on the day before November 16, 2018, in any law, regulation, map, document, record, or other paper of the United States shall be deemed to be a reference to the Director of the Cybersecurity and Infrastructure Security Agency.
(c) ResponsibilitiesThe Director shall—(1) lead cybersecurity and critical infrastructure security programs, operations, and associated policy for the Agency, including national cybersecurity asset response activities; (2) coordinate with Federal entities, including Sector-Specific Agencies, and non-Federal entities, including international entities, to carry out the cybersecurity and critical infrastructure activities of the Agency, as appropriate; (3) carry out the responsibilities of the Secretary to secure Federal information and information systems consistent with law, including subchapter II of chapter 35 of title 44 and the Cybersecurity Act of 2015 (contained in division N of the Consolidated Appropriations Act, 2016 (Public Law 114–113)), including by carrying out a periodic strategic assessment of the related programs and activities of the Agency to ensure such programs and activities contemplate the innovation of information systems and changes in cybersecurity risks and cybersecurity threats; (4) coordinate a national effort to secure and protect against critical infrastructure risks, consistent with subsection (e)(1)(E); (5) upon request, provide analyses, expertise, and other technical assistance to critical infrastructure owners and operators and, where appropriate, provide those analyses, expertise, and other technical assistance in coordination with Sector-Specific Agencies and other Federal departments and agencies; (6) develop and utilize mechanisms for active and frequent collaboration between the Agency and Sector-Specific Agencies to ensure appropriate coordination, situational awareness, and communications with Sector-Specific Agencies; (7) maintain and utilize mechanisms for the regular and ongoing consultation and collaboration among the Divisions of the Agency to further operational coordination, integrated situational awareness, and improved integration across the Agency in accordance with this chapter; (8) develop, coordinate, and implement—(A) comprehensive strategic plans for the activities of the Agency; and (B) risk assessments by and for the Agency; (9) carry out emergency communications responsibilities, in accordance with subchapter XIII; (10) carry out cybersecurity, infrastructure security, and emergency communications stakeholder outreach and engagement and coordinate that outreach and engagement with critical infrastructure Sector-Specific Agencies, as appropriate; (11) provide education, training, and capacity development to Federal and non-Federal entities to enhance the security and resiliency of domestic and global cybersecurity and infrastructure security; (12) appoint a Cybersecurity State Coordinator in each State, as described in section 665c of this title; (13) carry out the duties and authorities relating to the .gov internet domain, as described in section 665 of this title; and (14) carry out such other duties and powers prescribed by law or delegated by the Secretary.
(d) Deputy DirectorThere shall be in the Agency a Deputy Director of the Cybersecurity and Infrastructure Security Agency who shall—(1) assist the Director in the management of the Agency; and (2) report to the Director.
(e) Cybersecurity and infrastructure security authorities of the Secretary(1) In generalThe responsibilities of the Secretary relating to cybersecurity and infrastructure security shall include the following:(A) To access, receive, and analyze law enforcement information, intelligence information, and other information from Federal Government agencies, State, local, tribal, and territorial government agencies, including law enforcement agencies, and private sector entities, and to integrate that information, in support of the mission responsibilities of the Department, in order to—(i) identify and assess the nature and scope of terrorist threats to the homeland; (ii) detect and identify threats of terrorism against the United States; and (iii) understand those threats in light of actual and potential vulnerabilities of the homeland. (B) To carry out comprehensive assessments of the vulnerabilities of the key resources and critical infrastructure of the United States, including the performance of risk assessments to determine the risks posed by particular types of terrorist attacks within the United States, including an assessment of the probability of success of those attacks and the feasibility and potential efficacy of various countermeasures to those attacks. At the discretion of the Secretary, such assessments may be carried out in coordination with Sector-Specific Agencies. (C) To integrate relevant information, analysis, and vulnerability assessments, regardless of whether the information, analysis, or assessments are provided or produced by the Department, in order to make recommendations, including prioritization, for protective and support measures by the Department, other Federal Government agencies, State, local, tribal, and territorial government agencies and authorities, the private sector, and other entities regarding terrorist and other threats to homeland security. (D) To ensure, pursuant to section 122 of this title, the timely and efficient access by the Department to all information necessary to discharge the responsibilities under this subchapter, including obtaining that information from other Federal Government agencies. (E) To develop, in coordination with the Sector-Specific Agencies with available expertise, a comprehensive national plan for securing the key resources and critical infrastructure of the United States, including power production, generation, and distribution systems, information technology and telecommunications systems (including satellites), electronic financial and property record storage and transmission systems, emergency communications systems, and the physical and technological assets that support those systems. (F) To recommend measures necessary to protect the key resources and critical infrastructure of the United States in coordination with other Federal Government agencies, including Sector-Specific Agencies, and in cooperation with State, local, tribal, and territorial government agencies and authorities, the private sector, and other entities. (G) To review, analyze, and make recommendations for improvements to the policies and procedures governing the sharing of information relating to homeland security within the Federal Government and between Federal Government agencies and State, local, tribal, and territorial government agencies and authorities. (H) To disseminate, as appropriate, information analyzed by the Department within the Department to other Federal Government agencies with responsibilities relating to homeland security and to State, local, tribal, and territorial government agencies and private sector entities with those responsibilities in order to assist in the deterrence, prevention, or preemption of, or response to, terrorist attacks against the United States. (I) To consult with State, local, tribal, and territorial government agencies and private sector entities to ensure appropriate exchanges of information, including law enforcement-related information, relating to threats of terrorism against the United States. (J) To ensure that any material received pursuant to this chapter is protected from unauthorized disclosure and handled and used only for the performance of official duties. (K) To request additional information from other Federal Government agencies, State, local, tribal, and territorial government agencies, and the private sector relating to threats of terrorism in the United States, or relating to other areas of responsibility assigned by the Secretary, including the entry into cooperative agreements through the Secretary to obtain such information. (L) To establish and utilize, in conjunction with the Chief Information Officer of the Department, a secure communications and information technology infrastructure, including data-mining and other advanced analytical tools, in order to access, receive, and analyze data and information in furtherance of the responsibilities under this section, and to disseminate information acquired and analyzed by the Department, as appropriate. (M) To coordinate training and other support to the elements and personnel of the Department, other Federal Government agencies, and State, local, tribal, and territorial government agencies that provide information to the Department, or are consumers of information provided by the Department, in order to facilitate the identification and sharing of information revealed in their ordinary duties and the optimal utilization of information received from the Department. (N) To coordinate with Federal, State, local, tribal, and territorial law enforcement agencies, and the private sector, as appropriate. (O) To exercise the authorities and oversight of the functions, personnel, assets, and liabilities of those components transferred to the Department pursuant to section 121(g) of this title. (P) To carry out the functions of the national cybersecurity and communications integration center under section 659 of this title. (Q) To carry out the requirements of the Chemical Facility Anti-Terrorism Standards Program established under subchapter XVI and the secure handling of ammonium nitrate program established under part J of subchapter VIII, or any successor programs. (R) To encourage and build cybersecurity awareness and competency across the United States and to develop, attract, and retain the cybersecurity workforce necessary for the cybersecurity related missions of the Department, including by—(i) overseeing elementary and secondary cybersecurity education and awareness related programs at the Agency; (ii) leading efforts to develop, attract, and retain the cybersecurity workforce necessary for the cybersecurity related missions of the Department; (iii) encouraging and building cybersecurity awareness and competency across the United States; and (iv) carrying out cybersecurity related workforce development activities, including through—(I) increasing the pipeline of future cybersecurity professionals through programs focused on elementary and secondary education, postsecondary education, and workforce development; and (II) building awareness of and competency in cybersecurity across the civilian Federal Government workforce. (2) ReallocationThe Secretary may reallocate within the Agency the functions specified in sections 653(b) and 654(b) of this title, consistent with the responsibilities provided in paragraph (1), upon certifying to and briefing the appropriate congressional committees, and making available to the public, at least 60 days prior to the reallocation that the reallocation is necessary for carrying out the activities of the Agency. (3) Staff(A) In generalThe Secretary shall provide the Agency with a staff of analysts having appropriate expertise and experience to assist the Agency in discharging the responsibilities of the Agency under this section. (B) Private sector analystsAnalysts under this subsection may include analysts from the private sector. (C) Security clearancesAnalysts under this subsection shall possess security clearances appropriate for their work under this section. (4) Detail of personnel(A) In generalIn order to assist the Agency in discharging the responsibilities of the Agency under this section, personnel of the Federal agencies described in subparagraph (B) may be detailed to the Agency for the performance of analytic functions and related duties. (B) AgenciesThe Federal agencies described in this subparagraph are—(i) the Department of State; (ii) the Central Intelligence Agency; (iii) the Federal Bureau of Investigation; (iv) the National Security Agency; (v) the National Geospatial-Intelligence Agency; (vi) the Defense Intelligence Agency; (vii) Sector-Specific Agencies; and (viii) any other agency of the Federal Government that the President considers appropriate. (C) Interagency agreementsThe Secretary and the head of a Federal agency described in subparagraph (B) may enter into agreements for the purpose of detailing personnel under this paragraph. (D) BasisThe detail of personnel under this paragraph may be on a reimbursable or non-reimbursable basis.
(f) CompositionThe Agency shall be composed of the following divisions:(1) The Cybersecurity Division, headed by an Executive Assistant Director. (2) The Infrastructure Security Division, headed by an Executive Assistant Director. (3) The Emergency Communications Division under subchapter XIII, headed by an Executive Assistant Director.
(g) Co-location(1) In generalTo the maximum extent practicable, the Director shall examine the establishment of central locations in geographical regions with a significant Agency presence. (2) CoordinationWhen establishing the central locations described in paragraph (1), the Director shall coordinate with component heads and the Under Secretary for Management to co-locate or partner on any new real property leases, renewing any occupancy agreements for existing leases, or agreeing to extend or newly occupy any Federal space or new construction.
(h) Privacy(1) In generalThere shall be a Privacy Officer of the Agency with primary responsibility for privacy policy and compliance for the Agency. (2) ResponsibilitiesThe responsibilities of the Privacy Officer of the Agency shall include—(A) assuring that the use of technologies by the Agency sustain, and do not erode, privacy protections relating to the use, collection, and disclosure of personal information; (B) assuring that personal information contained in systems of records of the Agency is handled in full compliance as specified in section 552a of title 5 (commonly known as the “Privacy Act of 1974”); (C) evaluating legislative and regulatory proposals involving collection, use, and disclosure of personal information by the Agency; and (D) conducting a privacy impact assessment of proposed rules of the Agency on the privacy of personal information, including the type of personal information collected and the number of people affected.
(i) SavingsNothing in this subchapter may be construed as affecting in any manner the authority, existing on the day before November 16, 2018, of any other component of the Department or any other Federal department or agency, including the authority provided to the Sector Risk Management Agency specified in section 61003(c) of division F of the Fixing America’s Surface Transportation Act (6 U.S.C. 121 note; Public Law 114–94).
6 U.S.C. § 652a Sector Risk Management Agencies
(a) DefinitionsIn this section:(1) Appropriate congressional committeesThe term “appropriate congressional committees” means—(A) the Committee on Homeland Security and the Committee on Armed Services in the House of Representatives; and (B) the Committee on Homeland Security and Governmental Affairs and the Committee on Armed Services in the Senate. (2) Critical infrastructureThe term “critical infrastructure” has the meaning given that term in section 5195c(e) of title 42. (3) DepartmentThe term “Department” means the Department of Homeland Security. (4) DirectorThe term “Director” means the Director of the Cybersecurity and Infrastructure Security Agency of the Department. (5) SecretaryThe term “Secretary” means the Secretary of Homeland Security. (7) 11 So in original. Probably should be “(6)”. Sector Risk Management AgencyThe term “Sector Risk Management Agency” has the meaning given the term in section 650 of this title.
(b) Critical infrastructure sector designation(1) Initial reviewNot later than 180 days after January 1, 2021, the Secretary, in consultation with the heads of Sector Risk Management Agencies, shall—(A) review the current framework for securing critical infrastructure, as described in section 652(c)(4) of this title and Presidential Policy Directive 21; and (B) submit to the President and appropriate congressional committees a report that includes—(i) information relating to—(I) the analysis framework or methodology used to—(aa) evaluate the current framework for securing critical infrastructure referred to in subparagraph (A); and (bb) develop recommendations to—(AA) revise the current list of critical infrastructure sectors designated pursuant to Presidential Policy Directive 21, any successor or related document, or policy; or (BB) identify and designate any subsectors of such sectors; (II) the data, metrics, and other information used to develop the recommendations required under clause (ii); and (ii) recommendations relating to—(I) revising—(aa) the current framework for securing critical infrastructure referred to in subparagraph (A); (bb) the current list of critical infrastructure sectors designated pursuant to Presidential Policy Directive 21, any successor or related document, or policy; or (cc) the identification and designation of any subsectors of such sectors; and (II) any revisions to the list of designated Federal departments or agencies that serve as the Sector Risk Management Agency for a sector or subsector of such section, necessary to comply with paragraph (3)(B). (2) Periodic evaluation by the SecretaryAt least once every five years, the Secretary, in consultation with the Director and the heads of Sector Risk Management Agencies, shall—(A) evaluate the current list of designated critical infrastructure sectors and subsectors of such sectors and the appropriateness of Sector Risk Management Agency designations, as set forth in Presidential Policy Directive 21, any successor or related document, or policy; and (B) recommend, as appropriate, to the President—(i) revisions to the current list of designated critical infrastructure sectors or subsectors of such sectors; and (ii) revisions to the designation of any Federal department or agency designated as the Sector Risk Management Agency for a sector or subsector of such sector. (3) Review and revision by the PresidentNot later than 180 days after the Secretary submits a recommendation pursuant to paragraph (1) or (2), the President shall—(A) review the recommendation and revise, as appropriate, the designation of a critical infrastructure sector or subsector or the designation of a Sector Risk Management Agency; and (B) submit to the appropriate congressional committees, the Majority and Minority Leaders of the Senate, and the Speaker and Minority Leader of the House of Representatives, a report that includes—(i) an explanation with respect to the basis for accepting or rejecting the recommendations of the Secretary; and (ii) information relating to the analysis framework, methodology, metrics, and data used to—(I) evaluate the current framework for securing critical infrastructure referred to in paragraph (1)(A); and (II) develop—(aa) recommendations to revise—(AA) the list of critical infrastructure sectors designated pursuant to Presidential Policy Directive 21, any successor or related document, or policy; or (BB) the designation of any subsectors of such sectors; and (bb) the recommendations of the Secretary. (4) PublicationAny designation of critical infrastructure sectors shall be published in the Federal Register.
(c) Sector Risk Management Agencies(1) Omitted (2) Omitted (3) ReferencesAny reference to a Sector Specific Agency (including any permutations or conjugations thereof) in any law, regulation, map, document, record, or other paper of the United States shall be deemed to—(A) be a reference to the Sector Risk Management Agency of the relevant critical infrastructure sector; and (B) have the meaning given such term in section 650 of this title. (4) Omitted
(d) Report and auditingNot later than two years after January 1, 2021 and every four years thereafter for 12 years, the Comptroller General of the United States shall submit to the Committee on Homeland Security of the House of Representatives and the Committee on Homeland Security and Governmental Affairs of the Senate a report on the effectiveness of Sector Risk Management Agencies in carrying out their responsibilities under section 665d of this title.
6 U.S.C. § 653 Cybersecurity Division
(a) Establishment(1) In generalThere is established in the Agency a Cybersecurity Division. (2) Executive Assistant DirectorThe Cybersecurity Division shall be headed by an Executive Assistant Director for Cybersecurity (in this section referred to as “the Executive Assistant Director”), who shall—(A) be at the level of Assistant Secretary within the Department; (B) be appointed by the President without the advice and consent of the Senate; and (C) report to the Director. (3) ReferenceAny reference to the Assistant Secretary for Cybersecurity and Communications or Assistant Director for Cybersecurity in any law, regulation, map, document, record, or other paper of the United States shall be deemed to be a reference to the Executive Assistant Director for Cybersecurity.
(b) FunctionsThe Executive Assistant Director shall—(1) direct the cybersecurity efforts of the Agency; (2) carry out activities, at the direction of the Director, related to the security of Federal information and Federal information systems consistent with law, including subchapter II of chapter 35 of title 44 and the Cybersecurity Act of 2015 (contained in division N of the Consolidated Appropriations Act, 2016 (Public Law 114–113)); (3) fully participate in the mechanisms required under section 652(c)(7) of this title; and (4) carry out such other duties and powers as prescribed by the Director.
6 U.S.C. § 654 Infrastructure Security Division
(a) Establishment(1) In generalThere is established in the Agency an Infrastructure Security Division. (2) Executive Assistant DirectorThe Infrastructure Security Division shall be headed by an Executive Assistant Director for Infrastructure Security (in this section referred to as “the Executive Assistant Director”), who shall—(A) be at the level of Assistant Secretary within the Department; (B) be appointed by the President without the advice and consent of the Senate; and (C) report to the Director. (3) ReferenceAny reference to the Assistant Secretary for Infrastructure Protection or Assistant Director for Infrastructure Security in any law, regulation, map, document, record, or other paper of the United States shall be deemed to be a reference to the Executive Assistant Director for Infrastructure Security.
(b) FunctionsThe Executive Assistant Director shall—(1) direct the critical infrastructure security efforts of the Agency; (2) carry out, at the direction of the Director, the Chemical Facilities Anti-Terrorism Standards Program established under subchapter XVI and the secure handling of ammonium nitrate program established under part J of subchapter VIII, or any successor programs; (3) fully participate in the mechanisms required under section 652(c)(7) of this title; and (4) carry out such other duties and powers as prescribed by the Director.
6 U.S.C. § 655 Enhancement of Federal and non-Federal cybersecurity
In carrying out the responsibilities under section 652 of this title, the Director of the Cybersecurity and Infrastructure Security Agency shall—
(1) as appropriate, provide to State and local government entities, and upon request to private entities that own or operate critical information systems—(A) analysis and warnings related to threats to, and vulnerabilities of, critical information systems; and (B) in coordination with the Under Secretary for Emergency Preparedness and Response, crisis management support in response to threats to, or attacks on, critical information systems;
(2) as appropriate, provide technical assistance, upon request, to the private sector and other government entities, in coordination with the Under Secretary for Emergency Preparedness and Response, with respect to emergency recovery plans to respond to major failures of critical information systems; and
(3) fulfill the responsibilities of the Secretary to protect Federal information systems under subchapter II of chapter 35 of title 44.
6 U.S.C. § 656 NET Guard
The Director of the Cybersecurity and Infrastructure Security Agency may establish a national technology guard, to be known as “NET Guard”, comprised of local teams of volunteers with expertise in relevant areas of science and technology, to assist local communities to respond and recover from attacks on information systems and communications networks.
6 U.S.C. § 657 Cyber Security Enhancement Act of 2002
(a) Short titleThis section may be cited as the “Cyber Security Enhancement Act of 2002”.
(b) Amendment of sentencing guidelines relating to certain computer crimes(1) Directive to the United States Sentencing CommissionPursuant to its authority under section 994(p) of title 28 and in accordance with this subsection, the United States Sentencing Commission shall review and, if appropriate, amend its guidelines and its policy statements applicable to persons convicted of an offense under section 1030 of title 18. (2) RequirementsIn carrying out this subsection, the Sentencing Commission shall—(A) ensure that the sentencing guidelines and policy statements reflect the serious nature of the offenses described in paragraph (1), the growing incidence of such offenses, and the need for an effective deterrent and appropriate punishment to prevent such offenses; (B) consider the following factors and the extent to which the guidelines may or may not account for them—(i) the potential and actual loss resulting from the offense; (ii) the level of sophistication and planning involved in the offense; (iii) whether the offense was committed for purposes of commercial advantage or private financial benefit; (iv) whether the defendant acted with malicious intent to cause harm in committing the offense; (v) the extent to which the offense violated the privacy rights of individuals harmed; (vi) whether the offense involved a computer used by the government in furtherance of national defense, national security, or the administration of justice; (vii) whether the violation was intended to or had the effect of significantly interfering with or disrupting a critical infrastructure; and (viii) whether the violation was intended to or had the effect of creating a threat to public health or safety, or injury to any person; (C) assure reasonable consistency with other relevant directives and with other sentencing guidelines; (D) account for any additional aggravating or mitigating circumstances that might justify exceptions to the generally applicable sentencing ranges; (E) make any necessary conforming changes to the sentencing guidelines; and (F) assure that the guidelines adequately meet the purposes of sentencing as set forth in section 3553(a)(2) of title 18.
(c) Study and report on computer crimesNot later than May 1, 2003, the United States Sentencing Commission shall submit a brief report to Congress that explains any actions taken by the Sentencing Commission in response to this section and includes any recommendations the Commission may have regarding statutory penalties for offenses under section 1030 of title 18.
(d) Emergency disclosure exception(1) Omitted (2) Reporting of disclosuresA government entity that receives a disclosure under section 2702(b) of title 18 shall file, not later than 90 days after such disclosure, a report to the Attorney General stating the paragraph of that section under which the disclosure was made, the date of the disclosure, the entity to which the disclosure was made, the number of customers or subscribers to whom the information disclosed pertained, and the number of communications, if any, that were disclosed. The Attorney General shall publish all such reports into a single report to be submitted to Congress 1 year after November 25, 2002.
6 U.S.C. § 658 Cybersecurity recruitment and retention
(a) DefinitionsIn this section:(1) Appropriate committees of CongressThe term “appropriate committees of Congress” means the Committee on Homeland Security and Governmental Affairs and the Committee on Appropriations of the Senate and the Committee on Homeland Security and the Committee on Appropriations of the House of Representatives. (2) Collective bargaining agreementThe term “collective bargaining agreement” has the meaning given that term in section 7103(a)(8) of title 5. (3) Excepted serviceThe term “excepted service” has the meaning given that term in section 2103 of title 5. (4) Preference eligibleThe term “preference eligible” has the meaning given that term in section 2108 of title 5. (5) Qualified positionThe term “qualified position” means a position, designated by the Secretary for the purpose of this section, in which the incumbent performs, manages, or supervises functions that execute the responsibilities of the Department relating to cybersecurity. (6) Senior Executive ServiceThe term “Senior Executive Service” has the meaning given that term in section 2101a of title 5.
(b) General authority(1) Establish positions, appoint personnel, and fix rates of pay(A) General authorityThe Secretary may—(i) establish, as positions in the excepted service, such qualified positions in the Department as the Secretary determines necessary to carry out the responsibilities of the Department relating to cybersecurity, including positions formerly identified as—(I) senior level positions designated under section 5376 of title 5; and (II) positions in the Senior Executive Service; (ii) appoint an individual to a qualified position (after taking into consideration the availability of preference eligibles for appointment to the position); and (iii) subject to the requirements of paragraphs (2) and (3), fix the compensation of an individual for service in a qualified position. (B) Construction with other lawsThe authority of the Secretary under this subsection applies without regard to the provisions of any other law relating to the appointment, number, classification, or compensation of employees. (2) Basic pay(A) Authority to fix rates of basic payIn accordance with this section, the Secretary shall fix the rates of basic pay for any qualified position established under paragraph (1) in relation to the rates of pay provided for employees in comparable positions in the Department of Defense and subject to the same limitations on maximum rates of pay established for such employees by law or regulation. (B) Prevailing rate systemsThe Secretary may, consistent with section 5341 of title 5, adopt such provisions of that title as provide for prevailing rate systems of basic pay and may apply those provisions to qualified positions for employees in or under which the Department may employ individuals described by section 5342(a)(2)(A) of that title. (3) Additional compensation, incentives, and allowances(A) Additional compensation based on title 5 authoritiesThe Secretary may provide employees in qualified positions compensation (in addition to basic pay), including benefits, incentives, and allowances, consistent with, and not in excess of the level authorized for, comparable positions authorized by title 5. (B) Allowances in nonforeign areasAn employee in a qualified position whose rate of basic pay is fixed under paragraph (2)(A) shall be eligible for an allowance under section 5941 of title 5, on the same basis and to the same extent as if the employee was an employee covered by such section 5941, including eligibility conditions, allowance rates, and all other terms and conditions in law or regulation. (4) Plan for execution of authoritiesNot later than 120 days after December 18, 2014, the Secretary shall submit a report to the appropriate committees of Congress with a plan for the use of the authorities provided under this subsection. (5) Collective bargaining agreementsNothing in paragraph (1) may be construed to impair the continued effectiveness of a collective bargaining agreement with respect to an office, component, subcomponent, or equivalent of the Department that is a successor to an office, component, subcomponent, or equivalent of the Department covered by the agreement before the succession. (6) Required regulationsThe Secretary, in coordination with the Director of the Office of Personnel Management, shall prescribe regulations for the administration of this section.
(c) Annual reportNot later than 1 year after December 18, 2014, and every year thereafter for 4 years, the Secretary shall submit to the appropriate committees of Congress a detailed report that—(1) discusses the process used by the Secretary in accepting applications, assessing candidates, ensuring adherence to veterans’ preference, and selecting applicants for vacancies to be filled by an individual for a qualified position; (2) describes—(A) how the Secretary plans to fulfill the critical need of the Department to recruit and retain employees in qualified positions; (B) the measures that will be used to measure progress; and (C) any actions taken during the reporting period to fulfill such critical need; (3) discusses how the planning and actions taken under paragraph (2) are integrated into the strategic workforce planning of the Department; (4) provides metrics on actions occurring during the reporting period, including—(A) the number of employees in qualified positions hired by occupation and grade and level or pay band; (B) the placement of employees in qualified positions by directorate and office within the Department; (C) the total number of veterans hired; (D) the number of separations of employees in qualified positions by occupation and grade and level or pay band; (E) the number of retirements of employees in qualified positions by occupation and grade and level or pay band; and (F) the number and amounts of recruitment, relocation, and retention incentives paid to employees in qualified positions by occupation and grade and level or pay band; and (5) describes the training provided to supervisors of employees in qualified positions at the Department on the use of the new authorities.
(d) Three-year probationary periodThe probationary period for all employees hired under the authority established in this section shall be 3 years.
(e) Incumbents of existing competitive service positions(1) In generalAn individual serving in a position on December 18, 2014, that is selected to be converted to a position in the excepted service under this section shall have the right to refuse such conversion. (2) Subsequent conversionAfter the date on which an individual who refuses a conversion under paragraph (1) stops serving in the position selected to be converted, the position may be converted to a position in the excepted service.
(f) Study and reportNot later than 120 days after December 18, 2014, the National Protection and Programs Directorate shall submit a report regarding the availability of, and benefits (including cost savings and security) of using, cybersecurity personnel and facilities outside of the National Capital Region (as defined in section 2674 of title 10) to serve the Federal and national need to—(1) the Subcommittee on Homeland Security of the Committee on Appropriations and the Committee on Homeland Security and Governmental Affairs of the Senate; and (2) the Subcommittee on Homeland Security of the Committee on Appropriations and the Committee on Homeland Security of the House of Representatives.
6 U.S.C. § 659 National cybersecurity and communications integration center
(a) DefinitionThe term “cybersecurity vulnerability” has the meaning given the term “security vulnerability” in section 650 of this title.
(b) CenterThere is in the Department a national cybersecurity and communications integration center (referred to in this section as the “Center”) to carry out certain responsibilities of the Director. The Center shall be located in the Cybersecurity and Infrastructure Security Agency. The head of the Center shall report to the Executive Assistant Director for Cybersecurity.
(c) FunctionsThe cybersecurity functions of the Center shall include—(1) being a Federal civilian interface for the multi-directional and cross-sector sharing of information related to cyber threat indicators, defensive measures, cybersecurity risks, incidents, analysis, and warnings for Federal and non-Federal entities, including the implementation of title I of the Cybersecurity Act of 2015 [6 U.S.C. 1501 et seq.]; (2) providing shared situational awareness to enable real-time, integrated, and operational actions across the Federal Government and non-Federal entities to address cybersecurity risks and incidents to Federal and non-Federal entities; (3) coordinating the sharing of information related to cyber threat indicators, defensive measures, cybersecurity risks, and incidents across the Federal Government; (4) facilitating cross-sector coordination to address cybersecurity risks and incidents, including cybersecurity risks and incidents that may be related or could have consequential impacts across multiple sectors; (5)(A) conducting integration and analysis, including cross-sector integration and analysis, of cyber threat indicators, defensive measures, cybersecurity risks, and incidents; (B) sharing mitigation protocols to counter cybersecurity vulnerabilities pursuant to subsection (n), as appropriate; and (C) sharing the analysis conducted under subparagraph (A) and mitigation protocols to counter cybersecurity vulnerabilities in accordance with subparagraph (B), as appropriate, with Federal and non-Federal entities; (6) upon request, providing operational and timely technical assistance, risk management support, and incident response capabilities to Federal and non-Federal entities with respect to cyber threat indicators, defensive measures, cybersecurity risks, and incidents, which may include attribution, mitigation, and remediation, which may take the form of continuous monitoring and detection of cybersecurity risks to critical infrastructure entities that own or operate industrial control systems that support national critical functions; (7) providing information and recommendations on security and resilience measures to Federal and non-Federal entities, including information and recommendations to—(A) facilitate information security; (B) strengthen information systems against cybersecurity risks and incidents; and (C) share cyber threat indicators and defensive measures; (8) engaging with international partners, in consultation with other appropriate agencies, to—(A) collaborate on cyber threat indicators, defensive measures, and information related to cybersecurity risks and incidents; and (B) enhance the security and resilience of global cybersecurity; (9) sharing cyber threat indicators, defensive measures, mitigation protocols to counter cybersecurity vulnerabilities, as appropriate, and other information related to cybersecurity risks and incidents with Federal and non-Federal entities, including across sectors of critical infrastructure and with State and major urban area fusion centers, as appropriate; (10) participating, as appropriate, in national exercises run by the Department; (11) in coordination with the Emergency Communications Division of the Department, assessing and evaluating consequence, vulnerability, and threat information regarding cyber incidents to public safety communications to help facilitate continuous improvements to the security and resiliency of such communications; (12) detecting, identifying, and receiving information for a cybersecurity purpose about security vulnerabilities relating to critical infrastructure in information systems and devices; and (13) receiving, aggregating, and analyzing reports related to covered cyber incidents (as defined in section 681 of this title) submitted by covered entities (as defined in section 681 of this title) and reports related to ransom payments (as defined in section 681 of this title) submitted by covered entities (as defined in section 681 of this title) in furtherance of the activities specified in sections 652(e), 653, and 681a of this title, this subsection, and any other authorized activity of the Director, to enhance the situational awareness of cybersecurity threats across critical infrastructure sectors.
(d) Composition(1) In generalThe Center shall be composed of—(A) appropriate representatives of Federal entities, such as—(i) sector-specific agencies; (ii) civilian and law enforcement agencies; and (iii) elements of the intelligence community; (B) appropriate representatives of non-Federal entities, such as—(i) State, local, and tribal governments; (ii) Information Sharing and Analysis Organizations, including information sharing and analysis centers; (iii) owners and operators of critical information systems; and (iv) private entities, including cybersecurity specialists; (C) components within the Center that carry out cybersecurity and communications activities; (D) a designated Federal official for operational coordination with and across each sector; (E) an entity that collaborates with State and local governments, including an entity that collaborates with election officials, on cybersecurity risks and incidents, and has entered into a voluntary information sharing relationship with the Center; and (F) other appropriate representatives or entities, as determined by the Secretary. (2) IncidentsIn the event of an incident, during exigent circumstances the Secretary may grant a Federal or non-Federal entity immediate temporary access to the Center.
(e) PrinciplesIn carrying out the functions under subsection (c), the Center shall ensure—(1) to the extent practicable, that—(A) timely, actionable, and relevant cyber threat indicators, defensive measures, and information related to cybersecurity risks, incidents, and analysis is shared; (B) when appropriate, cyber threat indicators, defensive measures, and information related to cybersecurity risks, incidents, and analysis is integrated with other relevant information and tailored to the specific characteristics of a sector; (C) activities are prioritized and conducted based on the level of risk; (D) industry sector-specific, academic, and national laboratory expertise is sought and receives appropriate consideration; (E) continuous, collaborative, and inclusive coordination occurs—(i) across sectors; and (ii) with—(I) sector coordinating councils; (II) Information Sharing and Analysis Organizations; and (III) other appropriate non-Federal partners; (F) as appropriate, the Center works to develop and use mechanisms for sharing information related to cyber threat indicators, defensive measures, cybersecurity risks, and incidents that are technology-neutral, interoperable, real-time, cost-effective, and resilient; (G) the Center works with other agencies to reduce unnecessarily duplicative sharing of information related to cyber threat indicators, defensive measures, cybersecurity risks, and incidents; (H) the Center designates an agency contact for non-Federal entities; and (I) activities of the Center address the security of both information technology and operational technology, including industrial control systems; (2) that information related to cyber threat indicators, defensive measures, cybersecurity risks, and incidents is appropriately safeguarded against unauthorized access or disclosure; and (3) that activities conducted by the Center comply with all policies, regulations, and laws that protect the privacy and civil liberties of United States persons, including by working with the Privacy Officer appointed under section 142 of this title to ensure that the Center follows the policies and procedures specified in subsections (b) and (d)(5)(C) of section 105 of the Cybersecurity Act of 2015 [6 U.S.C. 1504].
(f) Cyber hunt and incident response teams(1) In generalThe Center shall maintain cyber hunt and incident response teams for the purpose of leading Federal asset response activities and providing timely technical assistance to Federal and non-Federal entities, including across all critical infrastructure sectors, regarding actual or potential security incidents, as appropriate and upon request, including—(A) assistance to asset owners and operators in restoring services following a cyber incident; (B) identification and analysis of cybersecurity risk and unauthorized cyber activity; (C) mitigation strategies to prevent, deter, and protect against cybersecurity risks; (D) recommendations to asset owners and operators for improving overall network and control systems security to lower cybersecurity risks, and other recommendations, as appropriate; and (E) such other capabilities as the Secretary determines appropriate. (2) Associated metricsThe Center shall—(A) define the goals and desired outcomes for each cyber hunt and incident response team; and (B) develop metrics—(i) to measure the effectiveness and efficiency of each cyber hunt and incident response team in achieving the goals and desired outcomes defined under subparagraph (A); and (ii) that—(I) are quantifiable and actionable; and (II) the Center shall use to improve the effectiveness and accountability of, and service delivery by, cyber hunt and incident response teams. (3) Cybersecurity specialistsAfter notice to, and with the approval of, the entity requesting action by or technical assistance from the Center, the Secretary may include cybersecurity specialists from the private sector on a cyber hunt and incident response team.
(g) No right or benefit(1) In generalThe provision of assistance or information to, and inclusion in the Center, or any team or activity of the Center, of, governmental or private entities under this section shall be at the sole and unreviewable discretion of the Director. (2) Certain assistance or informationThe provision of certain assistance or information to, or inclusion in the Center, or any team or activity of the Center, of, one governmental or private entity pursuant to this section shall not create a right or benefit, substantive or procedural, to similar assistance or information for any other governmental or private entity.
(h) Automated information sharing(1) In generalThe Director, in coordination with industry and other stakeholders, shall develop capabilities making use of existing information technology industry standards and best practices, as appropriate, that support and rapidly advance the development, adoption, and implementation of automated mechanisms for the sharing of cyber threat indicators and defensive measures in accordance with title I of the Cybersecurity Act of 2015 [6 U.S.C. 1501 et seq.]. (2) Annual reportThe Director shall submit to the Committee on Homeland Security and Governmental Affairs of the Senate and the Committee on Homeland Security of the House of Representatives an annual report on the status and progress of the development of the capabilities described in paragraph (1). Such reports shall be required until such capabilities are fully implemented.
(i) Voluntary information sharing procedures(1) Procedures(A) In generalThe Center may enter into a voluntary information sharing relationship with any consenting non-Federal entity for the sharing of cyber threat indicators and defensive measures for cybersecurity purposes in accordance with this section. Nothing in this subsection may be construed to require any non-Federal entity to enter into any such information sharing relationship with the Center or any other entity. The Center may terminate a voluntary information sharing relationship under this subsection, at the sole and unreviewable discretion of the Secretary, acting through the Director, for any reason, including if the Center determines that the non-Federal entity with which the Center has entered into such a relationship has violated the terms of this subsection. (B) National securityThe Secretary may decline to enter into a voluntary information sharing relationship under this subsection, at the sole and unreviewable discretion of the Secretary, acting through the Director, for any reason, including if the Secretary determines that such is appropriate for national security. (2) Voluntary information sharing relationshipsA voluntary information sharing relationship under this subsection may be characterized as an agreement described in this paragraph.(A) Standard agreementFor the use of a non-Federal entity, the Center shall make available a standard agreement, consistent with this section, on the Department’s website. (B) Negotiated agreementAt the request of a non-Federal entity, and if determined appropriate by the Center, at the sole and unreviewable discretion of the Secretary, acting through the Director, the Department shall negotiate a non-standard agreement, consistent with this section. (C) Existing agreementsAn agreement between the Center and a non-Federal entity that is entered into before December 18, 2015, or such an agreement that is in effect before such date, shall be deemed in compliance with the requirements of this subsection, notwithstanding any other provision or requirement of this subsection. An agreement under this subsection shall include the relevant privacy protections as in effect under the Cooperative Research and Development Agreement for Cybersecurity Information Sharing and Collaboration, as of December 31, 2014. Nothing in this subsection may be construed to require a non-Federal entity to enter into either a standard or negotiated agreement to be in compliance with this subsection.
(j) Direct reportingThe Secretary shall develop policies and procedures for direct reporting to the Secretary by the Director of the Center regarding significant cybersecurity risks and incidents.
(k) Reports on international cooperationNot later than 180 days after December 18, 2015, and periodically thereafter, the Secretary of Homeland Security shall submit to the Committee on Homeland Security and Governmental Affairs of the Senate and the Committee on Homeland Security of the House of Representatives a report on the range of efforts underway to bolster cybersecurity collaboration with relevant international partners in accordance with subsection (c)(8).
(l) OutreachNot later than 60 days after December 18, 2015, the Secretary, acting through the Director, shall—(1) disseminate to the public information about how to voluntarily share cyber threat indicators and defensive measures with the Center; and (2) enhance outreach to critical infrastructure owners and operators for purposes of such sharing.
(m) Cybersecurity outreach(1) In generalThe Secretary may leverage small business development centers to provide assistance to small business concerns by disseminating information on cyber threat indicators, defense measures, cybersecurity risks, incidents, analyses, and warnings to help small business concerns in developing or enhancing cybersecurity infrastructure, awareness of cyber threat indicators, and cyber training programs for employees. (2) DefinitionsFor purposes of this subsection, the terms “small business concern” and “small business development center” have the meaning given such terms, respectively, under section 632 of title 15.
(n) Coordinated vulnerability disclosureThe Secretary, in coordination with industry and other stakeholders, may develop and adhere to Department policies and procedures for coordinating vulnerability disclosures.
(o) Protocols to counter certain cybersecurity vulnerabilitiesThe Director may, as appropriate, identify, develop, and disseminate actionable protocols to mitigate cybersecurity vulnerabilities to information systems and industrial control systems, including in circumstances in which such vulnerabilities exist because software or hardware is no longer supported by a vendor.
(p) Subpoena authority(1) DefinitionIn this subsection, the term “covered device or system”—(A) means a device or system commonly used to perform industrial, commercial, scientific, or governmental functions or processes that relate to critical infrastructure, including operational and industrial control systems, distributed control systems, and programmable logic controllers; and (B) does not include personal devices and systems, such as consumer mobile devices, home computers, residential wireless routers, or residential internet enabled consumer devices. (2) Authority(A) In generalIf the Director identifies a system connected to the internet with a specific security vulnerability and has reason to believe such security vulnerability relates to critical infrastructure and affects a covered device or system, and the Director is unable to identify the entity at risk that owns or operates such covered device or system, the Director may issue a subpoena for the production of information necessary to identify and notify such entity at risk, in order to carry out a function authorized under subsection (c)(12). (B) Limit on informationA subpoena issued pursuant to subparagraph (A) may seek information—(i) only in the categories set forth in subparagraphs (A), (B), (D), and (E) of section 2703(c)(2) of title 18; and (ii) for not more than 20 covered devices or systems. (C) Liability protections for disclosing providersThe provisions of section 2703(e) of title 18, shall apply to any subpoena issued pursuant to subparagraph (A). (3) Coordination(A) In generalIf the Director exercises the subpoena authority under this subsection, and in the interest of avoiding interference with ongoing law enforcement investigations, the Director shall coordinate the issuance of any such subpoena with the Department of Justice, including the Federal Bureau of Investigation, pursuant to interagency procedures which the Director, in coordination with the Attorney General, shall develop not later than 60 days after January 1, 2021. (B) ContentsThe inter-agency procedures developed under this paragraph shall provide that a subpoena issued by the Director under this subsection shall be—(i) issued to carry out a function described in subsection (c)(12); and (ii) subject to the limitations specified in this subsection. (4) NoncomplianceIf any person, partnership, corporation, association, or entity fails to comply with any duly served subpoena issued pursuant to this subsection, the Director may request that the Attorney General seek enforcement of such subpoena in any judicial district in which such person, partnership, corporation, association, or entity resides, is found, or transacts business. (5) NoticeNot later than seven days after the date on which the Director receives information obtained through a subpoena issued pursuant to this subsection, the Director shall notify any entity identified by information obtained pursuant to such subpoena regarding such subpoena and the identified vulnerability. (6) Authentication(A) In generalAny subpoena issued pursuant to this subsection shall be authenticated with a cryptographic digital signature of an authorized representative of the Agency, or other comparable successor technology, that allows the Agency to demonstrate that such subpoena was issued by the Agency and has not been altered or modified since such issuance. (B) Invalid if not authenticatedAny subpoena issued pursuant to this subsection that is not authenticated in accordance with subparagraph (A) shall not be considered to be valid by the recipient of such subpoena. (7) ProceduresNot later than 90 days after January 1, 2021, the Director shall establish internal procedures and associated training, applicable to employees and operations of the Agency, regarding subpoenas issued pursuant to this subsection, which shall address the following:(A) The protection of and restriction on dissemination of nonpublic information obtained through such a subpoena, including a requirement that the Agency not disseminate nonpublic information obtained through such a subpoena that identifies the party that is subject to such subpoena or the entity at risk identified by information obtained, except that the Agency may share the nonpublic information with the Department of Justice for the purpose of enforcing such subpoena in accordance with paragraph (4), and may share with a Federal agency the nonpublic information of the entity at risk if—(i) the Agency identifies or is notified of a cybersecurity incident involving such entity, which relates to the vulnerability which led to the issuance of such subpoena; (ii) the Director determines that sharing the nonpublic information with another Federal department or agency is necessary to allow such department or agency to take a law enforcement or national security action, consistent with the interagency procedures under paragraph (3)(A), or actions related to mitigating or otherwise resolving such incident; (iii) the entity to which the information pertains is notified of the Director’s determination, to the extent practicable consistent with national security or law enforcement interests, consistent with such interagency procedures; and (iv) the entity consents, except that the entity’s consent shall not be required if another Federal department or agency identifies the entity to the Agency in connection with a suspected cybersecurity incident. (B) The restriction on the use of information obtained through such a subpoena for a cybersecurity purpose. (C) The retention and destruction of nonpublic information obtained through such a subpoena, including—(i) destruction of such information that the Director determines is unrelated to critical infrastructure immediately upon providing notice to the entity pursuant to paragraph (5); and (ii) destruction of any personally identifiable information not later than 6 months after the date on which the Director receives information obtained through such a subpoena, unless otherwise agreed to by the individual identified by the subpoena respondent. (D) The processes for providing notice to each party that is subject to such a subpoena and each entity identified by information obtained under such a subpoena. (E) The processes and criteria for conducting critical infrastructure security risk assessments to determine whether a subpoena is necessary prior to being issued pursuant to this subsection. (F) The information to be provided to an entity at risk at the time of the notice of the vulnerability, which shall include—(i) a discussion or statement that responding to, or subsequent engagement with, the Agency, is voluntary; and (ii) to the extent practicable, information regarding the process through which the Director identifies security vulnerabilities. (8) Limitation on proceduresThe internal procedures established pursuant to paragraph (7) may not require an owner or operator of critical infrastructure to take any action as a result of a notice of vulnerability made pursuant to this chapter. (9) Review of proceduresNot later than 1 year after January 1, 2021, the Privacy Officer of the Agency shall—(A) review the internal procedures established pursuant to paragraph (7) to ensure that—(i) such procedures are consistent with fair information practices; and (ii) the operations of the Agency comply with such procedures; and (B) notify the Committee on Homeland Security and Governmental Affairs of the Senate and the Committee on Homeland Security of the House of Representatives of the results of the review under subparagraph (A). (10) Publication of informationNot later than 120 days after establishing the internal procedures under paragraph (7), the Director shall publish information on the website of the Agency regarding the subpoena process under this subsection, including information regarding the following:(A) Such internal procedures. (B) The purpose for subpoenas issued pursuant to this subsection. (C) The subpoena process. (D) The criteria for the critical infrastructure security risk assessment conducted prior to issuing a subpoena. (E) Policies and procedures on retention and sharing of data obtained by subpoenas. (F) Guidelines on how entities contacted by the Director may respond to notice of a subpoena. (11) Annual reportsThe Director shall annually submit to the Committee on Homeland Security and Governmental Affairs of the Senate and the Committee on Homeland Security of the House of Representatives a report (which may include a classified annex but with the presumption of declassification) on the use of subpoenas issued pursuant to this subsection, which shall include the following:(A) A discussion of the following:(i) The effectiveness of the use of such subpoenas to mitigate critical infrastructure security vulnerabilities. (ii) The critical infrastructure security risk assessment process conducted for subpoenas issued under this subsection. (iii) The number of subpoenas so issued during the preceding year. (iv) To the extent practicable, the number of vulnerable covered devices or systems mitigated under this subsection by the Agency during the preceding year. (v) The number of entities notified by the Director under this subsection, and their responses, during the preceding year. (B) For each subpoena issued pursuant to this subsection, the following:(i) Information relating to the source of the security vulnerability detected, identified, or received by the Director. (ii) Information relating to the steps taken to identify the entity at risk prior to issuing the subpoena. (iii) A description of the outcome of the subpoena, including discussion on the resolution or mitigation of the critical infrastructure security vulnerability. (12) Publication of the annual reportsThe Director shall publish a version of the annual report required under paragraph (11) on the website of the Agency, which shall, at a minimum, include the findings described in clauses (iii), (iv), and (v) of subparagraph (A) of such paragraph. (13) Prohibition on use of information for unauthorized purposesAny information obtained pursuant to a subpoena issued under this subsection may not be provided to any other Federal department or agency for any purpose other than a cybersecurity purpose or for the purpose of enforcing a subpoena issued pursuant to this subsection.
(q) Industrial control systemsThe Director shall maintain capabilities to identify and address threats and vulnerabilities to products and technologies intended for use in the automated control of critical infrastructure processes. In carrying out this subsection, the Director shall—(1) lead Federal Government efforts, in consultation with Sector Risk Management Agencies, as appropriate, to identify and mitigate cybersecurity threats to industrial control systems, including supervisory control and data acquisition systems; (2) maintain threat hunting and incident response capabilities to respond to industrial control system cybersecurity risks and incidents; (3) provide cybersecurity technical assistance to industry end-users, product manufacturers, Sector Risk Management Agencies, other Federal agencies, and other industrial control system stakeholders to identify, evaluate, assess, and mitigate vulnerabilities; (4) collect, coordinate, and provide vulnerability information to the industrial control systems community by, as appropriate, working closely with security researchers, industry end-users, product manufacturers, Sector Risk Management Agencies, other Federal agencies, and other industrial control systems stakeholders; and (5) conduct such other efforts and assistance as the Secretary determines appropriate.
(r) Coordination on cybersecurity for SLTT entities(1) 11 So in original. There is no par. (2). CoordinationThe Center shall, upon request and to the extent practicable, and in coordination as appropriate with Federal and non-Federal entities, such as the Multi-State Information Sharing and Analysis Center—(A) conduct exercises with SLTT entities; (B) provide operational and technical cybersecurity training to SLTT entities to address cybersecurity risks or incidents, with or without reimbursement, related to—(i) cyber threat indicators; (ii) defensive measures; (iii) cybersecurity risks; (iv) vulnerabilities; and (v) incident response and management; (C) in order to increase situational awareness and help prevent incidents, assist SLTT entities in sharing, in real time, with the Federal Government as well as among SLTT entities, actionable—(i) cyber threat indicators; (ii) defensive measures; (iii) information about cybersecurity risks; and (iv) information about incidents; (D) provide SLTT entities notifications containing specific incident and malware information that may affect them or their residents; (E) provide to, and periodically update, SLTT entities via an easily accessible platform and other means—(i) information about tools; (ii) information about products; (iii) resources; (iv) policies; (v) guidelines; (vi) controls; and (vii) other cybersecurity standards and best practices and procedures related to information security, including, as appropriate, information produced by other Federal agencies; (F) work with senior SLTT entity officials, including chief information officers and senior election officials and through national associations, to coordinate the effective implementation by SLTT entities of tools, products, resources, policies, guidelines, controls, and procedures related to information security to secure the information systems, including election systems, of SLTT entities; (G) provide operational and technical assistance to SLTT entities to implement tools, products, resources, policies, guidelines, controls, and procedures on information security; (H) assist SLTT entities in developing policies and procedures for coordinating vulnerability disclosures consistent with international and national standards in the information technology industry; and (I) promote cybersecurity education and awareness through engagements with Federal agencies and non-Federal entities.
(s) ReportNot later than 1 year after June 21, 2022, and every 2 years thereafter, the Secretary shall submit to the Committee on Homeland Security and Governmental Affairs of the Senate and the Committee on Homeland Security of the House of Representatives a report on the services and capabilities that the Agency directly and indirectly provides to SLTT entities.
6 U.S.C. § 660 Cybersecurity plans
(a) DefinitionsIn this section, the term “agency information system” means an information system used or operated by an agency or by another entity on behalf of an agency.
(b) Intrusion assessment plan(1) RequirementThe Secretary, in coordination with the Director of the Office of Management and Budget, shall—(A) develop and implement an intrusion assessment plan to proactively detect, identify, and remove intruders in agency information systems on a routine basis; and (B) update such plan as necessary. (2) ExceptionThe intrusion assessment plan required under paragraph (1) shall not apply to the Department of Defense, a national security system, or an element of the intelligence community.
(c) Cyber incident response planThe Director of the Cybersecurity and Infrastructure Security Agency shall, in coordination with appropriate Federal departments and agencies, State and local governments, sector coordinating councils, Information Sharing and Analysis Organizations, owners and operators of critical infrastructure, and other appropriate entities and individuals, develop, update not less often than biennially, maintain, and exercise adaptable cyber incident response plans to address cybersecurity risks to critical infrastructure. The Director, in consultation with relevant Sector Risk Management Agencies and the National Cyber Director, shall develop mechanisms to engage with stakeholders to educate such stakeholders regarding Federal Government cybersecurity roles and responsibilities for cyber incident response.
(d) National Response FrameworkThe Secretary, in coordination with the heads of other appropriate Federal departments and agencies, and in accordance with the National Cybersecurity Incident Response Plan required under subsection (c), shall regularly update, maintain, and exercise the Cyber Incident Annex to the National Response Framework of the Department.
(e) Homeland Security Strategy to Improve the Cybersecurity of State, Local, Tribal, and Territorial Governments(1) In general(A) RequirementNot later than one year after December 27, 2021, the Secretary, acting through the Director, shall, in coordination with the heads of appropriate Federal agencies, State, local, Tribal, and territorial governments, and other stakeholders, as appropriate, develop and make publicly available a Homeland Security Strategy to Improve the Cybersecurity of State, Local, Tribal, and Territorial Governments. (B) Recommendations and requirementsThe strategy required under subparagraph (A) shall provide recommendations relating to the ways in which the Federal Government should support and promote the ability of State, local, Tribal, and territorial governments to identify, mitigate against, protect against, detect, respond to, and recover from cybersecurity risks, cybersecurity threats, and incidents. (2) ContentsThe strategy required under paragraph (1) shall—(A) identify capability gaps in the ability of State, local, Tribal, and territorial governments to identify, protect against, detect, respond to, and recover from cybersecurity risks, cybersecurity threats, incidents, and ransomware incidents; (B) identify Federal resources and capabilities that are available or could be made available to State, local, Tribal, and territorial governments to help those governments identify, protect against, detect, respond to, and recover from cybersecurity risks, cybersecurity threats, incidents, and ransomware incidents; (C) identify and assess the limitations of Federal resources and capabilities available to State, local, Tribal, and territorial governments to help those governments identify, protect against, detect, respond to, and recover from cybersecurity risks, cybersecurity threats, incidents, and ransomware incidents and make recommendations to address such limitations; (D) identify opportunities to improve the coordination of the Agency with Federal and non-Federal entities, such as the Multi-State Information Sharing and Analysis Center, to improve—(i) incident exercises, information sharing and incident notification procedures; (ii) the ability for State, local, Tribal, and territorial governments to voluntarily adapt and implement guidance in Federal binding operational directives; and (iii) opportunities to leverage Federal schedules for cybersecurity investments under section 502 of title 40; (E) recommend new initiatives the Federal Government should undertake to improve the ability of State, local, Tribal, and territorial governments to identify, protect against, detect, respond to, and recover from cybersecurity risks, cybersecurity threats, incidents, and ransomware incidents; (F) set short-term and long-term goals that will improve the ability of State, local, Tribal, and territorial governments to identify, protect against, detect, respond to, and recover from cybersecurity risks, cybersecurity threats, incidents, and ransomware incidents; and (G) set dates, including interim benchmarks, as appropriate for State, local, Tribal, and territorial governments to establish baseline capabilities to identify, protect against, detect, respond to, and recover from cybersecurity risks, cybersecurity threats, incidents, and ransomware incidents. (3) ConsiderationsIn developing the strategy required under paragraph (1), the Director, in coordination with the heads of appropriate Federal agencies, State, local, Tribal, and territorial governments, and other stakeholders, as appropriate, shall consider—(A) lessons learned from incidents that have affected State, local, Tribal, and territorial governments, and exercises with Federal and non-Federal entities; (B) the impact of incidents that have affected State, local, Tribal, and territorial governments, including the resulting costs to such governments; (C) the information related to the interest and ability of state and non-state threat actors to compromise information systems owned or operated by State, local, Tribal, and territorial governments; and (D) emerging cybersecurity risks and cybersecurity threats to State, local, Tribal, and territorial governments resulting from the deployment of new technologies. (4) ExemptionChapter 35 of title 44 (commonly known as the “Paperwork Reduction Act”) shall not apply to any action to implement this subsection.
6 U.S.C. § 661 Cybersecurity strategy
(a) In generalNot later than 90 days after December 23, 2016, the Secretary shall develop a departmental strategy to carry out cybersecurity responsibilities as set forth in law.
(b) ContentsThe strategy required under subsection (a) shall include the following:(1) Strategic and operational goals and priorities to successfully execute the full range of the Secretary’s cybersecurity responsibilities. (2) Information on the programs, policies, and activities that are required to successfully execute the full range of the Secretary’s cybersecurity responsibilities, including programs, policies, and activities in furtherance of the following:(A) Cybersecurity functions set forth in section 659 of this title (relating to the national cybersecurity and communications integration center). (B) Cybersecurity investigations capabilities. (C) Cybersecurity research and development. (D) Engagement with international cybersecurity partners.
(c) ConsiderationsIn developing the strategy required under subsection (a), the Secretary shall—(1) consider—(A) the cybersecurity strategy for the Homeland Security Enterprise published by the Secretary in November 2011; (B) the Department of Homeland Security Fiscal Years 2014–2018 Strategic Plan; and (C) the most recent Quadrennial Homeland Security Review issued pursuant to section 347 of this title; and (2) include information on the roles and responsibilities of components and offices of the Department, to the extent practicable, to carry out such strategy.
(d) Implementation planNot later than 90 days after the development of the strategy required under subsection (a), the Secretary shall issue an implementation plan for the strategy that includes the following:(1) Strategic objectives and corresponding tasks. (2) Projected timelines and costs for such tasks. (3) Metrics to evaluate performance of such tasks.
(e) Congressional oversightThe Secretary shall submit to Congress for assessment the following:(1) A copy of the strategy required under subsection (a) upon issuance. (2) A copy of the implementation plan required under subsection (d) upon issuance, together with detailed information on any associated legislative or budgetary proposals.
(f) Classified informationThe strategy required under subsection (a) shall be in an unclassified form but may contain a classified annex.
(g) Rule of constructionNothing in this section may be construed as permitting the Department to engage in monitoring, surveillance, exfiltration, or other collection activities for the purpose of tracking an individual’s personally identifiable information.
6 U.S.C. § 662 Clearances
The Secretary shall make available the process of application for security clearances under Executive Order 13549 (75 Fed. Reg. 162; 11 So in original. Probably should be “51609;”. relating to a classified national security information program) or any successor Executive Order to appropriate representatives of sector coordinating councils, sector Information Sharing and Analysis Organizations, owners and operators of critical infrastructure, and any other person that the Secretary determines appropriate.
6 U.S.C. § 663 Federal intrusion detection and prevention system
(a) DefinitionsIn this section—(1) the term “agency” has the meaning given the term in section 3502 of title 44; (2) the term “agency information” means information collected or maintained by or on behalf of an agency; 11 So in original. Probably should be followed by “and”. (3) the term “agency information system” has the meaning given the term in section 660 of this title; and 22 So in original. The “; and” probably should be a period.
(b) Requirement(1) In generalNot later than 1 year after December 18, 2015, the Secretary shall deploy, operate, and maintain, to make available for use by any agency, with or without reimbursement—(A) a capability to detect cybersecurity risks in network traffic transiting or traveling to or from an agency information system; and (B) a capability to prevent network traffic associated with such cybersecurity risks from transiting or traveling to or from an agency information system or modify such network traffic to remove the cybersecurity risk. (2) Regular improvementThe Secretary shall regularly deploy new technologies and modify existing technologies to the intrusion detection and prevention capabilities described in paragraph (1) as appropriate to improve the intrusion detection and prevention capabilities.
(c) ActivitiesIn carrying out subsection (b), the Secretary—(1) may access, and the head of an agency may disclose to the Secretary or a private entity providing assistance to the Secretary under paragraph (2), information transiting or traveling to or from an agency information system, regardless of the location from which the Secretary or a private entity providing assistance to the Secretary under paragraph (2) accesses such information, notwithstanding any other provision of law that would otherwise restrict or prevent the head of an agency from disclosing such information to the Secretary or a private entity providing assistance to the Secretary under paragraph (2); (2) may enter into contracts or other agreements with, or otherwise request and obtain the assistance of, private entities to deploy, operate, and maintain technologies in accordance with subsection (b); (3) may retain, use, and disclose information obtained through the conduct of activities authorized under this section only to protect information and information systems from cybersecurity risks; (4) shall regularly assess through operational test and evaluation in real world or simulated environments available advanced protective technologies to improve detection and prevention capabilities, including commercial and noncommercial technologies and detection technologies beyond signature-based detection, and acquire, test, and deploy such technologies when appropriate; (5) shall establish a pilot through which the Secretary may acquire, test, and deploy, as rapidly as possible, technologies described in paragraph (4); and (6) shall periodically update the privacy impact assessment required under section 208(b) of the E-Government Act of 2002 (44 U.S.C. 3501 note).
(d) PrinciplesIn carrying out subsection (b), the Secretary shall ensure that—(1) activities carried out under this section are reasonably necessary for the purpose of protecting agency information and agency information systems from a cybersecurity risk; (2) information accessed by the Secretary will be retained no longer than reasonably necessary for the purpose of protecting agency information and agency information systems from a cybersecurity risk; (3) notice has been provided to users of an agency information system concerning access to communications of users of the agency information system for the purpose of protecting agency information and the agency information system; and (4) the activities are implemented pursuant to policies and procedures governing the operation of the intrusion detection and prevention capabilities.
(e) Private entities(1) ConditionsA private entity described in subsection (c)(2) may not—(A) disclose any network traffic transiting or traveling to or from an agency information system to any entity other than the Department or the agency that disclosed the information under subsection (c)(1), including personal information of a specific individual or information that identifies a specific individual not directly related to a cybersecurity risk; or (B) use any network traffic transiting or traveling to or from an agency information system to which the private entity gains access in accordance with this section for any purpose other than to protect agency information and agency information systems against cybersecurity risks or to administer a contract or other agreement entered into pursuant to subsection (c)(2) or as part of another contract with the Secretary. (2) Limitation on liabilityNo cause of action shall lie in any court against a private entity for assistance provided to the Secretary in accordance with this section and any contract or agreement entered into pursuant to subsection (c)(2). (3) Rule of constructionNothing in paragraph (2) shall be construed to authorize an Internet service provider to break a user agreement with a customer without the consent of the customer.
(f) Privacy Officer reviewNot later than 1 year after December 18, 2015, the Privacy Officer appointed under section 142 of this title, in consultation with the Attorney General, shall review the policies and guidelines for the program carried out under this section to ensure that the policies and guidelines are consistent with applicable privacy laws, including those governing the acquisition, interception, retention, use, and disclosure of communications.
6 U.S.C. § 664 National asset database
(a) Establishment(1) National asset databaseThe Secretary shall establish and maintain a national database of each system or asset that—(A) the Secretary, in consultation with appropriate homeland security officials of the States, determines to be vital and the loss, interruption, incapacity, or destruction of which would have a negative or debilitating effect on the economic security, public health, or safety of the United States, any State, or any local government; or (B) the Secretary determines is appropriate for inclusion in the database. (2) Prioritized critical infrastructure listIn accordance with Homeland Security Presidential Directive–7, as in effect on January 1, 2007, the Secretary shall establish and maintain a single classified prioritized list of systems and assets included in the database under paragraph (1) that the Secretary determines would, if destroyed or disrupted, cause national or regional catastrophic effects.
(b) Use of databaseThe Secretary shall use the database established under subsection (a)(1) in the development and implementation of Department plans and programs as appropriate.
(c) Maintenance of database(1) In generalThe Secretary shall maintain and annually update the database established under subsection (a)(1) and the list established under subsection (a)(2), including—(A) establishing data collection guidelines and providing such guidelines to the appropriate homeland security official of each State; (B) regularly reviewing the guidelines established under subparagraph (A), including by consulting with the appropriate homeland security officials of States, to solicit feedback about the guidelines, as appropriate; (C) after providing the homeland security official of a State with the guidelines under subparagraph (A), allowing the official a reasonable amount of time to submit to the Secretary any data submissions recommended by the official for inclusion in the database established under subsection (a)(1); (D) examining the contents and identifying any submissions made by such an official that are described incorrectly or that do not meet the guidelines established under subparagraph (A); and (E) providing to the appropriate homeland security official of each relevant State a list of submissions identified under subparagraph (D) for review and possible correction before the Secretary finalizes the decision of which submissions will be included in the database established under subsection (a)(1). (2) Organization of information in databaseThe Secretary shall organize the contents of the database established under subsection (a)(1) and the list established under subsection (a)(2) as the Secretary determines is appropriate. Any organizational structure of such contents shall include the categorization of the contents—(A) according to the sectors listed in National Infrastructure Protection Plan developed pursuant to Homeland Security Presidential Directive–7; and (B) by the State and county of their location. (3) Private sector integrationThe Secretary shall identify and evaluate methods, including the Department’s Protected Critical Infrastructure Information Program, to acquire relevant private sector information for the purpose of using that information to generate any database or list, including the database established under subsection (a)(1) and the list established under subsection (a)(2). (4) Retention of classificationThe classification of information required to be provided to Congress, the Department, or any other department or agency under this section by a Sector Risk Management Agency, including the assignment of a level of classification of such information, shall be binding on Congress, the Department, and that other Federal agency.
(d) Reports(1) Report requiredNot later than 180 days after August 3, 2007, and annually thereafter, the Secretary shall submit to the Committee on Homeland Security and Governmental Affairs of the Senate and the Committee on Homeland Security of the House of Representatives a report on the database established under subsection (a)(1) and the list established under subsection (a)(2). (2) Contents of reportEach such report shall include the following:(A) The name, location, and sector classification of each of the systems and assets on the list established under subsection (a)(2). (B) The name, location, and sector classification of each of the systems and assets on such list that are determined by the Secretary to be most at risk to terrorism. (C) Any significant challenges in compiling the list of the systems and assets included on such list or in the database established under subsection (a)(1). (D) Any significant changes from the preceding report in the systems and assets included on such list or in such database. (E) If appropriate, the extent to which such database and such list have been used, individually or jointly, for allocating funds by the Federal Government to prevent, reduce, mitigate, or respond to acts of terrorism. (F) The amount of coordination between the Department and the private sector, through any entity of the Department that meets with representatives of private sector industries for purposes of such coordination, for the purpose of ensuring the accuracy of such database and such list. (G) Any other information the Secretary deems relevant. (3) Classified informationThe report shall be submitted in unclassified form but may contain a classified annex.
(e) National Infrastructure Protection ConsortiumThe Secretary may establish a consortium to be known as the “National Infrastructure Protection Consortium”. The Consortium may advise the Secretary on the best way to identify, generate, organize, and maintain any database or list of systems and assets established by the Secretary, including the database established under subsection (a)(1) and the list established under subsection (a)(2). If the Secretary establishes the National Infrastructure Protection Consortium, the Consortium may—(1) be composed of national laboratories, Federal agencies, State and local homeland security organizations, academic institutions, or national Centers of Excellence that have demonstrated experience working with and identifying critical infrastructure and key resources; and (2) provide input to the Secretary on any request pertaining to the contents of such database or such list.
6 U.S.C. § 665 Duties and authorities relating to .gov internet domain
(a) DefinitionIn this section, the term “agency” has the meaning given the term in section 3502 of title 44.
(b) Availability of .gov internet domainThe Director shall make .gov internet domain name registration services, as well as any supporting services described in subsection (e), generally available—(1) to any Federal, State, local, or territorial government entity, or other publicly controlled entity, including any Tribal government recognized by the Federal Government or a State government, that complies with the requirements for registration developed by the Director as described in subsection (c); (2) without conditioning registration on the sharing of any information with the Director or any other Federal entity, other than the information required to meet the requirements described in subsection (c); and (3) without conditioning registration on participation in any separate service offered by the Director or any other Federal entity.
(c) RequirementsThe Director, with the approval of the Director of the Office of Management and Budget for agency .gov internet domain requirements and in consultation with the Director of the Office of Management and Budget for .gov internet domain requirements for entities that are not agencies, shall establish and publish on a publicly available website requirements for the registration and operation of .gov internet domains sufficient to—(1) minimize the risk of .gov internet domains whose names could mislead or confuse users; (2) establish that .gov internet domains may not be used for commercial or political campaign purposes; (3) ensure that domains are registered and maintained only by authorized individuals; and (4) limit the sharing or use of any information obtained through the administration of the .gov internet domain with any other Department component or any other agency for any purpose other than the administration of the .gov internet domain, the services described in subsection (e), and the requirements for establishing a .gov inventory described in subsection (h).
(d) Executive branch(1) In generalThe Director of the Office of Management and Budget shall establish applicable processes and guidelines for the registration and acceptable use of .gov internet domains by agencies. (2) Approval requiredThe Director shall obtain the approval of the Director of the Office of Management and Budget before registering a .gov internet domain name for an agency. (3) ComplianceEach agency shall ensure that any website or digital service of the agency that uses a .gov internet domain is in compliance with the 21st Century IDEA Act (44 U.S.C. 3501 note) and implementation guidance issued pursuant to that Act.
(e) Supporting services(1) In generalThe Director may provide services to the entities described in subsection (b)(1) specifically intended to support the security, privacy, reliability, accessibility, and speed of registered .gov internet domains. (2) Rule of constructionNothing in paragraph (1) shall be construed to—(A) limit other authorities of the Director to provide services or technical assistance to an entity described in subsection (b)(1); or (B) establish new authority for services other than those the purpose of which expressly supports the operation of .gov internet domains and the needs of .gov internet domain registrants.
(f) Fees(1) In generalThe Director may provide any service relating to the availability of the .gov internet domain program, including .gov internet domain name registration services described in subsection (b) and supporting services described in subsection (e), to entities described in subsection (b)(1) with or without reimbursement, including variable pricing. (2) LimitationThe total fees collected for new .gov internet domain registrants or annual renewals of .gov internet domains shall not exceed the direct operational expenses of improving, maintaining, and operating the .gov internet domain, .gov internet domain services, and .gov internet domain supporting services.
(g) ConsultationThe Director shall consult with the Director of the Office of Management and Budget, the Administrator of General Services, other civilian Federal agencies as appropriate, and entities representing State, local, Tribal, or territorial governments in developing the strategic direction of the .gov internet domain and in establishing requirements under subsection (c), in particular on matters of privacy, accessibility, transparency, and technology modernization.
(h) .gov inventory(1) In generalThe Director shall, on a continuous basis—(A) inventory all hostnames and services in active use within the .gov internet domain; and (B) provide the data described in subparagraph (A) to domain registrants at no cost. (2) RequirementsIn carrying out paragraph (1)—(A) data may be collected through analysis of public and non-public sources, including commercial data sets; (B) the Director shall share with Federal and non-Federal domain registrants all unique hostnames and services discovered within the zone of their registered domain; (C) the Director shall share any data or information collected or used in the management of the .gov internet domain name registration services relating to Federal executive branch registrants with the Director of the Office of Management and Budget for the purpose of fulfilling the duties of the Director of the Office of Management and Budget under section 3553 of title 44; (D) the Director shall publish on a publicly available website discovered hostnames that describe publicly accessible agency websites, to the extent consistent with the security of Federal information systems but with the presumption of disclosure; (E) the Director may publish on a publicly available website any analysis conducted and data collected relating to compliance with Federal mandates and industry best practices, to the extent consistent with the security of Federal information systems but with the presumption of disclosure; and (F) the Director shall—(i) collect information on the use of non-.gov internet domain suffixes by agencies for their official online services; (ii) collect information on the use of non-.gov internet domain suffixes by State, local, Tribal, and territorial governments; and (iii) publish the information collected under clause (i) on a publicly available website to the extent consistent with the security of the Federal information systems, but with the presumption of disclosure. (3) National security coordination(A) In generalIn carrying out this subsection, the Director shall inventory, collect, and publish hostnames and services in a manner consistent with the protection of national security information. (B) LimitationThe Director may not inventory, collect, or publish hostnames or services under this subsection if the Director, in coordination with other heads of agencies, as appropriate, determines that the collection or publication would—(i) disrupt a law enforcement investigation; (ii) endanger national security or intelligence activities; (iii) impede national defense activities or military operations; or (iv) hamper security remediation actions. (4) StrategyNot later than 180 days after December 27, 2020, the Director shall develop and submit to the Committee on Homeland Security and Governmental Affairs and the Committee on Rules and Administration of the Senate and the Committee on Homeland Security, the Committee on Oversight and Reform, and the Committee on House Administration of the House of Representatives a strategy to utilize the information collected under this subsection for countering malicious cyber activity.
6 U.S.C. § 665a Intelligence and cybersecurity diversity fellowship program
(a) DefinitionsIn this section:(1) Appropriate committees of CongressThe term “appropriate committees of Congress” means—(A) the Committee on Homeland Security and Governmental Affairs and the Select Committee on Intelligence of the Senate; and (B) the Committee on Homeland Security and the Permanent Select Committee on Intelligence of the House of Representatives. (2) Excepted serviceThe term “excepted service” has the meaning given that term in section 2103 of title 5. (3) Historically Black college or universityThe term “historically Black college or university” has the meaning given the term “part B institution” in section 1061 of title 20. (4) Institution of higher educationThe term “institution of higher education” has the meaning given that term in section 1001 of title 20. (5) Minority-serving institutionThe term “minority-serving institution” means an institution of higher education described in section 1067q(a) of title 20.
(b) ProgramThe Secretary shall carry out an intelligence and cybersecurity diversity fellowship program (in this section referred to as the “Program”) under which an eligible individual may—(1) participate in a paid internship at the Department that relates to intelligence, cybersecurity, or some combination thereof; (2) receive tuition assistance from the Secretary; and (3) upon graduation from an institution of higher education and successful completion of the Program (as defined by the Secretary), receive an offer of employment to work in an intelligence or cybersecurity position of the Department that is in the excepted service.
(c) EligibilityTo be eligible to participate in the Program, an individual shall—(1) be a citizen of the United States; and (2) as of the date of submitting the application to participate in the Program—(A) have a cumulative grade point average of at least 3.2 on a 4.0 scale; (B) be a socially disadvantaged individual (as that term in 11 So in original. Probably should be “is”. defined in section 124.103 of title 13, Code of Federal Regulations, or successor regulation); and (C) be a sophomore, junior, or senior at an institution of higher education.
(d) Direct hire authorityIf an individual who receives an offer of employment under subsection (b)(3) accepts such offer, the Secretary shall appoint, without regard to provisions of subchapter I of chapter 33 of title 5 (except for section 3328 of such title) such individual to the position specified in such offer.
(e) Reports(1) ReportsNot later than 1 year after December 27, 2020, and on an annual basis thereafter, the Secretary shall submit to the appropriate committees of Congress a report on the Program. (2) MattersEach report under paragraph (1) shall include, with respect to the most recent year, the following:(A) A description of outreach efforts by the Secretary to raise awareness of the Program among institutions of higher education in which eligible individuals are enrolled. (B) Information on specific recruiting efforts conducted by the Secretary to increase participation in the Program. (C) The number of individuals participating in the Program, listed by the institution of higher education in which the individual is enrolled at the time of participation, and information on the nature of such participation, including on whether the duties of the individual under the Program relate primarily to intelligence or to cybersecurity. (D) The number of individuals who accepted an offer of employment under the Program and an identification of the element within the Department to which each individual was appointed.
6 U.S.C. § 665b Joint cyber planning office
(a) Establishment of OfficeThere is established in the Agency an office for joint cyber planning (in this section referred to as the “Office”) to develop, for public and private sector entities, plans for cyber defense operations, including the development of a set of coordinated actions to protect, detect, respond to, and recover from cybersecurity risks or incidents or limit, mitigate, or defend against coordinated, malicious cyber operations that pose a potential risk to critical infrastructure or national interests. The Office shall be headed by a senior official of the Agency selected by the Director.
(b) Planning and executionIn leading the development of plans for cyber defense operations pursuant to subsection (a), the head of the Office shall—(1) coordinate with relevant Federal departments and agencies to establish processes and procedures necessary to develop and maintain ongoing coordinated plans for cyber defense operations; (2) leverage cyber capabilities and authorities of participating Federal departments and agencies, as appropriate, in furtherance of plans for cyber defense operations; (3) ensure that plans for cyber defense operations are, to the greatest extent practicable, developed in collaboration with relevant private sector entities, particularly in areas in which such entities have comparative advantages in limiting, mitigating, or defending against a cybersecurity risk or incident or coordinated, malicious cyber operation; (4) ensure that plans for cyber defense operations, as appropriate, are responsive to potential adversary activity conducted in response to United States offensive cyber operations; (5) facilitate the exercise of plans for cyber defense operations, including by developing and modeling scenarios based on an understanding of adversary threats to, vulnerability of, and potential consequences of disruption or compromise of critical infrastructure; (6) coordinate with and, as necessary, support relevant Federal departments and agencies in the establishment of procedures, development of additional plans, including for offensive and intelligence activities in support of cyber defense operations, and creation of agreements necessary for the rapid execution of plans for cyber defense operations when a cybersecurity risk or incident or malicious cyber operation has been identified; and (7) support public and private sector entities, as appropriate, in the execution of plans developed pursuant to this section.
(c) CompositionThe Office shall be composed of—(1) a central planning staff; and (2) appropriate representatives of Federal departments and agencies, including—(A) the Department; (B) United States Cyber Command; (C) the National Security Agency; (D) the Federal Bureau of Investigation; (E) the Department of Justice; and (F) the Office of the Director of National Intelligence.
(d) ConsultationIn carrying out its responsibilities described in subsection (b), the Office shall regularly consult with appropriate representatives of non-Federal entities, such as—(1) State, local, federally-recognized Tribal, and territorial governments; (2) Information Sharing and Analysis Organizations, including information sharing and analysis centers; (3) owners and operators of critical information systems; (4) private entities; and (5) other appropriate representatives or entities, as determined by the Secretary.
(e) Interagency agreementsThe Secretary and the head of a Federal department or agency referred to in subsection (c) may enter into agreements for the purpose of detailing personnel on a reimbursable or non-reimbursable basis.
(f) DefinitionsIn this section, the term “cyber defense operation” means the defensive activities performed for a cybersecurity purpose.
6 U.S.C. § 665c Cybersecurity State Coordinator
(a) AppointmentThe Director shall appoint an employee of the Agency in each State, with the appropriate cybersecurity qualifications and expertise, who shall serve as the Cybersecurity State Coordinator.
(b) DutiesThe duties of a Cybersecurity State Coordinator appointed under subsection (a) shall include—(1) building strategic public and, on a voluntary basis, private sector relationships, including by advising on establishing governance structures to facilitate the development and maintenance of secure and resilient infrastructure; (2) serving as the Federal cybersecurity risk advisor and supporting preparation, response, and remediation efforts relating to cybersecurity risks and incidents; (3) facilitating the sharing of cyber threat information to improve understanding of cybersecurity risks and situational awareness of cybersecurity incidents; (4) raising awareness of the financial, technical, and operational resources available from the Federal Government to non-Federal entities to increase resilience against cyber threats; (5) supporting training, exercises, and planning for continuity of operations to expedite recovery from cybersecurity incidents, including ransomware; (6) serving as a principal point of contact for non-Federal entities to engage, on a voluntary basis, with the Federal Government on preparing, managing, and responding to cybersecurity incidents; (7) assisting non-Federal entities in developing and coordinating vulnerability disclosure programs consistent with Federal and information security industry standards; (8) assisting State, local, Tribal, and territorial governments, on a voluntary basis, in the development of State cybersecurity plans; (9) coordinating with appropriate officials within the Agency; and (10) performing such other duties as determined necessary by the Director to achieve the goal of managing cybersecurity risks in the United States and reducing the impact of cyber threats to non-Federal entities.
(c) FeedbackThe Director shall consult with relevant State, local, Tribal, and territorial officials regarding the appointment, and State, local, Tribal, and territorial officials and other non-Federal entities regarding the performance, of the Cybersecurity State Coordinator of a State.
6 U.S.C. § 665d Sector Risk Management Agencies
(a) In generalConsistent with applicable law, Presidential directives, Federal regulations, and strategic guidance from the Secretary, each Sector Risk Management Agency, in coordination with the Director, shall—(1) provide specialized sector-specific expertise to critical infrastructure owners and operators within its designated critical infrastructure sector or subsector of such sector; and (2) support programs and associated activities of such sector or subsector of such sector.
(b) ImplementationIn carrying out this section, Sector Risk Management Agencies shall—(1) coordinate with the Department and, as appropriate, other relevant Federal departments and agencies; (2) collaborate with critical infrastructure owners and operators within the designated critical infrastructure sector or subsector of such sector; and (3) coordinate with independent regulatory agencies, and State, local, Tribal, and territorial entities, as appropriate.
(c) ResponsibilitiesConsistent with applicable law, Presidential directives, Federal regulations, and strategic guidance from the Secretary, each Sector Risk Management Agency shall utilize its specialized expertise regarding its designated critical infrastructure sector or subsector of such sector and authorities under applicable law to—(1) support sector risk management, in coordination with the Director, including—(A) establishing and carrying out programs to assist critical infrastructure owners and operators within the designated sector or subsector of such sector in identifying, understanding, and mitigating threats, vulnerabilities, and risks to their systems or assets, or within a region, sector, or subsector of such sector; and (B) recommending security measures to mitigate the consequences of destruction, compromise, and disruption of systems and assets; (2) assess sector risk, in coordination with the Director, including—(A) identifying, assessing, and prioritizing risks within the designated sector or subsector of such sector, considering physical security and cybersecurity threats, vulnerabilities, and consequences; and (B) supporting national risk assessment efforts led by the Department; (3) sector coordination, including—(A) serving as a day-to-day Federal interface for the prioritization and coordination of sector-specific activities and responsibilities under this title; (B) serving as the Federal Government coordinating council chair for the designated sector or subsector of such sector; and (C) participating in cross-sector coordinating councils, as appropriate; (4) facilitating, in coordination with the Director, the sharing with the Department and other appropriate Federal department of information regarding physical security and cybersecurity threats within the designated sector or subsector of such sector, including—(A) facilitating, in coordination with the Director, access to, and exchange of, information and intelligence necessary to strengthen the security of critical infrastructure, including through Information Sharing and Analysis Organizations and the national cybersecurity and communications integration center established pursuant to section 659 of this title; (B) facilitating the identification of intelligence needs and priorities of critical infrastructure owners and operators in the designated sector or subsector of such sector, in coordination with the Director of National Intelligence and the heads of other Federal departments and agencies, as appropriate; (C) providing the Director, and facilitating awareness within the designated sector or subsector of such sector, of ongoing, and where possible, real-time awareness of identified threats, vulnerabilities, mitigations, and other actions related to the security of such sector or subsector of such sector; and (D) supporting the reporting requirements of the Department under applicable law by providing, on an annual basis, sector-specific critical infrastructure information; (5) supporting incident management, including—(A) supporting, in coordination with the Director, incident management and restoration efforts during or following a security incident; and (B) supporting the Director, upon request, in national cybersecurity asset response activities for critical infrastructure; and (6) contributing to emergency preparedness efforts, including—(A) coordinating with critical infrastructure owners and operators within the designated sector or subsector of such sector and the Director in the development of planning documents for coordinated action in the event of a natural disaster, act of terrorism, or other man-made disaster or emergency; (B) participating in and, in coordination with the Director, conducting or facilitating, exercises and simulations of potential natural disasters, acts of terrorism, or other man-made disasters or emergencies within the designated sector or subsector of such sector; and (C) supporting the Department and other Federal departments or agencies in developing planning documents or conducting exercises or simulations when relevant to the designated sector or subsector or such sector.
6 U.S.C. § 665e Cybersecurity Advisory Committee
(a) EstablishmentThe Secretary shall establish within the Agency a Cybersecurity Advisory Committee (referred to in this section as the “Advisory Committee”).
(b) Duties(1) In generalThe Advisory Committee shall advise, consult with, report to, and make recommendations to the Director, as appropriate, on the development, refinement, and implementation of policies, programs, planning, and training pertaining to the cybersecurity mission of the Agency. (2) Recommendations(A) In generalThe Advisory Committee shall develop, at the request of the Director, recommendations for improvements to advance the cybersecurity mission of the Agency and strengthen the cybersecurity of the United States. (B) Recommendations of subcommitteesRecommendations agreed upon by subcommittees established under subsection (d) for any year shall be approved by the Advisory Committee before the Advisory Committee submits to the Director the annual report under paragraph (4) for that year. (3) Periodic reportsThe Advisory Committee shall periodically submit to the Director—(A) reports on matters identified by the Director; and (B) reports on other matters identified by a majority of the members of the Advisory Committee. (4) Annual report(A) In generalThe Advisory Committee shall submit to the Director an annual report providing information on the activities, findings, and recommendations of the Advisory Committee, including its subcommittees, for the preceding year. (B) PublicationNot later than 180 days after the date on which the Director receives an annual report for a year under subparagraph (A), the Director shall publish a public version of the report describing the activities of the Advisory Committee and such related matters as would be informative to the public during that year, consistent with section 552(b) of title 5. (5) FeedbackNot later than 90 days after receiving any recommendation submitted by the Advisory Committee under paragraph (2), (3), or (4), the Director shall respond in writing to the Advisory Committee with feedback on the recommendation. Such a response shall include—(A) with respect to any recommendation with which the Director concurs, an action plan to implement the recommendation; and (B) with respect to any recommendation with which the Director does not concur, a justification for why the Director does not plan to implement the recommendation. (6) Congressional notificationNot less frequently than once per year after January 1, 2021, the Director shall provide to the Committee on Homeland Security and Governmental Affairs and the Committee on Appropriations of the Senate and the Committee on Homeland Security, the Committee on Energy and Commerce, and the Committee on Appropriations of the House of Representatives a briefing on feedback from the Advisory Committee. (7) Governance rulesThe Director shall establish rules for the structure and governance of the Advisory Committee and all subcommittees established under subsection (d).
(c) Membership(1) Appointment(A) In generalNot later than 180 days after the date of enactment of the Cybersecurity Advisory Committee Authorization Act of 2020,11 See References in Text note below. the Director shall appoint the members of the Advisory Committee. (B) CompositionThe membership of the Advisory Committee shall consist of not more than 35 individuals. (C) Representation(i) In generalThe membership of the Advisory Committee shall satisfy the following criteria:(I) Consist of subject matter experts. (II) Be geographically balanced. (III) Include representatives of State, local, and Tribal governments and of a broad range of industries, which may include the following:(aa) Defense. (bb) Education. (cc) Financial services and insurance. (dd) Healthcare. (ee) Manufacturing. (ff) Media and entertainment. (gg) Chemicals. (hh) Retail. (ii) Transportation. (jj) Energy. (kk) Information Technology. (ll) Communications. (mm) Other relevant fields identified by the Director. (ii) ProhibitionNot fewer than one member nor more than three members may represent any one category under clause (i)(III). (iii) Publication of membership listThe Advisory Committee shall publish its membership list on a publicly available website not less than once per fiscal year and shall update the membership list as changes occur. (2) Term of office(A) TermsThe term of each member of the Advisory Committee shall be two years, except that a member may continue to serve until a successor is appointed. (B) RemovalThe Director may review the participation of a member of the Advisory Committee and remove such member any time at the discretion of the Director. (C) ReappointmentA member of the Advisory Committee may be reappointed for an unlimited number of terms. (3) Prohibition on compensationThe members of the Advisory Committee may not receive pay or benefits from the United States Government by reason of their service on the Advisory Committee. (4) Meetings(A) In generalThe Director shall require the Advisory Committee to meet not less frequently than semiannually, and may convene additional meetings as necessary. (B) Public meetingsAt least one of the meetings referred to in subparagraph (A) shall be open to the public. (C) AttendanceThe Advisory Committee shall maintain a record of the persons present at each meeting. (5) Member access to classified information(A) In generalNot later than 60 days after the date on which a member is first appointed to the Advisory Committee and before the member is granted access to any classified information, the Director shall determine, for the purposes of the Advisory Committee, if the member should be restricted from reviewing, discussing, or possessing classified information. (B) AccessAccess to classified materials shall be managed in accordance with Executive Order No. 13526 of December 29, 2009 (75 Fed. Reg. 707), or any subsequent corresponding Executive Order. (C) ProtectionsA member of the Advisory Committee shall protect all classified information in accordance with the applicable requirements for the particular level of classification of such information. (D) Rule of constructionNothing in this paragraph shall be construed to affect the security clearance of a member of the Advisory Committee or the authority of a Federal agency to provide a member of the Advisory Committee access to classified information. (6) ChairpersonThe Advisory Committee shall select, from among the members of the Advisory Committee—(A) a member to serve as chairperson of the Advisory Committee; and (B) a member to serve as chairperson of each subcommittee of the Advisory Committee established under subsection (d).
(d) Subcommittees(1) In generalThe Director shall establish subcommittees within the Advisory Committee to address cybersecurity issues, which may include the following:(A) Information exchange. (B) Critical infrastructure. (C) Risk management. (D) Public and private partnerships. (2) Meetings and reportingEach subcommittee shall meet not less frequently than semiannually, and submit to the Advisory Committee for inclusion in the annual report required under subsection (b)(4) information, including activities, findings, and recommendations, regarding subject matter considered by the subcommittee. (3) Subject matter expertsThe chair of the Advisory Committee shall appoint members to subcommittees and shall ensure that each member appointed to a subcommittee has subject matter expertise relevant to the subject matter of the subcommittee.
6 U.S.C. § 665f Cybersecurity education and training programs
(a) Establishment(1) In generalThe Cybersecurity Education and Training Assistance Program (referred to in this section as “CETAP”) is established within the Agency. (2) PurposeThe purpose of CETAP shall be to support the effort of the Agency in building and strengthening a national cybersecurity workforce pipeline capacity through enabling elementary and secondary cybersecurity education, including by—(A) providing foundational cybersecurity awareness and literacy; (B) encouraging cybersecurity career exploration; and (C) supporting the teaching of cybersecurity skills at the elementary and secondary education levels.
(b) RequirementsIn carrying out CETAP, the Director shall—(1) ensure that the program—(A) creates and disseminates cybersecurity-focused curricula and career awareness materials appropriate for use at the elementary and secondary education levels; (B) conducts professional development sessions for teachers; (C) develops resources for the teaching of cybersecurity-focused curricula described in subparagraph (A); (D) provides direct student engagement opportunities through camps and other programming; (E) engages with State educational agencies and local educational agencies to promote awareness of the program and ensure that offerings align with State and local curricula; (F) integrates with existing post-secondary education and workforce development programs at the Department; (G) promotes and supports national standards for elementary and secondary cyber education; (H) partners with cybersecurity and education stakeholder groups to expand outreach; and (I) any other activity the Director determines necessary to meet the purpose described in subsection (a)(2); and (2) enable the deployment of CETAP nationwide, with special consideration for underserved populations or communities.
(c) Briefings(1) In generalNot later than 1 year after the establishment of CETAP, and annually thereafter, the Secretary shall brief the Committee on Homeland Security and Governmental Affairs of the Senate and the Committee on Homeland Security of the House of Representatives on the program. (2) ContentsEach briefing conducted under paragraph (1) shall include—(A) estimated figures on the number of students reached and teachers engaged; (B) information on outreach and engagement efforts, including the activities described in subsection (b)(1)(E); (C) information on any grants or cooperative agreements made pursuant to subsection (e), including how any such grants or cooperative agreements are being used to enhance cybersecurity education for underserved populations or communities; (D) information on new curricula offerings and teacher training platforms; and (E) information on coordination with post-secondary education and workforce development programs at the Department.
(d) Mission promotionThe Director may use appropriated amounts to purchase promotional and recognition items and marketing and advertising services to publicize and promote the mission and services of the Agency, support the activities of the Agency, and to recruit and retain Agency personnel.
(e) Grants and cooperative agreementsThe Director may award financial assistance in the form of grants or cooperative agreements to States, local governments, institutions of higher education (as such term is defined in section 1001 of title 20), nonprofit organizations, and other non-Federal entities as determined appropriate by the Director for the purpose of funding cybersecurity and infrastructure security education and training programs and initiatives to—(1) carry out the purposes of CETAP; and (2) enhance CETAP to address the national shortfall of cybersecurity professionals.
6 U.S.C. § 665g State and Local Cybersecurity Grant Program
(a) DefinitionsIn this section:(1) Cybersecurity PlanThe term “Cybersecurity Plan” means a plan submitted by an eligible entity under subsection (e)(1). (2) Eligible entityThe term “eligible entity” means a—(A) State; or (B) Tribal government. (3) Multi-entity groupThe term “multi-entity group” means a group of 2 or more eligible entities desiring a grant under this section. (4) Online serviceThe term “online service” means any internet-facing service, including a website, email, virtual private network, or custom application. (5) Rural areaThe term “rural area” has the meaning given the term in section 5302 of title 49. (6) State and Local Cybersecurity Grant ProgramThe term “State and Local Cybersecurity Grant Program” means the program established under subsection (b). (7) Tribal governmentThe term “Tribal government” means the recognized governing body of any Indian or Alaska Native Tribe, band, nation, pueblo, village, community, component band, or component reservation, that is individually identified (including parenthetically) in the most recent list published pursuant to section 5131 of title 25.
(b) Establishment(1) In generalThere is established within the Department a program to award grants to eligible entities to address cybersecurity risks and cybersecurity threats to information systems owned or operated by, or on behalf of, State, local, or Tribal governments. (2) ApplicationAn eligible entity desiring a grant under the State and Local Cybersecurity Grant Program shall submit to the Secretary an application at such time, in such manner, and containing such information as the Secretary may require.
(c) AdministrationThe State and Local Cybersecurity Grant Program shall be administered in the same office of the Department that administers grants made under sections 604 and 605 of this title.
(d) Use of fundsAn eligible entity that receives a grant under this section and a local government that receives funds from a grant under this section, as appropriate, shall use the grant to—(1) implement the Cybersecurity Plan of the eligible entity; (2) develop or revise the Cybersecurity Plan of the eligible entity; (3) pay expenses directly relating to the administration of the grant, which shall not exceed 5 percent of the amount of the grant; (4) assist with activities that address imminent cybersecurity threats, as confirmed by the Secretary, acting through the Director, to the information systems owned or operated by, or on behalf of, the eligible entity or a local government within the jurisdiction of the eligible entity; or (5) fund any other appropriate activity determined by the Secretary, acting through the Director.
(e) Cybersecurity plans(1) In generalAn eligible entity applying for a grant under this section shall submit to the Secretary a Cybersecurity Plan for review in accordance with subsection (i). (2) Required elementsA Cybersecurity Plan of an eligible entity shall—(A) incorporate, to the extent practicable—(i) any existing plans of the eligible entity to protect against cybersecurity risks and cybersecurity threats to information systems owned or operated by, or on behalf of, State, local, or Tribal governments; and (ii) if the eligible entity is a State, consultation and feedback from local governments and associations of local governments within the jurisdiction of the eligible entity; (B) describe, to the extent practicable, how the eligible entity will—(i) manage, monitor, and track information systems, applications, and user accounts owned or operated by, or on behalf of, the eligible entity or, if the eligible entity is a State, local governments within the jurisdiction of the eligible entity, and the information technology deployed on those information systems, including legacy information systems and information technology that are no longer supported by the manufacturer of the systems or technology; (ii) monitor, audit, and,11 So in original. The comma probably should not appear. track network traffic and activity transiting or traveling to or from information systems, applications, and user accounts owned or operated by, or on behalf of, the eligible entity or, if the eligible entity is a State, local governments within the jurisdiction of the eligible entity; (iii) enhance the preparation, response, and resiliency of information systems, applications, and user accounts owned or operated by, or on behalf of, the eligible entity or, if the eligible entity is a State, local governments within the jurisdiction of the eligible entity, against cybersecurity risks and cybersecurity threats; (iv) implement a process of continuous cybersecurity vulnerability assessments and threat mitigation practices prioritized by degree of risk to address cybersecurity risks and cybersecurity threats on information systems, applications, and user accounts owned or operated by, or on behalf of, the eligible entity or, if the eligible entity is a State, local governments within the jurisdiction of the eligible entity; (v) ensure that the eligible entity and, if the eligible entity is a State, local governments within the jurisdiction of the eligible entity, adopt and use best practices and methodologies to enhance cybersecurity, such as—(I) the practices set forth in the cybersecurity framework developed by the National Institute of Standards and Technology; (II) cyber chain supply chain risk management best practices identified by the National Institute of Standards and Technology; and (III) knowledge bases of adversary tools and tactics; (vi) promote the delivery of safe, recognizable, and trustworthy online services by the eligible entity and, if the eligible entity is a State, local governments within the jurisdiction of the eligible entity, including through the use of the .gov internet domain; (vii) ensure continuity of operations of the eligible entity and, if the eligible entity is a State, local governments within the jurisdiction of the eligible entity, in the event of a cybersecurity incident, including by conducting exercises to practice responding to a cybersecurity incident; (viii) use the National Initiative for Cybersecurity Education Workforce Framework for Cybersecurity developed by the National Institute of Standards and Technology to identify and mitigate any gaps in the cybersecurity workforces of the eligible entity and, if the eligible entity is a State, local governments within the jurisdiction of the eligible entity, enhance recruitment and retention efforts for those workforces, and bolster the knowledge, skills, and abilities of personnel of the eligible entity and, if the eligible entity is a State, local governments within the jurisdiction of the eligible entity, to address cybersecurity risks and cybersecurity threats, such as through cybersecurity hygiene training; (ix) if the eligible entity is a State, ensure continuity of communications and data networks within the jurisdiction of the eligible entity between the eligible entity and local governments within the jurisdiction of the eligible entity in the event of an incident involving those communications or data networks; (x) assess and mitigate, to the greatest degree possible, cybersecurity risks and cybersecurity threats relating to critical infrastructure and key resources, the degradation of which may impact the performance of information systems within the jurisdiction of the eligible entity; (xi) enhance capabilities to share cyber threat indicators and related information between the eligible entity and—(I) if the eligible entity is a State, local governments within the jurisdiction of the eligible entity, including by expanding information sharing agreements with the Department; and (II) the Department; (xii) leverage cybersecurity services offered by the Department; (xiii) implement an information technology and operational technology modernization cybersecurity review process that ensures alignment between information technology and operational technology cybersecurity objectives; (xiv) develop and coordinate strategies to address cybersecurity risks and cybersecurity threats in consultation with—(I) if the eligible entity is a State, local governments and associations of local governments within the jurisdiction of the eligible entity; and (II) as applicable—(aa) eligible entities that neighbor the jurisdiction of the eligible entity or, as appropriate, members of an Information Sharing and Analysis Organization; and (bb) countries that neighbor the jurisdiction of the eligible entity; (xv) ensure adequate access to, and participation in, the services and programs described in this subparagraph by rural areas within the jurisdiction of the eligible entity; and (xvi) distribute funds, items, services, capabilities, or activities to local governments under subsection (n)(2)(A), including the fraction of that distribution the eligible entity plans to distribute to rural areas under subsection (n)(2)(B); (C) assess the capabilities of the eligible entity relating to the actions described in subparagraph (B); (D) describe, as appropriate and to the extent practicable, the individual responsibilities of the eligible entity and local governments within the jurisdiction of the eligible entity in implementing the plan; (E) outline, to the extent practicable, the necessary resources and a timeline for implementing the plan; and (F) describe the metrics the eligible entity will use to measure progress towards—(i) implementing the plan; and (ii) reducing cybersecurity risks to, and identifying, responding to, and recovering from cybersecurity threats to, information systems owned or operated by, or on behalf of, the eligible entity or, if the eligible entity is a State, local governments within the jurisdiction of the eligible entity. (3) Discretionary elementsIn drafting a Cybersecurity Plan, an eligible entity may—(A) consult with the Multi-State Information Sharing and Analysis Center; (B) include a description of cooperative programs developed by groups of local governments within the jurisdiction of the eligible entity to address cybersecurity risks and cybersecurity threats; and (C) include a description of programs provided by the eligible entity to support local governments and owners and operators of critical infrastructure to address cybersecurity risks and cybersecurity threats.
(f) Multi-entity grants(1) In generalThe Secretary may award grants under this section to a multi-entity group to support multi-entity efforts to address cybersecurity risks and cybersecurity threats to information systems within the jurisdictions of the eligible entities that comprise the multi-entity group. (2) Satisfaction of other requirementsIn order to be eligible for a multi-entity grant under this subsection, each eligible entity that comprises a multi-entity group shall have—(A) a Cybersecurity Plan that has been reviewed by the Secretary in accordance with subsection (i); and (B) a cybersecurity planning committee established in accordance with subsection (g). (3) Application(A) In generalA multi-entity group applying for a multi-entity grant under paragraph (1) shall submit to the Secretary an application at such time, in such manner, and containing such information as the Secretary may require. (B) Multi-entity project planAn application for a grant under this section of a multi-entity group under subparagraph (A) shall include a plan describing—(i) the division of responsibilities among the eligible entities that comprise the multi-entity group; (ii) the distribution of funding from the grant among the eligible entities that comprise the multi-entity group; and (iii) how the eligible entities that comprise the multi-entity group will work together to implement the Cybersecurity Plan of each of those eligible entities.
(g) Planning committees(1) In generalAn eligible entity that receives a grant under this section shall establish a cybersecurity planning committee to—(A) assist with the development, implementation, and revision of the Cybersecurity Plan of the eligible entity; (B) approve the Cybersecurity Plan of the eligible entity; and (C) assist with the determination of effective funding priorities for a grant under this section in accordance with subsections (d) and (j). (2) CompositionA committee of an eligible entity established under paragraph (1) shall—(A) be comprised of representatives from—(i) the eligible entity; (ii) if the eligible entity is a State, counties, cities, and towns within the jurisdiction of the eligible entity; and (iii) institutions of public education and health within the jurisdiction of the eligible entity; and (B) include, as appropriate, representatives of rural, suburban, and high-population jurisdictions. (3) Cybersecurity expertiseNot less than one-half of the representatives of a committee established under paragraph (1) shall have professional experience relating to cybersecurity or information technology. (4) Rule of construction regarding existing planning committeesNothing in this subsection shall be construed to require an eligible entity to establish a cybersecurity planning committee if the eligible entity has established and uses a multijurisdictional planning committee or commission that—(A) meets the requirements of this subsection; or (B) may be expanded or leveraged to meet the requirements of this subsection, including through the formation of a cybersecurity planning subcommittee. (5) Rule of construction regarding control of information systems of eligible entitiesNothing in this subsection shall be construed to permit a cybersecurity planning committee of an eligible entity that meets the requirements of this subsection to make decisions relating to information systems owned or operated by, or on behalf of, the eligible entity.
(h) Special rule for Tribal governmentsWith respect to any requirement under subsection (e) or (g), the Secretary, in consultation with the Secretary of the Interior and Tribal governments, may prescribe an alternative substantively similar requirement for Tribal governments if the Secretary finds that the alternative requirement is necessary for the effective delivery and administration of grants to Tribal governments under this section.
(i) Review of plans(1) Review as condition of grant(A) In generalSubject to paragraph (3), before an eligible entity may receive a grant under this section, the Secretary, acting through the Director, shall—(i) review the Cybersecurity Plan of the eligible entity, including any revised Cybersecurity Plans of the eligible entity; and (ii) determine that the Cybersecurity Plan reviewed under clause (i) satisfies the requirements under paragraph (2). (B) Duration of determinationIn the case of a determination under subparagraph (A)(ii) that a Cybersecurity Plan satisfies the requirements under paragraph (2), the determination shall be effective for the 2-year period beginning on the date of the determination. (C) Annual renewalNot later than 2 years after the date on which the Secretary determines under subparagraph (A)(ii) that a Cybersecurity Plan satisfies the requirements under paragraph (2), and annually thereafter, the Secretary, acting through the Director, shall—(i) determine whether the Cybersecurity Plan and any revisions continue to meet the criteria described in paragraph (2); and (ii) renew the determination if the Secretary, acting through the Director, makes a positive determination under clause (i). (2) Plan requirementsIn reviewing a Cybersecurity Plan of an eligible entity under this subsection, the Secretary, acting through the Director, shall ensure that the Cybersecurity Plan—(A) satisfies the requirements of subsection (e)(2); and (B) has been approved by—(i) the cybersecurity planning committee of the eligible entity established under subsection (g); and (ii) the Chief Information Officer, the Chief Information Security Officer, or an equivalent official of the eligible entity. (3) ExceptionNotwithstanding subsection (e) and paragraph (1) of this subsection, the Secretary may award a grant under this section to an eligible entity that does not submit a Cybersecurity Plan to the Secretary for review before September 30, 2023, if the eligible entity certifies to the Secretary that—(A) the activities that will be supported by the grant are—(i) integral to the development of the Cybersecurity Plan of the eligible entity; or (ii) necessary to assist with activities described in subsection (d)(4), as confirmed by the Director; and (B) the eligible entity will submit to the Secretary a Cybersecurity Plan for review under this subsection by September 30, 2023. (4) Rule of constructionNothing in this subsection shall be construed to provide authority to the Secretary to—(A) regulate the manner by which an eligible entity or local government improves the cybersecurity of the information systems owned or operated by, or on behalf of, the eligible entity or local government; or (B) condition the receipt of grants under this section on—(i) participation in a particular Federal program; or (ii) the use of a specific product or technology.
(j) Limitations on uses of funds(1) In generalAny entity that receives funds from a grant under this section may not use the grant—(A) to supplant State or local funds; (B) for any recipient cost-sharing contribution; (C) to pay a ransom; (D) for recreational or social purposes; or (E) for any purpose that does not address cybersecurity risks or cybersecurity threats on information systems owned or operated by, or on behalf of, the eligible entity that receives the grant or a local government within the jurisdiction of the eligible entity. (2) Compliance oversightIn addition to any other remedy available, the Secretary may take such actions as are necessary to ensure that a recipient of a grant under this section uses the grant for the purposes for which the grant is awarded. (3) Rule of constructionNothing in paragraph (1)(A) shall be construed to prohibit the use of funds from a grant under this section awarded to a State, local, or Tribal government for otherwise permissible uses under this section on the basis that the State, local, or Tribal government has previously used State, local, or Tribal funds to support the same or similar uses.
(k) Opportunity to amend applicationsIn considering applications for grants under this section, the Secretary shall provide applicants with a reasonable opportunity to correct any defects in those applications before making final awards, including by allowing applicants to revise a submitted Cybersecurity Plan.
(l) ApportionmentFor fiscal year 2022 and each fiscal year thereafter, the Secretary shall apportion amounts appropriated to carry out this section among eligible entities as follows:(1) Baseline amountThe Secretary shall first apportion—(A) 0.25 percent of such amounts to each of American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands; (B) 1 percent of such amounts to each of the remaining States; and (C) 3 percent of such amounts to Tribal governments. (2) RemainderThe Secretary shall apportion the remainder of such amounts to States as follows:(A) 50 percent of such remainder in the ratio that the population of each State, bears to the population of all States; and (B) 50 percent of such remainder in the ratio that the population of each State that resides in rural areas, bears to the population of all States that resides in rural areas. (3) Apportionment among Tribal governmentsIn determining how to apportion amounts to Tribal governments under paragraph (1)(C), the Secretary shall consult with the Secretary of the Interior and Tribal governments. (4) Multi-entity grantsAn amount received from a multi-entity grant awarded under subsection (f)(1) by a State or Tribal government that is a member of the multi-entity group shall qualify as an apportionment for the purpose of this subsection.
(m) Federal share(1) In generalThe Federal share of the cost of an activity carried out using funds made available with a grant under this section may not exceed—(A) in the case of a grant to an eligible entity—(i) for fiscal year 2022, 90 percent; (ii) for fiscal year 2023, 80 percent; (iii) for fiscal year 2024, 70 percent; and (iv) for fiscal year 2025, 60 percent; and (B) in the case of a grant to a multi-entity group—(i) for fiscal year 2022, 100 percent; (ii) for fiscal year 2023, 90 percent; (iii) for fiscal year 2024, 80 percent; and (iv) for fiscal year 2025, 70 percent. (2) Waiver(A) In generalThe Secretary may waive or modify the requirements of paragraph (1) if an eligible entity or multi-entity group demonstrates economic hardship. (B) GuidelinesThe Secretary shall establish and publish guidelines for determining what constitutes economic hardship for the purposes of this subsection. (C) ConsiderationsIn developing guidelines under subparagraph (B), the Secretary shall consider, with respect to the jurisdiction of an eligible entity—(i) changes in rates of unemployment in the jurisdiction from previous years; (ii) changes in the percentage of individuals who are eligible to receive benefits under the supplemental nutrition assistance program established under the Food and Nutrition Act of 2008 (7 U.S.C. 2011 et seq.) from previous years; and (iii) any other factors the Secretary considers appropriate. (3) Waiver for Tribal governmentsNotwithstanding paragraph (2), the Secretary, in consultation with the Secretary of the Interior and Tribal governments, may waive or modify the requirements of paragraph (1) for 1 or more Tribal governments if the Secretary determines that the waiver is in the public interest.
(n) Responsibilities of grantees(1) CertificationEach eligible entity or multi-entity group that receives a grant under this section shall certify to the Secretary that the grant will be used—(A) for the purpose for which the grant is awarded; and (B) in compliance with subsections (d) and (j). (2) Availability of funds to local governments and rural areas(A) In generalSubject to subparagraph (C), not later than 45 days after the date on which an eligible entity or multi-entity group receives a grant under this section, the eligible entity or multi-entity group shall, without imposing unreasonable or unduly burdensome requirements as a condition of receipt, obligate or otherwise make available to local governments within the jurisdiction of the eligible entity or the eligible entities that comprise the multi-entity group, consistent with the Cybersecurity Plan of the eligible entity or the Cybersecurity Plans of the eligible entities that comprise the multi-entity group—(i) not less than 80 percent of funds available under the grant; (ii) with the consent of the local governments, items, services, capabilities, or activities having a value of not less than 80 percent of the amount of the grant; or (iii) with the consent of the local governments, grant funds combined with other items, services, capabilities, or activities having the total value of not less than 80 percent of the amount of the grant. (B) Availability to rural areasIn obligating funds, items, services, capabilities, or activities to local governments under subparagraph (A), the eligible entity or eligible entities that comprise the multi-entity group shall ensure that rural areas within the jurisdiction of the eligible entity or the eligible entities that comprise the multi-entity group receive not less than—(i) 25 percent of the amount of the grant awarded to the eligible entity; (ii) items, services, capabilities, or activities having a value of not less than 25 percent of the amount of the grant awarded to the eligible entity; or (iii) grant funds combined with other items, services, capabilities, or activities having the total value of not less than 25 percent of the grant awarded to the eligible entity. (C) ExceptionsThis paragraph shall not apply to—(i) any grant awarded under this section that solely supports activities that are integral to the development or revision of the Cybersecurity Plan of the eligible entity; or (ii) the District of Columbia, the Commonwealth of Puerto Rico, American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, the United States Virgin Islands, or a Tribal government. (3) Certifications regarding distribution of grant funds to local governmentsAn eligible entity or multi-entity group shall certify to the Secretary that the eligible entity or multi-entity group has made the distribution to local governments required under paragraph (2). (4) Extension of period(A) In generalAn eligible entity or multi-entity group may request in writing that the Secretary extend the period of time specified in paragraph (2) for an additional period of time. (B) ApprovalThe Secretary may approve a request for an extension under subparagraph (A) if the Secretary determines the extension is necessary to ensure that the obligation and expenditure of grant funds align with the purpose of the State and Local Cybersecurity Grant Program. (5) Direct fundingIf an eligible entity does not make a distribution to a local government required under paragraph (2) in a timely fashion, the local government may petition the Secretary to request the Secretary to provide funds directly to the local government. (6) Limitation on constructionA grant awarded under this section may not be used to acquire land or to construct, remodel, or perform alterations of buildings or other physical facilities. (7) Consultation in allocating fundsAn eligible entity applying for a grant under this section shall agree to consult the Chief Information Officer, the Chief Information Security Officer, or an equivalent official of the eligible entity in allocating funds from a grant awarded under this section. (8) PenaltiesIn addition to other remedies available to the Secretary, if an eligible entity violates a requirement of this subsection, the Secretary may—(A) terminate or reduce the amount of a grant awarded under this section to the eligible entity; or (B) distribute grant funds previously awarded to the eligible entity—(i) in the case of an eligible entity that is a State, directly to the appropriate local government as a replacement grant in an amount determined by the Secretary; or (ii) in the case of an eligible entity that is a Tribal government, to another Tribal government or Tribal governments as a replacement grant in an amount determined by the Secretary.
(o) Consultation with State, local, and Tribal representativesIn carrying out this section, the Secretary shall consult with State, local, and Tribal representatives with professional experience relating to cybersecurity, including representatives of associations representing State, local, and Tribal governments, to inform—(1) guidance for applicants for grants under this section, including guidance for Cybersecurity Plans; (2) the study of risk-based formulas required under subsection (q)(4); (3) the development of guidelines required under subsection (m)(2)(B); and (4) any modifications described in subsection (q)(2)(D).
(p) Notification to CongressNot later than 3 business days before the date on which the Department announces the award of a grant to an eligible entity under this section, including an announcement to the eligible entity, the Secretary shall provide to the appropriate congressional committees notice of the announcement.
(q) Reports, study, and review(1) Annual reports by grant recipients(A) In generalNot later than 1 year after the date on which an eligible entity receives a grant under this section for the purpose of implementing the Cybersecurity Plan of the eligible entity, including an eligible entity that comprises a multi-entity group that receives a grant for that purpose, and annually thereafter until 1 year after the date on which funds from the grant are expended or returned, the eligible entity shall submit to the Secretary a report that, using the metrics described in the Cybersecurity Plan of the eligible entity, describes the progress of the eligible entity in—(i) implementing the Cybersecurity Plan of the eligible entity; and (ii) reducing cybersecurity risks to, and identifying, responding to, and recovering from cybersecurity threats to, information systems owned or operated by, or on behalf of, the eligible entity or, if the eligible entity is a State, local governments within the jurisdiction of the eligible entity. (B) Absence of planNot later than 1 year after the date on which an eligible entity that does not have a Cybersecurity Plan receives funds under this section, and annually thereafter until 1 year after the date on which funds from the grant are expended or returned, the eligible entity shall submit to the Secretary a report describing how the eligible entity obligated and expended grant funds to—(i) develop or revise a Cybersecurity Plan; or (ii) assist with the activities described in subsection (d)(4). (2) Annual reports to CongressNot less frequently than annually, the Secretary, acting through the Director, shall submit to Congress a report on—(A) the use of grants awarded under this section; (B) the proportion of grants used to support cybersecurity in rural areas; (C) the effectiveness of the State and Local Cybersecurity Grant Program; (D) any necessary modifications to the State and Local Cybersecurity Grant Program; and (E) any progress made toward—(i) developing, implementing, or revising Cybersecurity Plans; and (ii) reducing cybersecurity risks to, and identifying, responding to, and recovering from cybersecurity threats to, information systems owned or operated by, or on behalf of, State, local, or Tribal governments as a result of the award of grants under this section. (3) Public availability(A) In generalThe Secretary, acting through the Director, shall make each report submitted under paragraph (2) publicly available, including by making each report available on the website of the Agency. (B) RedactionsIn making each report publicly available under subparagraph (A), the Director may make redactions that the Director, in consultation with each eligible entity, determines necessary to protect classified or other information exempt from disclosure under section 552 of title 5 (commonly referred to as the “Freedom of Information Act”). (4) Study of risk-based formulas(A) In generalNot later than September 30, 2024, the Secretary, acting through the Director, shall submit to the appropriate congressional committees a study and legislative recommendations on the potential use of a risk-based formula for apportioning funds under this section, including—(i) potential components that could be included in a risk-based formula, including the potential impact of those components on support for rural areas under this section; (ii) potential sources of data and information necessary for the implementation of a risk-based formula; (iii) any obstacles to implementing a risk-based formula, including obstacles that require a legislative solution; (iv) if a risk-based formula were to be implemented for fiscal year 2026, a recommended risk-based formula for the State and Local Cybersecurity Grant Program; and (v) any other information that the Secretary, acting through the Director, determines necessary to help Congress understand the progress towards, and obstacles to, implementing a risk-based formula. (B) Inapplicability of Paperwork Reduction ActThe requirements of chapter 35 of title 44 (commonly referred to as the “Paperwork Reduction Act”), shall not apply to any action taken to carry out this paragraph. (5) Tribal cybersecurity needs reportNot later than 2 years after November 15, 2021, the Secretary, acting through the Director, shall submit to Congress a report that—(A) describes the cybersecurity needs of Tribal governments, which shall be determined in consultation with the Secretary of the Interior and Tribal governments; and (B) includes any recommendations for addressing the cybersecurity needs of Tribal governments, including any necessary modifications to the State and Local Cybersecurity Grant Program to better serve Tribal governments. (6) GAO reviewNot later than 3 years after November 15, 2021, the Comptroller General of the United States shall conduct a review of the State and Local Cybersecurity Grant Program, including—(A) the grant selection process of the Secretary; and (B) a sample of grants awarded under this section.
(r) Authorization of appropriations(1) In generalThere are authorized to be appropriated for activities under this section—(A) for fiscal year 2022, $200,000,000; (B) for fiscal year 2023, $400,000,000; (C) for fiscal year 2024, $300,000,000; and (D) for fiscal year 2025, $100,000,000. (2) Transfers authorized(A) In generalDuring a fiscal year, the Secretary or the head of any component of the Department that administers the State and Local Cybersecurity Grant Program may transfer not more than 5 percent of the amounts appropriated pursuant to paragraph (1) or other amounts appropriated to carry out the State and Local Cybersecurity Grant Program for that fiscal year to an account of the Department for salaries, expenses, and other administrative costs incurred for the management, administration, or evaluation of this section. (B) Additional appropriationsAny funds transferred under subparagraph (A) shall be in addition to any funds appropriated to the Department or the components described in subparagraph (A) for salaries, expenses, and other administrative costs.
(s) Termination(1) In generalSubject to paragraph (2), the requirements of this section shall terminate on September 30, 2026. (2) ExceptionThe reporting requirements under subsection (q) shall terminate on the date that is 1 year after the date on which the final funds from a grant under this section are expended or returned.
6 U.S.C. § 665h National Cyber Exercise Program
(a) Establishment of program(1) In generalThere is established in the Agency the National Cyber Exercise Program (referred to in this section as the “Exercise Program”) to evaluate the National Cyber Incident Response Plan, and other related plans and strategies. (2) Requirements(A) In generalThe Exercise Program shall be—(i) based on current risk assessments, including credible threats, vulnerabilities, and consequences; (ii) designed, to the extent practicable, to simulate the partial or complete incapacitation of a government or critical infrastructure network resulting from a cyber incident; (iii) designed to provide for the systematic evaluation of cyber readiness and enhance operational understanding of the cyber incident response system and relevant information sharing agreements; and (iv) designed to promptly develop after-action reports and plans that can quickly incorporate lessons learned into future operations. (B) Model exercise selectionThe Exercise Program shall—(i) include a selection of model exercises that government and private entities can readily adapt for use; and (ii) aid such governments and private entities with the design, implementation, and evaluation of exercises that—(I) conform to the requirements described in subparagraph (A); (II) are consistent with any applicable national, State, local, or Tribal strategy or plan; and (III) provide for systematic evaluation of readiness. (3) ConsultationIn carrying out the Exercise Program, the Director may consult with appropriate representatives from Sector Risk Management Agencies, the Office of the National Cyber Director, cybersecurity research stakeholders, and Sector Coordinating Councils.
(b) DefinitionsIn this section:(1) StateThe term “State” means any State of the United States, the District of Columbia, the Commonwealth of Puerto Rico, the Northern Mariana Islands, the United States Virgin Islands, Guam, American Samoa, and any other territory or possession of the United States. (2) Private entityThe term “private entity” has the meaning given such term in section 1501 of this title.
(c) Rule of constructionNothing in this section shall be construed to affect the authorities or responsibilities of the Administrator of the Federal Emergency Management Agency pursuant to section 748 of this title.
6 U.S.C. § 665i CyberSentry program
(a) EstablishmentThere is established in the Agency a program, to be known as “CyberSentry”, to provide continuous monitoring and detection of cybersecurity risks to critical infrastructure entities that own or operate industrial control systems that support national critical functions, upon request and subject to the consent of such owner or operator.
(b) ActivitiesThe Director, through CyberSentry, shall—(1) enter into strategic partnerships with critical infrastructure owners and operators that, in the determination of the Director and subject to the availability of resources, own or operate regionally or nationally significant industrial control systems that support national critical functions, in order to provide technical assistance in the form of continuous monitoring of industrial control systems and the information systems that support such systems and detection of cybersecurity risks to such industrial control systems and other cybersecurity services, as appropriate, based on and subject to the agreement and consent of such owner or operator; (2) leverage sensitive or classified intelligence about cybersecurity risks regarding particular sectors, particular adversaries, and trends in tactics, techniques, and procedures to advise critical infrastructure owners and operators regarding mitigation measures and share information as appropriate; (3) identify cybersecurity risks in the information technology and information systems that support industrial control systems which could be exploited by adversaries attempting to gain access to such industrial control systems, and work with owners and operators to remediate such vulnerabilities; (4) produce aggregated, anonymized analytic products, based on threat hunting and continuous monitoring and detection activities and partnerships, with findings and recommendations that can be disseminated to critical infrastructure owners and operators; and (5) support activities authorized in accordance with section 1501 of the National Defense Authorization Act for Fiscal Year 2022.
(c) Privacy reviewNot later than 180 days after December 27, 2021, the Privacy Officer of the Agency under section 652(h) of this title shall—(1) review the policies, guidelines, and activities of CyberSentry for compliance with all applicable privacy laws, including such laws governing the acquisition, interception, retention, use, and disclosure of communities; and (2) submit to the Committee on Homeland Security of the House of Representatives and the Committee on Homeland Security and Governmental Affairs of the Senate a report certifying compliance with all applicable privacy laws as referred to in paragraph (1), or identifying any instances of noncompliance with such privacy laws.
(d) Report to CongressNot later than one year after December 27, 2021, the Director shall provide to the Committee on Homeland Security of the House of Representatives and the Committee on Homeland Security and Governmental Affairs of the Senate a briefing and written report on implementation of this section.
(e) SavingsNothing in this section may be construed to permit the Federal Government to gain access to information of a remote computing service provider to the public or an electronic service provider to the public, the disclosure of which is not permitted under section 2702 of title 18.
(f) DefinitionIn this section, the term “industrial control system” means an information system used to monitor and/or control industrial processes such as manufacturing, product handling, production, and distribution, including supervisory control and data acquisition (SCADA) systems used to monitor and/or control geographically dispersed assets, distributed control systems (DCSs), Human-Machine Interfaces (HMIs), and programmable logic controllers that control localized processes.
(g) TerminationThe authority to carry out a program under this section shall terminate on the date that is seven years after December 27, 2021.
6 U.S.C. § 665j Ransomware threat mitigation activities
(a) Joint Ransomware Task Force(1) In generalNot later than 180 days after March 15, 2022, the Director, in consultation with the National Cyber Director, the Attorney General, and the Director of the Federal Bureau of Investigation, shall establish and chair the Joint Ransomware Task Force to coordinate an ongoing nationwide campaign against ransomware attacks, and identify and pursue opportunities for international cooperation. (2) CompositionThe Joint Ransomware Task Force shall consist of participants from Federal agencies, as determined appropriate by the National Cyber Director in consultation with the Secretary of Homeland Security. (3) ResponsibilitiesThe Joint Ransomware Task Force, utilizing only existing authorities of each participating Federal agency, shall coordinate across the Federal Government the following activities:(A) Prioritization of intelligence-driven operations to disrupt specific ransomware actors. (B) Consult with relevant private sector, State, local, Tribal, and territorial governments and international stakeholders to identify needs and establish mechanisms for providing input into the Joint Ransomware Task Force. (C) Identifying, in consultation with relevant entities, a list of highest threat ransomware entities updated on an ongoing basis, in order to facilitate—(i) prioritization for Federal action by appropriate Federal agencies; and (ii) identify 11 So in original. metrics for success of said actions. (D) Disrupting ransomware criminal actors, associated infrastructure, and their finances. (E) Facilitating coordination and collaboration between Federal entities and relevant entities, including the private sector, to improve Federal actions against ransomware threats. (F) Collection, sharing, and analysis of ransomware trends to inform Federal actions. (G) Creation of after-action reports and other lessons learned from Federal actions that identify successes and failures to improve subsequent actions. (H) Any other activities determined appropriate by the Joint Ransomware Task Force to mitigate the threat of ransomware attacks.
(b) Rule of constructionNothing in this section shall be construed to provide any additional authority to any Federal agency.
6 U.S.C. § 665k Federal Clearinghouse on School Safety Evidence-based Practices
(a) Establishment(1) In generalThe Secretary, in coordination with the Secretary of Education, the Attorney General, and the Secretary of Health and Human Services, shall establish a Federal Clearinghouse on School Safety Evidence-based Practices (in this section referred to as the “Clearinghouse”) within the Department. (2) PurposeThe Clearinghouse shall serve as a Federal resource to identify and publish online through SchoolSafety.gov, or any successor website, evidence-based practices and recommendations to improve school safety for use by State and local educational agencies, institutions of higher education, State and local law enforcement agencies, health professionals, and the general public. (3) Personnel(A) AssignmentsThe Clearinghouse shall be assigned such personnel and resources as the Secretary considers appropriate to carry out this section. (B) DetaileesThe Secretary of Education, the Attorney General, and the Secretary of Health and Human Services may detail personnel to the Clearinghouse. (4) Exemptions(A) Paperwork Reduction ActChapter 35 of title 44 (commonly known as the “Paperwork Reduction Act”), shall not apply to any rulemaking or information collection required under this section. (B) Federal Advisory Committee ActThe Federal Advisory Committee Act (5 U.S.C. App.) 11 See References in Text note below. shall not apply for the purposes of carrying out this section.
(b) Clearinghouse contents(1) ConsultationIn identifying the evidence-based practices and recommendations for the Clearinghouse, the Secretary shall—(A) consult with appropriate Federal, State, local, Tribal, private sector, and nongovernmental organizations, including civil rights and disability rights organizations; and (B) consult with the Secretary of Education to ensure that evidence-based practices published by the Clearinghouse are aligned with evidence-based practices to support a positive and safe learning environment for all students. (2) Criteria for evidence-based practices and recommendationsThe evidence-based practices and recommendations of the Clearinghouse shall—(A) include comprehensive evidence-based school safety measures; (B) include the evidence or research rationale supporting the determination of the Clearinghouse that the evidence-based practice or recommendation under subparagraph (A) has been shown to have a significant effect on improving the health, safety, and welfare of persons in school settings, including—(i) relevant research that is evidence-based, as defined in section 7801 of title 20, supporting the evidence-based practice or recommendation; (ii) findings and data from previous Federal or State commissions recommending improvements to the safety posture of a school; or (iii) other supportive evidence or findings relied upon by the Clearinghouse in determining evidence-based practices and recommendations, as determined in consultation with the officers described in subsection (a)(3)(B); (C) include information on Federal programs for which implementation of each evidence-based practice or recommendation is an eligible use for the program; (D) be consistent with Federal civil rights laws, including title II of the Americans with Disabilities Act of 1990 (42 U.S.C. 12131 et seq.), the Rehabilitation Act of 1973 (29 U.S.C. 701 et seq.), and title VI of the Civil Rights Act of 1964 (42 U.S.C. 2000d et seq.); and (E) include options for developmentally appropriate recommendations for use in educational settings with respect to children’s ages and physical, social, sensory, and emotionally developmental statuses. (3) Past commission recommendationsThe Clearinghouse shall present, as determined in consultation with the officers described in subsection (a)(3)(B), Federal, State, local, Tribal, private sector, and nongovernmental organization issued best practices and recommendations and identify any best practice or recommendation of the Clearinghouse that was previously issued by any such organization or commission.
(c) Assistance and trainingThe Secretary may produce and publish materials on the Clearinghouse to assist and train educational agencies and law enforcement agencies on the implementation of the evidence-based practices and recommendations.
(d) Continuous improvementThe Secretary shall—(1) collect for the purpose of continuous improvement of the Clearinghouse—(A) Clearinghouse data analytics; (B) user feedback on the implementation of resources, evidence-based practices, and recommendations identified by the Clearinghouse; and (C) any evaluations conducted on implementation of the evidence-based practices and recommendations of the Clearinghouse; and (2) in coordination with the Secretary of Education, the Secretary of Health and Human Services, and the Attorney General—(A) regularly assess and identify Clearinghouse evidence-based practices and recommendations for which there are no resources available through Federal Government programs for implementation; and (B) establish an external advisory board, which shall be comprised of appropriate State, local, Tribal, private sector, and nongovernmental organizations, including organizations representing parents of elementary and secondary school students, representative 22 So in original. Probably should be “representatives”. from civil rights organizations, representatives of disability rights organizations, representatives of educators, representatives of law enforcement, and nonprofit school safety and security organizations, to—(i) provide feedback on the implementation of evidence-based practices and recommendations of the Clearinghouse; and (ii) propose additional recommendations for evidence-based practices for inclusion in the Clearinghouse that meet the requirements described in subsection (b)(2)(B).
(e) Parental assistanceThe Clearinghouse shall produce materials in accessible formats to assist parents and legal guardians of students with identifying relevant Clearinghouse resources related to supporting the implementation of Clearinghouse evidence-based practices and recommendations.
6 U.S.C. § 665l School and daycare protection
(a) In generalNot later than 180 days after December 23, 2022, and annually thereafter, the Secretary of Homeland Security shall submit to the Committee on Homeland Security of the House of Representatives and the Committee on Homeland Security and Governmental Affairs of the Senate a report regarding the following:(1) The Department of Homeland Security’s activities, policies, and plans to enhance the security of early childhood education programs, elementary schools, and secondary schools during the preceding year that includes information on the Department’s activities through the Federal School Safety Clearinghouse. (2) Information on all structures or efforts within the Department intended to bolster coordination among departmental components and offices involved in carrying out paragraph (1) and, with respect to each structure or effort, specificity on which components and offices are involved and which component or office leads such structure or effort. (3) A detailed description of the measures used to ensure privacy rights, civil rights, and civil liberties protections in carrying out these activities.
(b) BriefingNot later than 30 days after the submission of each report required under subsection (a), the Secretary of Homeland Security shall provide to the Committee on Homeland Security and Governmental Affairs of the Senate and the Committee on Homeland Security of the House of Representatives a briefing regarding such report and the status of efforts to carry out plans included in such report for the preceding year.
(c) DefinitionsIn this section, the terms “early childhood education program”, “elementary school”, and “secondary school” have the meanings given such terms in section 7801 of title 20.
6 U.S.C. § 665m President’s Cup Cybersecurity Competition
(a) In generalThe Director of the Cybersecurity and Infrastructure Security Agency (in this section referred to as the “Director”) of the Department of Homeland Security is authorized to hold an annual cybersecurity competition to be known as the “Department of Homeland Security Cybersecurity and Infrastructure Security Agency’s President’s Cup Cybersecurity Competition” (in this section referred to as the “competition”) for the purpose of identifying, challenging, and competitively awarding prizes, including cash prizes, to the United States Government’s best cybersecurity practitioners and teams across offensive and defensive cybersecurity disciplines.
(b) EligibilityTo be eligible to participate in the competition, an individual shall be a Federal civilian employee or member of the uniformed services (as such term is defined in section 2101(3) of title 5) and shall comply with any rules promulgated by the Director regarding the competition.
(c) Competition administrationThe Director may enter into a grant, contract, cooperative agreement, or other agreement with a private sector for-profit or nonprofit entity or State or local government agency to administer the competition.
(d) Competition parametersEach competition shall incorporate the following elements:(1) Cybersecurity skills outlined in the National Initiative for Cybersecurity Education Framework, or any successor framework. (2) Individual and team events. (3) Categories demonstrating offensive and defensive cyber operations, such as software reverse engineering and exploitation, network operations, forensics, big data analysis, cyber analysis, cyber defense, cyber exploitation, secure programming, obfuscated coding, or cyber-physical systems. (4) Any other elements related to paragraphs (1), (2), or (3), as determined necessary by the Director.
(e) Use of funds(1) In generalIn order to further the goals and objectives of the competition, the Director may use amounts made available to the Director for the competition for reasonable expenses for the following:(A) Advertising, marketing, and promoting the competition. (B) Meals for participants and organizers of the competition if attendance at the meal during the competition is necessary to maintain the integrity of the competition. (C) Promotional items, including merchandise and apparel. (D) Consistent with section 4503 of title 5, necessary expenses for the honorary recognition of competition participants, including members of the uniformed services. (E) Monetary and nonmonetary awards for competition participants, including members of the uniformed services, subject to subsection (f). (2) ApplicationThis subsection shall apply to amounts appropriated on or after December 23, 2022.
(f) Prize limitation(1) Awards by the DirectorThe Director may make one or more awards per competition, except that the amount or value of each shall not exceed $10,000. (2) Awards by the Secretary of Homeland SecurityThe Secretary of Homeland Security may make one or more awards per competition, except the amount or the value of each shall not exceed $25,000. (3) Regular payA monetary award under this section shall be in addition to the regular pay of the recipient. (4) Overall yearly award limitThe total amount or value of awards made under this Act 11 So in original. Probably should refer to “this section”. See References in Text note below. during a fiscal year may not exceed $100,000.
(g) Reporting requirementsThe Director shall annually provide to the Committee on Homeland Security of the House of Representatives and the Committee on Homeland Security and Governmental Affairs of the Senate a report that includes the following with respect to each competition conducted in the preceding year:(1) A description of available amounts. (2) A description of authorized expenditures. (3) Information relating to participation. (4) Information relating to lessons learned, and how such lessons may be applied to improve cybersecurity operations and recruitment of the Cybersecurity and Infrastructure Security Agency of the Department of Homeland Security.
6 U.S.C. § 665n Industrial Control Systems Cybersecurity Training Initiative
(a) Establishment(1) In generalThe Industrial Control Systems Cybersecurity Training Initiative (in this section referred to as the “Initiative”) is established within the Agency. (2) PurposeThe purpose of the Initiative is to develop and strengthen the skills of the cybersecurity workforce related to securing industrial control systems.
(b) RequirementsIn carrying out the Initiative, the Director shall—(1) ensure the Initiative includes—(A) virtual and in-person trainings and courses provided at no cost to participants; (B) trainings and courses available at different skill levels, including introductory level courses; (C) trainings and courses that cover cyber defense strategies for industrial control systems, including an understanding of the unique cyber threats facing industrial control systems and the mitigation of security vulnerabilities in industrial control systems technology; and (D) appropriate consideration regarding the availability of trainings and courses in different regions of the United States; and 11 So in original. The word “and” probably should not appear. (2) engage in—(A) collaboration with the National Laboratories of the Department of Energy in accordance with section 189 of this title; (B) consultation with Sector Risk Management Agencies;22 So in original. Probably should be followed by “and”. (C) as appropriate, consultation with private sector entities with relevant expertise, such as vendors of industrial control systems technologies; and (3) consult, to the maximum extent practicable, with commercial training providers and academia to minimize the potential for duplication of other training opportunities.
(c) Reports(1) In generalNot later than one year after December 23, 2022, and annually thereafter, the Director shall submit to the Committee on Homeland Security of the House of Representatives and the Committee on Homeland Security and Governmental Affairs of the Senate a report on the Initiative. (2) ContentsEach report submitted under paragraph (1) shall include the following:(A) A description of the courses provided under the Initiative. (B) A description of outreach efforts to raise awareness of the availability of such courses. (C) The number of participants in each course. (D) Voluntarily provided information on the demographics of participants in such courses, including by sex, race, and place of residence. (E) Information on the participation in such courses of workers from each critical infrastructure sector. (F) Plans for expanding access to industrial control systems education and training, including expanding access to women and underrepresented populations, and expanding access to different regions of the United States. (G) Recommendations regarding how to strengthen the state of industrial control systems cybersecurity education and training.
6 U.S.C. § 671 Definitions
In this part:
(1) AgencyThe term “agency” has the meaning given it in section 551 of title 5.
(2) Covered Federal agencyThe term “covered Federal agency” means the Department of Homeland Security.
(3) Critical infrastructure informationThe term “critical infrastructure information” has the meaning given the term in section 650 of this title.
(4) Critical infrastructure protection programThe term “critical infrastructure protection program” means any component or bureau of a covered Federal agency that has been designated by the President or any agency head to receive critical infrastructure information.
(5) Protected systemThe term “protected system”—(A) means any service, physical or computer-based system, process, or procedure that directly or indirectly affects the viability of a facility of critical infrastructure; and (B) includes any physical or computer-based system, including a computer, computer system, computer or communications network, or any component hardware or element thereof, software program, processing instructions, or information or data in transmission or storage therein, irrespective of the medium of transmission or storage.
(6) Voluntary(A) In generalThe term “voluntary”, in the case of any submittal of critical infrastructure information to a covered Federal agency, means the submittal thereof in the absence of such agency’s exercise of legal authority to compel access to or submission of such information and may be accomplished by a single entity or an Information Sharing and Analysis Organization on behalf of itself or its members. (B) ExclusionsThe term “voluntary”—(i) in the case of any action brought under the securities laws as is defined in section 78c(a)(47) of title 15—(I) does not include information or statements contained in any documents or materials filed with the Securities and Exchange Commission, or with Federal banking regulators, pursuant to section 78l(i) of title 15; and (II) with respect to the submittal of critical infrastructure information, does not include any disclosure or writing that when made accompanied the solicitation of an offer or a sale of securities; and (ii) does not include information or statements submitted or relied upon as a basis for making licensing or permitting determinations, or during regulatory proceedings.
6 U.S.C. § 672 Designation of critical infrastructure protection program
A critical infrastructure protection program may be designated as such by one of the following:
(1) The President.
(2) The Secretary of Homeland Security.
6 U.S.C. § 673 Protection of voluntarily shared critical infrastructure information
(a) Protection(1) In generalNotwithstanding any other provision of law, critical infrastructure information (including the identity of the submitting person or entity) that is voluntarily submitted to a covered Federal agency for use by that agency regarding the security of critical infrastructure and protected systems, analysis, warning, interdependency study, recovery, reconstitution, or other informational purpose, when accompanied by an express statement specified in paragraph (2)—(A) shall be exempt from disclosure under section 552 of title 5 (commonly referred to as the Freedom of Information Act); (B) shall not be subject to any agency rules or judicial doctrine regarding ex parte communications with a decision making official; (C) shall not, without the written consent of the person or entity submitting such information, be used directly by such agency, any other Federal, State, or local authority, or any third party, in any civil action arising under Federal or State law if such information is submitted in good faith; (D) shall not, without the written consent of the person or entity submitting such information, be used or disclosed by any officer or employee of the United States for purposes other than the purposes of this part, except—(i) in furtherance of an investigation or the prosecution of a criminal act; or (ii) when disclosure of the information would be—(I) to either House of Congress, or to the extent of matter within its jurisdiction, any committee or subcommittee thereof, any joint committee thereof or subcommittee of any such joint committee; or (II) to the Comptroller General, or any authorized representative of the Comptroller General, in the course of the performance of the duties of the Government Accountability Office.11 So in original. The period probably should be a semicolon. (E) shall not, if provided to a State or local government or government agency—(i) be made available pursuant to any State or local law requiring disclosure of information or records; (ii) otherwise be disclosed or distributed to any party by said State or local government or government agency without the written consent of the person or entity submitting such information; or (iii) be used other than for the purpose of protecting critical infrastructure or protected systems, or in furtherance of an investigation or the prosecution of a criminal act; and (F) does not constitute a waiver of any applicable privilege or protection provided under law, such as trade secret protection. (2) Express statementFor purposes of paragraph (1), the term “express statement”, with respect to information or records, means—(A) in the case of written information or records, a written marking on the information or records substantially similar to the following: “This information is voluntarily submitted to the Federal Government in expectation of protection from disclosure as provided by the provisions of the Critical Infrastructure Information Act of 2002.”; or (B) in the case of oral information, a similar written statement submitted within a reasonable period following the oral communication.
(b) LimitationNo communication of critical infrastructure information to a covered Federal agency made pursuant to this part shall be considered to be an action subject to the requirements of chapter 10 of title 5.
(c) Independently obtained informationNothing in this section shall be construed to limit or otherwise affect the ability of a State, local, or Federal Government entity, agency, or authority, or any third party, under applicable law, to obtain critical infrastructure information in a manner not covered by subsection (a), including any information lawfully and properly disclosed generally or broadly to the public and to use such information in any manner permitted by law. For purposes of this section a permissible use of independently obtained information includes the disclosure of such information under section 2302(b)(8) of title 5.
(d) Treatment of voluntary submittal of informationThe voluntary submittal to the Government of information or records that are protected from disclosure by this part shall not be construed to constitute compliance with any requirement to submit such information to a Federal agency under any other provision of law.
(e) Procedures(1) In generalThe Secretary of the Department of Homeland Security shall, in consultation with appropriate representatives of the National Security Council and the Office of Science and Technology Policy, establish uniform procedures for the receipt, care, and storage by Federal agencies of critical infrastructure information that is voluntarily submitted to the Government. The procedures shall be established not later than 90 days after November 25, 2002. (2) ElementsThe procedures established under paragraph (1) shall include mechanisms regarding—(A) the acknowledgement of receipt by Federal agencies of critical infrastructure information that is voluntarily submitted to the Government; (B) the maintenance of the identification of such information as voluntarily submitted to the Government for purposes of and subject to the provisions of this part; (C) the care and storage of such information; and (D) the protection and maintenance of the confidentiality of such information so as to permit the sharing of such information within the Federal Government and with State and local governments, and the issuance of notices and warnings related to the protection of critical infrastructure and protected systems, in such manner as to protect from public disclosure the identity of the submitting person or entity, or information that is proprietary, business sensitive, relates specifically to the submitting person or entity, and is otherwise not appropriately in the public domain.
(f) PenaltiesWhoever, being an officer or employee of the United States or of any department or agency thereof, knowingly publishes, divulges, discloses, or makes known in any manner or to any extent not authorized by law, any critical infrastructure information protected from disclosure by this part coming to him in the course of this employment or official duties or by reason of any examination or investigation made by, or return, report, or record made to or filed with, such department or agency or officer or employee thereof, shall be fined under title 18, imprisoned not more than 1 year, or both, and shall be removed from office or employment.
(g) Authority to issue warningsThe Federal Government may provide advisories, alerts, and warnings to relevant companies, targeted sectors, other governmental entities, or the general public regarding potential threats to critical infrastructure as appropriate. In issuing a warning, the Federal Government shall take appropriate actions to protect from disclosure—(1) the source of any voluntarily submitted critical infrastructure information that forms the basis for the warning; or (2) information that is proprietary, business sensitive, relates specifically to the submitting person or entity, or is otherwise not appropriately in the public domain.
(h) Authority to delegateThe President may delegate authority to a critical infrastructure protection program, designated under section 672 of this title, to enter into a voluntary agreement to promote critical infrastructure security, including with any Information Sharing and Analysis Organization, or a plan of action as otherwise defined in section 4558 of title 50.
6 U.S.C. § 674 No private right of action
Nothing in this part may be construed to create a private right of action for enforcement of any provision of this chapter.
6 U.S.C. § 677 Sense of Congress
It is the sense of Congress that—
(1) the purpose of this part is to authorize the Secretary to declare that a significant incident has occurred and to establish the authorities that are provided under the declaration to respond to and recover from the significant incident; and
(2) the authorities established under this part are intended to enable the Secretary to provide voluntary assistance to non-Federal entities impacted by a significant incident.
6 U.S.C. § 677a Definitions
For the purposes of this part:
(1) Asset response activityThe term “asset response activity” means an activity to support an entity impacted by an incident with the response to, remediation of, or recovery from, the incident, including—(A) furnishing technical and advisory assistance to the entity to protect the assets of the entity, mitigate vulnerabilities, and reduce the related impacts; (B) assessing potential risks to the critical infrastructure sector or geographic region impacted by the incident, including potential cascading effects of the incident on other critical infrastructure sectors or geographic regions; (C) developing courses of action to mitigate the risks assessed under subparagraph (B); (D) facilitating information sharing and operational coordination with entities performing threat response activities; and (E) providing guidance on how best to use Federal resources and capabilities in a timely, effective manner to speed recovery from the incident.
(2) DeclarationThe term “declaration” means a declaration of the Secretary under section 677b(a)(1) of this title.
(3) DirectorThe term “Director” means the Director of the Cybersecurity and Infrastructure Security Agency.
(4) Federal agencyThe term “Federal agency” has the meaning given the term “agency” in section 3502 of title 44.
(5) FundThe term “Fund” means the Cyber Response and Recovery Fund established under section 677c(a) of this title.
(6) IncidentThe term “incident” has the meaning given the term in section 3552 of title 44.
(7) RenewalThe term “renewal” means a renewal of a declaration under section 677b(d) of this title.
(8) Significant incidentThe term “significant incident”—(A) means an incident or a group of related incidents that results, or is likely to result, in demonstrable harm to—(i) the national security interests, foreign relations, or economy of the United States; or (ii) the public confidence, civil liberties, or public health and safety of the people of the United States; and (B) does not include an incident or a portion of a group of related incidents that occurs on—(i) a national security system (as defined in section 3552 of title 44); or (ii) an information system described in paragraph (2) or (3) of section 3553(e) of title 44.
6 U.S.C. § 677b Declaration
(a) In general(1) DeclarationThe Secretary, in consultation with the National Cyber Director, may make a declaration of a significant incident in accordance with this section for the purpose of enabling the activities described in this part if the Secretary determines that—(A) a specific significant incident—(i) has occurred; or (ii) is likely to occur imminently; and (B) otherwise available resources, other than the Fund, are likely insufficient to respond effectively to, or to mitigate effectively, the specific significant incident described in subparagraph (A). (2) Prohibition on delegationThe Secretary may not delegate the authority provided to the Secretary under paragraph (1).
(b) Asset response activitiesUpon a declaration, the Director shall coordinate—(1) the asset response activities of each Federal agency in response to the specific significant incident associated with the declaration; and (2) with appropriate entities, which may include—(A) public and private entities and State and local governments with respect to the asset response activities of those entities and governments; and (B) Federal, State, local, and Tribal law enforcement agencies with respect to investigations and threat response activities of those law enforcement agencies; and (3) Federal, State, local, and Tribal emergency management and response agencies.
(c) DurationSubject to subsection (d), a declaration shall terminate upon the earlier of—(1) a determination by the Secretary that the declaration is no longer necessary; or (2) the expiration of the 120-day period beginning on the date on which the Secretary makes the declaration.
(d) RenewalThe Secretary, without delegation, may renew a declaration as necessary.
(e) Publication(1) In generalNot later than 72 hours after a declaration or a renewal, the Secretary shall publish the declaration or renewal in the Federal Register. (2) ProhibitionA declaration or renewal published under paragraph (1) may not include the name of any affected individual or private company.
(f) Advance actions(1) In generalThe Secretary—(A) shall assess the resources available to respond to a potential declaration; and (B) may take actions before and while a declaration is in effect to arrange or procure additional resources for asset response activities or technical assistance the Secretary determines necessary, which may include entering into standby contracts with private entities for cybersecurity services or incident responders in the event of a declaration. (2) Expenditure of fundsAny expenditure from the Fund for the purpose of paragraph (1)(B) shall be made from amounts available in the Fund, and amounts available in the Fund shall be in addition to any other appropriations available to the Cybersecurity and Infrastructure Security Agency for such purpose.
6 U.S.C. § 677c Cyber Response and Recovery Fund
(a) In generalThere is established a Cyber Response and Recovery Fund, which shall be available for—(1) the coordination of activities described in section 677b(b) of this title; (2) response and recovery support for the specific significant incident associated with a declaration to Federal, State, local, and Tribal, entities and public and private entities on a reimbursable or non-reimbursable basis, including through asset response activities and technical assistance, such as—(A) vulnerability assessments and mitigation; (B) technical incident mitigation; (C) malware analysis; (D) analytic support; (E) threat detection and hunting; and (F) network protections; (3) as the Director determines appropriate, grants for, or cooperative agreements with, Federal, State, local, and Tribal public and private entities to respond to, and recover from, the specific significant incident associated with a declaration, such as—(A) hardware or software to replace, update, improve, harden, or enhance the functionality of existing hardware, software, or systems; and (B) technical contract personnel support; and (4) advance actions taken by the Secretary under section 677b(f)(1)(B) of this title.
(b) Deposits and expenditures(1) In generalAmounts shall be deposited into the Fund from—(A) appropriations to the Fund for activities of the Fund; and (B) reimbursement from Federal agencies for the activities described in paragraphs (1), (2), and (4) of subsection (a), which shall only be from amounts made available in advance in appropriations Acts for such reimbursement. (2) ExpendituresAny expenditure from the Fund for the purposes of this part shall be made from amounts available in the Fund from a deposit described in paragraph (1), and amounts available in the Fund shall be in addition to any other appropriations available to the Cybersecurity and Infrastructure Security Agency for such purposes.
(c) Supplement not supplantAmounts in the Fund shall be used to supplement, not supplant, other Federal, State, local, or Tribal funding for activities in response to a declaration.
(d) ReportingThe Secretary shall require an entity that receives amounts from the Fund to submit a report to the Secretary that details the specific use of the amounts.
6 U.S.C. § 677d Notification and reporting
(a) NotificationUpon a declaration or renewal, the Secretary shall immediately notify the National Cyber Director and appropriate congressional committees and include in the notification—(1) an estimation of the planned duration of the declaration; (2) with respect to a notification of a declaration, the reason for the declaration, including information relating to the specific significant incident or imminent specific significant incident, including—(A) the operational or mission impact or anticipated impact of the specific significant incident on Federal and non-Federal entities; (B) if known, the perpetrator of the specific significant incident; and (C) the scope of the Federal and non-Federal entities impacted or anticipated to be impacted by the specific significant incident; (3) with respect to a notification of a renewal, the reason for the renewal; (4) justification as to why available resources, other than the Fund, are insufficient to respond to or mitigate the specific significant incident; and (5) a description of the coordination activities described in section 677b(b) of this title that the Secretary anticipates the Director to perform.
(b) Report to CongressNot later than 180 days after the date of a declaration or renewal, the Secretary shall submit to the appropriate congressional committees a report that includes—(1) the reason for the declaration or renewal, including information and intelligence relating to the specific significant incident that led to the declaration or renewal; (2) the use of any funds from the Fund for the purpose of responding to the incident or threat described in paragraph (1); (3) a description of the actions, initiatives, and projects undertaken by the Department and State and local governments and public and private entities in responding to and recovering from the specific significant incident described in paragraph (1); (4) an accounting of the specific obligations and outlays of the Fund; and (5) an analysis of—(A) the impact of the specific significant incident described in paragraph (1) on Federal and non-Federal entities; (B) the impact of the declaration or renewal on the response to, and recovery from, the specific significant incident described in paragraph (1); and (C) the impact of the funds made available from the Fund as a result of the declaration or renewal on the recovery from, and response to, the specific significant incident described in paragraph (1).
(c) ClassificationEach notification made under subsection (a) and each report submitted under subsection (b)—(1) shall be in an unclassified form with appropriate markings to indicate information that is exempt from disclosure under section 552 of title 5 (commonly known as the “Freedom of Information Act”); and (2) may include a classified annex.
(d) Consolidated reportThe Secretary shall not be required to submit multiple reports under subsection (b) for multiple declarations or renewals if the Secretary determines that the declarations or renewals substantively relate to the same specific significant incident.
(e) ExemptionThe requirements of subchapter I of chapter 35 of title 44 (commonly known as the “Paperwork Reduction Act”) shall not apply to the voluntary collection of information by the Department during an investigation of, a response to, or an immediate post-response review of, the specific significant incident leading to a declaration or renewal.
6 U.S.C. § 677e Rule of construction
Nothing in this part shall be construed to impair or limit the ability of the Director to carry out the authorized activities of the Cybersecurity and Infrastructure Security Agency.
6 U.S.C. § 677f Authorization of appropriations
There are authorized to be appropriated to the Fund $20,000,000 for fiscal year 2022 and each fiscal year thereafter until September 30, 2028, which shall remain available until September 30, 2028.
6 U.S.C. § 677g Sunset
The authorities granted to the Secretary or the Director under this part shall expire on the date that is 7 years after November 15, 2021.
6 U.S.C. § 681 Definitions
In this part:
(1) CenterThe term “Center” means the center established under section 659 of this title.
(2) CouncilThe term “Council” means the Cyber Incident Reporting Council described in section 681f of this title.
(3) Covered cyber incidentThe term “covered cyber incident” means a substantial cyber incident experienced by a covered entity that satisfies the definition and criteria established by the Director in the final rule issued pursuant to section 681b(b) of this title.
(4) Covered entityThe term “covered entity” means an entity in a critical infrastructure sector, as defined in Presidential Policy Directive 21, that satisfies the definition established by the Director in the final rule issued pursuant to section 681b(b) of this title.
(5) Cyber incidentThe term “cyber incident”—(A) has the meaning given the term “incident” in section 659 11 See References in Text note below. of this title; and (B) does not include an occurrence that imminently, but not actually, jeopardizes—(i) information on information systems; or (ii) information systems.
(6) Cyber threatThe term “cyber threat” has the meaning given the term “cybersecurity threat” in section 650 of this title.
(7) Federal entityThe term “Federal entity” has the meaning given the term in section 1501 of this title.
(8) Ransom paymentThe term “ransom payment” means the transmission of any money or other property or asset, including virtual currency, or any portion thereof, which has at any time been delivered as ransom in connection with a ransomware attack.
(9) Significant cyber incidentThe term “significant cyber incident” means a cyber incident, or a group of related cyber incidents, that the Secretary determines is likely to result in demonstrable harm to the national security interests, foreign relations, or economy of the United States or to the public confidence, civil liberties, or public health and safety of the people of the United States.
(10) Virtual currencyThe term “virtual currency” means the digital representation of value that functions as a medium of exchange, a unit of account, or a store of value.
(11) Virtual currency addressThe term “virtual currency address” means a unique public cryptographic key identifying the location to which a virtual currency payment can be made.
6 U.S.C. § 681a Cyber incident review
(a) ActivitiesThe Center shall—(1) receive, aggregate, analyze, and secure, using processes consistent with the processes developed pursuant to the Cybersecurity Information Sharing Act of 2015 (6 U.S.C. 1501 et seq.) reports from covered entities related to a covered cyber incident to assess the effectiveness of security controls, identify tactics, techniques, and procedures adversaries use to overcome those controls and other cybersecurity purposes, including to assess potential impact of cyber incidents on public health and safety and to enhance situational awareness of cyber threats across critical infrastructure sectors; (2) coordinate and share information with appropriate Federal departments and agencies to identify and track ransom payments, including those utilizing virtual currencies; (3) leverage information gathered about cyber incidents to—(A) enhance the quality and effectiveness of information sharing and coordination efforts with appropriate entities, including agencies, sector coordinating councils, Information Sharing and Analysis Organizations, State, local, Tribal, and territorial governments, technology providers, critical infrastructure owners and operators, cybersecurity and cyber incident response firms, and security researchers; and (B) provide appropriate entities, including sector coordinating councils, Information Sharing and Analysis Organizations, State, local, Tribal, and territorial governments, technology providers, cybersecurity and cyber incident response firms, and security researchers, with timely, actionable, and anonymized reports of cyber incident campaigns and trends, including, to the maximum extent practicable, related contextual information, cyber threat indicators, and defensive measures, pursuant to section 681e of this title; (4) establish mechanisms to receive feedback from stakeholders on how the Agency can most effectively receive covered cyber incident reports, ransom payment reports, and other voluntarily provided information, and how the Agency can most effectively support private sector cybersecurity; (5) facilitate the timely sharing, on a voluntary basis, between relevant critical infrastructure owners and operators of information relating to covered cyber incidents and ransom payments, particularly with respect to ongoing cyber threats or security vulnerabilities and identify and disseminate ways to prevent or mitigate similar cyber incidents in the future; (6) for a covered cyber incident, including a ransomware attack, that also satisfies the definition of a significant cyber incident, or is part of a group of related cyber incidents that together satisfy such definition, conduct a review of the details surrounding the covered cyber incident or group of those incidents and identify and disseminate ways to prevent or mitigate similar incidents in the future; (7) with respect to covered cyber incident reports under section 11 So in original. Probably should be “sections”. 681b(a) and 681c of this title involving an ongoing cyber threat or security vulnerability, immediately review those reports for cyber threat indicators that can be anonymized and disseminated, with defensive measures, to appropriate stakeholders, in coordination with other divisions within the Agency, as appropriate; (8) publish quarterly unclassified, public reports that describe aggregated, anonymized observations, findings, and recommendations based on covered cyber incident reports, which may be based on the unclassified information contained in the briefings required under subsection (c); (9) proactively identify opportunities, consistent with the protections in section 681e of this title, to leverage and utilize data on cyber incidents in a manner that enables and strengthens cybersecurity research carried out by academic institutions and other private sector organizations, to the greatest extent practicable; and (10) in accordance with section 681e of this title and subsection (b) of this section, as soon as possible but not later than 24 hours after receiving a covered cyber incident report, ransom payment report, voluntarily submitted information pursuant to section 681c of this title, or information received pursuant to a request for information or subpoena under section 681d of this title, make available the information to appropriate Sector Risk Management Agencies and other appropriate Federal agencies.
(b) Interagency sharingThe President or a designee of the President—(1) may establish a specific time requirement for sharing information under subsection (a)(10); and (2) shall determine the appropriate Federal agencies under subsection (a)(10).
(c) Periodic briefingNot later than 60 days after the effective date of the final rule required under section 681b(b) of this title, and on the first day of each month thereafter, the Director, in consultation with the National Cyber Director, the Attorney General, and the Director of National Intelligence, shall provide to the majority leader of the Senate, the minority leader of the Senate, the Speaker of the House of Representatives, the minority leader of the House of Representatives, the Committee on Homeland Security and Governmental Affairs of the Senate, and the Committee on Homeland Security of the House of Representatives a briefing that characterizes the national cyber threat landscape, including the threat facing Federal agencies and covered entities, and applicable intelligence and law enforcement information, covered cyber incidents, and ransomware attacks, as of the date of the briefing, which shall—(1) include the total number of reports submitted under sections 681b and 681c of this title during the preceding month, including a breakdown of required and voluntary reports; (2) include any identified trends in covered cyber incidents and ransomware attacks over the course of the preceding month and as compared to previous reports, including any trends related to the information collected in the reports submitted under sections 681b and 681c of this title, including—(A) the infrastructure, tactics, and techniques malicious cyber actors commonly use; and (B) intelligence gaps that have impeded, or currently are impeding, the ability to counter covered cyber incidents and ransomware threats; (3) include a summary of the known uses of the information in reports submitted under sections 681b and 681c of this title; and (4) include an unclassified portion, but may include a classified component.
6 U.S.C. § 681b Required reporting of certain cyber incidents
(a) In general(1) Covered cyber incident reports(A) In generalA covered entity that experiences a covered cyber incident shall report the covered cyber incident to the Agency not later than 72 hours after the covered entity reasonably believes that the covered cyber incident has occurred. (B) LimitationThe Director may not require reporting under subparagraph (A) any earlier than 72 hours after the covered entity reasonably believes that a covered cyber incident has occurred. (2) Ransom payment reports(A) In generalA covered entity that makes a ransom payment as the result of a ransomware attack against the covered entity shall report the payment to the Agency not later than 24 hours after the ransom payment has been made. (B) ApplicationThe requirements under subparagraph (A) shall apply even if the ransomware attack is not a covered cyber incident subject to the reporting requirements under paragraph (1). (3) Supplemental reportsA covered entity shall promptly submit to the Agency an update or supplement to a previously submitted covered cyber incident report if substantial new or different information becomes available or if the covered entity makes a ransom payment after submitting a covered cyber incident report required under paragraph (1), until such date that such covered entity notifies the Agency that the covered cyber incident at issue has concluded and has been fully mitigated and resolved. (4) Preservation of informationAny covered entity subject to requirements of paragraph (1), (2), or (3) shall preserve data relevant to the covered cyber incident or ransom payment in accordance with procedures established in the final rule issued pursuant to subsection (b). (5) Exceptions(A) Reporting of covered cyber incident with ransom paymentIf a covered entity is the victim of a covered cyber incident and makes a ransom payment prior to the 72 hour requirement under paragraph (1), such that the reporting requirements under paragraphs (1) and (2) both apply, the covered entity may submit a single report to satisfy the requirements of both paragraphs in accordance with procedures established in the final rule issued pursuant to subsection (b). (B) Substantially similar reported information(i) In generalSubject to the limitation described in clause (ii), where the Agency has an agreement in place that satisfies the requirements of section 681g(a) of this title, the requirements under paragraphs (1), (2), and (3) shall not apply to a covered entity required by law, regulation, or contract to report substantially similar information to another Federal agency within a substantially similar timeframe. (ii) LimitationThe exemption in clause (i) shall take effect with respect to a covered entity once an agency agreement and sharing mechanism is in place between the Agency and the respective Federal agency, pursuant to section 681g(a) of this title. (iii) Rules of constructionNothing in this paragraph shall be construed to—(I) exempt a covered entity from the reporting requirements under paragraph (3) unless the supplemental report also meets the requirements of clauses (i) and (ii) of this paragraph; 11 So in original. Probably should be “subparagraph”. (II) prevent the Agency from contacting an entity submitting information to another Federal agency that is provided to the Agency pursuant to section 681g of this title; or (III) prevent an entity from communicating with the Agency. (C) Domain name systemThe requirements under paragraphs (1), (2) and (3) shall not apply to a covered entity or the functions of a covered entity that the Director determines constitute critical infrastructure owned, operated, or governed by multi-stakeholder organizations that develop, implement, and enforce policies concerning the Domain Name System, such as the Internet Corporation for Assigned Names and Numbers or the Internet Assigned Numbers Authority. (6) Manner, timing, and form of reportsReports made under paragraphs (1), (2), and (3) shall be made in the manner and form, and within the time period in the case of reports made under paragraph (3), prescribed in the final rule issued pursuant to subsection (b). (7) Effective dateParagraphs (1) through (4) shall take effect on the dates prescribed in the final rule issued pursuant to subsection (b).
(b) Rulemaking(1) Notice of proposed rulemakingNot later than 24 months after March 15, 2022, the Director, in consultation with Sector Risk Management Agencies, the Department of Justice, and other Federal agencies, shall publish in the Federal Register a notice of proposed rulemaking to implement subsection (a). (2) Final ruleNot later than 18 months after publication of the notice of proposed rulemaking under paragraph (1), the Director shall issue a final rule to implement subsection (a). (3) Subsequent rulemakings(A) In generalThe Director is authorized to issue regulations to amend or revise the final rule issued pursuant to paragraph (2). (B) ProceduresAny subsequent rules issued under subparagraph (A) shall comply with the requirements under chapter 5 of title 5, including the issuance of a notice of proposed rulemaking under section 553 of such title.
(c) ElementsThe final rule issued pursuant to subsection (b) shall be composed of the following elements:(1) A clear description of the types of entities that constitute covered entities, based on—(A) the consequences that disruption to or compromise of such an entity could cause to national security, economic security, or public health and safety; (B) the likelihood that such an entity may be targeted by a malicious cyber actor, including a foreign country; and (C) the extent to which damage, disruption, or unauthorized access to such an entity, including the accessing of sensitive cybersecurity vulnerability information or penetration testing tools or techniques, will likely enable the disruption of the reliable operation of critical infrastructure. (2) A clear description of the types of substantial cyber incidents that constitute covered cyber incidents, which shall—(A) at a minimum, require the occurrence of—(i) a cyber incident that leads to substantial loss of confidentiality, integrity, or availability of such information system or network, or a serious impact on the safety and resiliency of operational systems and processes; (ii) a disruption of business or industrial operations, including due to a denial of service attack, ransomware attack, or exploitation of a zero day vulnerability, against 22 So in original. Probably should be followed by a dash.(I) an information system or network; or (II) an operational technology system or process; or (iii) unauthorized access or disruption of business or industrial operations due to loss of service facilitated through, or caused by, a compromise of a cloud service provider, managed service provider, or other third-party data hosting provider or by a supply chain compromise; (B) consider—(i) the sophistication or novelty of the tactics used to perpetrate such a cyber incident, as well as the type, volume, and sensitivity of the data at issue; (ii) the number of individuals directly or indirectly affected or potentially affected by such a cyber incident; and (iii) potential impacts on industrial control systems, such as supervisory control and data acquisition systems, distributed control systems, and programmable logic controllers; and (C) exclude—(i) any event where the cyber incident is perpetrated in good faith by an entity in response to a specific request by the owner or operator of the information system; and (ii) the threat of disruption as extortion, as described in section 681(14)(A) 33 See References in Text note below. of this title. (3) A requirement that, if a covered cyber incident or a ransom payment occurs following an exempted threat described in paragraph (2)(C)(ii), the covered entity shall comply with the requirements in this part in reporting the covered cyber incident or ransom payment. (4) A clear description of the specific required contents of a report pursuant to subsection (a)(1), which shall include the following information, to the extent applicable and available, with respect to a covered cyber incident:(A) A description of the covered cyber incident, including—(i) identification and a description of the function of the affected information systems, networks, or devices that were, or are reasonably believed to have been, affected by such cyber incident; (ii) a description of the unauthorized access with substantial loss of confidentiality, integrity, or availability of the affected information system or network or disruption of business or industrial operations; (iii) the estimated date range of such incident; and (iv) the impact to the operations of the covered entity. (B) Where applicable, a description of the vulnerabilities exploited and the security defenses that were in place, as well as the tactics, techniques, and procedures used to perpetrate the covered cyber incident. (C) Where applicable, any identifying or contact information related to each actor reasonably believed to be responsible for such cyber incident. (D) Where applicable, identification of the category or categories of information that were, or are reasonably believed to have been, accessed or acquired by an unauthorized person. (E) The name and other information that clearly identifies the covered entity impacted by the covered cyber incident, including, as applicable, the State of incorporation or formation of the covered entity, trade names, legal names, or other identifiers. (F) Contact information, such as telephone number or electronic mail address, that the Agency may use to contact the covered entity or an authorized agent of such covered entity, or, where applicable, the service provider of such covered entity acting with the express permission of, and at the direction of, the covered entity to assist with compliance with the requirements of this part. (5) A clear description of the specific required contents of a report pursuant to subsection (a)(2), which shall be the following information, to the extent applicable and available, with respect to a ransom payment:(A) A description of the ransomware attack, including the estimated date range of the attack. (B) Where applicable, a description of the vulnerabilities, tactics, techniques, and procedures used to perpetrate the ransomware attack. (C) Where applicable, any identifying or contact information related to the actor or actors reasonably believed to be responsible for the ransomware attack. (D) The name and other information that clearly identifies the covered entity that made the ransom payment or on whose behalf the payment was made. (E) Contact information, such as telephone number or electronic mail address, that the Agency may use to contact the covered entity that made the ransom payment or an authorized agent of such covered entity, or, where applicable, the service provider of such covered entity acting with the express permission of, and at the direction of, that covered entity to assist with compliance with the requirements of this part. (F) The date of the ransom payment. (G) The ransom payment demand, including the type of virtual currency or other commodity requested, if applicable. (H) The ransom payment instructions, including information regarding where to send the payment, such as the virtual currency address or physical address the funds were requested to be sent to, if applicable. (I) The amount of the ransom payment. (6) A clear description of the types of data required to be preserved pursuant to subsection (a)(4), the period of time for which the data is required to be preserved, and allowable uses, processes, and procedures. (7) Deadlines and criteria for submitting supplemental reports to the Agency required under subsection (a)(3), which shall—(A) be established by the Director in consultation with the Council; (B) consider any existing regulatory reporting requirements similar in scope, purpose, and timing to the reporting requirements to which such a covered entity may also be subject, and make efforts to harmonize the timing and contents of any such reports to the maximum extent practicable; (C) balance the need for situational awareness with the ability of the covered entity to conduct cyber incident response and investigations; and (D) provide a clear description of what constitutes substantial new or different information. (8) Procedures for—(A) entities, including third parties pursuant to subsection (d)(1), to submit reports required by paragraphs (1), (2), and (3) of subsection (a), including the manner and form thereof, which shall include, at a minimum, a concise, user-friendly web-based form; (B) the Agency to carry out—(i) the enforcement provisions of section 681d of this title, including with respect to the issuance, service, withdrawal, referral process, and enforcement of subpoenas, appeals and due process procedures; (ii) other available enforcement mechanisms including acquisition, suspension and debarment procedures; and (iii) other aspects of noncompliance; (C) implementing the exceptions provided in subsection (a)(5); and (D) protecting privacy and civil liberties consistent with processes adopted pursuant to section 1504(b) of this title and anonymizing and safeguarding, or no longer retaining, information received and disclosed through covered cyber incident reports and ransom payment reports that is known to be personal information of a specific individual or information that identifies a specific individual that is not directly related to a cybersecurity threat. (9) Other procedural measures directly necessary to implement subsection (a).
(d) Third party report submission and ransom payment(1) Report submissionA covered entity that is required to submit a covered cyber incident report or a ransom payment report may use a third party, such as an incident response company, insurance provider, service provider, Information Sharing and Analysis Organization, or law firm, to submit the required report under subsection (a). (2) Ransom paymentIf a covered entity impacted by a ransomware attack uses a third party to make a ransom payment, the third party shall not be required to submit a ransom payment report for itself under subsection (a)(2). (3) Duty to reportThird-party reporting under this subparagraph 44 So in original. Probably should be “subsection”. does not relieve a covered entity from the duty to comply with the requirements for covered cyber incident report or ransom payment report submission. (4) Responsibility to adviseAny third party used by a covered entity that knowingly makes a ransom payment on behalf of a covered entity impacted by a ransomware attack shall advise the impacted covered entity of the responsibilities of the impacted covered entity regarding reporting ransom payments under this section.
(e) Outreach to covered entities(1) In generalThe Agency shall conduct an outreach and education campaign to inform likely covered entities, entities that offer or advertise as a service to customers to make or facilitate ransom payments on behalf of covered entities impacted by ransomware attacks and other appropriate entities of the requirements of paragraphs (1), (2), and (3) of subsection (a). (2) ElementsThe outreach and education campaign under paragraph (1) shall include the following:(A) An overview of the final rule issued pursuant to subsection (b). (B) An overview of mechanisms to submit to the Agency covered cyber incident reports, ransom payment reports, and information relating to the disclosure, retention, and use of covered cyber incident reports and ransom payment reports under this section. (C) An overview of the protections afforded to covered entities for complying with the requirements under paragraphs (1), (2), and (3) of subsection (a). (D) An overview of the steps taken under section 681d of this title when a covered entity is not in compliance with the reporting requirements under subsection (a). (E) Specific outreach to cybersecurity vendors, cyber incident response providers, cybersecurity insurance entities, and other entities that may support covered entities. (F) An overview of the privacy and civil liberties requirements in this part. (3) CoordinationIn conducting the outreach and education campaign required under paragraph (1), the Agency may coordinate with—(A) the Critical Infrastructure Partnership Advisory Council established under section 451 of this title; (B) Information Sharing and Analysis Organizations; (C) trade associations; (D) information sharing and analysis centers; (E) sector coordinating councils; and (F) any other entity as determined appropriate by the Director.
(f) ExemptionSections 3506(c), 3507, 3508, and 3509 of title 44 shall not apply to any action to carry out this section.
(g) Rule of constructionNothing in this section shall affect the authorities of the Federal Government to implement the requirements of Executive Order 14028 (86 Fed. Reg. 26633; relating to improving the nation’s cybersecurity), including changes to the Federal Acquisition Regulations and remedies to include suspension and debarment.
(h) Savings provisionNothing in this section shall be construed to supersede or to abrogate, modify, or otherwise limit the authority that is vested in any officer or any agency of the United States Government to regulate or take action with respect to the cybersecurity of an entity.
6 U.S.C. § 681c Voluntary reporting of other cyber incidents
(a) In generalEntities may voluntarily report cyber incidents or ransom payments to the Agency that are not required under paragraph (1), (2), or (3) of section 681b(a) of this title, but may enhance the situational awareness of cyber threats.
(b) Voluntary provision of additional information in required reportsCovered entities may voluntarily include in reports required under paragraph (1), (2), or (3) of section 681b(a) of this title information that is not required to be included, but may enhance the situational awareness of cyber threats.
(c) Application of section 681e of this titleSection 681e of this title shall apply in the same manner and to the same extent to reports and information submitted under subsections (a) and (b) as it applies to reports and information submitted under section 681b of this title.
6 U.S.C. § 681d Noncompliance with required reporting
(a) PurposeIn the event that a covered entity that is required to submit a report under section 681b(a) of this title fails to comply with the requirement to report, the Director may obtain information about the cyber incident or ransom payment by engaging the covered entity directly to request information about the cyber incident or ransom payment, and if the Director is unable to obtain information through such engagement, by issuing a subpoena to the covered entity, pursuant to subsection (c), to gather information sufficient to determine whether a covered cyber incident or ransom payment has occurred.
(b) Initial request for information(1) In generalIf the Director has reason to believe, whether through public reporting or other information in the possession of the Federal Government, including through analysis performed pursuant to paragraph (1) or (2) of section 681a(a) of this title, that a covered entity has experienced a covered cyber incident or made a ransom payment but failed to report such cyber incident or payment to the Agency in accordance with section 681b(a) of this title, the Director may request additional information from the covered entity to confirm whether or not a covered cyber incident or ransom payment has occurred. (2) TreatmentInformation provided to the Agency in response to a request under paragraph (1) shall be treated as if it was submitted through the reporting procedures established in section 681b of this title 11 So in original. Probably should be followed by a comma. including that section 681e of this title shall apply to such information in the same manner and to the same extent to information submitted in response to requests under paragraph (1) as it applies to information submitted under section 681b of this title.
(c) Enforcement(1) In generalIf, after the date that is 72 hours from the date on which the Director made the request for information in subsection (b), the Director has received no response from the covered entity from which such information was requested, or received an inadequate response, the Director may issue to such covered entity a subpoena to compel disclosure of information the Director deems necessary to determine whether a covered cyber incident or ransom payment has occurred and obtain the information required to be reported pursuant to section 681b of this title and any implementing regulations, and assess potential impacts to national security, economic security, or public health and safety. (2) Civil action(A) In generalIf a covered entity fails to comply with a subpoena, the Director may refer the matter to the Attorney General to bring a civil action in a district court of the United States to enforce such subpoena. (B) VenueAn action under this paragraph may be brought in the judicial district in which the covered entity against which the action is brought resides, is found, or does business. (C) Contempt of courtA court may punish a failure to comply with a subpoena issued under this subsection as contempt of court. (3) Non-delegationThe authority of the Director to issue a subpoena under this subsection may not be delegated. (4) Authentication(A) In generalAny subpoena issued electronically pursuant to this subsection shall be authenticated with a cryptographic digital signature of an authorized representative of the Agency, or other comparable successor technology, that allows the Agency to demonstrate that such subpoena was issued by the Agency and has not been altered or modified since such issuance. (B) Invalid if not authenticatedAny subpoena issued electronically pursuant to this subsection that is not authenticated in accordance with subparagraph (A) shall not be considered to be valid by the recipient of such subpoena.
(d) Provision of certain information to Attorney General(1) In generalNotwithstanding section 681e(a)(5) of this title and paragraph (b)(2) of this section, if the Director determines, based on the information provided in response to a subpoena issued pursuant to subsection (c), that the facts relating to the cyber incident or ransom payment at issue may constitute grounds for a regulatory enforcement action or criminal prosecution, the Director may provide such information to the Attorney General or the head of the appropriate Federal regulatory agency, who may use such information for a regulatory enforcement action or criminal prosecution. (2) ConsultationThe Director may consult with the Attorney General or the head of the appropriate Federal regulatory agency when making the determination under paragraph (1).
(e) ConsiderationsWhen determining whether to exercise the authorities provided under this section, the Director shall take into consideration—(1) the complexity in determining if a covered cyber incident has occurred; and (2) prior interaction with the Agency or awareness of the covered entity of the policies and procedures of the Agency for reporting covered cyber incidents and ransom payments.
(f) ExclusionsThis section shall not apply to a State, local, Tribal, or territorial government entity.
(g) Report to CongressThe Director shall submit to Congress an annual report on the number of times the Director—(1) issued an initial request for information pursuant to subsection (b); (2) issued a subpoena pursuant to subsection (c); or (3) referred a matter to the Attorney General for a civil action pursuant to subsection (c)(2).
(h) Publication of the annual reportThe Director shall publish a version of the annual report required under subsection (g) on the website of the Agency, which shall include, at a minimum, the number of times the Director—(1) issued an initial request for information pursuant to subsection (b); or (2) issued a subpoena pursuant to subsection (c).
(i) Anonymization of reportsThe Director shall ensure any victim information contained in a report required to be published under subsection (h) be anonymized before the report is published.
6 U.S.C. § 681e Information shared with or provided to the Federal Government
(a) Disclosure, retention, and use(1) Authorized activitiesInformation provided to the Agency pursuant to section 681b or 681c of this title may be disclosed to, retained by, and used by, consistent with otherwise applicable provisions of Federal law, any Federal agency or department, component, officer, employee, or agent of the Federal Government solely for—(A) a cybersecurity purpose; (B) the purpose of identifying—(i) a cyber threat, including the source of the cyber threat; or (ii) a security vulnerability; (C) the purpose of responding to, or otherwise preventing or mitigating, a specific threat of death, a specific threat of serious bodily harm, or a specific threat of serious economic harm, including a terrorist act or use of a weapon of mass destruction; (D) the purpose of responding to, investigating, prosecuting, or otherwise preventing or mitigating, a serious threat to a minor, including sexual exploitation and threats to physical safety; or (E) the purpose of preventing, investigating, disrupting, or prosecuting an offense arising out of a cyber incident reported pursuant to section 681b or 681c of this title or any of the offenses listed in section 1504(d)(5)(A)(v) of this title. (2) Agency actions after receipt(A) Rapid, confidential sharing of cyber threat indicatorsUpon receiving a covered cyber incident or ransom payment report submitted pursuant to this section, the Agency shall immediately review the report to determine whether the cyber incident that is the subject of the report is connected to an ongoing cyber threat or security vulnerability and where applicable, use such report to identify, develop, and rapidly disseminate to appropriate stakeholders actionable, anonymized cyber threat indicators and defensive measures. (B) Principles for sharing security vulnerabilitiesWith respect to information in a covered cyber incident or ransom payment report regarding a security vulnerability referred to in paragraph (1)(B)(ii), the Director shall develop principles that govern the timing and manner in which information relating to security vulnerabilities may be shared, consistent with common industry best practices and United States and international standards. (3) Privacy and civil libertiesInformation contained in covered cyber incident and ransom payment reports submitted to the Agency pursuant to section 681b of this title shall be retained, used, and disseminated, where permissible and appropriate, by the Federal Government in accordance with processes to be developed for the protection of personal information consistent with processes adopted pursuant to section 1504 of this title and in a manner that protects personal information from unauthorized use or unauthorized disclosure. (4) Digital securityThe Agency shall ensure that reports submitted to the Agency pursuant to section 681b of this title, and any information contained in those reports, are collected, stored, and protected at a minimum in accordance with the requirements for moderate impact Federal information systems, as described in Federal Information Processing Standards Publication 199, or any successor document. (5) Prohibition on use of information in regulatory actions(A) In generalA Federal, State, local, or Tribal government shall not use information about a covered cyber incident or ransom payment obtained solely through reporting directly to the Agency in accordance with this part to regulate, including through an enforcement action, the activities of the covered entity or entity that made a ransom payment, unless the government entity expressly allows entities to submit reports to the Agency to meet regulatory reporting obligations of the entity. (B) ClarificationA report submitted to the Agency pursuant to section 681b or 681c of this title may, consistent with Federal or State regulatory authority specifically relating to the prevention and mitigation of cybersecurity threats to information systems, inform the development or implementation of regulations relating to such systems.
(b) Protections for reporting entities and informationReports describing covered cyber incidents or ransom payments submitted to the Agency by entities in accordance with section 681b of this title, as well as voluntarily-submitted cyber incident reports submitted to the Agency pursuant to section 681c of this title, shall—(1) be considered the commercial, financial, and proprietary information of the covered entity when so designated by the covered entity; (2) be exempt from disclosure under section 552(b)(3) of title 5 (commonly known as the “Freedom of Information Act”), as well as any provision of State, Tribal, or local freedom of information law, open government law, open meetings law, open records law, sunshine law, or similar law requiring disclosure of information or records; (3) be considered not to constitute a waiver of any applicable privilege or protection provided by law, including trade secret protection; and (4) not be subject to a rule of any Federal agency or department or any judicial doctrine regarding ex parte communications with a decision-making official.
(c) Liability protections(1) In generalNo cause of action shall lie or be maintained in any court by any person or entity and any such action shall be promptly dismissed for the submission of a report pursuant to section 681b(a) of this title that is submitted in conformance with this part and the rule promulgated under section 681b(b) of this title, except that this subsection shall not apply with regard to an action by the Federal Government pursuant to section 681d(c)(2) of this title. (2) ScopeThe liability protections provided in this subsection shall only apply to or affect litigation that is solely based on the submission of a covered cyber incident report or ransom payment report to the Agency. (3) RestrictionsNotwithstanding paragraph (2), no report submitted to the Agency pursuant to this part or any communication, document, material, or other record, created for the sole purpose of preparing, drafting, or submitting such report, may be received in evidence, subject to discovery, or otherwise used in any trial, hearing, or other proceeding in or before any court, regulatory body, or other authority of the United States, a State, or a political subdivision thereof, provided that nothing in this part shall create a defense to discovery or otherwise affect the discovery of any communication, document, material, or other record not created for the sole purpose of preparing, drafting, or submitting such report.
(d) Sharing with non-Federal entitiesThe Agency shall anonymize the victim who reported the information when making information provided in reports received under section 681b of this title available to critical infrastructure owners and operators and the general public.
(e) Stored Communications ActNothing in this part shall be construed to permit or require disclosure by a provider of a remote computing service or a provider of an electronic communication service to the public of information not otherwise permitted or required to be disclosed under chapter 121 of title 18 (commonly known as the “Stored Communications Act”).
6 U.S.C. § 681f Cyber Incident Reporting Council
(a) Responsibility of the SecretaryThe Secretary shall lead an intergovernmental Cyber Incident Reporting Council, in consultation with the Director of the Office of Management and Budget, the Attorney General, the National Cyber Director, Sector Risk Management Agencies, and other appropriate Federal agencies, to coordinate, deconflict, and harmonize Federal incident reporting requirements, including those issued through regulations.
(b) Rule of constructionNothing in subsection (a) shall be construed to provide any additional regulatory authority to any Federal entity.
6 U.S.C. § 681g Federal sharing of incident reports
(a) Cyber incident reporting sharing(1) In generalNotwithstanding any other provision of law or regulation, any Federal agency, including any independent establishment (as defined in section 104 of title 5), that receives a report from an entity of a cyber incident, including a ransomware attack, shall provide the report to the Agency as soon as possible, but not later than 24 hours after receiving the report, unless a shorter period is required by an agreement made between the Department of Homeland Security (including the Cybersecurity and Infrastructure Security Agency) and the recipient Federal agency. The Director shall share and coordinate each report pursuant to section 681a(b) of this title, as added by section 103 of this division. (2) Rule of constructionThe requirements described in paragraph (1) and section 681e(d) of this title, as added by section 103 of this division, may not be construed to be a violation of any provision of law or policy that would otherwise prohibit disclosure or provision of information within the executive branch. (3) Protection of informationThe Director shall comply with any obligations of the recipient Federal agency described in paragraph (1) to protect information, including with respect to privacy, confidentiality, or information security, if those obligations would impose greater protection requirements than this division or the amendments made by this division. (4) Effective dateThis subsection shall take effect on the effective date of the final rule issued pursuant to section 681b(b) of this title, as added by section 103 of this division. (5) Agency agreements(A) In generalThe Agency and any Federal agency, including any independent establishment (as defined in section 104 of title 5), that receives incident reports from entities, including due to ransomware attacks, shall, as appropriate, enter into a documented agreement to establish policies, processes, procedures, and mechanisms to ensure reports are shared with the Agency pursuant to paragraph (1). (B) AvailabilityTo the maximum extent practicable, each documented agreement required under subparagraph (A) shall be made publicly available. (C) RequirementThe documented agreements required by subparagraph (A) shall require reports be shared from Federal agencies with the Agency in such time as to meet the overall timeline for covered entity reporting of covered cyber incidents and ransom payments established in section 681b of this title, as added by section 103 of this division.
(b) Harmonizing reporting requirementsThe Secretary of Homeland Security, acting through the Director, shall, in consultation with the Cyber Incident Reporting Council described in section 681f of this title, as added by section 103 of this division, to the maximum extent practicable—(1) periodically review existing regulatory requirements, including the information required in such reports, to report incidents and ensure that any such reporting requirements and procedures avoid conflicting, duplicative, or burdensome requirements; and (2) coordinate with appropriate Federal partners and regulatory authorities that receive reports relating to incidents to identify opportunities to streamline reporting processes, and where feasible, facilitate interagency agreements between such authorities to permit the sharing of such reports, consistent with applicable law and policy, without impacting the ability of the Agency to gain timely situational awareness of a covered cyber incident or ransom payment.
6 U.S.C. § 650 Definitions
Except as otherwise specifically provided, in this subchapter:
(1) AgencyThe term “Agency” means the Cybersecurity and Infrastructure Security Agency.
(2) Appropriate congressional committeesThe term “appropriate congressional committees” means—(A) the Committee on Homeland Security and Governmental Affairs of the Senate; and (B) the Committee on Homeland Security of the House of Representatives.
(3) Cloud service providerThe term “cloud service provider” means an entity offering products or services related to cloud computing, as defined by the National Institute of Standards and Technology in NIST Special Publication 800–145 and any amendatory or superseding document relating thereto.
(4) Critical infrastructure informationThe term “critical infrastructure information” means information not customarily in the public domain and related to the security of critical infrastructure or protected systems—(A) actual, potential, or threatened interference with, attack on, compromise of, or incapacitation of critical infrastructure or protected systems by either physical or computer-based attack or other similar conduct (including the misuse of or unauthorized access to all types of communications and data transmission systems) that violates Federal, State, or local law, harms interstate commerce of the United States, or threatens public health or safety; (B) the ability of any critical infrastructure or protected system to resist such interference, compromise, or incapacitation, including any planned or past assessment, projection, or estimate of the vulnerability of critical infrastructure or a protected system, including security testing, risk evaluation thereto, risk management planning, or risk audit; or (C) any planned or past operational problem or solution regarding critical infrastructure or protected systems, including repair, recovery, reconstruction, insurance, or continuity, to the extent it is related to such interference, compromise, or incapacitation.
(5) Cyber threat indicatorThe term “cyber threat indicator” means information that is necessary to describe or identify—(A) malicious reconnaissance, including anomalous patterns of communications that appear to be transmitted for the purpose of gathering technical information related to a cybersecurity threat or security vulnerability; (B) a method of defeating a security control or exploitation of a security vulnerability; (C) a security vulnerability, including anomalous activity that appears to indicate the existence of a security vulnerability; (D) a method of causing a user with legitimate access to an information system or information that is stored on, processed by, or transiting an information system to unwittingly enable the defeat of a security control or exploitation of a security vulnerability; (E) malicious cyber command and control; (F) the actual or potential harm caused by an incident, including a description of the information exfiltrated as a result of a particular cybersecurity threat; (G) any other attribute of a cybersecurity threat, if disclosure of such attribute is not otherwise prohibited by law; or (H) any combination thereof.
(6) Cybersecurity purposeThe term “cybersecurity purpose” means the purpose of protecting an information system or information that is stored on, processed by, or transiting an information system from a cybersecurity threat or security vulnerability.
(7) Cybersecurity riskThe term “cybersecurity risk”—(A) means threats to and vulnerabilities of information or information systems and any related consequences caused by or resulting from unauthorized access, use, disclosure, degradation, disruption, modification, or destruction of such information or information systems, including such related consequences caused by an act of terrorism; and (B) does not include any action that solely involves a violation of a consumer term of service or a consumer licensing agreement.
(8) Cybersecurity threat(A) In generalExcept as provided in subparagraph (B), the term “cybersecurity threat” means an action, not protected by the First Amendment to the Constitution of the United States, on or through an information system that may result in an unauthorized effort to adversely impact the security, availability, confidentiality, or integrity of an information system or information that is stored on, processed by, or transiting an information system. (B) ExclusionThe term “cybersecurity threat” does not include any action that solely involves a violation of a consumer term of service or a consumer licensing agreement.
(9) Defensive measure(A) In generalExcept as provided in subparagraph (B), the term “defensive measure” means an action, device, procedure, signature, technique, or other measure applied to an information system or information that is stored on, processed by, or transiting an information system that detects, prevents, or mitigates a known or suspected cybersecurity threat or security vulnerability. (B) ExclusionThe term “defensive measure” does not include a measure that destroys, renders unusable, provides unauthorized access to, or substantially harms an information system or information stored on, processed by, or transiting such information system not owned by—(i) the private entity, as defined in section 1501 of this title, operating the measure; or (ii) another entity or Federal entity that is authorized to provide consent and has provided consent to that private entity for operation of such measure.
(10) DirectorThe term “Director” means the Director of the Cybersecurity and Infrastructure Security Agency.
(11) Homeland Security EnterpriseThe term “Homeland Security Enterprise” means relevant governmental and nongovernmental entities involved in homeland security, including Federal, State, local, and Tribal government officials, private sector representatives, academics, and other policy experts.
(12) IncidentThe term “incident” means an occurrence that actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information on an information system, or actually or imminently jeopardizes, without lawful authority, an information system.
(13) Information Sharing and Analysis OrganizationThe term “Information Sharing and Analysis Organization” means any formal or informal entity or collaboration created or employed by public or private sector organizations, for purposes of—(A) gathering and analyzing critical infrastructure information, including information related to cybersecurity risks and incidents, in order to better understand security problems and interdependencies related to critical infrastructure, including cybersecurity risks and incidents, and protected systems, so as to ensure the availability, integrity, and reliability thereof; (B) communicating or disclosing critical infrastructure information, including cybersecurity risks and incidents, to help prevent, detect, mitigate, or recover from the effects of an interference, a compromise, or an incapacitation problem related to critical infrastructure, including cybersecurity risks and incidents, or protected systems; and (C) voluntarily disseminating critical infrastructure information, including cybersecurity risks and incidents, to its members, State, local, and Federal Governments, or any other entities that may be of assistance in carrying out the purposes specified in subparagraphs (A) and (B).
(14) Information systemThe term “information system”—(A) has the meaning given the term in section 3502 of title 44; and (B) includes industrial control systems, such as supervisory control and data acquisition systems, distributed control systems, and programmable logic controllers.
(15) Intelligence communityThe term “intelligence community” has the meaning given the term in section 3003(4) of title 50.
(16) Malicious cyber command and controlThe term “malicious cyber command and control” means a method for unauthorized remote identification of, access to, or use of, an information system or information that is stored on, processed by, or transiting an information system.
(17) Malicious reconnaissanceThe term “malicious reconnaissance” 11 So in original. Probably should be followed by “means”. a method for actively probing or passively monitoring an information system for the purpose of discerning security vulnerabilities of the information system, if such method is associated with a known or suspected cybersecurity threat.
(18) Managed service providerThe term “managed service provider” means an entity that delivers services, such as network, application, infrastructure, or security services, via ongoing and regular support and active administration on the premises of a customer, in the data center of the entity (such as hosting), or in a third party data center.
(19) MonitorThe term “monitor” means to acquire, identify, or scan, or to possess, information that is stored on, processed by, or transiting an information system.
(20) National cybersecurity asset response activitiesThe term “national cybersecurity asset response activities” means—(A) furnishing cybersecurity technical assistance to entities affected by cybersecurity risks to protect assets, mitigate vulnerabilities, and reduce impacts of cyber incidents; (B) identifying other entities that may be at risk of an incident and assessing risk to the same or similar vulnerabilities; (C) assessing potential cybersecurity risks to a sector or region, including potential cascading effects, and developing courses of action to mitigate such risks; (D) facilitating information sharing and operational coordination with threat response; and (E) providing guidance on how best to utilize Federal resources and capabilities in a timely, effective manner to speed recovery from cybersecurity risks.
(21) National security systemThe term “national security system” has the meaning given the term in section 11103 of title 40.
(22) Ransomware attackThe term “ransomware attack”—(A) means an incident that includes the use or threat of use of unauthorized or malicious code on an information system, or the use or threat of use of another digital mechanism such as a denial of service attack, to interrupt or disrupt the operations of an information system or compromise the confidentiality, availability, or integrity of electronic data stored on, processed by, or transiting an information system to extort a demand for a ransom payment; and (B) does not include any such event in which the demand for payment is—(i) not genuine; or (ii) made in good faith by an entity in response to a specific request by the owner or operator of the information system.
(23) Sector Risk Management AgencyThe term “Sector Risk Management Agency” means a Federal department or agency, designated by law or Presidential directive, with responsibility for providing institutional knowledge and specialized expertise of a sector, as well as leading, facilitating, or supporting programs and associated activities of its designated critical infrastructure sector in the all hazards environment in coordination with the Department.
(24) Security controlThe term “security control” means the management, operational, and technical controls used to protect against an unauthorized effort to adversely affect the confidentiality, integrity, and availability of an information system or its information.
(25) Security vulnerabilityThe term “security vulnerability” means any attribute of hardware, software, process, or procedure that could enable or facilitate the defeat of a security control.
(26) SharingThe term “sharing” (including all conjugations thereof) means providing, receiving, and disseminating (including all conjugations of each such terms).
(27) SLTT entityThe term “SLTT entity” means a domestic government entity that is a State government, local government, Tribal government, territorial government, or any subdivision thereof.
(28) Supply chain compromiseThe term “supply chain compromise” means an incident within the supply chain of an information system that an adversary can leverage, or does leverage, to jeopardize the confidentiality, integrity, or availability of the information system or the information the system processes, stores, or transmits, and can occur at any point during the life cycle.