← Back Contractor Insights Cybersecurity and CMMC Readiness: What Should Government Contractors Do Now? November 17, 2026Last Updated: November 20, 2026 Adapted from the FPS webinar "Cybersecurity Risk and Compliance in Government Contracting: Preparing for What's Next," featuring Perry E. Keating, Randy Armknecht, and Kristi Gilliat of Protiviti and Protiviti Government Services. Information reviewed November 17, 2026. Government contractors should continue protecting sensitive information, maintaining required assessments, and documenting their security practices while CMMC implementation undergoes review. The suspension of the planned Phase II expansion leaves Phase I self-assessment requirements and existing contractual safeguarding obligations in place. business.defense.gov For organizations trying to determine their next steps, the FPS webinar offered a practical starting point: understand the contract, identify the information, map the systems involved, and maintain evidence that required protections are working. That approach brings cybersecurity into everyday contract performance. It also helps organizations make informed decisions about technology, training, service providers, and remediation spending. What does the CMMC pause mean for contractors? The Cybersecurity Maturity Model Certification, or CMMC, program assesses whether defense contractors have implemented required protections for sensitive unclassified information. On July 13, 2026, the defense department announced the suspension of Phase II requirements originally scheduled to take effect on November 10, 2026, and initiated a comprehensive review of the program. Official guidance continues to state that Phase I self-assessment requirements remain in place. Existing obligations to safeguard covered defense information under DFARS 252.204-7012 also continue. business.defense.gov Contractors should review the requirements for each procurement, including applicable clauses, deviations, and formal modifications. Organizations should also assign someone to monitor the official CMMC program updates. The practical priorities remain clear: address security gaps, maintain accurate assessment information, and preserve evidence supporting the organization's representations. Why should cybersecurity compliance start with the contract? A cybersecurity framework provides structure, but the solicitation and contract establish the obligations that apply to a particular engagement. FAR 52.204-21 establishes 15 basic safeguarding requirements for covered contractor information systems handling Federal Contract Information. These address areas such as access, authentication, physical security, malicious code protection, and system flaws. www.acquisition.gov For covered defense work, DFARS 252.204-7012 addresses safeguarding covered defense information, qualifying cyber incident reporting, evidence preservation, and applicable cloud and subcontractor obligations. Other clauses address assessment information, government assessment access, and CMMC requirements. Acquisition.GOV Contract review should involve the people who negotiate the requirements and those who implement them. Contracts personnel may recognize a clause, while IT and security teams understand the systems affected. Program managers know how information moves during performance. Connecting those perspectives early helps prevent a disconnect between what the organization promises and what its operating environment supports. What is the difference between FCI and CUI? Correctly identifying information is a foundation of cybersecurity readiness. Federal Contract Information, or FCI, generally means nonpublic information provided by or generated for the government under a contract to develop or deliver a product or service. It excludes publicly available government information and simple transactional information needed to process payments. www.acquisition.gov Controlled Unclassified Information, or CUI, requires safeguarding or dissemination controls under applicable law, regulation, or government-wide policy. It is unclassified information that still requires protection. Government-related information does not automatically qualify as CUI. www.archives.gov The webinar emphasized the difficulty of working with incomplete or unclear markings. Contractors should establish a process for resolving those questions with the appropriate government customer or prime contractor. Useful questions include:What information will the organization receive or create?Which CUI category and authority apply?Are there additional handling or dissemination restrictions?How should the information be marked, transmitted, and stored? The National Archives CUI Registry provides a reference for understanding CUI categories and their authorities. Where does protected information live and move? After identifying the information, contractors need to understand its path through the organization. That path can include email, laptops, shared drives, collaboration platforms, backups, printers, cloud services, and subcontractors. It may also include tools employees adopt without understanding their security implications. Consider a project team receiving a controlled technical drawing through an approved file-sharing platform. If an employee downloads the drawing to a personal device or uploads it into an unapproved AI application, the organization has introduced another location and another potential exposure. The webinar described this challenge through the concept of a security boundary: the defined environment involved in handling and protecting information. A useful boundary should align with actual operations. System descriptions, inventories, diagrams, and employee practices should tell a consistent story about where information resides and who can access it. How should contractors evaluate cloud services and subcontractors? Outside providers become part of the information protection picture when they handle protected information or support the systems that secure it. Before selecting a cloud service or managed service provider, contractors should understand the applicable requirements, the provider's responsibilities, and the responsibilities retained by the contractor. A product's security features are only part of that evaluation. The same attention belongs in subcontract management. Organizations should determine what information a subcontractor will receive, identify applicable flowdown obligations, and establish appropriate transfer and handling arrangements. DFARS 252.204-7012 includes specific provisions addressing external cloud services and covered subcontracts. Contractors should evaluate those provisions against the services and information involved. www.acquisition.gov A written responsibility agreement can help teams understand who manages access, monitors activity, preserves evidence, and supports incident response. What evidence demonstrates cybersecurity readiness? One of the webinar's recurring themes was the difference between describing a security practice and demonstrating its implementation. A policy may state that access is reviewed regularly. Supporting evidence might include completed reviews, approvals, and records showing that unnecessary access was removed. An incident response plan may identify roles and procedures. Exercise records can help demonstrate that the team has practiced using it. The following table translates the webinar's themes into practical review questions. What should a cybersecurity readiness review include?Readiness areaQuestion to askExamples of supporting documentationContract requirementsHave we identified the obligations that apply to our work?Contract clause inventory, documented reviews, applicable modificationsInformation identificationDo we understand the FCI and CUI we receive or create?Information inventory, handling instructions, documented customer clarificationSecurity boundaryDo our records match where information actually lives and moves?System diagrams, asset inventories, data flow mapsAccess managementCan we show that access is authorized and reviewed?Access approvals, review records, account removal recordsService providersHave we assigned and documented security responsibilities?Provider agreements, responsibility matrices, subcontract provisionsIncident responseCan we recognize, escalate, report, and respond to an incident?Response plan, contact lists, exercise records, reporting proceduresAssessments and remediationDo our submissions reflect actual implementation?Assessment evidence, required affirmations, remediation recordsEmployee practicesDo employees understand approved tools and handling procedures?Training records, technology policies, reporting instructions This table is a planning aid. It does not replace a complete assessment of applicable requirements. What should an incident response plan address? An incident response plan should explain how the organization recognizes an incident, escalates it, contains the impact, preserves evidence, evaluates reporting obligations, and restores operations. Where DFARS 252.204-7012 applies, qualifying cyber incidents must be reported within 72 hours of discovery. The clause also establishes preservation and cooperation requirements. The Defense Cyber Crime Center provides reporting information, including procedures for submitting additional information after an initial report. Acquisition.GOV Organizations should prepare reporting access and escalation contacts in advance. A tabletop exercise can reveal whether employees know whom to call and whether leadership, counsel, IT, security, and service providers understand their roles. Testing backup restoration is equally useful. A backup supports resilience only when the organization can use it to recover needed information and operations. How does AI affect cybersecurity accountability? AI can support activities such as organizing documentation, reviewing information, and identifying potential gaps. It also introduces new questions about access, data movement, retention, and human oversight. Before using AI with government contract information, organizations should determine whether the tool is approved for the information involved and whether its operating environment supports applicable requirements. The webinar emphasized that people remain responsible for reviewing the results. AI-generated documentation should be checked against actual system configurations and practices. Assessment statements and affirmations need support from reliable evidence. Employees also need clear instructions about which tools they may use and what information they may enter. How can contractors turn readiness into an ongoing practice? Cybersecurity readiness requires coordination across the organization. Leadership sets priorities and resources. Contracts teams identify obligations. IT and security implement safeguards. Human resources supports training and account changes. Procurement manages provider relationships. Program teams handle information throughout performance. A practical starting point is to review one active contract and trace the information associated with it. Confirm the requirements, map the systems and partners involved, examine supporting evidence, and assign owners to identified gaps. Repeating that process across the organization helps establish a more reliable picture of readiness. It also gives leaders a clearer basis for deciding where training, technology, and corrective action are needed. How can FPS help your team strengthen cybersecurity readiness? Federal Publications Seminars provides training that helps government contracting professionals understand their responsibilities and apply them throughout the contracting lifecycle. Explore FPS training and learning resources for cybersecurity, compliance, and government contracting education. Organizations seeking training across multiple roles can learn about FPS Corporate Solutions or contact FPS to discuss their team's needs. Perry Keating Managing Director and President, Protiviti Government Services (Pro Gov)Perry Keating is the Managing Director and President of Protiviti Government Services (Pro Gov), with over 30 years of experience in business and service with the government and the Defense Industrial Base (DIB). Perry’s technical expertise includes protecting government data, systems, and networks from cybersecurity assessments, policy development, and remediation through incident response for compliance with a variety of frameworks (FAR 52.204-21, DFARS 252.204-7012, FISMA, FedRAMP, NIST RMF, NIST 800-53; NIST 800-171, CMMC). His experience gives him unique industry insight into the Aerospace & Defense (A&D), Government Contractors (GovCon), Defense Industrial Base (DIB), and Public Sector (US Federal, State & Local) as well as the Telecommunications and High-Tech industries. Perry earned his MBA from Virginia Polytechnic Institute and State University and a Bachelor of Science in Computer Science from Tulane University. He proudly served as a Commissioned Officer in the US Army Corps of Engineers. He is a member of the Association of Computing Machinery (ACM); the Armed Forces Communications & Electronics Association (AFCEA); the Army Engineer Association (AEA); the Association of the United States Army (AUSA); the Information Systems Audit and Control Association (ISACA); and the Reserve Officers Association (ROA) Education BS in Computer Science from Tulane University MBA from Virginia Polytechnic Institute and State Related Now that the Midterm Elections are over, what's next for government contractors? November 16, 2026 Following the 2026 midterm elections, government contractors face a changing political landscape as Democrats take control of Congress. This article explores the potential impact on FY 2027 funding, the National Defense Authorization Act (NDAA), increased congressional oversight, and False Claims Act exposure. It also outlines steps contractors can take to prepare for funding disruptions, investigations, and evolving procurement priorities. Shield & Spear - AI Chipmaker Crisis, FAA's $50B Tech Request, and CMMC Updates November 16, 2026 This week's edition of Hunton's Shield & Spear covers major developments in government contracting, including cybersecurity enforcement, AI and national security concerns, federal contract awards, and regulatory changes. Key updates include the continued pause of CMMC Phase 2, False Claims Act settlements, NASA's $10 billion lunar delivery contract, small business size standard proposals, and recent GAO protest decisions. Explore the latest compliance risks, contracting opportunities, and upcoming regulatory deadlines impacting federal contractors. What Is the FAR? A Beginner's Guide to the Federal Acquisition Regulation November 11, 2026 Understanding the Federal Acquisition Regulation (FAR) is essential for government contractors. Learn what the FAR covers, how it is organized, and how to navigate requirements throughout the federal contracting lifecycle. CMMC Phase 2 Remains Paused: What's Next? November 10, 2026 The Department of Defense's pause on CMMC Phase 2 remains in effect, with no announced end date or additional guidance for contractors. While third-party assessment requirements remain uncertain, existing cybersecurity obligations under CMMC Phase 1, FAR 52.204-21, and NIST SP 800-171 still apply. This article explores potential next steps for CMMC Phase 2 and what government contractors should consider as they maintain compliance.
Adapted from the FPS webinar "Cybersecurity Risk and Compliance in Government Contracting: Preparing for What's Next," featuring Perry E. Keating, Randy Armknecht, and Kristi Gilliat of Protiviti and Protiviti Government Services. Information reviewed November 17, 2026. Government contractors should continue protecting sensitive information, maintaining required assessments, and documenting their security practices while CMMC implementation undergoes review. The suspension of the planned Phase II expansion leaves Phase I self-assessment requirements and existing contractual safeguarding obligations in place. business.defense.gov For organizations trying to determine their next steps, the FPS webinar offered a practical starting point: understand the contract, identify the information, map the systems involved, and maintain evidence that required protections are working. That approach brings cybersecurity into everyday contract performance. It also helps organizations make informed decisions about technology, training, service providers, and remediation spending. What does the CMMC pause mean for contractors? The Cybersecurity Maturity Model Certification, or CMMC, program assesses whether defense contractors have implemented required protections for sensitive unclassified information. On July 13, 2026, the defense department announced the suspension of Phase II requirements originally scheduled to take effect on November 10, 2026, and initiated a comprehensive review of the program. Official guidance continues to state that Phase I self-assessment requirements remain in place. Existing obligations to safeguard covered defense information under DFARS 252.204-7012 also continue. business.defense.gov Contractors should review the requirements for each procurement, including applicable clauses, deviations, and formal modifications. Organizations should also assign someone to monitor the official CMMC program updates. The practical priorities remain clear: address security gaps, maintain accurate assessment information, and preserve evidence supporting the organization's representations. Why should cybersecurity compliance start with the contract? A cybersecurity framework provides structure, but the solicitation and contract establish the obligations that apply to a particular engagement. FAR 52.204-21 establishes 15 basic safeguarding requirements for covered contractor information systems handling Federal Contract Information. These address areas such as access, authentication, physical security, malicious code protection, and system flaws. www.acquisition.gov For covered defense work, DFARS 252.204-7012 addresses safeguarding covered defense information, qualifying cyber incident reporting, evidence preservation, and applicable cloud and subcontractor obligations. Other clauses address assessment information, government assessment access, and CMMC requirements. Acquisition.GOV Contract review should involve the people who negotiate the requirements and those who implement them. Contracts personnel may recognize a clause, while IT and security teams understand the systems affected. Program managers know how information moves during performance. Connecting those perspectives early helps prevent a disconnect between what the organization promises and what its operating environment supports. What is the difference between FCI and CUI? Correctly identifying information is a foundation of cybersecurity readiness. Federal Contract Information, or FCI, generally means nonpublic information provided by or generated for the government under a contract to develop or deliver a product or service. It excludes publicly available government information and simple transactional information needed to process payments. www.acquisition.gov Controlled Unclassified Information, or CUI, requires safeguarding or dissemination controls under applicable law, regulation, or government-wide policy. It is unclassified information that still requires protection. Government-related information does not automatically qualify as CUI. www.archives.gov The webinar emphasized the difficulty of working with incomplete or unclear markings. Contractors should establish a process for resolving those questions with the appropriate government customer or prime contractor. Useful questions include:What information will the organization receive or create?Which CUI category and authority apply?Are there additional handling or dissemination restrictions?How should the information be marked, transmitted, and stored? The National Archives CUI Registry provides a reference for understanding CUI categories and their authorities. Where does protected information live and move? After identifying the information, contractors need to understand its path through the organization. That path can include email, laptops, shared drives, collaboration platforms, backups, printers, cloud services, and subcontractors. It may also include tools employees adopt without understanding their security implications. Consider a project team receiving a controlled technical drawing through an approved file-sharing platform. If an employee downloads the drawing to a personal device or uploads it into an unapproved AI application, the organization has introduced another location and another potential exposure. The webinar described this challenge through the concept of a security boundary: the defined environment involved in handling and protecting information. A useful boundary should align with actual operations. System descriptions, inventories, diagrams, and employee practices should tell a consistent story about where information resides and who can access it. How should contractors evaluate cloud services and subcontractors? Outside providers become part of the information protection picture when they handle protected information or support the systems that secure it. Before selecting a cloud service or managed service provider, contractors should understand the applicable requirements, the provider's responsibilities, and the responsibilities retained by the contractor. A product's security features are only part of that evaluation. The same attention belongs in subcontract management. Organizations should determine what information a subcontractor will receive, identify applicable flowdown obligations, and establish appropriate transfer and handling arrangements. DFARS 252.204-7012 includes specific provisions addressing external cloud services and covered subcontracts. Contractors should evaluate those provisions against the services and information involved. www.acquisition.gov A written responsibility agreement can help teams understand who manages access, monitors activity, preserves evidence, and supports incident response. What evidence demonstrates cybersecurity readiness? One of the webinar's recurring themes was the difference between describing a security practice and demonstrating its implementation. A policy may state that access is reviewed regularly. Supporting evidence might include completed reviews, approvals, and records showing that unnecessary access was removed. An incident response plan may identify roles and procedures. Exercise records can help demonstrate that the team has practiced using it. The following table translates the webinar's themes into practical review questions. What should a cybersecurity readiness review include?Readiness areaQuestion to askExamples of supporting documentationContract requirementsHave we identified the obligations that apply to our work?Contract clause inventory, documented reviews, applicable modificationsInformation identificationDo we understand the FCI and CUI we receive or create?Information inventory, handling instructions, documented customer clarificationSecurity boundaryDo our records match where information actually lives and moves?System diagrams, asset inventories, data flow mapsAccess managementCan we show that access is authorized and reviewed?Access approvals, review records, account removal recordsService providersHave we assigned and documented security responsibilities?Provider agreements, responsibility matrices, subcontract provisionsIncident responseCan we recognize, escalate, report, and respond to an incident?Response plan, contact lists, exercise records, reporting proceduresAssessments and remediationDo our submissions reflect actual implementation?Assessment evidence, required affirmations, remediation recordsEmployee practicesDo employees understand approved tools and handling procedures?Training records, technology policies, reporting instructions This table is a planning aid. It does not replace a complete assessment of applicable requirements. What should an incident response plan address? An incident response plan should explain how the organization recognizes an incident, escalates it, contains the impact, preserves evidence, evaluates reporting obligations, and restores operations. Where DFARS 252.204-7012 applies, qualifying cyber incidents must be reported within 72 hours of discovery. The clause also establishes preservation and cooperation requirements. The Defense Cyber Crime Center provides reporting information, including procedures for submitting additional information after an initial report. Acquisition.GOV Organizations should prepare reporting access and escalation contacts in advance. A tabletop exercise can reveal whether employees know whom to call and whether leadership, counsel, IT, security, and service providers understand their roles. Testing backup restoration is equally useful. A backup supports resilience only when the organization can use it to recover needed information and operations. How does AI affect cybersecurity accountability? AI can support activities such as organizing documentation, reviewing information, and identifying potential gaps. It also introduces new questions about access, data movement, retention, and human oversight. Before using AI with government contract information, organizations should determine whether the tool is approved for the information involved and whether its operating environment supports applicable requirements. The webinar emphasized that people remain responsible for reviewing the results. AI-generated documentation should be checked against actual system configurations and practices. Assessment statements and affirmations need support from reliable evidence. Employees also need clear instructions about which tools they may use and what information they may enter. How can contractors turn readiness into an ongoing practice? Cybersecurity readiness requires coordination across the organization. Leadership sets priorities and resources. Contracts teams identify obligations. IT and security implement safeguards. Human resources supports training and account changes. Procurement manages provider relationships. Program teams handle information throughout performance. A practical starting point is to review one active contract and trace the information associated with it. Confirm the requirements, map the systems and partners involved, examine supporting evidence, and assign owners to identified gaps. Repeating that process across the organization helps establish a more reliable picture of readiness. It also gives leaders a clearer basis for deciding where training, technology, and corrective action are needed. How can FPS help your team strengthen cybersecurity readiness? Federal Publications Seminars provides training that helps government contracting professionals understand their responsibilities and apply them throughout the contracting lifecycle. Explore FPS training and learning resources for cybersecurity, compliance, and government contracting education. Organizations seeking training across multiple roles can learn about FPS Corporate Solutions or contact FPS to discuss their team's needs.