CRADA and community of interest lead from NIST NCCoE; eligibility, timing, and fit require current official verification.
No application or relationship exists. This record does not establish eligibility, availability, funding, recommendation, provider interest, or authorization to apply.
Provider
NIST NCCoE
Kind
CRADA and community of interest
Status
active; project-specific
Timing
Recurring and project-specific. Formal collaborator calls are announced through Federal Register notices; informal communities of interest, events, and public-comment periods operate as available.
Eligibility
Formal collaborators must offer products, technologies, or engineering expertise that meet a project's published technical requirements, submit a letter of interest, and sign a CRADA if selected. NIST evaluates technically acceptable letters on a first-come, first-served basis.
Access notes
The NCEP partnership program has a separate interest process and memorandum of understanding; supporting individual projects first is encouraged. Informal participation is distinct from formal collaborator or partner status.
Official link checked
2026-07-25
Relationship
indexed only; no formal relationship
Potential fit and evidence boundary
Zero trust, OT, supply chain, PQC, and AI assurance
Evidence boundary: The official NCCoE page returned a command-line access denial but rendered successfully in the web renderer. That official page establishes formal and informal routes, CRADA and letter-of-interest mechanics, and selection boundaries; no matching current call, technical acceptability, or relationship is implied.
Project-specific public collaboration may fit a civil recovery use case; acceptance and independence are not implied.
Required artifact: A public defensive use case with no sensitive operational data.
Action status: proposed; not undertaken
Proposed founder action—not undertaken
Join no formal process until a reviewed cyber-assurance capability matches a live Federal Register notice; use public documents and comment periods for learning, and seek authorization before any letter, form, or claimed affiliation.
Conflicts and change triggers
Conflicts: Vendor neutrality, product claims, disclosure, IP, test-result interpretation, sponsorship optics, and government-collaboration language require careful governance.
What would change this record? A live Federal Register notice matching a GShips-derived cyber capability, an accepted letter of interest, or revised NCEP criteria would change this assessment.
The official NCCoE page returned a command-line access denial but rendered successfully in the web renderer. That official page establishes formal and informal routes, CRADA and letter-of-interest mechanics, and selection boundaries; no matching current call, technical acceptability, or relationship is implied.
Indexing and task matching do not establish eligibility, recommendation, availability, funding, provider interest, a relationship, or authorization to apply.
What would change this page?
A live Federal Register notice matching a GShips-derived cyber capability, an accepted letter of interest, or revised NCEP criteria would change this assessment.
Vendor neutrality, product claims, disclosure, IP, test-result interpretation, sponsorship optics, and government-collaboration language require careful governance.
The maintainer intends to explore a commercial venture based on some GShips work. No entity, outside funding, customer, sponsor, or indexed-organization relationship currently exists.