Managed IT and Cybersecurity for Columbus Manufacturers
Your line runs on equipment older than your ERP, and the controller driving it will never take another patch. If you sell into the defense supply chain, a prime is now asking for an SPRS score and a CMMC status you are not sure how to produce. Both problems land on the same small IT budget.
Our machines run software the vendor stopped supporting. How do we protect them?
Most plants have a controller, an HMI or a machine PC running something the vendor stopped supporting years ago, and you cannot replace it without replacing the machine around it. The answer is to make it unreachable from everything that does not need it.
CISA’s Cross-Sector Cybersecurity Performance Goals treat this case as normal. Where patching is not possible, or would substantially compromise availability or safety, they call for compensating controls such as segmentation and monitoring, and for recording that they were applied.
It starts with a list, not a firewall rule: every controller, HMI and machine PC on the floor, what it runs, and whether anyone still has a login to it. Plants with a few generations of equipment usually find devices nobody remembers configuring, some still phoning home to a vendor that no longer exists. Then come the controls:
- A segmented design where the office VLAN and the plant floor are not the same broadcast domain.
- Tight rules about which traffic crosses between them.
- Monitoring at that boundary.
The failure this guards against is an ordinary one. Someone in accounting opens an attachment, and nothing in the network stops it from reaching the line. Keeping the list current and the boundary enforced as equipment gets added or replaced is ongoing work, and it is what our Managed IT and Network Operations Center coverage is built to carry.
Why would attackers pick a manufacturer like us?
Because it works. IBM’s 2026 X-Force Threat Index put manufacturing at the top of its most-attacked list for the fifth year running, with data theft the most common goal.
The logic is downtime math you already know. When a line stops, the cost is large and immediate, so a manufacturer is more likely to pay fast. And a supplier holding drawings and process data on a file server is worth stealing from even when nothing gets encrypted.
That sets the priorities. Test backups by restoring from them, because a green checkmark in the console is not a test. Put multifactor authentication on every account, including the ones vendors and integrators use to reach your equipment. And give the security program one owner. That is what our Virtual CISO and IT Strategy work does for shops with no security leader on staff.
If you do not know where you stand, start with our Security Analysis at https://outreach.ttscyber.com/analysis. It is $349, fully independent, and mapped to 38 compliance frameworks, and it is also the input that makes a CMMC scoping conversation worth having.
A customer sent us a CMMC questionnaire. How does CMMC reach a supplier like us?
Through the purchase order. It usually shows up as a questionnaire from a customer of many years, with a deadline attached.
The main safeguarding clause, DFARS 252.204-7012, flows down at every tier to subcontracts whose work involves covered defense information, and separately to subcontracts for operationally critical support. So a supplier can be caught by it without ever receiving a drawing.
What your customer has to check before awarding you work depends on its own contract. Where the CMMC clause is in it, the customer has to confirm you hold a current CMMC status at the level the work calls for, backed by an annual affirmation. Where its contract carries DFARS 252.204-7020, it also cannot award you a subcontract carrying the NIST SP 800-171 requirements unless you have completed at least a Basic self-assessment in the previous three years. Solicitations issued under the FAR overhaul since February 2026 use a different clause without that check.
Your level turns on what lands in your systems, not on how a document is marked. Federal Contract Information, meaning information the government provided or that you generated for it under a contract and that is not meant for public release, puts you at Level 1. Drawings, specs and part data that are Controlled Unclassified Information put you at Level 2. CUI does not stop being CUI because a prime failed to mark it.
Sorting that out is scoping: which machines, file shares and mailboxes touch the data. Set it too wide and the whole plant gets hardened for no reason. Set it too narrow and the affirmation you sign, a formal statement to the government, is inaccurate. Our cybersecurity and virtual CISO work covers the scoping, the control set and the documentation behind it.
A prime wants our SPRS score. What does producing one take?
The score itself is arithmetic. The work is the 110 determinations underneath it: someone has to take each requirement in NIST SP 800-171 and decide whether it is implemented in the environment you run. The network diagram is not the environment.
The checks are specific. Is multifactor authentication on every account, or on most of them? Do the file share permissions still match who works there now? Are the logs anyone would need after an incident being kept anywhere at all? A control running on one server and not the other three is not in place across the environment, and the determination has to say which it is.
Honest first passes usually land lower than the shop expected, and that is the useful outcome. The gap analysis is the deliverable. The number falls out of it.
Keep the evidence as you go. For multifactor authentication, that is the export listing every account and whether it is enforced, with each exception and its reason, not a screenshot of the policy. The same record answers a customer’s security questionnaire and a cyber insurance renewal.
None of it stays done. Equipment gets replaced, people leave, and the self-assessment comes back around. Our virtual CISO and Compliance-as-a-Service work keeps the record current between reposts, so the next one is a short review and a prime’s questionnaire gets answered from what you already have.
What does CMMC require right now, after the 2026 suspension?
The acquisition rule that puts CMMC into contracts took effect on November 10, 2025. A contracting officer can make CMMC status a condition of award, and the required level appears in the solicitation before anything is signed. What is in force today is Phase 1.
- Level 1, for contracts carrying the CMMC clause where you handle Federal Contract Information: a self-assessment against 15 basic safeguarding requirements, performed again and posted to SPRS every year, with an affirmation. No plans of action are allowed, so every requirement has to be met.
- Level 2, where you handle Controlled Unclassified Information: all 110 requirements of NIST SP 800-171 Revision 2, self-assessed every three years. The result goes to SPRS, with an affirmation at completion and annually after that. Level 2 (Self) is the only Level 2 a new requirement can carry today.
On July 13, 2026, the Department of War (the Department of Defense) suspended Phase 2. That is the stage that would have required third-party certification starting November 10, 2026. The same memo put all pending and future CMMC milestones on hold. A reform task force’s report was due September 11. As of September 21, 2026, it had not been made public and no further guidance had been issued.
Contracting officers have been told to remove any Level 2 (C3PAO) or Level 3 (DIBCAC) requirement already in a contract by modification. A C3PAO is an authorized third-party assessor, and DIBCAC is the assessment center of the Defense Contract Management Agency. Until the modification is made, the contract as awarded still contains the requirement.
What did not change: Phase 1’s self-assessment requirements, and DFARS 252.204-7012 with its NIST SP 800-171 Revision 2 requirements. Separately, the same 15 safeguards reach most federal contracts where your systems may hold Federal Contract Information, even without the CMMC clause. Acquisitions of commercially available off-the-shelf items are carved out, which matters if you sell catalog parts. On their own, those safeguards carry no SPRS or affirmation duty. If someone says CMMC went away, check the contract before believing it. Working out where a specific contract stands, and the work list that creates, is where our engagements with manufacturers start.
Start here
Find out where you actually stand
The Security Analysis is a fixed-scope review of your environment, run independently and mapped to 38 compliance frameworks. It replaces an assumption about your posture with a finding.
Questions we get asked
Does CMMC reach a manufacturer with no DoD work at all?
No. CMMC follows the contract clause, so where there is no DoD work anywhere in the chain, the clause never lands and no CMMC obligation attaches. The controls still matter. Commercial customers send security questionnaires as a condition of supply, and cyber insurance applications ask whether multifactor authentication, tested backups and endpoint detection are in place. NIST SP 800-171 is a sensible checklist to work from even when nobody requires it. TTS Cyber is not a law firm; this is not legal advice.
What is the difference between an SPRS score and a CMMC status?
An SPRS score is a number. It starts at 110 and drops by a weighted amount for each NIST SP 800-171 requirement not implemented, so it can land well below zero.
A CMMC status is a determination at a given level, recorded with an affirmation. Final means the requirements were met. Conditional means the assessment passed with a qualifying plan of action, which has 180 days to close, and award can still happen meanwhile. The third state is no status at all. Level 1 has no conditional status, because every requirement must be met. One can exist without the other. TTS Cyber is not a law firm; this is not legal advice.
Do we need a fresh CMMC Level 1 self-assessment every year, or will a re-signed affirmation do?
A fresh one. The self-assessment against the 15 safeguarding requirements has to be performed again and reposted to the Supplier Performance Risk System every year, and re-signing last year’s result does not satisfy it. No plans of action are allowed at Level 1, so every requirement has to be met on the day of the affirmation. TTS Cyber is not a law firm; this is not legal advice.
One person clicked something yesterday and now three other computers have it, including the PC out in the warehouse that runs our machines. Those were supposed to be separate. Why did it spread, and how do we stop it while we clean up?
The common reason is that the two networks were only separate on paper. If the office VLAN and the plant floor are the same broadcast domain, nothing between them is inspecting that traffic, so an attachment opened in accounting can reach the line. Nobody can tell you that is what happened here without looking at what crossed.
While you clean up, containment comes before diagnosis: get the affected machines off the network, and treat the boundary between office and production as untrusted until you know what crossed it. The lasting fix is an accurate inventory of the production network, a segmented design, tight rules about which traffic crosses, and monitoring at that boundary.
Can you come out to the plant, or is this remote only?
Remote support covers most of what a manufacturer needs day to day. Our office is in Columbus and most of our onsite work is in Central Ohio, but onsite support can be arranged in any of the 50 states. Plant floor work in particular, walking the production network and tracing what is connected to what, usually needs someone there in person at least once.
Primary sources
Read the rules yourself
These are the official texts for the main rules this page covers. The page also draws on other sources named in the text above, which are not linked here. Where a section is named above, it is worth reading in the instrument rather than taking a summary for it, including this one.
- 32 CFR Part 170: CMMC Program
- DFARS 252.204-7012: safeguarding covered defense information
- DFARS 252.204-7021: CMMC requirement
- DFARS 252.204-7025: notice of CMMC level requirements
- NIST SP 800-171 Revision 2: protecting controlled unclassified information
- DoW CIO memo suspending CMMC Phase 2 and creating the CMMC Reform Task Force (July 13, 2026)
- DoW acquisition memo implementing the CMMC Phase 2 suspension (July 13, 2026)
- DoD Class Deviation 2026-O0025, Revision 3 (September 3, 2026)
- FAR overhaul Part 52, including clause 52.240-93
Services
What we do
- Managed IT Services
- Cyber Security Solutions
- Virtual CISO (vCISO) Services
- Cloud IT Services
- Network Operations Center (NOC) Services
- IT Strategy & Virtual CIO Services
- Backup & Disaster Recovery
- Microsoft 365 Management
- Security Awareness Training
- Co-Managed IT
- Penetration Testing
- Vulnerability Assessments
Further reading
From our blog
Not legal advice
TTS Cyber is an IT and cybersecurity company, not a law firm, and nothing on this page is legal advice. This page summarises published rules and cites them so they can be read directly; where this page and the source differ, the source governs. Whether a particular rule reaches a particular business, and what it requires of that business, are legal questions for that business's own attorney.
Page last updated .