November 16, 2026
Key takeaways
  • Prompt injection attacks manipulate AI guardrails using natural language, exploiting the semantic gap to get models to ignore developer instructions.
  • AI social engineering scales faster and lowers attacker skill barriers, enabling automated, targeted campaigns like deepfakes and credential theft.
  • Primary harms include data exfiltration, unauthorized transactions, and malicious or biased outputs that damage reputation and operations.
  • Defenses are immature; require layered controls: human in the loop, prompt firewalls, input sanitization, least privilege, fuzz testing, patching, and user training.

Last Updated on November 16, 2026

Many clients in the defense sector are asking about changes to Cybersecurity Maturity Model Certification (CMMC) Level 2 compliance and assessment requirements during and after the CMMC Phase 2 suspension.

What should DIB orgs with controlled unclassified information (CUI) do now to maintain compliance, honor current contracts, and stay on track for what’s next?

This post gives business and technical decision-makers a quick overview of what is most important now and going forward for US Department of War (DoW) compliance if you handle CUI.

Key takeaways

  • You remain obligated to implement the 110 controls in NIST SP 800-171 Rev. 2 per the DFARS 252.204-7012 clause in current contracts.
  • The DoW still requires you to maintain a valid, defensible, up-to-date NIST SP 800-171 self-assessment compliance score and associated executive attestation in the Supplier Performance Risk System (SPRS) database.
  • Many prime contractors (including the five largest) may still require CMMC Level 2 compliance or certification as part of their flow-down requirements to protect the CUI they share with subcontractors.
  • Only third-party audit mandates are on hold.

What has and has not changed with the CMMC Phase 2 suspension?

On July 13, 2026, the DoW paused the CMMC Phase 2 rollout pending a 60-day program review. CMMC Phase 2 would have required third-party certification of CMMC Level 2 compliance for most contractors that handle CUI, effective November 10, 2026.

What has changed is the requirement for an independent certification assessment to validate your compliance with DoW cybersecurity mandates.

What has not changed are your critical obligations to protect CUI. Still fully in force are:

  • Contract agreements under DFARS 7012 to implement the 110 controls and 320 assessment objectives in NIST SP 800-171 Rev. 2.
  • The requirement to maintain a valid, current (less than 3 years old) NIST SP 800-171 compliance self-assessment score and substantiating evidence (e.g., a current System Security Plan, historical logs) in SPRS.
  • The requirement for an annual affirmation by a senior leader that your SPRS self-assessment score is valid.
  • The US Department of Justice (DoJ) Civil Cyber-Fraud Initiative, which exposes your business and its executives to prosecution under the False Claims Act if your SPRS score does not withstand scrutiny.

DoW paused CMMC Phase 2 to release resistance and bottlenecks associated with third-party audit costs and timelines. The longstanding obligation to protect CUI on non-government systems remains. According to Under Secretary of War Michael Duffey, the reason for suspending CMMC Phase 2 was to “maintain a strict security baseline while removing paralyzing costs.”

What are essential next steps for DIB orgs that handle CUI?

Even if your cybersecurity program already complies fully with NIST SP 800-171 and you have posted a perfect 110 score and associated documentation in SPRS, you still need to sustain compliance as your environment continuously changes and threats advance. If you have documented Plans of Action & Milestones (POA&Ms) in SPRS, you need to continue resolving those and moving toward full compliance. This is essential to maintain your good standing with the DoW and prime contractors, demonstrate a commitment to protecting sensitive data to stakeholders, and avoid negative competitive impacts for weak cybersecurity or data breach exposure.

If your cybersecurity program does not yet conform to DoW requirements, you should not lose momentum but use this extra time to keep following through on your NIST SP 800-171 compliance roadmap and close remaining gaps. Threat actors are targeting your organization, and a cyber incident could bring not just competitive losses but also audit scrutiny, legal impacts, and reputational damage even outside your defense business.

The government’s 60-day review period was to evaluate streamlining CMMC, not scaling back CUI protections in the face of escalating threats. Keep an eye out for news and updates on CMMC reforms and DoW recommendations.

What is the real risk from overstating NIST SP 800-171 compliance?

Above all, do not inflate or falsify your self-attestations, as this is a federal crime and False Claims Act prosecution remains aggressive with financial penalties up to triple the contract value. Self-attested compliance scores that you cannot support are also cause for loss of DoW contracts and disqualification from participation in future contracts. If you think your organization can risk overstating its NIST SP 800-171 compliance score in SPRS because your chances of facing a government-led audit are low, consider that a high percentage of False Claims Act prosecutions result from whistleblower claims lodged by internal staff, third-party consultants, and others. Under the law, whistleblowers receive 15% to 30% of the total funds the DoJ recovers from a successful lawsuit or settlement.

Prior to CMMC, DIB orgs were self-attesting to compliance with NIST 800-171 using the DoW’s SPRS database. But with little follow-up or oversight, not all self-reports were rigorous and reliable.

What’s different now is that a senior executive of the company must personally attest to the veracity of the self-assessment. This puts the signer squarely in the crosshairs of the US Department of Justice (DoJ), whose Civil Cyber-Fraud Initiative clarifies that the False Claims Act (FCA) can be used to prosecute individuals as well as corporations.

John Verry, Managing Director at CBIZ Cybersecurity, points out that this approach could work very well to incentivize cybersecurity investments among SMBs in the DIB: “We do a lot of work with the DIB, and very often we’ve got SMBs with an IT director who’s responsible for information security. And he’s the guy we’re on the phone with, who’s saying, ‘I don’t have the bandwidth. I don’t have the time. They’re not giving me the budget.’”

“So, realistically, his hammer is no longer ‘a C3PAO is going to show up.’ His hammer is, ‘Hey, Mr. President, here is the letter that I need you to sign. And I’m telling you that we don’t actually meet these requirements. And if somebody asks me, I’m going to tell them that we don’t,’” says John.

CMMC 2.0 compliance at Level 1

For DIB companies that only handle federal contract information (FCI) but not CUI, the compliance target is the 15 requirements in FAR clause 52.204-21, Basic Safeguarding of Covered Contractor Information Systems.

What’s different is that CMMC 2.0 takes the requirement for a third-party audit/certification off the table for CMMC Level 1 compliance. Instead, you’ll need to make a yearly self-attestation in the form of an affirmation letter signed by a senior executive.

The bottom line for DIB orgs at CMMC Level 1 is:

  • You’ll save considerable money by foregoing an initial certification audit plus recertification audits every third year.
  • The cybersecurity controls that you need to implement haven’t changed at all. Moreover, these minimal requirements are universally regarded as essential for any internet-connected business in any industry to reduce egregious cyber risk.

CMMC 2.0 compliance at Level 2

DoW suppliers that handle CUI will need to comply with CMMC Level 2, which centers on the 110 controls in NIST 800-171. This has always been the standard for safeguarding CUI in the eyes of the federal government overall, per the National Archives and Records Administration (NARA), which has authority over the CUI program.

CMMC Level 2 allows POA&Ms for some incomplete requirements. The window for POA&Ms will be 180 days.

Do you really not have CUI?

Since the US DoW Cybersecurity Maturity Model Certification (CMMC) first appeared on the horizon in 2020, orgs across the US defense industrial base (DIB) have been saying that CMMC shouldn’t apply to them because they don’t have controlled unclassified information (CUI).

Say you work for a small DIB staffing company that “just puts bodies on bases.” The government is telling you to prepare for CMMC Level 2 compliance. But you don’t think you handle any CUI on your systems or networks. How do you respond?

The first step is to look carefully at your contract(s) and what you’ve agreed to do for the DoW. If you accepted a DFARS 7012 clause in your contract, you’re required to implement the NIST 800-171 framework that is the foundation of CMMC Level 2.

When in doubt, build a CMMC enclave

What if your contract has a DFARS 7012 clause today but you really, truly don’t have any CUI? One solution could be to build a special enclave to capture any CUI that gets sent your way. That way you’re “CUI ready” and can even achieve CMMC Level 2 certification.

Spoiler alert: The top CMMC challenges are all related

By near universal agreement among CMMC service providers and orgs seeking certification (OSCs), the 3 top challenges DIB SMBs consistently face with CMMC 2.0 are:

  • Scoping, by a wide margin.
  • CUI marking and asset management.
  • Getting management buy-in to finally make CMMC investments.

What makes these challenges even more formidable is, you can’t solve one without solving the others. For example, without first marking CUI you can’t accurately know your CMMC scope. Plus, you need to know your CMMC scope to identify the CMMC relevant assets to manage. But none of these activities will get off the ground if senior leaders balk at providing the necessary resources.

Top challenge #1: Scoping, far and away

Defining the scope of your CMMC environment is among the first activities you need to complete on the path to CMMC Level 2/NIST 800-171 compliance. Scoping determines the subset of your total IT environment that a certified third-party assessor organization (C3PAO) will audit for compliance. Since CMMC’s goal is to safeguard CUI, CMMC scoping centers on identifying all the CUI you handle, where it is stored, and what assets (systems, networks, processes, and people, including cloud-based assets and service provider assets) store, process, transmit, and/or create CUI (see challenge #2). As you identify your CUI, you can start diagraming all your CUI data flows and pinpointing the associated in-scope assets. This will let you define the boundaries of your CMMC compliance environment, also known as a CMMC enclave.

The tried-and-true way to approach scoping hasn’t changed at all. You start with knowing where your CUI is. Where does CUI come into your system? Do you create any CUI? Then you diagram your CUI data flows and identify the assets that those flows touch. Keep tracking the CUI all the way to archiving and/or destruction.

Once you have a lifecycle view of your CUI flows, you can identify and categorize all your in-scope assets (technology, people, data storage, SaaS or on-premises security solutions, etc.). The rest of your systems are out of scope or risk managed.

According to the DoW’s CMMC Level 2 scoping guide, you should consider these four asset types as part of your CMMC scope:

  • CUI assets, which are those that directly store, process, and/or transmit CUI.
  • Security protection assets, which include the hardware, software, etc. used to protect CUI. Examples include a firewall or endpoint protection solution. Managed service providers (MSPs) and managed security service providers (MSSPs), along with other cybersecurity vendors and their cloud-based or on-premises infrastructure and services are also considered security protection assets relative to CUI.
  • Contractor risk managed assets, which are the assets you use to reduce the risk associated with sharing CUI with subcontractors and other third parties. An example would be a policy and associated procedures that prevent or limit sharing CUI.
  • Specialized assets, which refers to a potentially huge range of systems and devices that can create and/or process CUI. This includes test equipment, CNC machines, PLC systems, and other operational technology (OT), sensors and other Internet of Things (IoT) devices, government furnished equipment (GFE), and more.

Scoping is a major challenge because it is both interdependent and dynamic. As you map your data flows you must plan how you can simplify and reduce the size of your CUI footprint and associated CMMC scope. Minimizing your CMMC enclave is critical to achieve and maintain compliance and certification in a resource efficient manner.

Top challenge #2: CUI marking and asset management

To complete your scoping exercise, you must identify and mark all your CUI and track down all your CUI relevant assets. Then you can devise a CMMC Level 2 compliant program to manage those assets.

As noted above, without comprehensive CUI marking you cannot identify the associated assets you must manage or know your CMMC enclave scope.

A major difficulty with mapping all your CUI is knowing what CUI is in the first place. Even when you talk with experts about whether a particular data type is CUI, the response is frequently, “It depends.”

There are many CUI groupings and categories, and many defense contracts fail to clearly identify what CUI a contractor will receive. There is a longstanding tendency to “call everything CUI” just to play it safe. This creates uncertainty around CUI marking and can add to compliance cost and complexity.

Of course, to sort out CUI from non-CUI assets, you need a working asset management process and an asset catalog. This is why asset management controls are seen as fundamental to cybersecurity. How can you protect it if you don’t even know you have it?

Top challenge #3: Getting management buy-in on CMMC investments

The fact that so many senior executives in the defense supply chain are still wavering on DoW mandated cybersecurity investments that have been in place since DFARS 7012 became effective in late 2017 says a lot about the true state of cybersecurity across the DIB. Many orgs are self-attesting to NIST 800-171 compliance scores that would not stand up to an independent audit.

A robust cybersecurity posture takes more than technical implementation, and it cannot be relegated solely to IT. It requires a coordinated effort and a cultural shift with active participation at every business level. Without “tone from the top,” a major ongoing effort like CMMC compliance has no real chance of success. This is why leading cybersecurity standards like CMMC and ISO 27001 require proof of ongoing senior management involvement.

What is the recommended approach to get started with these challenges?

While the top CMMC challenges just discussed are interdependent and are often addressed in parallel, there is a recommended approach to help with the “chicken versus egg” conundrum:

  • Engage the awareness and ultimately the support of senior leaders. A recommended “interdepartmental communication” approach is to discuss costs, ROI, etc. over the common ground of managing business risk.
  • Take a look at your contract and/or speak with your contracting officer and legal advisor to pinpoint any data the contract identifies as CUI or as otherwise needing protection.
  • With that guidance as a starting point, comprehensively map all relevant data flows and identify where CUI, federal contract information (FCI), and any other CMMC relevant data is stored, transmitted, or processed. Be certain to identify all CUI Specified data, such as ITAR data, which requires controls beyond CMMC Level 2. You may need specialized expertise to ensure success and avoid onerous noncompliance risk or a failed certification audit.
  • Having definitively marked your CUI, you can identify all the assets that relate to CUI and define your CMMC enclave scope. Then you’ll know what you need to protect to achieve CMMC Level 2 compliance and certification.
  • After having identified your CMMC relevant assets, you can develop a sound asset management plan in line with CMMC requirements as part of your CMMC compliance activities.

CUI and FCI: Should We Keep Them Separate for CMMC Level 2 Compliance?

Any organization that is pursuing Cybersecurity Maturity Model Certification (CMMC) 2.0 Level 2 certification needs to safeguard controlled unclassified information (CUI), as well as federal contract information (FCI). The DoW mandates cybersecurity protections for both these information types. But CUI is considered more sensitive and is subject to significantly more stringent compliance requirements.

For a secure and cost-effective control environment, is it a best practice to separate CUI and FCI into separate “enclaves”? Or is it better to treat FCI like CUI for simplicity?

Does a CMMC Level 2 assessment cover both CUI and FCI?

By default, a CMMC Level 2 assessment with a C3PAO covers both FCI and CUI, even though FCI is only required to have CMMC Level 1 protections.

However, an organization can specify that it is keeping FCI and CUI separate and for cost reasons wants its Level 2 assessment to cover only the CUI environment. The company would then also need to submit a separate CMMC Level 1 self-assessment for the FCI environment.

What is a CMMC enclave?

One of the most important steps on the path to a CMMC Level 2 implementation and certification is minimizing the scope of your FCI and CUI compliance footprint. The smaller your CMMC environment, the more efficiently and cost-effectively you can comply with DoW cybersecurity requirements. CMMC scoping identifies the systems and processes that store, process, and/or transmit FCI, CUI, and other sensitive data assets. Once you know where your FCI and CUI resides and flows, you can isolate the minimum set of assets that are subject to compliance assessment. This will be your CMMC enclave. If you fail to appropriately segregate your CMMC assets and users, your entire network could be in scope for your CMMC Level 2 assessment, creating a prohibitively complex and expensive compliance scenario. The purpose of a CMMC enclave is to physically and logically separate assets that interact with FCI and CUI and so are subject to CMMC Level 2 cybersecurity controls and compliance obligations.

Should every DIB org create a CMMC enclave? Not always. The greater the percentage of your business that is in scope for CMMC, the less benefit an enclave offers. An accepted rule of thumb is that if over 60% of your business systems will be in scope for CMMC, it could make more sense to forego an enclave and certify your whole network for CMMC Level 2 compliance.

What IT assets could be part of our CMMC enclave?

As a rough starting point for scoping your CMMC enclave, most DIB orgs hold FCI and CUI (if present) in systems or assets like these:

  • Systems that store or process email from the government (often the whole email environment)
  • Systems that hold files received from the government, including backups
  • Instant messaging and conferencing systems that transmit government data
  • Workstations, laptops, and other devices that access and/or store emails, instant messages, and similar data from the government
  • Operational technology (OT) devices that process or store government data
  • USB drives, DVDs, and other storage media to which government data has been copied or moved
  • Administrative or governance solutions that manage any of the above systems or assets

When should we keep CUI and FCI together?

Before you can architect your CMMC enclave, you need to know exactly what FCI and CUI you have, how you receive it, where it resides on your systems, who can access it, and how it is transmitted and processed. It is axiomatic that “all CUI is FCI,” but FCI includes data types that do not require the stronger CUI safeguards.

Effectively, CUI is a subset of FCI. But many DIB orgs lack experience and in-house skills to correctly separate the two. Smaller defense contractors store, process, and transmit FCI and CUI across a range of systems, networks, and physical locations, potentially putting nearly the whole IT environment “in scope” for CMMC Level 2 compliance.

For firms in this position, it often makes more sense to “play it safe” and treat FCI the same as CUI. Any cost savings associated with handling FCI separately could be offset by the risks of marking CUI incorrectly and thus failing to protect it, leading to potential compliance violations. Further, the additional time and planning required to successfully separate FCI and CUI could jeopardize CMMC certification timelines and compromise your company’s ability to bid on contracts.

When should we separate CUI from FCI?

Companies with more sophisticated IT environments that can successfully separate FCI and CUI into different enclaves with completely different networks, systems and processes in place, different users, etc. may find it cost-effective to do so. Bigger businesses may manage contracts and associated FCI within their ERP solution, for example. Why make that environment “CUI relevant” if you don’t have to? Contractors that can successfully isolate the assets and people that interact with FCI and CUI have the option to implement data-specific cybersecurity and compliance processes that streamline CMMC certification and ongoing compliance. Some of the benefits of separating FCI and CUI include:

  • Enhanced CUI security, especially if FCI is compromised.
  • An overall reduced and simplified compliance burden.
  • An improved ability to demonstrate compliance with data-specific contract requirements.
  • Reduced data governance costs

What if some of our FCI becomes CUI?

Experience shows that for some DIB orgs FCI can become CUI, often because of details in the contract itself concerning the manufacturing process or the product/service being produced. This possibility is another reason for DIB SMBs to simply treat all the non-classified information they receive from the government as CUI and process it all within the same environment.

What Will It Take to Survive a Third-Party CMMC Level 2 Assessment?

Yes, you need an SSP

Absolutely you will need a robust system security plan (SSP) to pass your CMMC Level 2 assessment. Not only is it a requirement in NIST 800-171, but also it is the launch pad for your entire CMMC program.

Advance planning tips

A great way to prepare for what happens in a CMMC Level 2 assessment is to check out NIST 800-171A, “Assessing Security Requirements for Controlled Unclassified Information.” This is the guidance that auditors will be using. It explains where they’ll be looking, what evidence they’ll be looking for around each control, and more.

The CMMC v2 assessment guides for Level 1 and Level 2, based on NIST 800-171A, are also valuable.

Is CMMC Level 2 Worth it for DIB SMBs?

To invest in CMMC or to not invest in CMMC? That is “the question” these days for many SMBs in the US defense industrial base (DIB). Some SMBs in the defense industrial base (DIB) are strongly considering leaving the market rather than make these investments.

The cost, effort, and time required to achieve CMMC Level 2 certification can be quite high for some companies. But failure to comply also has its costs, including inability to bid on future contracts, loss of current contracts, regulatory fines and scrutiny in the wake of a cyber incident, or even prosecution under the False Claims Act for improper compliance self-attestation.

What are the pros and cons of CMMC Level 2 compliance?

The choice to pursue CMMC Level 2 compliance or not depends on the specific costs and benefits to your organization. If you’re starting from scratch or have major gaps in your controls, the outlay could be daunting.

It is important to weigh your pros and cons carefully and comprehensively. While some companies are exiting the DIB to avoid cybersecurity investments, others are strengthening their cybersecurity postures and attaining early CMMC Level 2 certification to gain a competitive advantage, take market share, and maximize their overall ROI.

The table below summarizes key pros and cons of achieving CMMC Level 2 certification through independent attestation.

Pros Cons
  • Strongly enhanced cybersecurity posture leading to reduced risk of a data breach, successful ransomware attack, etc.
  • Competitive advantage versus firms that are not yet certified.
  • Greater trust and peace of mind among all stakeholders, including investors, regulators, and boards.
  • Improved market reputation.
  • More effective risk management.
  • Better operational efficiency.
  • Significant financial savings from avoiding the costs of a cyber incident, which usually exceed the costs of CMMC Level 2 certification.
  • Reduces the risk of False Claims Act actions and other lawsuits stemming from a cyber incident or whistleblower scenario.
  • High upfront cost (totaling $100,000 and up even for orgs that currently attest to NIST 800-171 compliance).
  • Ongoing annual costs to maintain certification and report compliance to the DoW.
  • Costs for recertification every 3 years.
  • Increased complexity of your IT infrastructure from adding cybersecurity controls and compliance processes.
  • Risk of noncompliance penalties if you achieve certification but fail to maintain compliance.
  • Increased IT operational impacts from managing cybersecurity and compliance assets.

What are the major CMMC Level 2 certification cost categories?

Understanding CMMC cost vectors early in your certification process helps with budget planning and resource distribution. On any CMMC Level 2 certification project, you should factor in these major cost categories:

  • “Hard” costs to implement and upgrade cybersecurity controls and associated hardware and software, including remediating vulnerabilities and compliance gaps. For companies that are far from CMMC Level 2 compliance today, this is often the largest cost area.
  • “Soft” costs like planning, budgeting, and risk assessment, as well as internal audits, creating/updating documentation (e.g., your system security plan and incident response plan), and employee training. Third-party consulting costs usually fall into this category as well.
  • “Time” costs like C-suite strategizing, project management, IT support, and employee or contractor work time.
  • Third-party assessment costs. A ballpark estimate of total costs for a formal C3PAO audit is $100,000, depending on the size of your CMMC scope and other factors (see below).
  • Maintenance costs for continuous compliance and continuous improvement of your CMMC Level 2 environment.

What factors will influence our CMMC Level 2 costs?

CMMC Level 2 compliance/certification costs vary widely based on multiple factors. The biggest factors for any DIB org include:

  • The size and complexity of your business, including how many sites you have. Bigger companies usually have higher certification costs because there are more people and systems involved.
  • Your current cybersecurity posture largely determines how close you are today to CMMC Level 2 compliance and how much work you still need to do.
  • How much CUI do you have, and where does it come from, including whether you generate CUI as well as receive it? The number of users and systems that access CUI also impacts costs, with more access creating a bigger, more complex “compliance boundary” or “CMMC enclave.”
  • The maturity of your governance, risk, and compliance (GRC) program, including tools and processes to automatically monitor and report on cyber compliance metrics.
  • Your choice of C3PAO, as their fees vary.
  • How much do you rely on external resources for both strategic and tactical activities? Consulting services initially add to costs, but third-party expertise can also save money by reducing wasted effort and driving better decisions.
  • Whether your timeline is relaxed or rushed. It generally costs more to make a project happen faster.

How can we reduce our CMMC scope?

Unless every person in your company handles CUI, it usually makes sense to decrease the scope of your CMMC environment by creating a separate enclave and workflow where CUI stays. The smaller your CMMC scope, the more streamlined your control implementation and the faster, simpler, and cheaper your certification audit. Scope reduction strategies include:

  • Keeping your CUI footprint as small as possible, including limiting the number of users who interact with CUI.
  • Leveraging skilled cybersecurity consultants who have years of experience with scoping.
  • Using pre-built documentation templates and other resources to save time and effort.
  • Paying attention to the user-friendliness of cybersecurity solutions, as usability impacts productivity and training costs.

Can external partners help us save time and money on CMMC certification?

Many DIB SMBs lack the internal cybersecurity expertise to correctly scope their CMMC environment, conduct a gap assessment, evaluate cyber risks, implement new technology, and address other challenges on the path to CMMC Level 2. An experienced external partner that is familiar with your industry and IT systems can often achieve better results in less time and with less risk of internal bias and blind spots.

Some of the benefits of engaging a trusted partner to support your CMMC certification journey include:

  • You can save money in the long run by accelerating your timeline and helping you sidestep potential pitfalls.
  • You get objective advice based on a proven, best-practice approach.
  • A third-party expert can evaluate cloud-based services, operational technology (OT), Internet of Things (IoT) equipment, and other specialized assets within your CMMC scope.
  • An independent assessment of your cybersecurity posture can help you prove CMMC alignment or conformance for competitive or legal purposes prior to your successful certification.
  • More than an internal assessment, a third-party audit of your cybersecurity posture helps build trust and peace of mind with stakeholders by showing that your business is committed to protecting CUI and other sensitive data.

What’s next?

Is your business in compliance with the DoW cybersecurity requirements in your current or prospective contracts? Are you able to post, justify, and attest to a strong compliance score in SPRS? CBIZ Pivot Point Security offers a full slate of advisory and consulting services for DIB companies. Our assessment, implementation, and remediation support will ensure you efficiently meet all cyber compliance obligations to participate in DoW contracts. Contact us today to schedule a conversation with a defense industry cybersecurity and compliance expert.

Back to Blog