Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  /

  / Employee Offboarding Checklist: 10 Steps to Revoke Access

Employee Offboarding Checklist: 10 Steps to Revoke Access

31% of organizations have caught former employees accessing SaaS applications after their departure (source). Seventy percent of intellectual property theft happens in the ninety days surrounding a resignation announcement. The pattern is so consistent that auditors now treat termination day as one of the highest-risk windows on the security calendar.

This article is a working employee offboarding checklist for IT, security, and HR teams who want to close that window cleanly. It walks through ten steps that revoke access without leaving gaps, then covers edge cases (remote workers, hostile exits, lost devices), the manual-versus-automation tradeoff, and post-offboarding monitoring. Use it as a baseline and adapt it to your environment.

Employee Offboarding Checklist

What Is Employee Offboarding and Why Does Access Revocation Matter?

Employee offboarding is the structured process of separating a person from an organization: removing their access, recovering company property, documenting their exit, and updating records. The access revocation piece is the part where most programs fail quietly.

Accounts get disabled in the identity provider but stay active in a dozen SaaS tools. Badges get collected but VPN tokens stay valid. The person is gone; the keys to the building are not.

Why Employee Offboarding Is a Critical Security Risk

Offboarding fails because access has multiplied faster than the processes designed to manage it. The average enterprise now operates somewhere between 275 and 660 SaaS applications depending on size, with employees touching dozens of them each week. Each application is a separate place that needs to be cleaned up, and each one creates an independent point of failure.

The departing employee is a particularly acute version of this risk because the motivation to walk away with something often peaks during the same window that access is supposed to be revoked.

The Cost of Leaving Access Open After Departure

The financial picture is well documented. The 2025 Ponemon Cost of Insider Risks report puts the average annual cost of insider-related incidents at $17.4 million per organization, with containment taking an average of 81 days. Even when a departed employee never actively misuses their access, the existence of a forgotten account is enough to compromise a SOC 2 audit, trigger a breach notification, or create the credentialed beachhead that an outside attacker eventually exploits.

The cases keep appearing. Cash App was breached in 2022 when a former employee accessed the records of 8 million customers after leaving. In May 2024, FinWise Bank disclosed that a former employee accessed internal systems after departure because access had never been fully revoked. Intel sued a former engineer in 2024 for downloading roughly 18,000 sensitive files in the days before he left.

Ponemon’s 2025 report found that containment costs scale steeply with time. Incidents resolved in under 30 days averaged about $11 million, while those over 90 days averaged $17 million. The biggest variable is not detection capability. It is how fast access actually came down on day one.

Compliance and Legal Implications of Incomplete Offboarding

Access revocation is not a “best practice.” It is an explicit control requirement in nearly every framework against which an organization is likely to be audited. NIST SP 800-53 control PS-4 requires that on termination, organizations disable system access within an organization-defined time period, terminate or revoke any authenticators, and retrieve organizational property.

ISO/IEC 27001 includes equivalent expectations under its Annex A controls for termination of employment. The AICPA Trust Services Criteria for SOC 2 cover this under Common Criteria CC6.2 and CC6.3, and auditors routinely pull a sample of terminated employees and verify timestamps in the identity provider against the HR system.

GDPR adds a separate dimension. If a former employee still has access to the personal data of EU residents, that constitutes unauthorised processing under Article 32, and it is the controller’s responsibility, regardless of intent. HIPAA does the same for protected health information. Whatever the framework, the question an auditor or regulator will ask is the same: how quickly was access revoked, and can you prove it?

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

Who is Responsible for Employee Offboarding

Who Is Responsible for Employee Offboarding?

Offboarding fails most often because no one owns the whole process. Four groups need to be in the loop, and each one has a distinct job.

HR and People Operations

HR is the source of truth for the termination event. Their job is to capture notice of departure, set the official last day, communicate timing to the rest of the business, and serve as the trigger that starts every downstream task. If HR does not record the termination in the HRIS, nothing automated will fire.

IT and Security Teams

IT executes the access teardown. They disable accounts in the identity provider, revoke SSO and OAuth tokens, remove SaaS application access, suspend email, and recover devices. Security teams typically run the audit trail and post-offboarding monitoring, and they are the ones answering when an account flagged six months later turns out to belong to a person who left in March.

Legal and Compliance

Legal handles NDA reminders, IP assignment confirmations, non-disclosure obligations, and any contractual surprises. Compliance owns the documentation: the evidence trail that proves the offboarding actually happened and met the relevant control requirements. For regulated industries this becomes audit evidence; for everyone else it becomes legal cover.

Direct Managers

Managers know things HR does not. They know which shared drives the person owned, which third-party vendors they had standing access to, which client passwords they may have rotated themselves, and which projects need a transition plan. A solid offboarding process forces the manager into the workflow with a checklist of role-specific items, because no central team can guess them.

Employee Offboarding Checklist

Employee Offboarding Checklist: 10 Steps to Revoke Access Without Leaving Gaps

This is the core sequence. The order matters: starting with notification and inventory before disabling accounts means you do not lock the person out of a system you still need them to hand off.

Step 1: Initiate Offboarding Immediately Upon Notice of Departure

The moment notice is given — resignation, termination decision, or end of contract — the offboarding workflow should start. This means logging the termination date in the HRIS, opening a ticket in the IT service management system, and notifying the relevant teams. Delays here are where most gaps begin. If the offboarding ticket is opened on the last day, you are already behind.

Step 2: Identify and Inventory All Access Points

Before touching anything, build a complete inventory of what the person has access to. Pull from the identity provider, the HRIS, the SSO logs, the SaaS management platform, the device management system, and any local app owners’ records. Pay special attention to access granted outside central IT: shared credentials, personal API tokens, third-party tools paid for on a corporate card, and physical keys or codes.

Step 3: Notify IT and Security Teams Without Delay

IT and security need lead time. Sending the notification four hours before the person walks out the door is not enough for anything but the most basic accounts. The window should be measured in days, with hostile or high-risk exits flagged immediately. Security should know whether the departure is amicable or contested, because the response differs significantly between the two.

Step 4: Disable or Deactivate User Accounts Across All Systems

At the agreed cutover time — typically end of business on the last day, or immediately for involuntary terminations — the identity provider account is disabled. This kills SSO-based access to most SaaS tools in one stroke if the environment is well-integrated. For non-SSO applications, each one needs to be disabled individually. Disable, do not delete. Deletion destroys audit evidence and breaks downstream references; deactivation preserves the trail while cutting access.

Step 5: Revoke Privileged, Shared, and Residual Access

Privileged accounts are the highest-risk category and the easiest to miss. Rotate any shared service account credentials that the person knew. Revoke admin access to AWS, GCP, Azure, GitHub, Salesforce, and any other system where they held elevated permissions. Pay particular attention to standing access to production environments, infrastructure-as-code repositories, customer data stores, and finance systems.

Personal API keys and OAuth tokens are an underrated risk. A developer who created a personal access token tied to a production system can still authenticate after their main account is disabled, because the token is its own credential. The same applies to OAuth grants in tools like Google Workspace, Slack, and GitHub: revoke them explicitly.

Important: Disabling the identity provider account does not automatically revoke active session cookies, OAuth refresh tokens, or personal access tokens. A user who is logged in when their account is disabled may stay logged in until their session expires. Force a session reset in every system where the option exists.

Step 6: Remove Access to Email, Collaboration Tools, and Telephony

Email is usually handled by suspending the mailbox and configuring forwarding (or an auto-reply) for a defined period. Collaboration tools — Slack, Teams, Zoom, Notion, Confluence — need their own treatment, especially guest access in external workspaces the person was invited to as part of customer or partner work. Telephony often gets overlooked: voicemail, call forwarding, soft phone clients, and any direct-dial numbers should be reassigned or deactivated.

Step 7: Revoke Physical Access to Facilities and Buildings

Badge access, parking access, keys, alarm codes, and any biometric enrolments need to be deactivated. For shared codes — server room PINs, conference room codes — rotate them if the departing person had standing access. For sites with visitor access controls, remove them from approved visitor lists at partner offices and customer sites where they had ongoing entry.

Step 8: Recover Company Devices and Assets

Laptops, phones, tablets, hardware tokens, smart cards, external drives, monitors, peripherals, and any specialty equipment need to be inventoried and recovered. The recovery plan should be set up before the last day, not improvised on it. For remote employees, prepaid shipping labels and chain-of-custody documentation are essential — this is covered in more detail in the remote offboarding section below.

Step 9: Wipe Devices and Manage Data Retention

Once devices are recovered, they should be wiped to manufacturer specifications before reissue. Mobile device management systems can trigger a remote wipe before the device is ever returned, which is the right move for sensitive roles and for any device that cannot be physically retrieved. Email and personal data on the device should be archived according to the organization’s data retention policy, which is often dictated by legal hold or regulatory requirements.

Step 10: Update Audit Logs, Documentation, and Compliance Records

The final step is closing the loop. Every action above should be logged with a timestamp, the actor who performed it, and the system affected. The completed offboarding record becomes evidence in the next audit and the reference point if an incident investigation later traces back to this person’s access. No documentation, no audit pass. See the checklist section below for a ready-to-use summary of what to capture.

Pro Tip: Identify and Inventory All Access Points

Build this inventory once for each role, not each person. Most engineers have similar access patterns, as do most sales reps. A role-based access map turns a frantic last-minute hunt into a five-minute confirmation that nothing unusual is attached to this individual.

Special Considerations for Remote Employee Offboarding

Remote offboarding strips out the physical handoff that used to anchor the process. There is no exit interview where the laptop changes hands across the table, no last-day badge return at the front desk. Everything has to be coordinated logistically, and each gap in that coordination is a security gap.

Device Return Logistics and Chain of Custody

The standard approach is a prepaid shipping kit sent to the employee’s home address, with tracking and signature confirmation. For higher-risk roles, a courier with chain-of-custody documentation is worth the cost. The device should be tracked from the moment it leaves the employee’s hands until it is logged back into the IT asset system, with timestamps at each handoff.

If the device contains sensitive data, a remote wipe should be triggered the moment the access cutover happens, not when the device is received. The wipe should be verifiable: an MDM audit log showing the device was cleared, ideally with a confirmation pulled from the device itself before it is reimaged or destroyed.

Revoking Access for Remote Workers Across Time Zones

A 5 PM Friday cutover in San Francisco is a Saturday morning event for a team member in Singapore. When access is revoked matters because it determines what windows of misuse are possible. The right answer is to set the cutover to the employee’s local end-of-business and to staff the offboarding window with someone who can monitor it in real time — not to default to headquarters time and hope for the best.

Handling Hostile or Unresponsive Departures Remotely

In a hostile remote departure, the device may never come back. The plan has to assume that outcome. Trigger the remote wipe, revoke all access immediately, rotate any shared credentials the person knew, and document the device as unrecovered. Where the device contained regulated data, this may trigger a breach notification obligation depending on jurisdiction — legal should be looped in before that determination is made.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

How to Handle Edge Cases and High-Risk Offboarding Scenarios

Most offboarding processes are designed around the friendly, two-weeks-notice scenario. The dangerous scenarios are the ones that do not fit that template.

Sudden Resignations or No-Notice Departures

When someone resigns and walks out the same day, the offboarding workflow has to compress from days into minutes. The cutover happens immediately. Some organizations build a separate “rapid offboarding” runbook for this case, with a smaller set of steps that can be executed in fifteen minutes by one IT staff member: identity provider disable, session revocation, email suspension, and badge deactivation. The rest follows on a normal timeline.

Lost, Stolen, or Unreturned Devices

Treat any device not recovered within a defined window — typically 7 to 14 days for amicable departures, 24 hours for hostile ones — as compromised. Trigger the wipe if it is still possible, flag the device for blocklisting on the corporate network, and escalate to legal if there are reasons to believe the device is being used. Insurance and asset write-offs follow once the device is officially declared lost.

Cross-Border and International Offboarding Challenges

International offboarding adds layers that domestic processes ignore. Local employment law in the EU, UK, and parts of Asia-Pacific limits what can be inspected on a device before return. Data residency rules may prevent moving certain records out of the country during the offboarding investigation. Tax and immigration consequences can apply if the person held a work visa tied to the role.

The practical implication is that offboarding processes for international employees should be reviewed by local counsel before they are needed, not improvised in the moment.

A process that works cleanly in California may be unlawful in Germany. The GDPR Article 32 obligations alone are enough to require a tailored approach for any employee handling EU personal data.

 

Manual vs. Automated Offboarding: Why Automation Reduces Access Gaps

The single biggest predictor of whether offboarding closes cleanly is whether the workflow is automated. Manual processes work fine in a 20-person company. They start failing at 200 and break completely at 2,000.

Limitations of Manual Offboarding Processes

Manual offboarding relies on a chain of human handoffs: HR emails IT, IT emails app owners, and app owners click through their dashboards. Every link in the chain is a place where something gets forgotten. Smaller apps with no direct integration tend to be the ones that get missed, which means the long tail of SaaS tools — often the majority by count — is where orphaned accounts accumulate.

How Offboarding Software Streamlines Access Revocation

Automated offboarding flows trigger from a single event — typically the termination status change in the HRIS — and fan out to every connected system. Identity providers like Okta and Microsoft Entra ID support lifecycle workflows that disable accounts, revoke sessions, and trigger downstream deprovisioning across hundreds of SaaS applications. SaaS management platforms can extend coverage into apps that do not natively integrate with the identity provider.

Integrating IT and HR Systems for Seamless Coordination

The integration that matters most is between the HRIS and the identity provider. When a termination is recorded in Workday, BambooHR, or whatever HR system the organization uses, the identity provider should pick it up automatically and start the deprovisioning sequence. Without that integration, every other improvement is bottlenecked on someone remembering to send an email, which is exactly the kind of single point of human failure that creates the incidents described at the top of this article.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

Security Monitoring After Offboarding Is Complete

Offboarding is not finished when the last checkbox is ticked on day one. The follow-up monitoring is what catches the gaps the original process missed.

Running Post-Offboarding Access Certifications

Within 30 to 60 days of departure, run an access certification against every system the person was known to use. The certification looks for any account, token, or grant that was missed in the initial cleanup. For sensitive roles, repeat this at 90 days. Each pass tends to find something, especially in tools that are not centrally managed.

Monitoring for Residual or Orphaned Accounts

Orphaned accounts are the long-term hazard. Industry research has found that around a quarter of accounts in audited environments belong to stale enabled users who have not logged in for over 90 days, and in some organizations, the figure runs much higher. Periodic sweeps of the identity provider and connected SaaS apps to identify and disable stale accounts close this gap on an ongoing basis, even when individual offboardings miss something.

Most orphaned accounts are not the freshly departed employee. They are the contractor whose engagement ended two years ago, the intern who left after the summer, or the person who transferred teams and never had their old access removed. A quarterly access review focused on time-since-last-login finds more orphaned accounts than any individual offboarding ever will.

 

Employee Offboarding Checklist Template

A practical checklist needs to fit on a single screen and cover every category without burying the user in detail. The four groupings below map to the responsible teams.

HR and Administrative Tasks

Record termination in the HRIS with the official last day. Notify IT, security, the direct manager, finance, and legal of the departure. Schedule and conduct the exit interview. Confirm final payroll, benefits transition (COBRA or local equivalent), and any outstanding expense reimbursements. Send NDA and IP assignment reminders.

IT and Security Tasks: Disable All Access

Disable the identity provider account at the agreed cutover time. Revoke active sessions, OAuth tokens, and personal access tokens. De-provision SaaS application access through SSO and through direct connectors. Suspend email and configure forwarding or auto-reply. Rotate shared credentials and service account passwords that the person knew. Revoke physical access badges, building keys, and parking access. Disable VPN, MFA tokens, and remote access tools.

Hardware and Asset Recovery

Inventory all assigned devices — laptop, phone, tablet, peripherals, hardware tokens, smart cards. Coordinate return logistics (in-person handoff for office workers, prepaid shipping kits for remote employees). Trigger remote wipe on devices before or upon receipt. Confirm device condition and update the asset management system.

Documentation and Compliance Records

Log every action with timestamp, actor, and system. Retain offboarding records according to the data retention policy. File completed offboarding evidence with the audit trail used for SOC 2, ISO 27001, or other applicable framework. Schedule the 30-day and 90-day post-offboarding access certifications.

 

A Final Word on Closing the Gap

Offboarding is one of the few security processes where the cost of getting it wrong is concrete, and the cost of getting it right is mostly process discipline. The frameworks are clear, the tooling is mature, and the failure modes are well understood.

What separates a clean program from a leaky one is usually not capability. It is whether the workflow is owned end-to-end and triggered automatically by the right system of record.

The ten steps above are the core sequence. Adapt them to the size and risk profile of the organization, and revisit them whenever a new system enters the environment.

Frequently Asked Questions About Employee Offboarding and Access Revocation

What access points should be revoked first during employee offboarding?

The identity provider account is the highest-priority target because it is the gatekeeper for SSO-based access to most modern SaaS applications. Disabling it cuts the broadest set of access in a single action. From there, the priority order is privileged accounts (admin access to cloud platforms, code repositories, finance systems), shared credentials the person knew, then email and collaboration tools, then non-SSO applications, then physical access. Sessions and OAuth tokens should be explicitly revoked alongside the identity provider step, because they can persist after the account itself is disabled.

Most security frameworks expect access to be revoked the same day, typically within 24 hours of the official termination. SOC 2 auditors commonly sample termination events and look for revocation within a one-business-day window. NIST SP 800-53 leaves the exact period to the organization but expects it to be defined and met consistently. For hostile or high-risk terminations, the target is immediate revocation: minutes, not hours.

In the best case, nothing happens and the account becomes an orphaned record that surfaces during the next access review. In the worst case, the former employee uses the access to take data, sabotage systems, or sell credentials. The FinWise Bank case in 2024 and the Cash App breach in 2022 are both examples of former employees retaining access and using it. Beyond the direct risk, an unrevoked account is an audit failure for SOC 2, ISO 27001, and most other frameworks, and a likely violation of GDPR or HIPAA if the access exposes personal or health data.

Treat the device as the first risk to manage: trigger a remote wipe at the cutover time and ship a prepaid return kit with tracking and signature confirmation. Revoke all access on the schedule the employee’s local time zone implies, not headquarters time. Conduct the exit interview by video and document it the same way an in-person interview would be documented. For hostile remote departures, assume the device may not come back and plan accordingly.

The minimum documentation for audit purposes is the official termination notice with date and time, evidence of access revocation in each affected system (timestamps from the identity provider and any non-SSO applications), confirmation of device return or remote wipe, completed exit interview record where applicable, and any final acknowledgements of NDA, IP assignment, or post-employment obligations. For regulated environments, retention periods are typically set by the framework or local law. The Trust Services Criteria for SOC 2 and ISO/IEC 27001 both specify what auditors expect to see as evidence.

Disabling an account suspends access while preserving the account record, including its history and permissions. Deletion removes the account entirely. The standard practice is to disable, not delete, because deletion destroys audit evidence and can break references in other systems — file ownership, ticket assignments, log records. Accounts are typically disabled at termination and deleted only after a retention period defined by policy, often 6 to 12 months.

The mechanics are similar but the timing and ownership differ. Contractor access is typically tied to a defined engagement end date rather than a termination event, which means the trigger is the contract end (or extension) rather than an HR status change. Contractors are also more likely to use their own devices, which limits the device recovery step and shifts the focus to access revocation and data return obligations defined in the contract. Contractors are more likely to have access provisioned outside the central identity provider, which makes the inventory step in the checklist particularly important.

Axipro Author

Picture of Pedro Dias

Pedro Dias

Pedro has been writing online for over 10 years. With experience in all things programming, cyber security, and compliance, he is our editor-in-chief at Axipro.

Blog Highlights

Explore More Articles

CMMC requirements started appearing in Department of Defense contracts on November 10, 2025, when the final DFARS rule took effect. By November 10, 2028, the clause at DFARS 252.204-7021 must appear in every solicitation and contract where contractor systems process, store, or transmit Controlled Unclassified Information (CUI). For most of the Defense Industrial Base (DIB), the math is blunt: pass a CMMC assessment or lose eligibility for DoD work. A CMMC readiness assessment is how you find out whether you’d pass before the stakes are real. It’s a structured review of your environment, documentation, and evidence against the requirements of the Cybersecurity Maturity Model Certification, done before you sit for a self-assessment or a Certified Third-Party Assessment Organization (C3PAO) audit. A good one tells you exactly where you stand and what to fix first. This guide covers what a readiness assessment includes, how the process works at each CMMC level, what it costs, how long it takes, and how to pick someone to run one. What Is a CMMC Readiness Assessment? A CMMC readiness assessment is a pre-certification evaluation that measures your organization against the specific requirements of your target CMMC level. It examines your scope, implemented controls, System Security Plan (SSP), Plan of Action and Milestones (POA&M), and the evidence supporting them, then produces a gap analysis and a remediation roadmap. The purpose is simple: surface every deficiency while it’s still cheap to fix. An assessor who finds a scoping error during a readiness review costs you a few weeks of rework. A C3PAO who finds the same error during a certification assessment can cost you the assessment fee, months of delay, and in some cases contract eligibility. How It Differs From an Official C3PAO Audit An official CMMC Level 2 certification assessment is conducted by a C3PAO accredited by the Cyber AB, the official accreditation body for the CMMC ecosystem. The C3PAO’s findings are binding. Results go into the DoD’s assessment systems, and a passing result produces a CMMC status that contracting officers verify before award. A readiness assessment carries no official weight. Nothing gets filed or certified, and a poor result costs you nothing beyond the work needed to fix it. That’s the whole point. It’s the only stage in the entire process where failure is free. There’s also a conflict-of-interest rule worth knowing. A C3PAO cannot provide consulting and remediation services to an organization and then certify that same organization. If a C3PAO helps you prepare, a different C3PAO has to assess you. How It Differs From a Mock Assessment A mock assessment is a dress rehearsal. It simulates the certification assessment itself: assessors interview control owners, request evidence on the spot, and score findings the way a C3PAO would. A readiness assessment is broader and comes earlier, and its job is discovering and closing gaps rather than rehearsing the exam. Most organizations run a readiness assessment first, remediate, then run a mock assessment a few weeks before the real one to see whether staff and evidence hold up under live questioning. How It Differs From a Self-Assessment A self-assessment is a formal CMMC mechanism rather than a preparation exercise. CMMC Level 1 and a subset of Level 2 contracts let organizations self-assess, post the results to the Supplier Performance Risk System (SPRS), and have a senior official affirm compliance annually. That affirmation is a representation to the government, and false or careless affirmations carry False Claims Act exposure. A readiness assessment is the check you run before making that representation, so the number you affirm reflects reality. Why a CMMC Readiness Assessment Matters Avoiding Failed Certification Attempts CMMC Level 2 covers all 110 security controls of NIST SP 800-171, evaluated against 320 assessment objectives. Every objective has to be met for a control to score, and there’s no partial credit. Organizations that skip readiness work routinely walk into certification believing they’re compliant because controls are “mostly” implemented. Mostly implemented scores the same as not implemented. Protecting DoD Contract Eligibility Under the phased rollout that began in November 2025, CMMC status is a condition of award. Prime contractors also have to flow the requirement down to subcontractors that handle Federal Contract Information (FCI) or CUI, and they’ve been pushing their supply chains hard. So a missed certification hurts twice: you lose the immediate contract, and you risk dropping out of a prime’s approved supplier pool during the exact window when those pools are being rebuilt around CMMC status. Reducing Remediation Costs and Delays Gaps found early get fixed on your schedule with your choice of solution. Gaps found during certification get fixed under deadline pressure, often with whatever expensive tooling can be deployed fastest. There’s a conditional CMMC status for organizations that pass with a limited POA&M, but closeout has to happen within 180 days, and only certain lower-weighted controls are POA&M-eligible in the first place. Readiness work keeps you out of that corner. Worth Knowing: The DoD Assessment Methodology The DoD Assessment Methodology weights each NIST SP 800-171 control at 1, 3, or 5 points, deducted from a starting score of 110. The floor is -203. To achieve even a conditional Level 2 status, you need a minimum score of 88. A handful of unmet 5-point controls, such as FIPS-validated encryption or multifactor authentication, can put certification out of reach on their own, so a readiness assessment should always show the point weight attached to every gap. When to Conduct a CMMC Readiness Assessment Before your first self-assessment. If a contract requires a Level 1 or Level 2 self-assessment, run readiness work before you post a score to SPRS. The score you affirm is a legal representation, and it’s far easier to fix the environment than to explain a misstated score later. When contract requirements are approaching. If CMMC language has shown up in a solicitation you plan to bid, or your prime has set a certification deadline, count backward. Remediation after a readiness assessment typically takes six to twelve months for organizations starting

CMMC certification costs between $4,000 and $30,000 at Level 1, $30,000 to $300,000 or more at Level 2, and $100,000 to well over $1 million at Level 3. Most contractors expect the audit fee to be the big number. It isn’t. The formal assessment typically accounts for only 25% to 40% of total spend, with preparation, remediation, and technology upgrades consuming the rest. The stakes changed in late 2025. The final 48 CFR acquisition rule took effect on November 10, 2025, which means CMMC requirements now appear directly in Department of Defense (DoD) solicitations and contracts. Starting in November 2026, Phase 2 of the rollout gives contracting officers the authority to require third-party certification for Level 2 work. If you handle Controlled Unclassified Information (CUI), certification is no longer optional, and the cost question becomes a budgeting exercise rather than a hypothetical. This guide breaks down every major cost category, what moves your number up or down, and how to keep the total under control. What Is CMMC Certification and Why Does Cost Vary? The Cybersecurity Maturity Model Certification (CMMC) is the DoD’s framework for verifying that companies in the Defense Industrial Base (DIB) actually protect the sensitive information they handle. The program, codified in 32 CFR Part 170, builds on the security requirements of NIST SP 800-171 and, at the top tier, selected controls from NIST SP 800-172. Costs vary so widely because you can’t buy CMMC off a shelf. Your environment has to reach a certain state and then stay there. A 15-person machine shop with one well-scoped CUI enclave faces a fundamentally different project than a 500-person prime contractor with CUI flowing through a dozen systems. Your starting security posture, the scope of your assessment boundary, and whether you build internally or hire help all move the total by six figures in either direction. Average CMMC Certification Cost at a Glance The DoD’s own published estimates are instructive. A triennial Level 2 certification assessment, including affirmations, is projected at roughly $105,000 for small entities and $118,000 for larger ones. Those figures cover only assessment and affirmation activities, though. The DoD excludes implementation costs from its estimates on the grounds that NIST SP 800-171 compliance has been contractually required under DFARS 252.204-7012 since 2017. Your real budget has to cover both. CMMC Certification Cost by Level CMMC Level 1 (Foundational) Cost: $5,000 – $30,000 Level 1 covers Federal Contract Information (FCI) and requires 15 basic safeguarding practices drawn from FAR 52.204-21. Because Level 1 permits an annual self-assessment with no third-party auditor, the costs are internal labor, basic tooling, and documentation. Small contractors with reasonable IT hygiene often land near the bottom of the range. The DoD estimates annual Level 1 assessment and affirmation activity at around $6,000 for a small entity, with the remainder of the range driven by any remediation needed to attest honestly. CMMC Level 2 (Advanced) Cost: $50,000 – $300,000+ Level 2 is where most of the DIB lands and where budgets get serious. It requires full implementation of all 110 security requirements in NIST SP 800-171, assessed across 320 individual objectives. For most contracts, a C3PAO (Certified Third-Party Assessor Organization) accredited by the Cyber AB has to conduct the assessment every three years. Market data puts C3PAO assessment fees at $30,000 to $100,000 depending on scope, site count, and complexity. Preparation dwarfs that figure for most organizations. Companies starting from a low maturity baseline routinely spend three to four times the assessment fee on readiness work before an auditor ever shows up. CMMC Level 3 (Expert) Cost: $300,000 – $1,000,000+ Level 3 adds 24 enhanced requirements from NIST SP 800-172 on top of a completed Level 2 certification, and the assessment is conducted by the government’s DIBCAC rather than a commercial C3PAO. DIBCAC charges no assessment fee, but don’t mistake free for cheap. The DoD estimated roughly $41,000 in additional implementation cost for the 800-172 controls alone, and total triennial assessment-related costs in the $146,000 to $159,000 range. Real-world totals run far higher once you account for the advanced tooling, threat hunting capability, and organizational changes Level 3 demands. Only contractors supporting the most sensitive programs need this tier. Worth Knowing: You can’t skip to Level 3. You can’t skip to Level 3. A final Level 2 certification with all POA&M items closed is a prerequisite for the same assessment scope, so Level 3 budgets always include a full Level 2 project first. CMMC Certification Cost Breakdown by Expense Category Gap Assessment and Readiness Planning Costs A gap assessment maps your current environment against NIST SP 800-171 and typically costs $1,500 to $20,000 depending on depth and scope. This is the most valuable dollar you’ll spend in the entire project, because everything downstream is priced off what it finds. Documentation and System Security Plan (SSP) Costs The System Security Plan (SSP) is the cornerstone document of any assessment, mapping every control to your specific implementation. Professionally developed SSPs and supporting policies run $12,000 to $60,000. A weak SSP is one of the most common reasons assessments stall or fail, so this is a poor place to economize. Remediation and Security Control Implementation Costs Closing the gaps is usually the largest line item: $20,000 to $150,000 or more. Multi-factor authentication, logging and SIEM deployment, encryption, access control restructuring, and incident response capability all live here. Organizations with mature security postures spend far less than those starting from scratch. Technology and Infrastructure Upgrade Costs Many contractors move CUI into a dedicated enclave rather than securing their entire network. Enclave platforms typically cost $300 to $400 per user per month. Others upgrade endpoint protection, replace unsupported systems, or migrate to government-grade cloud environments, each with its own licensing and migration costs. C3PAO Assessment and Audit Fees The formal Level 2 assessment runs $30,000 to $100,000, driven by assessor-days, number of sites, and evidence quality. Well-organized evidence directly reduces assessor time and therefore your invoice. Consulting and Advisory Fees Specialist consultants, including Registered Practitioners (RPs) and

SOC 2 and ISO 27001 Engagement

After a SOC 2 and ISO 27001 engagement, there are two documents out of the whole pile that actually close deals: the SOC 2 attestation report and the ISO 27001 certificate. Everything else your engagement produces exists to create those two, support them, or keep them alive for another year. Companies routinely ask their auditor for a SOC 2 certificate, which doesn’t exist. They send a prospect their full ISMS documentation when a one-page certificate would have done. They pay for six months of readiness work and then can’t say what they’re holding at the end of it. So here’s the full list. What a SOC 2 engagement produces, what an ISO 27001 engagement produces, what a combined program produces, and who gets to see each one. Understanding SOC 2 and ISO 27001 Engagement Outputs The Core Difference: Report vs. Certificate SOC 2 is an attestation. A licensed CPA firm examines your controls against the Trust Services Criteria under standards set by the AICPA, then writes up what it found and signs an opinion. No certificate. No logo from the AICPA. No pass or fail stamp. What you get is the report, and it usually runs 60 to 120 pages. ISO 27001 is a certification. An accredited certification body audits your Information Security Management System (ISMS) against ISO/IEC 27001:2022, and if you conform, it issues a certificate of registration. The certificate itself is a page or two. All the detail lives behind it, in your ISMS documentation and the audit reports the certification body writes as it goes. SOC 2 Engagement Deliverables The SOC 2 Attestation Report The report is the engagement. The AICPA’s illustrative SOC 2 report lays out the standard structure: auditor’s report, management’s assertion, system description, the Trust Services Criteria in scope, and the controls tested with their results. A Type I covers control design at one point in time. A Type II covers whether those controls actually operated over a period, usually three to twelve months, and most enterprise buyers now won’t accept anything else. Independent Auditor’s Opinion Letter First section of the report, and the first thing anyone experienced turns to. It gives the scope, the examination period, and the auditor’s conclusion. An unqualified opinion means the description held up and the controls worked. A qualified opinion means the auditor found something material, and every serious reviewer will want to talk about it. Management Assertion Your leadership signs a written statement stating that the system description is accurate and that the controls were properly designed and are operating. It reads like a formality, and it isn’t. The auditor’s entire examination runs against what management asserts here, so overstating anything creates real exposure. System Description Usually the longest part of the report, and you write it, not the auditor. It covers the services in scope, your infrastructure, software, people, processes, how data moves, which subservice organizations you depend on, and the complementary user entity controls your customers have to run on their side for your controls to hold up. Trust Services Criteria Applied Security (the Common Criteria) is in every SOC 2. Availability, Processing Integrity, Confidentiality, and Privacy are optional, and the report names exactly which ones you picked. Whatever you decide during scoping ends up printed in a document your customers read for the next several years. Description of Tests of Controls and Results (Type II) The matrix: every control, what the auditor did to test it, and what came back, including exceptions. Reviewers spend most of their time here, because the exceptions tell them things the opinion letter won’t. Bridge Letter / Gap Letter Your report covers a fixed window, so one ending December 31 leaves a hole for a customer doing diligence in June. A bridge letter from your management, not the auditor, confirms that nothing material changed in the control environment between the report’s end date and today. You’ll write these often enough to keep a template. Management Letter and Observations Plenty of auditors also send an internal-only letter covering observations, minor exceptions, and suggestions that never reached the threshold of a qualified opinion. It’s the closest thing to free consulting you’ll get before next year’s audit starts. Insider Note: Ask early whether your auditor issues a management letter, and whether exceptions land in the report body or only in that letter. Firms handle this differently, and the answer decides what your customers see versus what stays behind your firewall. It rarely comes up in the proposal, but it changes how the finished report reads to a buyer. ISO 27001 Engagement Deliverables ISO 27001 Certificate of Registration The document everyone asks for. It names the certified legal entity, states the ISMS scope, identifies the certification body, carries an accreditation mark from a body recognized under the International Accreditation Forum such as UKAS or ANAB, and shows the validity dates. It’s good for three years as long as you pass annual surveillance audits. Read the scope statement carefully, on your own certificate as much as anyone else’s. A certificate covering one office or one product line says nothing about the rest of the business. Statement of Applicability (SoA) After the certificate, this is the document buyers request most. The Statement of Applicability runs through all 93 Annex A controls in ISO/IEC 27001:2022, says which apply to you, justifies the ones you excluded, and records where each stands. Auditors use it as the map of your control environment, and larger customers increasingly want to see it or a summary of it during diligence. Risk Assessment and Risk Treatment Plan Your methodology, the register it produced, and the Risk Treatment Plan showing what you decided to do about each significant risk: mitigate it with a control, transfer it, avoid it, or accept it. ISO 27001 is built around risk, so these documents are what justify every control decision recorded in the SoA. Information Security Management System (ISMS) Documentation The policy and procedure set, plus the operational records that prove any of it happens. Information