Background and Need for Legislation
In 2002, Congress passed the Federal Information Security
Management Act (FISMA), which established a framework to
protect federal agency information systems. FISMA 2024 updates
the 2002 FISMA law, as well as the subsequent 2014 revision, by
further clarifying federal cybersecurity roles and
responsibilities.\1\
---------------------------------------------------------------------------
\1\Federal Information Security Management Act, Pub. L. No. 107-
347, 116 Stat. 2899 (2002); Federal Information Security Modernization
Act, Pub. L. No. 113-283, 128 Stat. 3073 (2014).
---------------------------------------------------------------------------
The U.S. government's increasing use of and reliance on
technology to provide information and services to all Americans
makes federal information systems a constant target of hostile
nations, criminal organizations, and other malicious actors
that leverage modern advances in technology. Attacks on federal
information systems are disruptive not just to agency missions
and programs, but also risk exposure of sensitive national
security and the public's private information.
Over the past decade, cyber incidents have become more
sophisticated, often presenting `zero-day' threats with the
potential to cause significant and widespread harm.
Adversaries--including criminal syndicates and nation states--
continue to exploit weaknesses borne from bureaucratic layers,
misaligned roles and responsibilities, and the resulting
confusion in the immediate aftermath of an intrusion.
For instance, in 2015, the Office of Personnel Management
announced the cyber theft of the sensitive information of over
20 million Americans.\2\ Between 2019 and 2020, nine federal
agencies and 100 private sector organizations were compromised
by the SolarWinds software supply-chain attack.\3\ In 2021, the
Colonial Pipeline ransomware attack showed the havoc an attack
on our nation's critical infrastructure could wreak as cars
lined up at gas stations in parts of the U.S. with ``panicked
Americans filling bags with fuel.''\4\ Also in 2021, meat
supplier JBS paid a ransom of $11 million when a cyber-attack
shut down its entire beef processing operation.\5\ And it is
not just cyber-attacks that cause problems, as evidenced by the
recent faulty CrowdStrike software update that led to the
``largest IT outage in history,''\6\ impacting several critical
industries worldwide including multiple federal agencies--a
stark reminder of how dependent many global organizations are
on common software systems.
---------------------------------------------------------------------------
\2\Ellen Nakashima, Hacks of OPM databases compromised 22.1 million
people, federal authorities say, The Washington Post (July 9, 2015).
\3\Jessica Davis, White House: SolarWinds hack impacted 9 Fed
agencies, 100 entities, TechTarget (Feb. 18, 2021).
\4\Blog Post, Cybersecurity and Infrastructure Security Agency, The
attack on Colonial Pipeline: what we've learned and what we've done
over the past two years (May 7, 2023).
\5\Brian Fung, JBS says it paid $11 million ransom after
cyberattack, CNN Business (June 9, 2021).
\6\Ruxandra Iordache et al, Microsoft-CrowdStrike issue causes
`largest IT outage in history,' CNBC (July 19, 2024).
---------------------------------------------------------------------------
To address some of the major gaps in federal cybersecurity
underscored by these examples, a core tenet of this legislation
is to equip the executive branch with the ability to evolve and
mature cyber policies on an ongoing basis, and avoid locking
overly prescriptive technical mandates into law. The bill also
attempts to avoid imposing statutory constraints that increase
compliance burdens or inflexibly mandate solutions which fail
to stand the test of time even as it pushes agencies toward
becoming diligent stewardsof the sensitive and valuable
information under its purview.
For the first time, the bill incorporates the recently
established National Cyber Director (NCD) more broadly into the
FISMA framework, granting the office greater visibility into
federal agency budget cyber resourcing, tasking it with
coordinating agency incident reporting, and providing the NCD a
central role in federal agency cyber policy consultation.
Beyond the operational roles agencies must play in
responding to and mitigating intrusions and attacks, timely and
fulsome reporting to Congress is crucial for oversight and
potential legislative response. Therefore, H.R. 4552 assigns
central incident intake and reporting roles to the NCD in order
to improve coordination between Congress and the private
sector.
The Committee also recognizes that the Office of Management
and Budget (OMB) Federal Chief Information Security Officer
(CISO) is a critical official lacking a legal mandate. The bill
therefor codifies the Federal CISO as a `dual-hatted' role
within OMB and as a Deputy NCD to provide a valuable
coordination link between the nationally focused NCD and the
government-wide policy setting functions of OMB.
In addition to the above structural reforms to federal
cybersecurity roles and responsibilities, the bill proposes
modifications to the FISMA structure to ensure federal agencies
are continuously evaluating risks posed to the security of
devices, networks, software, and personnel within their
control. Specifically, the bill:
Requires agencies to designate Chief Privacy
Officers (Sec. 3(a)).
Advances the adoption of automation and zero
trust architectural principles (Sec. 3(c) & Sec. 9).
Requires continuous, ongoing Federal Risk
Assessments performed by CISA of the whole-of-
government cybersecurity risk posture (Sec. 3(c)).
Requires continuous, ongoing agency risk
assessments of high value assets, data, and systems, by
implementing penetration testing and agency
vulnerability disclosure programs (Sec. 3(c), Sec. 7, &
Sec. 8).
Adds a new framework for Federal System
Incident Response that includes notification
requirements for individuals potentially put at risk by
a cyber breach (Sec. 3(e) new Sec. 3592).
Mandates agencies notify Congress, OMB,
CISA, NCD, GAO, and the relevant agency Inspector
General within 72 hours of a major incident and include
a summary of the major incident (how the incident
occurred and the threat origin). Requires a
supplemental update to Congress within 30 days after
the notification (Sec. 3(e) new Sec. 3593).
Directs CISA to perform continuous and
automated monitoring of compromises, to improve
incident response (Sec. 3(e) new Sec. 3594).
Requires contractors or awardees to report
incidents and breaches to the contracting agency within
a day, which will then report to DHS. If a contractor
or awardee receives information about a security
vulnerability or supply chain compromise through a
third party (such as a vulnerability disclosure
program), then the contractor or awardee must notify
the contracting agency and DHS within 90 days (Sec.
3(e) new Sec. 3595).
Requires an agency that experiences a
covered breach to determine whether to send a notice to
potentially impacted individuals within 45 days--with
some exceptions allowing for a delay to 60 days--and
notification to relevant congressional committees
within 30 days (Sec. 3(e) new Sec. 3592).
Establishes a federal penetration testing
policy to understand agency preparedness (Sec. 7) and
codifies agency vulnerability disclosure programs to
address known problems (Sec. 8).
Requires an OMB and GAO report on the ways
AI can help automate and enhance agency cybersecurity
functions and for GAO to report on the privacy risks
associated with federal agency use of AI (Sec. 10).
Improves existing agency identity management
requirements and addresses shortcomings of the GSA-
developed Login.gov single sign-on identity platform
with increased oversight and guidance (Sec. 11).
H.R. 4552 represents a prudent and effective response to
the recent escalation of costly cyber-attacks and intrusions,
updating authorities to strengthen the federal government's
cyber defense as technology evolves and threats become more
sophisticated, persistent, and malicious.
Section-by-Section Analysis
Section 1. Short title
The short title is ``Federal Information Security
Modernization Act of 2024.''
Section 2. Definitions
This section defines the following terms for the
Act: agency, appropriate congressional committees, awardee,
contractor, Director, federal information system, incident,
national security system, penetration test, threat hunting, and
zero trust architecture.
Section 3. Amendments to title 44
Subsection (a) amends several sections in
subchapter I (Federal Information Policy) of chapter 35 of
title 44 related to federal information policy.
(a)(1) amends 44 U.S.C. Sec. 3504
related to the authority and functions of the Director
of the Office of Management and Budget (OMB). It
requires the OMB Director to consult with the National
Cyber Director (NCD) when developing and overseeing the
implementation of policies, principles, standards, and
guidelines on information security.
(a)(2) amends 44 U.S.C. Sec. 3505
related to the assignment of tasks and deadlines. It
requires agency heads to include internet-accessible
information systems and assets in the inventory of
major information systems required by the subsection.
Agency heads are directed to make the inventory
available to the NCD and the Director of the
Cybersecurity and Infrastructure Security
Administration (CISA) in addition to the Comptroller
General, and to maintain it on a continual basis
through the use of automation, machine-readable data,
and scanning wherever practicable. The paragraph also
removes a duplicated subsection (c) from section 3505.
(a)(3) amends 44 U.S.C. Sec. 3506
related to federal agency responsibilities. It requires
each agency Chief Information Officer (CIO) to
coordinate with the agency Chief Data Officer, as
appropriate, in ensuring prompt, efficient, and
effective implementation of, and compliance with,
information policies and resources management
responsibilities. It also requires agencies to improve
the availability of information to all users, both
within and outside the agency.
(a)(4) amends 44 U.S.C. Sec. 3513. It
requires agencies to provide any portion of a written
plan, developed in response to an OMB review under
Sec. 3513(a), addressing information security or
cybersecurity, to the National Cyber Director and
Secretary of Homeland Security.
Subsection (b) amends definitions in U.S.C.
subchapter II (Information Security) of chapter 35 of title 44.
(b)(1) amends 44 U.S.C. Sec. 3552(b) to
add definitions for the following terms: high value
asset, major incident, penetration test, shared
service, and zero trust architecture.
(b)(2) contains conforming amendments to
align various federal statutes with the updated
definitions in section 3552.
Subsection (c) amends U.S.C. sections in
subchapter II of chapter 35 of title 44.
(c)(1) amends 44 U.S.C. Sec. 3551
related to the purposes of the subchapter. It clarifies
that automated tools to continuously diagnose and
improve the security of agency information security
programs should also continuously integrate and deliver
security. It also recognizes that each agency has
specific mission requirements that lead to unique
cybersecurity requirements, with varying levels of
resources, and should not be expected to have the
capability to secure its systems from advanced
adversaries alone. Rather, a holistic federal
cybersecurity model is necessary to account for these
differences.
(c)(2) amends 44 U.S.C. Sec. 3553
related to the authority and functions of OMB and the
Secretary of Homeland Security. The subsection:
D Requires OMB to work with CISA, the NCD,
and the National Institute of Standards and
Technology (NIST) to promote the use of
automation and zero trust architecture to
improve cybersecurity.
D Requires the Secretary of Homeland Security
to consult with the NCD, in addition to OMB, in
implementing agency information security
policies and practices.
D Directs CISA to seek opportunities to
reduce costs, administrative burdens, and other
barriers to information technology security and
modernization faced by agencies, including
through shared services contracts and technical
assistance and expertise on the selection and
successful engagement of government-wide
contract vehicles offered by the GSA.
D Reduces the frequency of OMB's report to
Congress on the state of federal information
security from annually to biennially and
removes the summary of incidents previously
required in the reports.
D Amends the OMB and DHS annual report to
appropriate congressional committees on actions
taken to oversee agency FISMA compliance,
adding a summary of the trends identified in
the federal risk assessments and requiring the
reports to be unclassified (with a classified
annex).
D Includes the NCD in developing the
procedures for issuing emergency directives and
requires that CISA notify the NCD, in addition
to OMB and the head of any affected agency,
immediately upon the issuance of an emergency
directive.
D Requires CISA to provide prior notice to
the NCD, in addition to OMB and the head and
CIO of each affected agency, when authorizing
the use of intrusion detection and prevention
capabilities.
D Creates a new requirement that federal risk
assessments by CISA be performed on an ongoing
and continual basis to determine the
cybersecurity posture of agencies. CISA is
required to brief OMB and the NCD on these
assessments, and OMB is required to include a
summary of each assessment in its annual report
to Congress.
D Requires CISA to report to appropriate
reporting entities, including Congress, on
agency status of implementing Emergency
Directives (first within 7 days with 30-day
updates) and Binding Operational Directives
(first within 30 days with 90-day updates)
issued by the Secretary of DHS.
D Directs OMB and GAO to review the efficacy
of OMB-issued information security guidance and
policies once every 3 years.
D Directs NIST to develop, as appropriate,
specifications to enable agencies to automate
the verification of NIST-required controls.
D Requires CISA to provide federal risk
assessment information to the Inspector General
of the Department of Homeland Security and
other appropriate IGs upon request.
(c)(3) amends 44 U.S.C. Sec. 3554
related to the responsibilities of agencies. The
subsection:
D Requires agency heads to perform an agency
system risk assessment on an ongoing and
continual basis. The assessment must identify
high value assets, evaluate data assets and
associated agency systems, assess threats based
on federal and non-federal cyber threat
intelligence products, analyze vulnerabilities
including through penetration testing and
agency vulnerability disclosure programs, and
assess the impacts and consequences of
potential incidents for both the agency and
other agencies. Agency heads must provide an
update on the assessment to OMB, CISA, and the
NCD at intervals determined by OMB guidance,
and upon request, to the agency inspector
general and the Government Accountability
Office (GAO).
D Aligns existing provisions of the Code with
the updated risk assessment, implementation
plan, and other programs added by the bill.
D Technical correction to remove provisions
requiring reporting of a major incident to
Congressional Committees within seven days of
reasonably knowing that the event occurred. The
bill instead adds a new section 3593
(``Congressional and executive branch
reports.'') to Title 44 that requires more
timely Congressional reporting with 72 hours of
a major incident occurring (see p. 51).
D Changes existing law by requiring each
agency to submit a biennial report, rather than
an annual report, summarizing its annual risk
assessment, evaluating the effectiveness of
cybersecurity policies, and summarizing the
status of remedial actions identified by the
agency Inspector General, GAO, or any other
source to OMB, DHS, Congressional leadership,
relevant Congressional committees, the NCD, and
GAO. The subsection directs that, to the
greatest extent practicable, those reports
should be unclassified, but may include 1 or
more annexes that contain classified or
sensitive information. The subsection also
mandates that OMB provide a briefing to
congressional committees the years a report is
not required. Finally, the subsection requires
each agency to identify a Chief Information
Security Officer (CISO) to manage information
security, cybersecurity budgets, and risk and
compliance activities.
(c)(4) amends 44 U.S.C. Sec. 3555
related to the annual independent evaluation of agency
information security programs. The subsection:
D Changes the independent evaluations of
agency information security programs and
practices from yearly to biennial (in line with
the change to have agencies submit biennial
rather than annual FISMA reports to Congress).
D Instructs OMB to identify any entity
performing this independent audit in OMB's
summary report to Congress of these
evaluations.
D Requires that OMB, in consultation with
CISA, the CIO Council, the Council of the
Inspectors General on Integrity and Efficiency
(CIGIE), and other interested parties, shall
develop risk-based guidance for evaluating the
effectiveness of information security programs
and practices.
D Requires the risk-based guidance to
prioritize the identification of the most
common threat patterns experienced by each
agency and the security controls that address
those patterns, and any other security risks
unique to the networks of each agency.
D Requires agency heads to coordinate with
their IGs to ensure consistent understanding of
agency cybersecurity policies.
(c)(5) amends 44 U.S.C. Sec. 3556(a) to
require the existing reference to a Federal information
security incident center be maintained at CISA. This
subsection also amends 44 U.S.C. Sec. 3556(a) to
require that the intelligence and information on cyber
threats, vulnerabilities, and incidents provided by the
federal information security incident center to
agencies be used in the risk assessments required by
section 3554(a)(1)(A).
Subsection (d) makes conforming amendments to
update the table of sections and update other references to
FISMA reports to be submitted every two years, instead of every
year, as changed in Sec. 3553.
Subsection (e)
Subsection (e)(1) amends U.S.C. by
adding a new subchapter IV, entitled ``Federal System
Incident Response,'' to chapter 35 of title 44. The new
subchapter contains the following sections:
D Section 3591 (``Definitions'') defines the
following terms: appropriate reporting
entities, awardee, breach, contractor, federal
information, federal information system,
intelligence community, nationwide consumer
reporting agency, and vulnerability disclosure.
D Section 3592 (``Notification of breach'')
requires agency heads to expeditiously
determine whether notice to individuals
potentially impacted by a cybersecurity breach
(involving not less than 50,000 people, but
subject to change if agency head makes such a
determination) is appropriate and, if
appropriate, to notify those individuals within
45 days after the agency has concluded that
such an incident occurred. The section:
Specifies the contents of
the notification, which must include a
description of the breach, a
description of the types of personally
identifiable information (PII) affected
by the breach (if possible), the
relevant contact information for the
agency, information on any remedy the
agency is offering, and educational
materials.
Allows the head of an agency
in coordination with OMB and the
National Cyber Director, and as
appropriate, with the Attorney General,
Director of National Intelligence, or
Secretary of Homeland Security to delay
the notification for 60 days, with an
option to renew the delay, if it would
impede a criminal investigation, reveal
sensitive sources and methods, cause
damage to national security, or hamper
security remediation actions.
Requires the agency head to
re-notify individuals within 30 days if
there is a significant change in
information or understanding related to
the breach.
Requires the head of an
agency to submit annual reports to
Congress regarding any delays of
notifications or determinations to not
provide notifications from the prior
two years.
Requires agencies affected
by a covered breach to notify Congress
within 30 days. The notice should
include information about the covered
breach, an estimate of the number of
affected individuals, including an
assessment of the risk of harm,
description of any circumstances
necessitating a delay in providing
notice to individuals affected by the
covered breach, and an estimate of when
the agency will provide notice to
impacted individuals.
Clarifies that this section
does not limit OMB from issuing
guidance related to notifications of
incidents or major incidents, nor does
it limit agency heads from notifying
individuals potentially impacted by
non-major breaches. It also does not
limit agency heads from issuing
notifications that provide more
information than required in this
section.
D Section 3593 (``Congressional and executive
branch reports on major incidents'') requires
agencies, within 72 hours of having reasonable
basis to conclude that a major incident
occurred, to provide written notification to
House and Senate leadership, the Senate
Committee on Homeland Security and Governmental
Affairs, the House Committee on Oversight and
Accountability, the House Committee on Homeland
Security, House Committee on Science, Space,
and Technology, and the appropriate
authorization and appropriations committees.
The section:
Specifies that the written
notification contain a summary of the
available information about the major
incident including how it occurred,
whether it was appropriate to provide
notification to potentially impacted
individuals, an assessment of any
impacts to government operations or
national security, among other things,
and whether any ransom has been
demanded or paid by an entity operating
or with access to a federal information
system.
It also requires a
supplemental written update within 30
days after the initial written
notification, and requires the agency
to provide an additional updated report
if the agency, OMB, or the NCD
determines there is any significant
change in the agency's understanding of
the incident followin
Committee Consideration
On March 7, 2024, the Committee met in open session and
ordered the bill, H.R. 4552, favorably reported with an
amendment in the nature of a substitute, by a roll call vote of
32-7, a quorum being present.
Roll Call Votes
In compliance with clause 3(b) of rule XIII of the Rules of
the House of Representatives, the following roll call vote
occurred during the Committee's consideration of H.R. 4552:
[GRAPHIC(S) NOT AVAILABLE IN TIFF FORMAT]
Explanation of Amendments
During Committee consideration of the bill, Representative
James Comer (R-KY), Chairman of the Committee, offered an
amendment in the nature of a substitute that removed seven bill
sections from the introduced text and made substantive edits
including to the contractor vulnerability and disclosure
policies and federal cybersecurity requirements. The amendment
in the nature of a substitute passed by voice vote.
List of Related Committee Hearings
In accordance with clause 3(c)(6) of rule XIII of the Rules
of the House of Representatives, (1) The following hearings
were used to develop or consider H.R. 4552:
On March 23, 2023, the Subcommittee on Cybersecurity,
Information Technology, and Government Innovation held a
hearing titled, ``Unpacking the White House National
Cybersecurity Strategy'' with Ms. Kemba Walden, Acting National
Cyber Director, White House Office of the National Director.
On May 10, 2023, the Subcommittee on Cybersecurity,
Information Technology, and Government Innovation held a
hearing titled, ``Risky Business: Costly Inaction on Federal
Legacy IT'' with Mr. Kevin Walsh, Director, Information
Technology and Cybersecurity, U.S. Government Accountability
Office; Ms. Suzette Kent, Chief Executive Officer, Kent
Advisory Services; and Mr. David Powner, Executive Director,
Center for Data-Driven Policy, The MITRE Corporation.
Statement of Oversight Findings and Recommendations of
the Committee
In compliance with clause 3(c)(1) of rule XIII and clause
(2)(b)(1) of rule X of the Rules of the House of
Representatives, the Committee's oversight findings and
recommendations are reflected in the Background and Need for
Legislation section above.
Statement of General Performance Goals and Objectives
In accordance with clause 3(c)(4) of rule XIII of the Rules
of the House of Representatives, the Committee's performance
goals or objectives of this bill are to update the Federal
Information Security Management Act of 2002 (FISMA), last
updated in 2014, by clarifying federal cybersecurity roles and
responsibilities.
Application of Law to the Legislative Branch
Section 102(b)(3) of Public Law 104-1 requires a
description of the application of this bill to the legislative
branch where the bill relates to the terms and conditions of
employment or access to public services and accommodations.
This bill does not relate to employment or access to public
services and accommodations in the legislative branch.
Duplication of Federal Programs
In accordance with clause 3(c)(5) of rule XIII of the Rules
of the House of Representatives, no provision of this bill
establishes or reauthorizes a program of the Federal Government
known to be duplicative of another Federal program, a program
that was included in any report from the Government
Accountability Office to Congress pursuant to section 21 of
Public Law 111-139, or a program related to a program
identified in the most recent Catalog of Federal Domestic
Assistance.
Federal Advisory Committee Act Statement
The Committee finds that this legislation does not direct
the establishment of advisory committees within the definition
of Section 5(b) of the appendix to title 5, U.S.C.
Unfunded Mandates Reform Act Statement
Pursuant to section 423 of the Congressional Budget Act of
1974 the Committee has included a letter received from the
Congressional Budget Office below.
Earmark Identification
This bill does not include any congressional earmarks,
limited tax benefits, or limited tariff benefits as defined in
clause 9 of rule XXI of the Rules of the House of
Representatives.
Committee Cost Estimate
Pursuant to clause 3(d) of rule XIII of the Rules of the
House of Representatives, the Committee includes below a cost
estimate of the bill prepared by the Director of the
Congressional Budget Office under section 402 of the
Congressional Budget Act of 1974.
New Budget Authority and Congressional Budget Office
Cost Estimate
Pursuant to clause 3(c)(2) of rule XIII of the Rules of the
House of Representatives and section 308(a) of the
Congressional Budget Act of 1974, and pursuant to clause
3(c)(3) of rule XIII of the Rules of the House of
Representatives, the cost estimate prepared by the Director of
the Congressional Budget Office and submitted pursuant to
section 402 of the Congressional Budget Act of 1974 is as
follows:
[GRAPHIC(S) NOT AVAILABLE IN TIFF FORMAT]
The bill would:
Update policies, procedures, and programs
for information security at federal agencies
Require all federal agencies to report
significant cyber incidents on their networks
Require agencies to train federal
information technology workers on responding to cyber
incidents
Estimated budgetary effects would mainly stem from:
Contracting with information security
service companies
Hiring information security analysts
Providing cyber incident response training
to federal employees
Reporting and responding to cyber incidents
at federal agencies
Areas of significant uncertainty include:
Anticipating the adoption schedules of new
cybersecurity procedures and programs
Predicting the staffing and contracting
requirements of federal information security offices
Bill summary: The Federal Information Security
Modernization Act (FISMA) provides a framework to protect
government information operations against cybersecurity
threats. H.R. 4552 would update FISMA to require federal
agencies to report all cybersecurity incidents and conduct
standardized cybersecurity procedures on a regular basis.
Estimated Federal cost: The estimated budgetary effects of
H.R. 4552 are shown in Table 1. The costs of the legislation
fall within budget functions 050 (national defense) and 800
(general government).
TABLE 1.--ESTIMATED BUDGETARY EFFECTS OF H.R. 4552
----------------------------------------------------------------------------------------------------------------
By fiscal year, millions of dollars--
----------------------------------------------------------------
2024 2025 2026 2027 2028 2029 2024-2029
----------------------------------------------------------------------------------------------------------------
INCREASES IN SPENDING SUBJECT TO APPROPRIATION
Federal Risk Assessment:
Estimated Authorization...................... * 3 3 3 3 3 15
Estimated Outlays............................ * 3 3 3 3 3 15
Cyber Incident Training:
Estimated Authorization...................... * 2 3 3 3 3 14
Estimated Outlays............................ * 2 3 3 3 3 14
Reporting Requirements:
Estimated Authorization...................... * * 4 2 6 2 14
Estimated Outlays............................ * * 4 2 6 2 14
Total Changes:
Estimated Authorization.................... * 5 10 8 12 8 43
Estimated Outlays.......................... * 5 10 8 12 8 43
----------------------------------------------------------------------------------------------------------------
In addition to the budgetary effects shown above, CBO estimates that enacting H.R. 4552 would have insignificant
effects on direct spending and the deficit over the 2024-2034 period.
*=between zero and $500,000.
Basis of estimate: For this estimate, CBO assumes that H.R.
4552 will be enacted in fiscal year 2024. Outlays are based on
historical spending patterns for existing or similar programs.
Spending subject to appropriation: CBO estimates that
implementing the bill would cost $43 million over the 2024-2029
period. Such spending would be subject to the availability of
appropriated funds.
Federal Risk Assessment: H.R. 4552 would codify and expand
the responsibility of the Cybersecurity and Infrastructure
Security Agency (CISA) to assess and report on cyber
preparedness at federal agencies. Using information from CISA
about risk assessments and reporting efforts similar to those
that the bill would require, CBO anticipates that the agency
would need five full-time employees to track and report on
cyber risks to federal agencies. Compensation and salaries for
those employees would total $5 million over the 2024-2029
period. CBO also expects that federal agencies would modify
existing cybersecurity services contracts to track and transmit
additional data from their information technology systems to
CISA at a cost of $10 million over that same period. In total,
implementing the risk assessments would cost $15 million over
the 2024-2029 period, CBO estimates.
Cyber Incident Training: H.R. 4552 would require federal
agencies to develop training for information technology workers
on how to identify and respond to cyber incidents. Using
information from agencies about government-wide training
efforts, CBO expects that CISA would need five full-time
employees to study best practices and establish standard
qualifications for the training. CBO also anticipates that
agencies will modify existing contracts for training to
incorporate the new content created by CISA. Accounting for the
time needed to develop the training, CBO estimates that
implementing this program would cost $14 million over the 2024-
2029 period for staff and information technology costs.
Reporting Requirements: H.R. 4552 would require federal
agencies to track and report on the effectiveness of their
information security programs. Under the bill, the Office of
Management and Budget (OMB) would compile those reports and
publish information about agency performance on a federal
dashboard. The Administration has issued executive orders and
memoranda concerning many of the reporting requirements
included in H.R. 4552. CBO expects those actions would satisfy
most of the requirements of the bill. H.R. 4552 also would
increase the frequency of some of the existing reporting
requirements and decrease the frequency of others. On the basis
of the costs of similar plans and reports, CBO estimates that
satisfying the reporting requirements of the bill would cost
$14million over the 2024-2029 period.
Direct spending: Enacting the bill could affect direct
spending by some federal agencies that are allowed to use fees,
receipts from the sale of goods, and other collections to cover
operating costs. CBO estimates that any net changes in direct
spending by those agencies would be negligible because most of
them can adjust amounts collected to reflect changes in
operating costs.
Uncertainty: Areas of uncertainty in this estimate include
predicting the implementation timeline at federal agencies. The
budgetary effects of the bill could be significantly higher or
lower than CBO's estimate if the time needed to adopt new
cybersecurity procedures and technology differs from CBO's
estimate.
The budgetary effects of the bill also would depend on the
number of additional employees that would be needed at CISA,
OMB, and other federal agencies to satisfy the requirements of
the bill. Costs would be moderately larger or smaller than this
estimate if the number of analysts hired differs from CBO's
estimate.
Pay-As-You-Go considerations: The Statutory Pay-As-You-Go
Act of 2010 establishes budget-reporting and enforcement
procedures for legislation affecting direct spending or
revenues. CBO estimates that enacting the bill would increase
direct spending by less than $500,000 over the 2024-2034
period.
Increase in long-term net direct spending and deficits: CBO
estimates that enacting H.R. 4552 would not significantly
increase net direct spending in any of the four consecutive 10-
year periods beginning in 2035.
CBO estimates that enacting H.R. 4552 would not
significantly increase on-budget deficits in any of the four
consecutive 10-year periods beginning in 2035.
Mandates: The bill contains no intergovernmental or
private-sector mandates as defined in the Unfunded Mandates
Reform Act.
Previous CBO estimate: On August 16, 2023, CBO transmitted
a cost estimate for S. 2251, the Cybersecurity Act of 2023, as
ordered reported by the Senate Committee on Homeland Security
and Governmental Affairs on July 26, 2023. The estimated cost
to CISA and federal agencies to implement H.R. 4552 is
substantially less than for S. 2551 because that bill included
requirements for data logging and retention, continuous risk
assessments, and additional personnel that would not be
required under H.R. 4552.
Estimate prepared by: Federal Costs: Aldo Prosperi;
Mandates: Brandon Lever.
Estimate reviewed by: David Newman, Chief, Defense,
International Affairs, and Veterans' Affairs Cost Estimates
Unit; Kathleen FitzGerald, Chief, Public and Private Mandates
Unit; Christina Hawley Anthony, Deputy Director of Budget
Analysis.
Estimate approved by: Phillip L. Swagel, Director,
Congressional Budget Office.
Changes in Existing Law Made by the Bill, as Reported
In compliance with clause 3(e) of rule XIII of the Rules of
the House of Representatives, changes in existing law made by
the bill, as reported, are shown as follows (existing law
proposed to be omitted is enclosed in black brackets, new
matter is printed in italics, and existing law in which no
change is proposed is shown in roman):
Changes in Existing Law Made by the Bill, as Reported
In compliance with clause 3(e) of rule XIII of the Rules of
the House of Representatives, changes in existing law made by
the bill, as reported, are shown as follows (existing law
proposed to be omitted is enclosed in black brackets, new
matter is printed in italics, and existing law in which no
change is proposed is shown in roman):
TITLE 44, UNITED STATES CODE
* * * * * * *
PART A--GENERAL
* * * * * * *
CHAPTER 35--COORDINATION OF FEDERAL
INFORMATION POLICY
* * * * * * *
SUBCHAPTER II--INFORMATION SECURITY
3551. Purposes.
* * * * * * *
[3555. Annual independent evaluation.]
3555. Independent evaluation.
* * * * * * *
3559A. Federal penetration testing.
3559B. Federal vulnerability disclosure policies.
* * * * * * *
SUBCHAPTER IV--FEDERAL SYSTEM INCIDENT RESPONSE
3591. Definitions.
3592. Notification of breach.
3593. Congressional and executive branch reports on major incidents.
3594. Government information sharing and incident response.
3595. Responsibilities of contractors and awardees.
3596. Training.
3597. Analysis and report on Federal incidents.
3598. Major incident definition.
* * * * * * *
SUBCHAPTER I--FEDERAL INFORMATION POLICY
* * * * * * *
Sec. 3504. Authority and functions of Director
(a)(1) The Director shall oversee the use of information
resources to improve the efficiency and effectiveness of
governmental operations to serve agency missions, including
burden reduction and service delivery to the public. In
performing such oversight, the Director shall--
(A) develop, coordinate and oversee the
implementation of Federal information resources
management policies, principles, standards, and
guidelines; and
(B) provide direction and oversee--
(i) the review and approval of the collection
of information and the reduction of the
information collection burden;
(ii) agency dissemination of and public
access to information;
(iii) statistical activities;
(iv) records management activities;
[(v) privacy, confidentiality, security,
disclosure, and sharing of information; and]
(v) privacy, confidentiality, disclosure, and
sharing of information;
(vi) in consultation with the National Cyber
Director, security of information; and
[(vi)] (vii) the acquisition and use of
information technology, including alternative
information technologies that provide for
electronic submission, maintenance, or
disclosure of information as a substitute for
paper and for the use and acceptance of
electronic signatures.
(2) The authority of the Director under this subchapter shall
be exercised consistent with applicable law.
(b) With respect to general information resources management
policy, the Director shall--
(1) develop and oversee the implementation of uniform
information resources management policies, principles,
standards, and guidelines;
(2) foster greater sharing, dissemination, and access
to public information, including through--
(A) the use of comprehensive data inventories
and the Federal data catalogue under section
3511; and
(B) the development and utilization of common
standards for information collection, storage,
processing and communication, including
standards for security, interconnectivity and
interoperability;
(3) initiate and review proposals for changes in
legislation, regulations, and agency procedures to
improve information resources management practices;
(4) oversee the development and implementation of
best practices in information resources management,
including training;
(5) oversee agency integration of program and
management functions with information resources
management functions; and
(6) issue guidance for agencies to implement section
3506(b)(6) in a manner that takes into account--
(A) risks and restrictions related to the
disclosure of personally identifiable
information, including the risk that an
individual data asset in isolation does not
pose a privacy or confidentiality risk but when
combined with other available information may
pose such a risk;
(B) security considerations, including the
risk that information in an individual data
asset in isolation does not pose a security
risk but when combined with other available
information may pose such a risk;
(C) the cost and benefits to the public of
converting a data asset into a machine-readable
format that is accessible and useful to the
public;
(D) whether the application of the
requirements described in such section to a
data asset could result in legal liability;
(E) a determination of whether a data asset--
(i) is subject to intellectual
property rights, including rights under
titles 17 and 35;
(ii) contains confidential business
information, that could be withheld
under section 552(b)(4) of title 5; or
(iii) is otherwise restricted by
contract or other binding, written
agreement;
(F) the requirement that a data asset be
disclosed, if it would otherwise be made
available under section 552 of title 5
(commonly known as the ``Freedom of Information
Act''); and
(G) any other considerations that the
Director determines to be relevant.
(c) With respect to the collection of information and the
control of paperwork, the Director shall--
(1) review and approve proposed agency collections of
information;
(2) coordinate the review of the collection of
information associated with Federal procurement and
acquisition by the Office of Information and Regulatory
Affairs with the Office of Federal Procurement Policy,
with particular emphasis on applying information
technology to improve the efficiency and effectiveness
of Federal procurement, acquisition and payment, and to
reduce information collection burdens on the public;
(3) minimize the Federal information collection
burden, with particular emphasis on those individuals
and entities most adversely affected;
(4) maximize the practical utility of and public
benefit from information collected by or for the
Federal Government;
(5) establish and oversee standards and guidelines by
which agencies are to estimate the burden to comply
with a proposed collection of information;
(6) publish in the Federal Register and make
available on the Internet (in consultation with the
Small Business Administration) on an annual basis a
list of the compliance assistance resources available
to small businesses, with the first such publication
occurring not later than 1 year after the date of
enactment of the Small Business Paperwork Relief Act of
2002.
(d) With respect to information dissemination, the Director
shall develop and oversee the implementation of policies,
principles, standards, and guidelines to--
(1) apply to Federal agency dissemination of public
information, regardless of the form or format in which
such information is disseminated; and
(2) promote public access to public information and
fulfill the purposes of this subchapter, including
through the effective use of information technology.
(e) With respect to statistical policy and coordination, the
Director shall--
(1) coordinate the activities of the Federal
statistical system to ensure--
(A) the efficiency and effectiveness of the
system; and
(B) the integrity, objectivity, impartiality,
utility, and confidentiality of information
collected for statistical purposes;
(2) ensure that budget proposals of agencies are
consistent with system-wide priorities for maintaining
and improving the quality of Federal statistics and
prepare an annual report on statistical program
funding;
(3) develop and oversee the implementation of
Gove