Government · Security & Resilience
Government: security and resilience
What to know now
Each number links to the point's source. Points checked unless the point shows another date.
- CISA’s BOD 26-04 (June 10, 2026) revokes BOD 22-01 and BOD 19-02. Remediation deadlines now depend on whether the asset is publicly exposed, whether the CVE is in the Known Exploited Vulnerabilities catalog, whether exploitation can be automated, and the technical impact. Within 180 days of issuance, agencies must remediate on the directive’s Table 1 timelines.1
- CISA’s BOD 26-02 (February 5, 2026) covers end-of-support edge devices on federal civilian networks. Within three months agencies inventory the devices on CISA’s EOS Edge Device List. Within twelve months they decommission listed devices with an end-of-support date on or before that deadline, and inventory all in-scope edge devices that are or will be out of support within twelve months. Within eighteen months they decommission all identified end-of-support edge devices, and within twenty-four months they set up continuous discovery.2
- OMB memorandum M-26-14 (May 22, 2026) rescinds M-21-31 and directs a risk-based, prioritized logging approach. CISA is to publish a Logging Reference Architecture within 90 days of the memo. Agencies then submit a logging plan within 90 days of its release and reach Basic, Intermediate and Advanced maturity within 120, 180 and 320 days.3
- OMB memorandum M-26-15 (June 24, 2026) carries out the June 22, 2026 executive order on post-quantum cryptography. Agencies aim to mitigate as much quantum risk as feasible by December 31, 2030. Its phases run from discovery in 2026 to 2027, pilots in 2027 to 2028 and prioritized migration in 2028 to 2030, to signature migration in 2031. It does not apply to national security systems.4
- Executive Order 14409 (June 2, 2026) directed DHS, through CISA, to release within 30 days binding operational directives and other guidance to expedite and prioritize the cyber defense of civilian federal information systems. They are also to expand AI-enabled defensive programs and help agencies, state and local authorities and critical infrastructure operators get cybersecurity tools and services, including covered frontier models where appropriate.5
- DHS announced an additional $91.7 million for the fiscal year 2025 State and Local Cybersecurity Grant Program on August 1, 2025. States must distribute at least 80 percent of funds to local governments, with at least 25 percent going to rural areas. All applicants had to resubmit approved Cybersecurity Plans by January 30, 2026.6
License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.
Sources
- Cybersecurity and Infrastructure Security Agency. BOD 26-04: Prioritizing Security Updates Based on Risk. Checked .
- Cybersecurity and Infrastructure Security Agency. BOD 26-02: Mitigating Risk From End-of-Support Edge Devices. Checked .
- Office of Management and Budget. M-26-14, Ensuring Effective and Efficient Agency Logging and Network Visibility to Defend Against Evolving Cyber Threats. Checked .
- Office of Management and Budget. M-26-15, Execution of the Migration to Post-Quantum Cryptography. Checked .
- Executive Office of the President. Executive Order 14409, Promoting Advanced Artificial Intelligence Innovation and Security, 91 FR 34565. Checked .
- Cybersecurity and Infrastructure Security Agency. State and Local Cybersecurity Grant Program. Checked .
How we source and check every fact: Editorial standards · Corrections
Last reviewed .
Spotted an error? Tell us and we will check it and correct the page where needed.
Looking Back
Week of October 12, 2026
Ivanti’s October zero-day was a directory incident that came in through the VPN
CISA gave agencies three days to patch and triage Ivanti Connect Secure. The attacker left no implant on the gateway and used its directory account to hunt for administrator passwords and BitLocker keys. Permissions set long before decided how far that reached.
Week of June 8, 2026
Why World Cup cyber risk sat in the city services residents use every day
The stadiums had federal, state and venue security teams. The cyber risk host cities owned sat somewhere less obvious: in the everyday services around the matches, from parking sites and traffic signals to 911 dispatch and the vendors neighboring cities share.
Week of April 27, 2026
Lower quantum estimates moved signatures up the post-quantum queue
New research in spring 2026 lowered estimates of what a quantum computer would need to break today’s digital locks. For agencies, the urgent part was proof of identity rather than secrecy: certificates, smart cards and device keys take longest to replace.
Week of September 22, 2025
Persistence below the patch: what ED 25-03 asked agencies to prove about their firewalls
CISA’s Emergency Directive 25-03 described attackers who hid inside the startup code of Cisco firewalls, surviving restarts and upgrades. Applying a fix was no longer enough. Agencies had to prove each device could be trusted, and that the fix was the right one.
Week of June 23, 2025
One alert, three threats: how local agencies should have read the June 2025 Iran warning
After U.S. strikes on Iran, federal warnings described one heightened threat. For cities, counties and utilities it was really three: hacktivist noise, opportunistic attacks on exposed control systems, and patient state operations. Each needs a different owner, a different clock and a different fix.
Week of February 3, 2025
In the Treasury payment access dispute, “read-only” was a claim until the records proved it
Set the politics aside and the fight over access to Treasury’s payment systems becomes a rare public lesson in who can touch the money. It came down to four separate controls, and to whether each could be proved rather than simply asserted.
Week of December 30, 2024
Treasury’s breach ran through a remote-support key the agency never held
Attackers walked into Treasury workstations using a stolen key from a vendor’s cloud remote-support service, a key the agency never held. Remote support is powerful insider access by another name, and governing it takes four controls.
Week of March 18, 2024
The governors’ water letter handed one problem to three state secretaries
In March 2024, the White House and EPA wrote to every governor about attacks on water systems, inviting each state’s environmental, health and homeland security secretaries. That guest list was the story: one problem, three offices, and rarely anyone in charge of all three.
Week of January 8, 2024
Why the SEC’s hijacked account was most valuable the day before a decision
The fake bitcoin ETF post from the SEC’s X account landed one day before the real approval, when markets would believe it. Agencies whose words move markets or behavior should guard official accounts as privileged credentials, by the calendar and for the audience.
Week of December 18, 2023
When the FBI offers a decryptor: what ALPHV’s takedown asked of public agencies
In December 2023 the FBI disrupted the ALPHV ransomware gang and handed hundreds of victims a free decryption tool. Taking that help well meant three things few agencies plan for: checking the offer is real, using the tool safely and keeping legal deadlines.
All 30 Looking Back articles in Government and Security & Resilience
Explainers, checklists and data
Explainer · November 14, 2026
FedRAMP notice NTC-0017: the December 7 vulnerability-rules deadline and the March 8, 2027 revocation
FedRAMP’s November 10, 2026 notice tells certified cloud services how it will collect progress on the move to its new vulnerability rules due December 7, 2026, and that services neither migrated nor under an approved corrective action plan on March 8, 2027 lose certification.
Explainer · November 14, 2026
DFARS 252.204-7012 safeguarding and 72-hour cyber incident reporting, explained
The DoD clause that protects covered defense information on contractor systems and requires cyber incidents to be reported within 72 hours of discovery. Class Deviation 2026-O0025, Revision 3, signed September 3, 2026 (digital signature), carries a revised text that names NIST SP 800-171 Revision 2.
Explainer · November 14, 2026
CISA BOD 26-04: risk-based vulnerability deadlines for federal agencies, explained
CISA’s directive of June 10, 2026 revokes BOD 22-01 and BOD 19-02. Federal civilian agencies now set each remediation deadline from four facts about the asset and the flaw, from three days with a forensic triage to the next system upgrade.
Checklist · November 14, 2026
Checklist: meeting OMB M-26-14 logging deadlines after CISA’s reference architecture
Thirteen steps for a federal agency’s CIO, CISO and security operations center, from the Agency Logging Plan due 90 days after CISA released the Logging Reference Architecture on August 20, 2026 to Advanced maturity at 320 days.
Checklist · November 14, 2026
Checklist: meeting CISA BOD 26-04 remediation and reporting duties
Thirteen steps for a federal civilian agency’s CIO, CISO and vulnerability team, from the policy update CISA required at once to the asset tagging and remediation timelines due within 180 days of June 10, 2026, each tied to the directive or CISA’s guidance.
Checklist · November 14, 2026
Checklist: weekly asset discovery and 14-day vulnerability enumeration under CISA BOD 23-01
Twelve steps for federal civilian agencies: what the directive’s scope takes in, the 7-day, 14-day, 24-hour and 72-hour requirements, CISA’s on-demand requests, performance data, and how BOD 26-04 now starts remediation clocks from BOD 23-01 results.