Skip to content

NSF CICI Eligibility: Cyberinfrastructure Security

Updated 6 official sources

Quick Answer: NSF CICI eligibility in 2026 turns on 7 checks: scientific cyberinfrastructure benefit, correct program area, security research or transition value, user workflow fit, budget cap, January 20 deadline, and route risk.

Full answer and how we checked it

NSF CICI eligibility in 2026 turns on 7 checks: scientific cyberinfrastructure benefit, correct program area, security research or transition value, user workflow fit, budget cap, January 20 deadline, and route risk.

Who this is for: Scientific cyberinfrastructure teams, research computing centers, cybersecurity researchers, data-intensive science groups, AI-ready data teams, and sponsored-research offices deciding whether CICI is the right NSF route.

Data note: This guide uses the official NSF CICI page (opens in a new tab), NSF 25-531 solicitation (opens in a new tab), NSF PAPPG (opens in a new tab), Research.gov proposal systems (opens in a new tab), Grants.gov listing 358004 (opens in a new tab), and Grantsights award-data signals checked on June 2, 2026.

In this guide

According to NSF Cybersecurity Innovation for Cyberinfrastructure (opens in a new tab), CICI aims to advance scientific discovery by improving the security and privacy of cyberinfrastructure. NSF lists NSF 25-531 and says the program supports development, deployment, and integration of cybersecurity that benefits the broader scientific community.

This is not a general enterprise cybersecurity grant. The key question is whether the security work directly improves scientific data, computation, workflows, collaboration, infrastructure, or AI-ready research data.

Use this guide with the live NSF CICI program record. Then compare NSF Mid-scale RI-1 guide, NSF CEDAR guide, NSF grants complete guide, what is a NOFO, and the Grantsights grant database.

Source Check

Checked June 2026.

Rechecked October 10, 2026: the NSF CICI page (opens in a new tab), updated October 5, 2026, still lists NSF 25-531 and a January 20, 2027 deadline, so the June figures below still hold.

8 official-source checks should happen before a team treats NSF 25-531 as the right CICI route. NSF marks the solicitation as current, lists January 21, 2026 and the third Wednesday in January annually thereafter, and sets the next planning deadline as January 20, 2027. NSF estimates 12 to 20 awards and $8,000,000 to $12,000,000 in total program funding, subject to funds being available.

The program-area budget limits are route-defining. UCSS and RSSD awards can request up to $600,000 total for up to 3 years. TCR awards can request up to $1,200,000 total for up to 3 years. IPAAI awards can request up to $900,000 total for up to 3 years. NSF also limits any individual to no more than 2 CICI proposals as PI, co-PI, or senior/key personnel.

Source checkWhat to verify before writing
Science CIScientific cyberinfrastructure, users, applications, or datasets are central
Program areaUCSS, RSSD, TCR, or IPAAI is chosen without hedging
BudgetProgram-area cap and 3-year limit are respected
UsersScientific users, domain partners, workflows, and adoption path are named
MetricsSecurity benefit metrics and threat model are explicit
SharingSoftware or datasets have open-source, public sharing, or community-platform logic where applicable
PersonnelNo person exceeds the 2-proposal CICI limit
Better routeSaTC, CyberTraining, Mid-scale RI-1, disciplinary NSF, or institutional IT is compared

The quickest route test is whether the project becomes generic cybersecurity after removing the scientific workflow. If it does, CICI is probably the wrong first read.

Get research funding calls by email

About once a week, we email open research funding calls with a real deadline, from federal agencies such as NIH and NSF, picked for research institutions. One click to unsubscribe.

No spam. Unsubscribe anytime.

7 NSF CICI Eligibility Stop Checks

Within 21 days, run this 7-point decision table before drafting.

Stop checkStrong CICI signalRed flag
Science CIScientific cyberinfrastructure benefit is centralEnterprise IT dominates
Program areaUCSS, RSSD, TCR, or IPAAI fitsArea is unclear
UsersScientific users and workflows are definedGeneric security users
TransitionDeployment or adoption path is crediblePrototype has no users
DataScientific data, workflows, AI data, or CI are explicitData context is vague
BudgetArea-specific cap is respectedBudget exceeds route
TimingJanuary 20 deadline is feasiblePartners or testbed are late

CICI concepts fail when they read like campus security upgrades. CICI needs a science cyberinfrastructure contribution.

5 Source Facts Applicants Should Know

According to NSF, CICI seeks proposals in four program areas: Usable and Collaborative Security for Science, Reference Scientific Security Datasets, Transition to Cyberinfrastructure Resilience, and Integrity, Provenance, and Authenticity for Artificial Intelligence Ready Data.

According to NSF, the next deadline is January 20, 2027 and the annual pattern is the third Wednesday in January. NSF lists total program funding of $8 million to $12 million, subject to availability of funds.

According to USAspending.gov (opens in a new tab) data, assistance listing 47.070 had about $1.02B in FY2024 obligations across 4,969 awards active that year.

According to NSF 25-531, the CICI program targets applied security research directly relevant to scientific cyberinfrastructure. According to NSF, CICI complements other OAC programs such as Campus Cyberinfrastructure and Cyberinfrastructure for Sustained Scientific Innovation.

FactSource-backed read
SolicitationNSF 25-531
ProgramCybersecurity Innovation for Cyberinfrastructure
Next deadlineJanuary 20, 2027
Program areasUCSS, RSSD, TCR, IPAAI
Live listingGrants.gov listing 358004

What NSF Doesn't Tell You

Within 21 days, answer 4 practical questions. First, CICI is about scientific cyberinfrastructure, not generic cybersecurity procurement. A campus firewall upgrade does not become CICI because researchers use the network.

Second, program area choice shapes the entire proposal. For example, a research computing center hardening scientific workflows with a transition partner could fit TCR, while an AI data team working on provenance for research datasets could fit IPAAI.

Third, usability matters. If scientists will not adopt the security practice, the project has a CICI weakness even if the technical idea is strong.

Fourth, check program-area fit, science CI benefit, user workflow, testbed readiness, budget cap, and route alternatives before drafting.

Grantsights analysis of award data and route evidence says applicants should apply only when the scientific users, workflow, data or compute asset, security gap, adoption path, and selected program area are all visible. If the project still reads the same after removing the scientific workflow, CICI is a bad fit.

6 Evidence Assets That Make This Proposal Stronger

Within 21 days, build 6 evidence assets. Asset 1 is the science-CI benefit memo. Identify the research community, infrastructure, data, computation, workflow, collaboration pattern, and security gap.

Asset 2 is the program-area memo. Compare UCSS, RSSD, TCR, and IPAAI, then explain why the selected area fits.

Asset 3 is the user-workflow map. Show the scientific workflow before and after the proposed security improvement.

Asset 4 is the deployment or dataset plan. For TCR, show transition and adoption. For RSSD, show dataset capture and reproducibility. For IPAAI, show data integrity and provenance. For UCSS, show user adoption and collaboration.

Asset 5 is the budget-cap proof. Tie each cost to the selected program area and expected duration.

Asset 6 is the route memo. Compare CICI with SaTC, CyberTraining, OAC cyberinfrastructure routes, Mid-scale RI-1, CEDAR, disciplinary programs, and institutional IT funding.

5 Route Choices Before Drafting

Within 21 days, compare 5 routes.

RouteBetter first read when...Why
CICI UCSSUsable security for science collaboration dominatesUCSS fits
CICI RSSDReference security datasets for science workflows dominateRSSD fits
CICI TCRTransition to CI resilience dominatesTCR fits
CICI IPAAIAI-ready scientific data integrity dominatesIPAAI fits
SaTC or institutional ITGeneral cybersecurity dominatesAnother route may fit

Warning: if the phrase "scientific cyberinfrastructure" can be removed and the project still sounds the same, don't start with CICI. The strongest CICI proposals make the scientific workflow impossible to miss.

6 Bad-Fit Signals

First, the work is general campus cybersecurity. Second, the scientific users are undefined. Third, the program area is unclear.

Fourth, adoption is assumed. Fifth, the budget cap is ignored. Sixth, the project is mainly AI governance without scientific dataset integrity, provenance, or authenticity.

These signals are route risks, not just writing issues. A hypothetical research computing center protecting shared scientific workflows with real adoption partners has a different CICI story from a university asking for routine enterprise security work.

21-Day CICI Readiness Plan

Days 1 through 3 should confirm science-CI benefit, program area, deadline, and budget cap. Days 4 through 7 should write the science-CI benefit memo and program-area memo.

Days 8 through 12 should build the user-workflow map, deployment or dataset plan, and partner roles. Days 13 through 16 should confirm testbeds, adoption, data, reproducibility, privacy, and broader impacts. Days 17 through 21 should compare CICI with SaTC, CyberTraining, Mid-scale RI-1, and institutional routes.

5 Signals to Check First

Within 21 days, use these 5 signals before drafting. Signal 1 is scientific cyberinfrastructure benefit. Signal 2 is UCSS, RSSD, TCR, or IPAAI fit. Signal 3 is user-workflow proof. Signal 4 is adoption or dataset readiness. Signal 5 is route comparison against SaTC, CyberTraining, Mid-scale RI-1, disciplinary routes, and institutional IT.

Check each signal against the solicitation itself: program-area scope, workflow and deployment detail, dataset plans, and the budget cap.

For example, one research computing center protecting a scientific workflow with adoption partners may fit TCR. A campus security upgrade without science users should compare institutional IT funding before CICI.

6 Final Research Checks Before Submission

Within 21 days, finish 6 final checks. Check 1 is the NSF CICI page (opens in a new tab). Check 2 is NSF PAPPG (opens in a new tab) compliance. Check 3 is NSF 25-531 fit. Check 4 is program-area choice. Check 5 is budget-cap fit. Check 6 is January 20 deadline readiness.

You're ready when the team can state the scientific cyberinfrastructure, security gap, program area, users, adoption path, and budget cap in 6 direct sentences.

4 Decision Questions Before You Draft

Within 21 days, ask 4 decision questions. Question 1: "Which scientific cyberinfrastructure is being secured?" Question 2: "Which CICI program area fits?" Question 3: "Who will adopt the security output?" Question 4: "Does the budget fit the selected area?"

If question 1 fails, redirect before the team writes a CICI proposal.

3 Last-Mile Checks For CICI Teams

Within 21 days, run 3 last-mile checks. Check 1 is science-CI proof. Check 2 is program-area proof. Check 3 is adoption proof.

If those checks are weak, the proposal may read like enterprise IT. A final note for applicants: write the CICI fit sentence before the overview. In 2 sentences, state the scientific cyberinfrastructure, security gap, program area, users, and reason CICI is the best NSF home.

5 Extra Fit Tests For Science-CI Teams

Within 21 days, add 5 extra fit tests before a CICI team starts drafting. Test 1: name the scientific workflow in one sentence. If the answer is "network security," the route is probably too broad.

Test 2: name the user group that will adopt the work. A security artifact without scientific users is weak for this program.

Test 3: name the program area without hedging. If the team cannot choose UCSS, RSSD, TCR, or IPAAI, it needs route work before narrative writing.

Test 4: name the testbed or dataset. CICI reviewers need a place where the idea touches scientific infrastructure, not only a conceptual model.

Test 5: compare NSF IGE guide when the project is mainly training and NSF Mid-scale RI-1 guide when the project is mainly infrastructure. CICI is strongest when security, scientific workflow, and adoption are all central.

Sources

Next steps

Where to go next

These next pages help you move from research into a specific grant choice.

Frequently Asked Questions

What does NSF CICI support?

It supports cybersecurity work that improves security, resilience, privacy, usability, and reproducibility for scientific cyberinfrastructure.

What solicitation applies?

NSF lists NSF 25-531 for Cybersecurity Innovation for Cyberinfrastructure.

What are the program areas?

NSF lists UCSS, RSSD, TCR, and IPAAI program areas.

What is the next deadline?

NSF lists January 20, 2027, with the third Wednesday in January annually thereafter.

Who should skip this route?

Skip it when the work is general cybersecurity, enterprise IT, or AI data governance without a clear scientific cyberinfrastructure benefit.

Last updated October 10, 2026. Corrected October 10, 2026: what changed. Published by Grantsights from public sources. See our editorial policy, how we build and check guides, corrections and how we make money.