What the FY2027 request buys
Verbatim from the R-2A exhibit for project MC30 of PE 0603890C. This is the budget justification's own description of work that has not happened yet — the one thing no other level of the budget carries.
- Initiates end-to-end support for DCO requirements for new systems, long-haul communications transition, cryptographic, end user support, and legacy cybersecurity tool modernization, and increased SAP network and storage requirements to support Missile Defense System - Next requirements.
Increase from FY 2026 to FY 2027 provides for multiple new requirements supporting the Missile Defense Agency capabilities, including end-to end support for DCO requirements to support new systems, long-haul communications transition, cryptographic, end user support, and legacy cybersecurity tool modernization, and increased SAP network and storage requirements. Increase also provides for realignment of cybersecurity requirements to new OMB Cybersecurity Taxonomy. MDA is required to develop and deliver a comprehensive cybersecurity strategy, methodology, and technical solution set to detect, analyze, and mitigate intrusions, ensure the resilience of its new information systems. This includes ensuring continuity of operations during crises, conducting thorough threat analysis through activities like red-teaming, and performing regular network readiness assessments to identify and reduce vulnerabilities. In the event of a cyber incident, a multi-stage response is required to be triggered, involving federal incident response centers. This required response includes detailed forensic analysis to assess the damage and attribute the attack methodology and responsible parties, followed by remediation and restoral of systems in a timely manner to continue the warfighter effort. This increase also supports the investigation and legal prosecution of those responsible for cyber intrusions related to MDA systems and data.
Three years, and no five-year plan
An R-2A activity publishes the prior year, the current year and the budget year. The FYDP outyears exist at project and program-element level and are deliberately absent here rather than inferred. Estimate types are colored and never summed into one figure.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 62.0 |
| FY2026 | Enacted | 44.1 |
| FY2027 | Request | 100.6 |
This activity is 37% of project MC30's FY2027 request and 6.9% of PE 0603890C's. In the request year the activities under a project sum to it exactly; in the current year they under-cover it in about 9% of cases, so an activity's delta can legitimately exceed its parent's and the two must not be compared row to row.
7 activities in project MC30
Every R-2A line of this project, largest FY2027 request first. Linked where the activity has enough of its own narrative to carry a page; the rest are shown in full on the project page.