IT security analysts reviewing systems and code on monitors during a cybersecurity gap assessment

A customer’s security questionnaire lands with 180 questions and a two-week deadline. Question 14 asks whether you enforce multifactor authentication on every remote access path. Your policy says yes. Then someone remembers the old VPN appliance the warehouse team still uses, the one that was set up before the MFA rollout.

A cybersecurity gap assessment compares the security controls you actually have running against the requirements of a framework like SOC 2, CMMC, FedRAMP, GDPR or the NIST Cybersecurity Framework, and gives you a prioritized list of what’s missing. Run a full one at least once a year, and a smaller one any time your environment changes in a way an auditor would notice.

What is a cybersecurity gap assessment?

A cybersecurity gap assessment is a structured review of your policies, technical controls and evidence against a specific framework. For each requirement it answers three questions: is the control in place, is it working, and can you prove it. The output is a remediation plan with owners and dates, not a pass or fail grade.

People often confuse it with two other things. Here’s how they differ:

Gap assessmentFormal audit or certificationPenetration test
Who runs itYour team or an outside advisorAn independent assessor (CPA firm for SOC, C3PAO for CMMC, 3PAO for FedRAMP)Security testers
Question it answersWhere do we fall short of the framework?Does an independent party agree we meet it?Can an attacker actually get in?
What you getPrioritized fix listReport, attestation or certificateExploited findings
Pass or failNoYesNo

A gap assessment is what you do before the audit so the audit has no surprises. It doesn’t give you a SOC 2 report, a CMMC certificate or a FedRAMP authorization.

Why passing last year’s audit doesn’t mean you’re compliant today

Most compliance gaps we find aren’t missing policies. They’re controls that drifted after the audit was signed off.

Take the MFA example. A company turns on multifactor authentication to satisfy a requirement. Six months later it deploys a new application that lets some users sign in without it. The written policy still says MFA is required. The technical control no longer backs that up, and the next questionnaire answer is wrong.

Drift usually comes from ordinary changes:

  • A new SaaS tool with its own login that never got connected to single sign-on
  • A Conditional Access exclusion in Microsoft Entra ID added “temporarily” for an executive’s travel
  • A departed employee whose account is still active in a vendor portal HR doesn’t know about
  • A backup job that started failing quietly after a server migration

Some frameworks write this expectation in directly. GDPR Article 32 requires “a process for regularly testing, assessing and evaluating” the effectiveness of your security measures. FedRAMP requires ongoing continuous monitoring, including monthly vulnerability scanning and an annual assessment by an independent assessor.

What does a cybersecurity gap assessment cover?

Scope depends on the framework, but nearly every compliance gap assessment checks the same eight areas. The last column is where assessments usually stall: the control exists, but nobody can produce the evidence.

AreaWhat the assessor checksEvidence to have ready
Policies and proceduresPolicies exist, are approved and reviewedSigned approval dates, annual review log
Identity and accessMFA coverage, least privilege, prompt offboardingMFA coverage report, quarterly access reviews, offboarding tickets matched to HR terminations
Vulnerability and patchingRegular scanning, risk-based fixes tracked to closureScan reports, patch timelines vs. your stated policy, closed tickets
Data protectionSensitive data identified and encryptedData inventory, device encryption status (e.g. BitLocker via Intune)
Monitoring and incident responseEvents logged and reviewed, roles definedLog retention settings, incident response plan, last tabletop exercise date
Backup and recoveryBackups protected and restorable within your targetsMost recent restore test vs. recovery time objective (how long you can be down)
Third-party riskVendors vetted, contracts understoodVendor inventory, collected SOC 2 reports, security clauses
TrainingStaff trained on scheduleCompletion records

How a gap assessment maps to SOC 2, CMMC, FedRAMP and GDPR

The controls overlap heavily across frameworks. The scope, the assessor and the stakes don’t.

SOC 2 readiness assessment (and SOC 1)

SOC 2 examines controls against the AICPA Trust Services Criteria: security, plus availability, processing integrity, confidentiality and privacy if they’re in scope. SOC 1 covers controls that affect your customers’ financial reporting. A Type 1 report looks at control design on a single date. A Type 2 report tests whether controls operated over a period, commonly 3 to 12 months.

The mistake we see: starting the Type 2 observation window before controls are running consistently. Every missed access review during that window becomes an exception printed in the report your customers read. Run the readiness assessment first, fix what it finds, then start the clock.

CMMC gap analysis

CMMC applies to Department of Defense contractors and subcontractors. Level 2, which covers Controlled Unclassified Information (CUI), is built on the 110 security requirements in NIST SP 800-171. The rollout began November 10, 2025, and Phase 2, which began November 10, 2026, makes third-party Level 2 assessments by a certified C3PAO a contract condition for many contracts.

A CMMC gap analysis starts with scoping: which systems, people and facilities touch CUI. Getting scope wrong is expensive in both directions. Too wide and you’re paying to harden systems that never see CUI. Too narrow and the assessor finds CUI in a file share you left out. Check the DoD CMMC program page for current requirements.

FedRAMP

FedRAMP applies to cloud service providers selling to federal agencies. A gap assessment maps your environment to the Low, Moderate or High baseline and builds the Plan of Action and Milestones (POA&M), the tracked list of open deficiencies FedRAMP expects you to maintain. Reassess whenever your cloud architecture changes, because new services can pull new components into your authorization boundary.

GDPR

GDPR applies to organizations that process personal data of people in the EU, including U.S. businesses that sell to or monitor people there. There’s no GDPR certificate to earn. The security piece of a gap assessment covers access restrictions, encryption, breach procedures and vendor contracts. Lawful basis, retention and individual rights are legal questions, so bring in privacy counsel for those.

NIST CSF as the common backbone

The NIST Cybersecurity Framework 2.0 isn’t a compliance requirement for most private companies, but it’s a practical way to organize a multi-framework security framework assessment. One quarterly access review, documented once, can serve as evidence for SOC 2 logical access criteria (CC6), the NIST SP 800-171 access control family and GDPR Article 32 at the same time.

How often should you do a gap assessment?

Do a full assessment annually, review high-risk controls quarterly, and reassess after any major change. Your framework’s own schedule always wins over a general rule.

CadenceWhat to reviewTypical trigger
AnnuallyAll applicable frameworks, controls, policies and evidenceAhead of your audit or renewal cycle
QuarterlyPrivileged access, MFA exceptions, open remediation items, vulnerability trendsCalendar
After a changeThe controls the change touchedAcquisition, cloud migration, new core application, security incident
Per frameworkWhatever the standard requiresFedRAMP continuous monitoring, contract terms

Quarterly reviews aren’t for everyone. A 60-person professional services firm with no regulated data and no customer questionnaires can get by with an annual assessment plus event-driven reviews. A SaaS company mid-way through a SOC 2 Type 2 window can’t.

A quarterly internal review also doesn’t replace a required independent assessment. It keeps you ready between them.

Which gaps should you fix first?

Fix gaps that are live security exposures first, then the ones blocking a deadline, then documentation. Most companies do it backwards because rewriting policies is easy and feels like progress, while the internet-facing server with a critical vulnerability waits.

  1. Gaps attackers can use today. Missing MFA on remote access, unpatched internet-facing systems, backups that have never been restore-tested.
  2. Gaps blocking revenue or an audit date. The control a key customer’s questionnaire asks about, or a CMMC requirement tied to a contract award.
  3. Evidence gaps. Controls that work but leave no record. Often a ticketing or logging fix, not a new tool.
  4. Maturity improvements. Things that make the program better but aren’t failing anything now.

Every item on the list gets an owner, a target date and a clear definition of “closed,” including the evidence that proves it. Without those three, the remediation plan from this year’s assessment becomes the findings list in next year’s.

Should you run a gap assessment in-house or hire someone?

In-house works when someone on your team knows the framework well and has real time set aside, not time borrowed from the help desk queue. It’s also cheaper for a re-check of a framework you’ve already been through.

An outside assessor makes more sense for a first assessment, a framework your team hasn’t worked with, or any assessment where independence matters to the customer or auditor reading the results. For CMMC, keep in mind that the C3PAO that certifies you can’t also be the firm that consulted on your readiness.

When we run framework assessments at Dataprise, our team draws on 750+ technical certifications across the frameworks clients are measured against. The goal is a remediation plan your team can execute, whether or not we’re the ones doing the work.

Frequently asked questions

How long does a cybersecurity gap assessment take?

It depends on how many frameworks are in scope, how many systems hold regulated data and how quickly your team can produce evidence. Evidence collection is usually the slowest part.

How much does a cybersecurity gap assessment cost?

Cost is driven by the number of frameworks, the size of the environment in scope and whether you need help with remediation afterward. A narrowly scoped CMMC or SOC 2 readiness assessment costs less than a multi-framework review across several business units.

Is a gap assessment the same as a risk assessment?

No. A risk assessment looks at threats to your business and how likely and damaging they are. A gap assessment measures you against a framework’s requirements. Many frameworks, including SOC 2 and NIST SP 800-171, require a documented risk assessment as one of their controls, so a gap assessment will check that you have one.

Can one assessment cover multiple frameworks?

Yes, and it should if more than one applies. Mapping controls to a common set means one piece of evidence can satisfy several frameworks. You still need framework-specific work, like CMMC scoping or GDPR’s lawful basis review, that no shared control covers.

Start with one number this week

Pull the MFA registration report from Microsoft Entra ID (or your identity provider) and compare its user count with your current HR roster. It takes about 30 minutes, and it tells you whether the answer you give most often on security questionnaires is still true. If the numbers don’t match, or you’d like a full picture against SOC 2, CMMC, FedRAMP or GDPR, talk to an expert about a cybersecurity gap assessment.

Dataprise

Dataprise is a national managed service provider that believes that technology should enable our clients to be the absolute best at what they do.

Let’s talk IT.

Request a consultation. Tell us where your offices are and one of our engineers will be in touch within one business day — no sales script, no obligation, just a working conversation about what you’re trying to do.

cyber insurance

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Your Name*