By James Gort. Originally published on LinkedIn on April 6, 2026.
If you support work around Davis–Monthan, CMMC now decides who keeps their contracts.
You built your company by solving real problems for the defense community in and around Tucson. You hire great people, hit deadlines, and support missions that matter.
Now CMMC 2.0 is showing up in conversations with contracting officers, and it may feel like a moving target that decides whether you can even bid. You are not alone in feeling that way.
What actually changed
For years many contractors could simply “self-attest" that they followed required cybersecurity practices. CMMC 2.0 changes this for a large part of the defense industrial base.
Most small suppliers fall into one of two buckets:
- Level 1: You only handle basic Federal Contract Information.
- Level 2: You work with Controlled Unclassified Information (CUI), which includes a lot of technical data and program details.
Level 2 usually requires an outside assessment every three years, not just a score you submit yourself. If the required level is on a contract and you do not have it in the system, you simply cannot win that work.
Arizona advisors are warning that many small contractors have roughly the next year or two to be ready, depending on contract cycles.
Why this feels heavy
You are not imagining the weight.
- There are 110 practices at Level 2, each with detailed assessment objectives.
- First-year costs for tooling, process work, and outside help can quickly reach the tens of thousands of dollars, especially for companies starting from a light security baseline.
Some small suppliers are already asking whether they can afford to stay in the defense market at all, which is precisely the concern raised in recent coverage.
The real risk is doing a little bit of everything, feeling busy, and then discovering too late that you still are not ready when CMMC language lands in a must-win contract.
A simple three-step plan
You do not need to turn your shop into a security company. You do need a clear, honest plan.
1. Confirm your level and timeline
Look at your current and expected contracts.
- Are you involved with CUI, or do you handle only basic contract data?
- When do key contracts renew or recompete?
If CUI is involved, consider preparing for Level 2 and plan accordingly.
2. Get a focused readiness review
Before buying tools, get a short gap assessment against the right level.
A good review will:
- Map where you already meet practices.
- Flag the handful of issues that would clearly fail an audit.
- Separate quick policy fixes from bigger investments.
This keeps you from overspending in the wrong places and gives you a punch list you can actually work on.
3. Choose what to own and where to partner
Your team should own the business decisions: which contracts matter most, which systems are critical, and how much risk you can accept.
You can lean on a specialized partner for:
- Designing a right‑sized security stack that lines up with CMMC.
- Implementing controls like MFA, patching, backups, and logging.
- Helping document what you do in a way an assessor can understand.
The goal is not to push responsibility away. It is to avoid trying to learn the entire CMMC rule set on top of running your company.
Where Fortress MSP can help
You are the hero in this story. You are deciding whether to stay and grow in the defense supply chain and how to do it on a realistic budget.
Fortress MSP steps in as a guide. We help small and mid-sized contractors:
- Clarify which CMMC level really applies.
- Build a practical roadmap tied to actual contract dates.
- Implement and monitor the key controls that matter for both security and future assessments.
If you support work tied to Davis–Monthan or other DoD programs and CMMC 2.0 feels like a moving target, the best next step is a short, plain‑English conversation. From there, we can help you see whether you are a few focused moves away from being ready or whether it is time to rethink which contracts you chase before the rule makes that choice for you.