# Cybersecurity and Infrastructure Security Agency (CISA)

**In short:** CISA is the Department of Homeland Security agency that took that name on November 16, 2018, and leads the national effort to understand, manage and reduce risk to cyber and physical infrastructure. Federal civilian executive branch agencies are required to comply with its binding operational directives and emergency directives, and its Continuous Diagnostics and Mitigation program gives participating agencies tools and dashboards for their assets and vulnerabilities. Its rule for critical infrastructure incident reporting under CIRCIA was still a proposal as checked on 2026-11-14, so that reporting is not yet required.

Federal agency · Government, Cross-sector. Published November 14, 2026. Last reviewed November 14, 2026. Official site: <https://www.cisa.gov/>.

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. <https://creativecommons.org/licenses/by/4.0/>. Attribution: "Moraph Insights", <https://insights.moraph.com/regulators/cisa>.

Each point ends with the number of its source in "Sources". Points were checked on November 14, 2026 unless the point gives another date. Data: <https://insights.moraph.com/regulators/cisa.json> (JSON).

## Remit

- By statute, the National Protection and Programs Directorate of the Department of Homeland Security has been known as the Cybersecurity and Infrastructure Security Agency since November 16, 2018; it is headed by a Director who reports to the Secretary (6 U.S.C. 652(a) and (b)). [2]
- The Director's statutory duties include leading the agency's cybersecurity and critical infrastructure security programs and operations, coordinating a national effort to secure critical infrastructure, carrying out the Secretary's responsibilities to secure federal information systems under subchapter II of chapter 35 of title 44, and running the .gov internet domain (6 U.S.C. 652(c)). [2]
- CISA describes its mission as leading the national effort to understand, manage and reduce risk to cyber and physical infrastructure, across three areas: cybersecurity, infrastructure security and emergency communications; it calls itself the National Coordinator for Critical Infrastructure Security and Resilience. [1]
- Binding operational directives may set requirements for reporting incidents to the federal information security incident center, for the contents of agencies' annual FISMA reports and for mitigating exigent risks; emergency directives respond to a known or reasonably suspected threat, vulnerability or incident that represents a substantial threat to an agency's information security, and must use the least intrusive means possible and the shortest period practicable (44 U.S.C. 3553(b)(2) and (h)). [3]

## Who it supervises

- Federal civilian executive branch agencies, which are required to comply with DHS-developed directives; the directives do not apply to statutorily defined national security systems or to certain systems operated by the Department of Defense or the Intelligence Community. [4]
- Contractors are outside BOD 26-04 unless the procurement contract says otherwise, but agencies must review their contracts for needed changes; for FedRAMP cloud offerings agencies work through the FedRAMP Program Management Office, and for other cloud offerings directly with the provider. [5]
- Critical infrastructure owners and operators receive analyses, expertise and technical assistance from CISA on request, in coordination with Sector-Specific Agencies where appropriate (6 U.S.C. 652(c)(5)). [2]

## How it examines

- The Continuous Diagnostics and Mitigation (CDM) program, developed in 2012, delivers cybersecurity tools, integration services and dashboards to participating agencies; its Shared Services Platform gives 75 eligible non-CFO Act agencies access to CDM capabilities. [8]
- BOD 23-01 (October 3, 2022) required agencies, by April 3, 2023, to run automated asset discovery every 7 days, start vulnerability enumeration across all discovered assets every 14 days, and feed the results into the CDM Agency Dashboard within 72 hours of discovery completion. [7]
- Under BOD 26-04 agencies report the status of Known Exploited Vulnerabilities through the CDM Dashboard; agencies that have not automated that reporting report manually every two weeks, and every seven days once the 180-day phase applies. They keep CISA Cyber Hygiene scanning running and attest their publicly exposed IP addresses and domain names once a quarter or on CISA's request. [5]

## Technology and security guidance

- CISA's Secure by Design work asks technology makers to take ownership of product security at the executive level; its page states that over 200 software manufacturers have committed to take specific, measurable actions in line with secure by design principles. [9]
- The Known Exploited Vulnerabilities catalog, set up in 2021 under BOD 22-01, remains in use under BOD 26-04, which keeps the criteria for adding a vulnerability unchanged; CISA publishes KEV status, exploit automation and technical impact for every CVE ID through its Vulnrichment program. [5]

## Recent rules

- BOD 26-04, Prioritizing Security Updates Based on Risk (June 10, 2026), supersedes and revokes BOD 19-02 and BOD 22-01 and sets remediation timelines by asset exposure, KEV status, exploit automation and technical impact; a timeline marked with forensic triage means remediation within three days plus a forensic triage of the asset. Agencies update their vulnerability management policies at once, update processes within 60 days and remediate to the timelines within 180 days of issuance. [5]
- BOD 26-02, Mitigating Risk From End-of-Support Edge Devices (February 5, 2026), requires agencies to inventory devices on CISA's end-of-support edge device list within 3 months, decommission listed devices whose end-of-support date falls on or before the 12-month deadline within 12 months, decommission all identified end-of-support edge devices within 18 months, and set up continuous discovery of edge devices within 24 months. [6]
- On January 8, 2026 CISA retired ten emergency directives issued between 2019 and 2024, among them ED 19-01 (DNS infrastructure tampering) and ED 21-01 (SolarWinds Orion); seven were tied to vulnerabilities now in the KEV catalog. [13]
- The CIRCIA proposed rule would implement the statute's requirement to report covered cyber incidents within 72 hours and ransom payments within 24 hours; CISA states the comment period ran from April 4 through July 3, 2024. As checked on 2026-11-14 CISA says it continues to work on the final rule, held four town halls from June 15 to June 18, 2026, and that funding lapses affected the rulemaking; a Federal Register API search that day for "CIRCIA" in documents published since April 1, 2024 found no final rule. [10]
- The proposed rule, Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA) Reporting Requirements, was published in the Federal Register on April 4, 2024 (89 FR 23644), with comments due June 3, 2024 as published. [11]

## Enforcement

What the regulator's own pages say about its enforcement. Not a count or a pattern of actions.

- BOD 26-04 requires each agency to set internal validation and enforcement procedures to ensure adherence, and internal tracking and reporting, with reports to CISA as requested. [5]
- Congress let the statutory authority for the Chemical Facility Anti-Terrorism Standards (6 CFR part 27) expire on July 28, 2023, so CISA states it cannot currently enforce those regulations, require chemical reporting or perform CFATS inspections. [12]
- CIRCIA incident and ransom payment reporting will not be required until the final rule takes effect; until then CISA encourages voluntary reporting. [10]

## Official channels

- Cybersecurity directives: <https://www.cisa.gov/news-events/directives>
- Known Exploited Vulnerabilities catalog: <https://www.cisa.gov/known-exploited-vulnerabilities-catalog>
- Report a cyber incident: <https://myservices.cisa.gov/irf>
- CIRCIA rulemaking: <https://www.cisa.gov/topics/cyber-threats-and-advisories/information-sharing/cyber-incident-reporting-critical-infrastructure-act-2022-circia>
- Secure by Design: <https://www.cisa.gov/securebydesign>

## Sources

1. Cybersecurity and Infrastructure Security Agency. About CISA. <https://www.cisa.gov/about> Checked November 14, 2026.
2. U.S. Government Publishing Office (govinfo), United States Code 2024 edition. 6 U.S.C. 652, Cybersecurity and Infrastructure Security Agency. <https://www.govinfo.gov/content/pkg/USCODE-2024-title6/html/USCODE-2024-title6-chap1-subchapXVIII-partA-sec652.htm> Checked November 14, 2026.
3. U.S. Government Publishing Office (govinfo), United States Code 2024 edition. 44 U.S.C. 3553, Authority and functions of the Director and the Secretary. <https://www.govinfo.gov/content/pkg/USCODE-2024-title44/html/USCODE-2024-title44-chap35-subchapII-sec3553.htm> Checked November 14, 2026.
4. Cybersecurity and Infrastructure Security Agency. Cybersecurity Directives. <https://www.cisa.gov/news-events/directives> Checked November 14, 2026.
5. Cybersecurity and Infrastructure Security Agency. BOD 26-04: Prioritizing Security Updates Based on Risk. <https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk> Checked November 14, 2026.
6. Cybersecurity and Infrastructure Security Agency. BOD 26-02: Mitigating Risk From End-of-Support Edge Devices. <https://www.cisa.gov/news-events/directives/bod-26-02-mitigating-risk-end-support-edge-devices> Checked November 14, 2026.
7. Cybersecurity and Infrastructure Security Agency. BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks. <https://www.cisa.gov/news-events/directives/bod-23-01-improving-asset-visibility-and-vulnerability-detection-federal-networks> Checked November 14, 2026.
8. Cybersecurity and Infrastructure Security Agency. Continuous Diagnostics and Mitigation (CDM) Program. <https://www.cisa.gov/resources-tools/programs/continuous-diagnostics-and-mitigation-cdm-program> Checked November 14, 2026.
9. Cybersecurity and Infrastructure Security Agency. Secure by Design. <https://www.cisa.gov/securebydesign> Checked November 14, 2026.
10. Cybersecurity and Infrastructure Security Agency. Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA). <https://www.cisa.gov/topics/cyber-threats-and-advisories/information-sharing/cyber-incident-reporting-critical-infrastructure-act-2022-circia> Checked November 14, 2026.
11. Office of the Federal Register. Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA) Reporting Requirements, proposed rule, 89 FR 23644 (April 4, 2024). <https://www.federalregister.gov/documents/2024/04/04/2024-06526/cyber-incident-reporting-for-critical-infrastructure-act-circia-reporting-requirements> Checked November 14, 2026.
12. Cybersecurity and Infrastructure Security Agency. Chemical Facility Anti-Terrorism Standards (CFATS). <https://www.cisa.gov/resources-tools/programs/chemical-facility-anti-terrorism-standards-cfats> Checked November 14, 2026.
13. Cybersecurity and Infrastructure Security Agency. CISA Retires Ten Emergency Directives, Marking an Era in Federal Cybersecurity (press release, January 8, 2026). <https://www.cisa.gov/news-events/news/cisa-retires-ten-emergency-directives-marking-era-federal-cybersecurity> Checked November 14, 2026.

Last reviewed: November 14, 2026
Canonical URL: <https://insights.moraph.com/regulators/cisa>
Publisher: Moraph Insights
