Costing & FinanceFree calculatorPDF, Excel, Word exportDefense

Defense Supplier Compliance Hours and Staffing Calculator

Most CMMC budgets focus on the one time remediation and forget that NIST 800-171 controls need people every week. This calculator adds up the recurring labor so a small manufacturer can see whether compliance needs a fraction of someone or a full hire.

Your numbers

60 users
hours per week

Covers audit log review, alert triage and correlating events.

minutes
minutes

Security awareness plus CUI handling and insider threat content.

hours per month
hours per month
items
hours
hours per year
$ per hour

Your results

Total annual hours
650
Equivalent FTE (1,800 productive hours)
0.3611
Log review hours
156
Access review hours
20
Training hours (all users)
90
Employee time, which is a real cost even though it is not IT labor.
Scan, patch and remediation hours
192
POA&M work hours
72
Annual labor cost
$55,250
Labor cost per user
$921

Covers internal recurring labor only. Tools, managed services, assessment fees and one time remediation projects are not included. Defaults are planning figures, not benchmarks.

Save results:

Annual compliance hours vs users in scope

Sweeps Users with access to the CUI environment from 5 to 400, holding your other inputs fixed.

Automate recurring evidence collection

See which of these hours can be reduced by pulling access, log and approval data automatically. Optional.

Optional. The tool and every export work without this. No spam.

How to use it

Start with the number of users who touch the CUI environment, not total headcount; shrinking scope with an enclave is the biggest lever. Enter weekly log review time, how often you review access, and minutes spent per user per review. Add training minutes, monthly scan and patch effort, open POA&M items and a yearly block for SSP upkeep, evidence collection and assessor preparation. Enter a loaded rate that includes benefits and overhead. The chart shows how total hours rise with users, since training and access review scale with headcount while log review and patching do not.

The arithmetic

Each recurring activity is converted to hours per year. Log review is weekly hours times 52. Access review is reviews per year times users times minutes per user divided by 60. Training is users times minutes divided by 60. Scanning and patching are monthly hours times 12. POA&M effort is items times hours each. The total divides by 1,800 productive hours to get FTE, a common planning figure after leave and meetings. Cost is hours times the loaded rate, and the per user figure divides cost by the in scope users.

  • Access review hours = reviews x users x minutes / 60
  • Training hours = users x minutes / 60
  • FTE = total hours / 1,800
  • Cost = total hours x loaded rate

Reading the result

A result under about 0.3 FTE means the work can be spread over existing IT and quality staff, but it still needs named owners or it will not happen. Between 0.3 and 1.0 FTE usually justifies a dedicated security or compliance role or a managed service. Above that, look at scope reduction first. Common mistakes include leaving out user training time, assuming logs review themselves, and ignoring that the annual affirmation and any reassessment add effort in specific months, not evenly across the year.

Frequently Asked Questions

Why count training time for all users?

Because it is real labor cost. Ninety minutes for 60 people is 90 hours a year. It does not come from the IT budget, but a complete compliance cost includes it, and it is what you give up if you reduce the number of in scope users.

What is a loaded labor rate?

Wages plus payroll taxes, benefits and overhead, usually 1.25 to 1.4 times base pay for a US employee. Use your finance team's figure if you have one.

Does this include the cost of tools?

No. Licenses for MFA, endpoint protection, logging, encryption and an enclave, plus any managed service or assessment fees, are separate. Use the remediation budget calculator for one time costs.

How do I reduce the hours?

Reduce the in scope users with a CUI enclave, automate evidence collection and access reviews, centralise logging with alert rules, and close POA&M items rather than carrying them. Scope reduction is the biggest lever.

If log review, access reviews and evidence collection eat hours every month, we can automate parts of that from your ERP and identity data, on premises if required.

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Manufacturing hubs

Comparisons

Software