FCI (Federal Contract Information) is US government information provided or generated under a contract that is not for public release. It is broader and less sensitive than CUI, and protecting it requires the basic safeguards of CMMC Level 1, verified by annual self-assessment. Contractors that also handle CUI face the higher requirements of CMMC Level 2.
FCI is the entry point of US defence contracting security: almost every contractor handles it, and doing so brings the first tier of CMMC obligations.
What is FCI and what does it require?
FCI, Federal Contract Information, is information provided by or generated for the US government under a contract to develop or deliver a product or service, and which is not intended for public release. It is a deliberately broad category, capturing the everyday non-public information that flows through a government contract, and it does not include information the government has released publicly or simple transactional information like payment details.
Protecting FCI requires the basic safeguarding requirements set out in US federal acquisition rules, which map to CMMC Level 1, a set of foundational cyber security practices covering access control, authentication, and basic system and boundary protection. At Level 1 these are verified through an annual self-assessment rather than an external audit, so FCI protection is the accessible, foundational tier of the CMMC framework that most contractors must meet.
FCI versus CUI
The key distinction is sensitivity and the resulting obligation. FCI is the broader, lower-sensitivity category, non-public information shared under a contract, while CUI is more sensitive information that carries specific protection or dissemination controls. In the CMMC model this maps directly onto the levels: protecting FCI requires the basic safeguards of Level 1, while protecting CUI requires the far more extensive controls of Level 2, generally verified by a third-party assessment. Most contractors handle FCI and therefore need Level 1; the subset that also handle CUI step up to Level 2. Working out which categories of information an organisation actually holds is the first step in scoping any CMMC effort. For an organisation working through US defence requirements alongside its Australian obligations, Cybernion can help through advisory.
Frequently asked questions
What is FCI?
FCI, or Federal Contract Information, is information provided by or generated for the United States government under a contract to develop or deliver a product or service, that is not intended for public release. It is a broad category covering the routine non-public information exchanged in the course of a government contract, and any contractor that handles it must protect it to a basic standard.
What is the difference between FCI and CUI?
FCI is the broader, lower-sensitivity category, non-public information shared under a contract, while CUI is more sensitive information that carries specific protection or dissemination controls. In the CMMC model, protecting FCI requires the basic safeguards of Level 1, whereas protecting CUI requires the more extensive controls of Level 2. So most contractors handle FCI, and a subset that handle CUI face higher requirements.
What protection does FCI require?
FCI must be protected with the basic safeguarding requirements set out in US federal acquisition rules, which correspond to CMMC Level 1, a set of foundational cyber security practices such as access control, authentication and basic system protection. These are assessed at Level 1 through an annual self-assessment rather than a third-party audit, making FCI protection the entry point of the CMMC framework.
Does a company handling FCI need CMMC?
Yes. A defence contractor that handles only FCI needs to meet CMMC Level 1, verified by annual self-assessment. A contractor that also handles the more sensitive CUI needs CMMC Level 2, which generally requires a third-party assessment. So handling FCI brings a company into the CMMC framework at its foundational level, and handling CUI raises the requirement.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- Cybersecurity Maturity Model Certification, US Department of Defense Chief Information Officer, 2026
- Controlled Unclassified Information (CUI) Registry, US National Archives, 2026
Last updated: 30 August, 2026
