R-2A Activity · President's Budget PB2027

Computer Network Defense (CND)

FY2027 Request
$15.1M
▼ 9.5% vs FY2026
HitchAI read

This activity requests $15.1M in FY2027, 52% of project 0734, down 9.5% on FY2026. The R-2A exhibit describes it across FY2026–FY2027, including what the FY2027 money is planned to buy.

FY2027 Request
$15.1M
▼ 9.5% vs FY2026
FY2026 Enacted
$16.7M
▲ 7.9% vs FY2025
FY2025 Actual
$15.5M
Prior year
Planned work

What the FY2027 request buys

Verbatim from the R-2A exhibit for project 0734 of PE 0303140N. 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.

FY2027 planned work

- Continue to manage obsolescence through technical refreshes and capability upgrades to CND subsystems. - Continue to develop and enhance Navy's portion of other mission requirements (details held at a higher classification) and BMD cyber security system of systems within the CND architecture. - Continue to implement DoW and USCC cybersecurity tools and mandates into ONE-Net and C4I networks, if still required. - Continue to provide technical guidance to support CANES deployment of new CND capabilities. - Continue to develop, integrate, and test solution to replace and assume acquisition management of NCDOC tactical sensor infrastructure. - Continue the enablement of high assurance infrastructure and cloud deployment in support of ZTA. - Continue to Refactor VRAM coding as needed and adapt VRAM to changing technologies utilized by the application, including adequate integration and testing prior to delivery/production. - Continue CND NCDOC COOP assessment of CND capabilities in an effort to comply with automated failover architecture, as required in support of NCDOC mission essential functions/operations at alternate failover site(s)

FY2026 to FY2027 change

FY2026 to FY2027 decrease of $1.593M is attributed to requirement adjustments for the development of modernized capabilities associated with network devices that include firewalls, routers, switches, intrusion detection and protection, hosting, logging and authentication services, etc. due to end-of-life/end-of service that ensures the latest cybersecurity tools are protecting the Navy's tactical networks.

Before the request year

FY2026: the year under way

Prior-year accomplishments and current-year plans from the same exhibit. Context for the FY2027 plan, not a series — an activity partitions its project exactly in the request year, but can under-cover it in earlier years.

FY2026 plans — current year

- Continue to manage obsolescence through technical refreshes and capability upgrades to CND subsystems. - Continue to develop and enhance Navy's portion of other mission requirements (details held at a higher classification) and BMD cyber security system of systems within the CND architecture. - Continue to implement DoW and USCC cybersecurity tools and mandates into ONE-Net and C4I networks. - Continue to provide technical guidance to support CANES deployment of new CND capabilities. - Continue efforts to further virtualize CND capabilities for more effective and cost-efficient deployment of cybersecurity technologies. - Continue to develop, integrate, and test solution to replace and assume acquisition management of NCDOC tactical sensor infrastructure. - Continue the enablement of high assurance infrastructure in support of ZTA. - Continue to Refactor Vulnerability Asset Remediation Manager (VRAM) coding as needed and adapt VRAM to changing technologies utilized by the application, including adequate integration and testing prior to delivery/production. - Continue CND NCDOC COOP assessment of CND capabilities in an effort to comply with automated failover architecture, as required in support of NCDOC mission essential functions/operations at alternate failover site(s)

Money

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.

015.5FY25ACTUAL16.7FY26ENACTED15.1FY27REQUEST
Actual Enacted Request
Fiscal YearEstimate TypeAmount ($M)
FY2025Actual15.5
FY2026Enacted16.7
FY2027Request15.1

This activity is 52% of project 0734's FY2027 request and 19% of PE 0303140N'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.

Where this sits

6 activities in project 0734

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.

Computer Network Defense (CND) — this activity$15.1M ▼ 10%
Navy Cryptography (Crypto)$8.6M ▲ 4%
SHARKCAGE$2.8M ▲ 22%
Navy Cyber Situational Awareness (NCSA)$1.9M ▼ 30%
Key Management (KM)$0.4M ▼ 58%
Public Key Infrastructure (PKI)$0.4M ▼ 15%
Source
FY2027 Department of the Navy RDT&E Budget Justification · Exhibit R-2A · PE 0303140N, project 0734 (President's Budget PB2027). Congressional marks are recorded on the program element, never on an activity.
Machine access
Markdown twin /programs/0303140N/0734/a0.md · MCP mcp.hitchintel.combudget_get_activity