Arkansas Legal Resource Navigator

6 U.S.C. § 162 — Transferred

Federal law — U.S. Code and appendices · legal_authorities

6 U.S.C. § 162 — Transferred

### Statutory Notes #### Codification Section 131, Pub. L. 107–296, title II, § 212, Nov. 25, 2002, 116 Stat. 2150; Pub. L. 114–113, div. N, title II, § 204, Dec. 18, 2015, 129 Stat. 2961, which related to definitions, was renumbered section 2222 of Pub. L. 107–296 by Pub. L. 115–278, § 2(g)(2)(H), Nov. 16, 2018, 132 Stat. 4178, and transferred to [section 671 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section671&num=0&edition=prelim). Section 132, Pub. L. 107–296, title II, § 213, Nov. 25, 2002, 116 Stat. 2152, which related to designation of critical infrastructure protection program, was renumbered section 2223 of Pub. L. 107–296 by Pub. L. 115–278, § 2(g)(2)(H), Nov. 16, 2018, 132 Stat. 4178, and transferred to [section 672 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section672&num=0&edition=prelim). Section 133, Pub. L. 107–296, title II, § 214, Nov. 25, 2002, 116 Stat. 2152; Pub. L. 108–271, § 8(b), July 7, 2004, 118 Stat. 814; Pub. L. 112–199, title I, § 111, Nov. 27, 2012, 126 Stat. 1472, which related to protection of voluntarily shared critical infrastructure information, was renumbered section 2224 of Pub. L. 107–296 by Pub. L. 115–278, § 2(g)(2)(H), Nov. 16, 2018, 132 Stat. 4178, and transferred to [section 673 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section673&num=0&edition=prelim). Section 134, Pub. L. 107–296, title II, § 215, Nov. 25, 2002, 116 Stat. 2155, which prohibited the construction of former part B as creating a private right of action for enforcement of any provision of this chapter, was renumbered section 2225 of Pub. L. 107–296 by Pub. L. 115–278, § 2(g)(2)(H), Nov. 16, 2018, 132 Stat. 4178, and transferred to [section

Source: Supplied U.S. Code snapshot — release unconfirmed · 6 U.S.C. § 162

Stored review status: release_metadata_unconfirmed. A text match is a research starting point; applicability is not established.

Original supplied file — preserved unchanged

Download original Markdown file

File SHA-256: 1bbe26e774f1c1464a4ca0b6e79960825530d9e1c343283f226dd423e4c555cc. The original may include catalog metadata, neighboring provisions, or embedded records outside this collection's scope. Search shows only the selected federal record. Historical editions and unverified snapshots are not a statement of current law.

Authority boundary: historical or unconfirmed source not current law verified.

Open the recorded source website ↗

Record provenance

Stable record: federal_law:legal_authorities:record_usc_1607434987c0dd9b386cc6e2
Source file: Laws/federal/codes/united-states-code/title-6/section-162-transferred--2b11363588.md
Pages: Not recorded – Not recorded
Passage SHA-256: df171768fbe297c8233d04c684077afb3fdf2f50b17536e45102209a573cc4b5

Source location: Title 6, Chapter 1, § 162; chapter-001-homeland-security-organization.md

Stored source content

### Statutory Notes #### Codification Section 131, Pub. L. 107–296, title II, § 212, Nov. 25, 2002, 116 Stat. 2150; Pub. L. 114–113, div. N, title II, § 204, Dec. 18, 2015, 129 Stat. 2961, which related to definitions, was renumbered section 2222 of Pub. L. 107–296 by Pub. L. 115–278, § 2(g)(2)(H), Nov. 16, 2018, 132 Stat. 4178, and transferred to [section 671 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section671&num=0&edition=prelim). Section 132, Pub. L. 107–296, title II, § 213, Nov. 25, 2002, 116 Stat. 2152, which related to designation of critical infrastructure protection program, was renumbered section 2223 of Pub. L. 107–296 by Pub. L. 115–278, § 2(g)(2)(H), Nov. 16, 2018, 132 Stat. 4178, and transferred to [section 672 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section672&num=0&edition=prelim). Section 133, Pub. L. 107–296, title II, § 214, Nov. 25, 2002, 116 Stat. 2152; Pub. L. 108–271, § 8(b), July 7, 2004, 118 Stat. 814; Pub. L. 112–199, title I, § 111, Nov. 27, 2012, 126 Stat. 1472, which related to protection of voluntarily shared critical infrastructure information, was renumbered section 2224 of Pub. L. 107–296 by Pub. L. 115–278, § 2(g)(2)(H), Nov. 16, 2018, 132 Stat. 4178, and transferred to [section 673 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section673&num=0&edition=prelim). Section 134, Pub. L. 107–296, title II, § 215, Nov. 25, 2002, 116 Stat. 2155, which prohibited the construction of former part B as creating a private right of action for enforcement of any provision of this chapter, was renumbered section 2225 of Pub. L. 107–296 by Pub. L. 115–278, § 2(g)(2)(H), Nov. 16, 2018, 132 Stat. 4178, and transferred to [section 674 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section674&num=0&edition=prelim).

Cross-references

Connections may be documented source relationships, shared citations or nearby passages. Each explains its basis; a connection alone does not establish applicability to your situation.

Federal law — U.S. Code and appendices · legal_authorities

6 U.S.C. § 673 — CyberSentry program

**(a) Establishment** There 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) Activities** The 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 detec

Source: Supplied U.S. Code snapshot — release unconfirmed · 6 U.S.C. § 673

Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

6 U.S.C. § 672 — National Cyber Exercise Program

**(a) Establishment of program** (1) **In general** — There 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 general* — The 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 selection* — The 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) **Consultation** — In 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) Def

Source: Supplied U.S. Code snapshot — release unconfirmed · 6 U.S.C. § 672

Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

6 U.S.C. § 671 — State and Local Cybersecurity Grant Program

**(a) Definitions** In this section: (1) **Cybersecurity Plan** — The term “Cybersecurity Plan” means a plan submitted by an eligible entity under subsection (e)(1). (2) **Eligible entity** — The term “eligible entity” means a— (A) State; or (B) Tribal government. (3) **Multi-entity group** — The term “multi-entity group” means a group of 2 or more eligible entities desiring a grant under this section. (4) **Online service** — The term “online service” means any internet-facing service, including a website, email, virtual private network, or custom application. (5) **Rural area** — The term “rural area” has the meaning given the term in [section 5302 of title 49](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title49-section5302&num=0&edition=prelim). (6) **State and Local Cybersecurity Grant Program** — The term “State and Local Cybersecurity Grant Program” means the program established under subsection (b). (7) **Tribal government** — The 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](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title25-section5131&num=0&edition=prelim). **(b) Establishment** (1) **In general** — There 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) **Application** — An eligible entity desiring a grant under the State and Local Cybersecurity Grant Pr

Source: Supplied U.S. Code snapshot — release unconfirmed · 6 U.S.C. § 671

Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

6 U.S.C. § 674 — Ransomware threat mitigation activities

**(a) Joint Ransomware Task Force** (1) **In general** — Not 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) **Composition** — The 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) **Responsibilities** — The 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) Coll

Source: Supplied U.S. Code snapshot — release unconfirmed · 6 U.S.C. § 674

Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

6 U.S.C. § 162 — Mission of Office; duties

Page 65 TITLE 6—DOMESTIC SECURITY § 162 PRIOR PROVISIONS A prior subtitle C of title II of Pub. L. 107–296, which was classified to this part, was redesignated subtitle B of title II of Pub. L. 107–296 by Pub. L. 115–278, § 2(g)(2)(K), Nov. 16, 2018, 132 Stat. 4178, and transferred to part B (§ 141 et seq.) of this subchapter. § 161. Establishment of Office; Director (a) Establishment (1) In general There is hereby established within the De- partment of Justice an Office of Science and Technology (hereinafter in this subchapter re- ferred to as the ‘‘Office’’). (2) Authority The Office shall be under the general author- ity of the Assistant Attorney General, Office of Justice Programs, and shall be established within the National Institute of Justice. (b) Director The Office shall be headed by a Director, who shall be an individual appointed based on ap- proval by the Office of Personnel Management of the executive qualifications of the individual. (Pub. L. 107–296, title II, § 231, Nov. 25, 2002, 116 Stat. 2159.) Editorial Notes REFERENCES IN TEXT This subchapter, referred to in subsec. (a)(1), was in the original ‘‘this title’’, meaning title II of Pub. L. 107–296, Nov. 25, 2002, 116 Stat. 2145, which enacted this subchapter, amended sections 1030, 2511, 2512, 2520, 2701 to 2703, and 3125 of Title 18, Crimes and Criminal Proce- dure, sections 10102 and 10122 of Title 34, Crime Control and Law Enforcement, and section 401a of Title 50, War and National Defense, and enacted provisions set out as a note under section 101 of this title and listed in a Pro- visions for Review, Promulgation, or Amendment of Federal Sentencing Guidelines Relating to Specific Of- fenses table set out under section 994 of Title 28, Judici- ary and Judicial Procedu

Source: Supplied 2024 U.S. Code historical extraction · 6 U.S.C. § 162

Stored review status: historical_2024_not_currentness_verified. Same stored citation; legal effect and authority still require review.