Air Force Cracks Down on Non-Compliant Computers and Software

Overview

The Air Force's 688th Cyberspace Operations Wing is actively enforcing the DoD (Department of Defense) Comply to Connect (C2C) framework by quarantining non‑compliant hardware and software on Air Force and Space Force networks. This enforcement is being implemented as part of the broader Zero Trust security framework tied to a 2021 executive order, and the DoD has identified 91 cybersecurity initiatives to be in place by the end of fiscal 2027. For government contractors with systems connected to Air Force or Space Force networks, the practical risk is immediate loss of network access or quarantine if devices or software do not meet DoD cybersecurity expectations. Contractors must validate that hardware, software, and endpoint posture align with applicable DoD requirements to avoid operational disruption. Action now reduces the risk of being quarantined, preserves program continuity, and positions bidders and incumbents to meet follow‑on access rules.

Immediate Actions (This Week)

• [ ] Inventory all devices (hardware and virtual endpoints) and software images that are connected, or could connect, to Air Force or Space Force networks; include firmware and third‑party agents.
• [ ] Identify systems that currently connect to Air Force/Space Force networks and flag any that lack centralized endpoint management, up‑to‑date patching, or clear configuration baselines.
• [ ] Contact your Air Force or Space Force program/technical point of contact to confirm current network access rules and any local C2C quarantine procedures affecting your program.
• [ ] Verify supplier and subcontractor software/firmware attestations and list any components without current attestations for prioritized remediation.
• [ ] Run an immediate vulnerability and configuration scan (or confirm recent scan results) against affected assets and document high‑severity findings for emergency patching.

Short-Term Actions (30 Days)

• [ ] Remediate critical and high vulnerabilities and apply vendor firmware/software updates to bring assets into compliance with DoD posture requirements.
• [ ] Map your current controls and evidence to the named compliance references (CMMC (Cybersecurity Maturity Model Certification), NIST 800-171 (NIST Special Publication 800-171), NIST 800-53, Zero Trust Architecture, Comply to Connect (C2C), DFARS (Defense Federal Acquisition Regulation Supplement) 252.204-7012, DFARS 252.204-7021) and prepare a prioritized remediation plan for gaps.

Long-Term Actions (90+ Days)

• [ ] Implement or mature an enterprise Comply to Connect (C2C) program: standardized asset inventory, endpoint management, automated posture enforcement, and quarantine/containment playbooks.
• [ ] Integrate C2C and Zero Trust acceptance criteria into procurement, supplier onboarding, and contract language so new assets arrive pre‑validated or with required attestations.
• [ ] Pursue formal program or organizational certification/assurance activities tied to the named compliance regimes as appropriate to your business lines.

Compliance Checklist

• [ ] Comply to Connect (C2C) — ensure devices meet network access posture checks and that quarantine/containment processes are documented.
• [ ] Zero Trust Architecture — implement least‑privilege network segmentation and device trust assessments consistent with Zero Trust principles named in the event.
• [ ] NIST 800-171 — map controlled unclassified information (CUI (Controlled Unclassified Information)) handling and device control requirements to on‑network assets.
• [ ] NIST 800-53 — where applicable, map higher‑assurance control baselines for systems that support DoD missions.
• [ ] CMMC — evaluate CMMC scope for affected contracts and plan evidence collection and remediation as needed.
• [ ] DFARS 252.204-7012 and DFARS 252.204-7021 — verify contractual flowdowns and ensure implementation of required cybersecurity protections and reporting capabilities.

Resources

• Executive Order 14028 — text: TBD pending source review
• DFARS 252.204-7012 — text: TBD pending source review
• DFARS 252.204-7021 — text: TBD pending source review
• Air Force / 688th Cyberspace Operations Wing guidance on Comply to Connect (C2C) — TBD pending source review

Helpful internal guidance:

• Primary hub: Secure Operations Guide (/insights/secure-operations-guide)
• Related guides:
• CMMC Compliance Guide (/insights/cmmc-compliance-guide)
• CUI-Safe CRM Guide (/insights/cui-safe-crm-guide)

How Cabrillo Club Automates This

Cabrillo Signals War Room

• Cabrillo Signals War Room has already detected this event and delivered this briefing within minutes. It continuously monitors federal policy shifts, agency guidance, and compliance events so you receive immediate briefings on enforcement actions like the 688th Cyberspace Operations Wing C2C quarantines. War Room will surface follow‑on Air Force or Space Force notices and compile timelineed alerts for capture and program teams.

Cabrillo Signals Match Engine

• The Signals Match Engine automatically rescors your opportunity pipeline and active ingest when events like this change agency risk or access requirements. It updates match scores, keyword weighting, and agency alignment in real time so capture managers see which opportunities become higher risk or require added compliance capability to remain competitive.

Cabrillo Signals Intelligence Hub

• The Signals Intelligence Hub tracks affected agencies, NAICS codes, and contract vehicles and supports saved searches and alerting for follow‑on solicitations and guidance. For this event, configure saved searches for Air Force and Space Force C2C guidance and for the listed NAICS codes in your portfolio so you get notified when the government posts clarification or solicitation language affecting access requirements.

Proposal Studio (Proposal OS)

• Proposal Studio generates compliance matrices, drafts technical approaches that call out your C2C and Zero Trust controls, and maintains your win‑theme and past performance library to accelerate responses. Use Proposal OS to produce first drafts of remediation plans, control mappings to NIST 800‑171/NIST 800‑53 where applicable, and to maintain the evidence library needed for DFARS clause compliance.

Proposal Studio Workflow Tracker

• The Workflow Tracker automates a 9‑gate capture progression and routes compliance reviews to contracts, legal, and security owners automatically. It tracks supplier certifications and evidence, enforces review gates for asset inventory and endpoint posture, and outputs audit‑ready documentation packages to support access requests or remediation attestations.

Call to action: Review the Immediate Actions above, then use your Cabrillo Signals War Room briefing and set up related saved searches in the Cabrillo Signals Intelligence Hub. If you need help turning the compliance checklist into proposal content or remediation deliverables, run a Proposal Studio draft and route it through the Proposal Studio Workflow Tracker for coordinated execution.