Browse Arkansas Code titles and sections
6 U.S.C. § 674 — Ransomware threat mitigation activities
Federal law — U.S. Code and appendices · legal_authorities
**(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. A text match is a research starting point; applicability is not established.
Original supplied file — preserved unchanged
Download original Markdown file
File SHA-256: 91f2eea5ae159933112fcf994919cf745505c16fafb47f697ecb6f409e929960. 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_61241e3186a38552b8922a41
Source file: Laws/federal/codes/united-states-code/title-6/section-674-ransomware-threat-mitigation-activities--5a70c10bb4.md
Pages: Not recorded – Not recorded
Passage SHA-256: 961f9be739523a94b6f817e16190d369ce6b65ba4b72ce221b2b869dd75987f5
Source location: Title 6, Chapter 1, § 674; chapter-001-homeland-security-organization.md
Stored source content
**(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) 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 construction** Nothing in this section shall be construed to provide any additional authority to any Federal agency.
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
**(a) Activities** The 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](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section1501&num=0&edition=prelim) 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
Source: Supplied U.S. Code snapshot — release unconfirmed · 6 U.S.C. § 101
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
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.
Source: Supplied U.S. Code snapshot — release unconfirmed · 6 U.S.C. § 681
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
In this part:
(1) **Center** — The term “Center” means the center established under [section 659 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section659&num=0&edition=prelim).
(2) **Council** — The term “Council” means the Cyber Incident Reporting Council described in [section 681f of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section681f&num=0&edition=prelim).
(3) **Covered cyber incident** — The 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](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section681b/b&num=0&edition=prelim).
(4) **Covered entity** — The 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](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section681b/b&num=0&edition=prelim).
(5) **Cyber incident** — The 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 threat** — The term “cyber threat” has the meaning given the term “cybersecurity threat” in [section 650 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title6-section650&num=0&edition=prelim).
(7) **Federal entit
Source: Supplied U.S. Code snapshot — release unconfirmed · 6 U.S.C. § 650
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
### 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. Incoming connection: Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
Page 381
TITLE 6—DOMESTIC SECURITY
§ 677a
structure 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 em-
ployee thereof, shall be fined under title 18, im-
prisoned not more than 1 year, or both, and shall
be removed from office or employment.
(g) Authority to issue warnings
The
Federal
Government
may
provide
advisories, alerts, and warnings to relevant com-
panies, targeted sectors, other governmental en-
tities, 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 submit-
ting person or entity, or is otherwise not ap-
propriately in the public domain.
(h) Authority to delegate
The President may delegate authority to a
critical infrastructure protection program, des-
ignated under section 672 of this title, to enter
into a voluntary agreement to promote critical
infrastructure security, including with any In-
formation Sharing and Analysis Organization,
or a plan of action as otherwise defined in sec-
tion 4558 of title 50.
(Pub. L. 107–296, title XXII, § 2224, formerly 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;
renumbered title XXII, § 2224, and amended Pub.
Source: Supplied 2024 U.S. Code historical extraction · 6 U.S.C. § 674
Stored review status: historical_2024_not_currentness_verified. Same stored citation; legal effect and authority still require review.