Regulators

Department of Defense Chief Information Officer (DoD CIO)

Federal agency

Each number links to the point's source. Points checked unless the point shows another date.

Remit

  • The Chief Information Officer of the Department of Defense is appointed by the President, by and with the advice and consent of the Senate, from among civilians qualified to serve, and reports directly to the Secretary of Defense (10 U.S.C. 142(a) and (d)).1
  • The statute gives the CIO responsibility for policy, oversight and guidance for the information technology, networking, information assurance, cybersecurity and cyber capability architectures of the Department, and authority, direction and control over the Defense Information Systems Agency and over the activities of the NSA Cybersecurity Directorate funded through the Information Systems Security Program (10 U.S.C. 142(b)(1)).1
  • The CIO reviews the proposed budgets of the military departments and Defense Agencies for these activities and, by January 31 of the year before the fiscal year concerned, reports to the Secretary of Defense with a certification of whether each is adequate (10 U.S.C. 142(b)(2)).1
  • The office describes itself as the Principal Staff Assistant and senior information technology advisor to the Secretary of Defense, responsible for the Department's information enterprise, including communications, spectrum management, network policy and standards, information systems, cybersecurity, and positioning, navigation and timing policy.2
  • Its CMMC pages, captured in November 2026, refer to the Department as the Department of War (DoW).4

Who it supervises

  • The military departments and Defense Agencies: none of them may develop or procure information technology that does not fully comply with the standards the CIO establishes, and the CIO runs a process to certify that capabilities being developed or procured meet published standards (10 U.S.C. 142(b)(3)).1
  • Defense contractors and subcontractors that will process, store or transmit Federal Contract Information or Controlled Unclassified Information on contractor information systems in performing a DoD contract (32 CFR 170.3(a)); the CMMC rules do not apply to federal information systems that contractors operate on behalf of the Government (32 CFR 170.3(b)).3
  • The CMMC assessment and certification ecosystem: the CMMC Program Management Office monitors the CMMC Accreditation Body's performance and keeps, on behalf of the Deputy CIO for Cybersecurity, the right to review the Accreditation Body's decisions (32 CFR 170.6(b) and (c)).3

How it examines

  • The Office of the Deputy CIO for Cybersecurity oversees the CMMC Program and sets CMMC assessment, accreditation and training requirements and program policy (32 CFR 170.6(a)).3
  • CMMC Level 1 calls for an annual self-assessment and annual affirmation of compliance with the 15 security requirements in FAR clause 52.204-21; a CMMC Status is valid for three years from the CMMC Status Date.4 Compare: CMMC levels compared: requirements, assessments and affirmations under 32 CFR part 170
  • DCMA's Defense Industrial Base Cybersecurity Assessment Center (DIBCAC) conducts Level 3 certification assessments and issues the certificates; Level 2 certification assessments come from authorized or accredited third-party assessment organizations (32 CFR 170.7 and 170.17).3 Compare: CMMC levels compared: requirements, assessments and affirmations under 32 CFR part 170
  • When a contractor's CMMC Status is called into question, the CMMC Program Management Office investigates and may have DIBCAC assess the contractor; DIBCAC results take precedence, DoD updates the Supplier Performance Risk System (SPRS) to show noncompliance, and standard contractual remedies apply on an active contract (32 CFR 170.6(e) and (f)).3
  • Separately from CMMC, an offeror required to implement NIST SP 800-171 must have a current NIST SP 800-171 DoD Assessment, not more than three years old unless the solicitation sets a shorter time, with summary scores posted in SPRS to be considered for award (DFARS 252.204-7019).9

Technology and security guidance

  • Its library, captured November 4, 2026, lists, under Defend Against Cyber Attacks, DoWI 8500.01, Cybersecurity, and DoWI 8510.01, Risk Management Framework (RMF) for DoW Systems, with memos on continuous authorization to operate (cATO) and reciprocity.11
  • The same library lists a memo on FedRAMP equivalency for cloud service providers and a document on DoW cybersecurity activities performed for cloud service offerings.11 Compare: Government cloud authorization programs compared: FedRAMP, GovRAMP, TX-RAMP and the DoD cloud SRG
  • Zero trust material in the library includes Zero Trust Capabilities and Activities, a Zero Trust Capability Execution Roadmap and Zero Trust for Operational Technology Activities and Outcomes.11 Compare: Federal zero trust models compared: OMB M-22-09, CISA ZTMM 2.0 and the DoD strategy
  • For the cyber workforce it lists DoWD 8140.01, Cyberspace Workforce Management, DoWI 8140.02 on identifying, tracking and reporting cyberspace workforce requirements, and DoWM 8140.03, the Cyberspace Workforce Qualification and Management Program.11

Recent rules

  • CMMC Program final rule (32 CFR part 170), published October 15, 2024 and effective December 16, 2024, establishing the program to verify that contractors have implemented the security requirements for Federal Contract Information and Controlled Unclassified Information.5 Compare: CMMC levels compared: requirements, assessments and affirmations under 32 CFR part 170
  • DFARS final rule 2019-D041, published September 10, 2025 and effective November 10, 2025, adds the contractual requirements for the CMMC Program to the Defense Federal Acquisition Regulation Supplement.6 Compare: CMMC levels compared: requirements, assessments and affirmations under 32 CFR part 170
  • Its clause DFARS 252.204-7021 (Nov 2025) requires a contractor to have and maintain, for the duration of the contract, a current CMMC status at the level the contracting officer inserts for all information systems used in performance that process, store or transmit FCI or CUI, and to complete an affirmation of continuous compliance in SPRS on an annual basis; it must flow the correct CMMC level down to subcontracts and ensure subcontractors and suppliers complete such an affirmation before subcontract award and annually after.7 Compare: CMMC levels compared: requirements, assessments and affirmations under 32 CFR part 170
  • DFARS Class Deviation 2026-O0025, Revision 3, tells contracting officers to work with requiring activities to remove or revise CMMC requirements in new and existing solicitations and contracts under the CIO's memorandum of July 13, 2026, Suspension of the Advancement to Cybersecurity Maturity Model Certification Phase 2 Requirements. The memorandum suspends the November 2026 Phase 2 transition, permits CMMC Level 1 (Self) or Level 2 (Self) assessments in procurement requests, and requires baseline compliance with NIST SP 800-171 Rev 2 under DFARS 252.204-7012; existing contracts drop the requirements by modification before the next option period or at the next scheduled administrative modification. Status as checked on 2026-11-14.12 Compare: CMMC levels compared: requirements, assessments and affirmations under 32 CFR part 170
  • Its CMMC page (archived copy captured November 13, 2026) says the first phase of CMMC implementation began on November 10, 2025, that the Phase II requirements had been scheduled for November 10, 2026, and that on July 13, 2026 the Department also set up a CMMC reform task force; the program is paused in Phase 1, may only require self-assessments at two levels, and during this period the Department enforces NIST SP 800-171 Rev 2 through self-assessments and select government-led assessments.4 Compare: CMMC levels compared: requirements, assessments and affirmations under 32 CFR part 170
  • DFARS 252.204-7012 (May 2024) requires contractors to report cyber incidents to DoD at dibnet.dod.mil within 72 hours of discovery, to submit requests to vary from NIST SP 800-171 for consideration by the DoD CIO, and to ensure that any external cloud service provider used for covered defense information meets security requirements equivalent to the FedRAMP Moderate baseline.8 Compare: Incident and breach reporting deadlines compared
  • DFARS 252.239-7010 (Jan 2023) requires contractors providing cloud computing services to apply the safeguards of the DoD Cloud Computing Security Requirements Guide unless the DoD CIO has waived it, and to keep Government data within the United States or outlying areas unless the contracting officer allows another location.10 Compare: Government cloud authorization programs compared: FedRAMP, GovRAMP, TX-RAMP and the DoD cloud SRG

Official channels

Links to the regulator's own pages, checked .

Get the data: JSON

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.

Sources

  1. U.S. Government Publishing Office (govinfo), United States Code 2024 edition. 10 U.S.C. 142, Chief Information Officer. Checked .
  2. Department of Defense Chief Information Officer. About DoD CIO (archived copy, Internet Archive, captured August 9, 2025). Checked .
  3. Office of the Federal Register (eCFR). 32 CFR part 170, Cybersecurity Maturity Model Certification (CMMC) Program (eCFR, current as of 2026-11-12). Checked .
  4. Department of Defense Chief Information Officer. About CMMC (archived copy, Internet Archive, captured November 13, 2026). Checked .
  5. Office of the Federal Register (Federal Register). Cybersecurity Maturity Model Certification (CMMC) Program, final rule, 89 FR 83092 (October 15, 2024). Checked .
  6. Office of the Federal Register (Federal Register). Defense Federal Acquisition Regulation Supplement: Assessing Contractor Implementation of Cybersecurity Requirements (DFARS Case 2019-D041), final rule, 90 FR 43560 (September 10, 2025). Checked .
  7. Office of the Federal Register (eCFR). 48 CFR 252.204-7021, Contractor Compliance with the Cybersecurity Maturity Model Certification Level Requirements (eCFR, current as of 2026-11-12). Checked .
  8. Office of the Federal Register (eCFR). 48 CFR 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting (eCFR, current as of 2026-11-12). Checked .
  9. Office of the Federal Register (eCFR). 48 CFR 252.204-7019, Notice of NIST SP 800-171 DoD Assessment Requirements (eCFR, current as of 2026-11-12). Checked .
  10. Office of the Federal Register (eCFR). 48 CFR 252.239-7010, Cloud Computing Services (eCFR, current as of 2026-11-12). Checked .
  11. Department of Defense Chief Information Officer. Library (archived copy, Internet Archive, captured November 4, 2026). Checked .
  12. Office of the Assistant Secretary of War for Acquisition and Sustainment, Defense Pricing, Contracting, and Acquisition Policy. Class Deviation 2026-O0025, Revision 3, Revolutionary FAR Overhaul Part 40, DFARS Part 240. Checked .

How we source and check every fact: Editorial standards · Corrections

Last reviewed .

Spotted an error? Tell us and we will check it and correct the page where needed.