Skip to main content
Background

CISA BOD 26-04: Akamai’s Strategic Blueprint for Federal Security

November 16, 2026 by Jason Turse

Share

Key takeaways

CISA’s Binding Operational Directive 26-04 (BOD 26-04) and the FedRAMP Consolidated Rules for 2026 (FedRAMP CR26) reinforce the need for continuous security, stronger validation, and ongoing readiness across federal environments.

CISA BOD 26-04 was explicitly designed because AI allows adversaries to weaponize vulnerabilities in hours rather than months, which drove the new mandate for rapid remediation of critical risks.

FedRAMP CR26 directly supports this by pulling its new vulnerability detection deadlines forward to December 2026 to align with BOD 26-04. Together, they require cloud providers to shift to a continuous, risk-based monitoring to defend against AI-accelerated attacks.

We are addressing new FedRAMP requirements by evolving its security architecture and Zero Trust approach to support changing federal requirements.

Federal customers and software as a service (SaaS) partners can expect transition support, FedRAMP alignment updates, and ongoing compliance guidance as requirements evolve.

Akamai’s mission to power and protect life online guides our work in supporting the mission-critical needs of the U.S. federal government and the partner ecosystem that serves it. As cyberthreats evolve, so must the frameworks and solutions that protect federal systems.

In June 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) issued Binding Operational Directive (BOD) 26-04, outlining new security requirements and operational expectations for federal networks. For cloud service providers, FedRAMP CR26 codifies the updated rules, aligning cloud compliance directly with CISA's accelerated remediation timelines and mandating continuous, machine-readable validation to ensure these rigorous defenses extend seamlessly to the commercial platforms that host government data.  

Also in June 2026, FedRAMP released the FedRAMP Consolidated Rules for 2026 (CR26), a consolidated set of rules for obtaining and maintaining FedRAMP certifications with mandatory adoption by January 1, 2027. CR26 is designed to provide a more consistent and predictable framework through the end of 2028. It also includes requirements for both the established Rev 5 path and the FedRAMP 20x model.

We are actively participating in industry working groups, as well as implementing system-level changes to meet both the new requirements and address emerging threats. We support CISA and FedRAMP objectives to strengthen federal cybersecurity posture and enable security in the face of AI-enabled threats — and we’re proactively updating our systems and security practices to meet and exceed these standards.

How are we strengthening our security architecture?

We have long supported federal cybersecurity by combining operational visibility with strong security and compliance capabilities. We view milestones like FedRAMP Moderate authorization and FedRAMP High Ready status as part of our ongoing security work.  

Our view of global traffic gives us real-time insight into emerging attack patterns and adversary tactics. That visibility, when combined with audit-ready telemetry, helps civilian, defense, and intelligence agencies support emerging NIST standards along with FedRAMP, CMMC, and Zero Trust requirements while improving automated detection, contextual threat intelligence, and rapid response. 

We employ our understanding of changing threats to proactively refine the defensive baselines and automated controls required under NIST SP 800-53 Rev 5. This intelligence-driven approach ensures that organizations not only satisfy the rigorous boundary protection and continuous monitoring demands of FedRAMP Moderate but also maintain resilient authorization postures against evolving adversary tactics.  

In turn, these updates reinforce our core roadmap by continuously strengthening our security architecture; automating validation where appropriate; and bridging the gap between legacy environments and modern, cloud native requirements. 

What does CR26 mean for FedRAMP continuous readiness?

FedRAMP is designed as a continuous security model rather than as a one-time certification exercise. CR26 reinforces this approach by establishing explicit rules for maintaining FedRAMP certification and managing changes over time. 

FedRAMP has also moved many FedRAMP-specific requirements out of individual Rev 5 control baselines and into the consolidated rules themselves, creating a clearer distinction between the underlying security controls and the program requirements for maintaining certification.

To align our infrastructure with the requirements applicable to BOD 26-04 and the evolving FedRAMP framework, we are working closely with our FedRAMP agency sponsors and the FedRAMP Program Management Office through the applicable change management and corrective action processes.

Operationalizing FedRAMP Moderate with Akamai Enterprise Application Access and microsegmentation

To support the transition to adaptive security models that are built on “Never trust, always verify” and Least Permissive Trust principles, we provide a suite of mission-critical Zero Trust and AI security solutions. Our FedRAMP Moderate-authorized Akamai Enterprise Application Access enforces granular Zero Trust Network Access  to applications and data to limit lateral movement, while Akamai Guardicore Segmentation uses microsegmentation to help protect internal data center communications against ransomware.

These solutions address critical NIST SP 800-53 controls applicable to FedRAMP Moderate, including those for Access Control, System and Communication Protection, Identification and Authentication, and Continuous Monitoring requirements. 

Additionally, as federal agencies increasingly adopt AI — and face new threats enabled by it — we are investing in our FedRAMP compliant services to help secure critical AI workloads and APIs at the edge, using machine learning and advanced threat hunting to counter sophisticated, AI-driven cyberattacks. And as more agency interactions become machine-to-machine, securing the APIs and workloads behind those systems becomes increasingly important to maintaining a continuously validated Zero Trust posture.

We combine our globally distributed infrastructure with deep, compliance-grade internal microsegmentation. This supports an end-to-end Zero Trust architecture that helps to secure the mission from remote users at the edge through to individual workloads in the data center.

What can customers and ecosystem partners expect?

We recognize that many leading agencies, technology partners, SaaS providers, and enterprise customers rely on our FedRAMP certification boundary and shared-responsibility model to support their own federal compliance obligations. Changes associated with BOD 26-04, CR26, and the transition toward the evolving FedRAMP certification model may require corresponding assessments or updates within downstream environments. 

Our objective is to make the transition predictable and transparent, with the highest priority to enable public sector missions to attain critical security and compliance outcomes. 

As BOD 26-04 and CR26 requirements evolve, we’ll continue to work with customers and partners through the transition in four key areas:

  1. Service continuity

  2. Transition support

  3. FedRAMP alignment

  4. Continuous updates

Service continuity

We are designing and implementing the required security and architectural changes to minimize operational impact to our core delivery, security, and compute services.

Transition support 

Our federal compliance task force, account teams, and compliance engineers are working with downstream SaaS providers to identify potential impacts, support Customer Responsibility Matrix (CRM) updates, and provide technical guidance.

FedRAMP alignment

We’re evaluating the implications of CR26 and the evolving FedRAMP certification model on our certification posture, architecture, documentation, and shared responsibility commitments. We will communicate the material changes that affect customers and partners as the applicable requirements and transition timelines take effect.

Continuous updates

We will provide milestone updates to FedRAMP customers through our secure compliance portal, including relevant documentation and guidance as our implementation progresses.

What comes next for federal cloud security?

The transition to CR26 significantly modernizes the federal cloud security ecosystem. FedRAMP has designed CR26 to provide a common ruleset for both Rev 5 and FedRAMP 20x while moving the program toward greater automation, clearer requirements, and more continuous validation.

At Akamai, we have spent more than two decades building a more secure internet. We view the implementation of CISA BOD 26-04 and the evolution of FedRAMP under CR26 as opportunities to meet evolving compliance obligations while further strengthening the security baseline for everyone who builds on our platform.

If you are a SaaS provider or federal tenant with questions about your specific environment, please contact your Akamai account team or visit the Akamai Compliance Trust Center for the latest documentation and guidance.

About the author

Jason Turse

Jason Turse

Jason Turse is a seasoned technology executive and former U.S. Navy officer with more than 20 years of experience in defense, intelligence, and cybersecurity. Jason is currently serving as the Senior Director for Product Management for Public Sector, and he has led transformative initiatives for the U.S. Federal Government.