Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  /

  / JumpCloud, Okta, or Entra for CMMC Level 2

JumpCloud, Okta, or Entra for CMMC Level 2

Only one of these three vendors sells a FedRAMP-authorized identity platform you can buy today as a defense contractor, one sells two of them, and one sells none.

Whether that matters for your CMMC Level 2 assessment depends entirely on whether your identity provider stores, processes, or transmits Controlled Unclassified Information (CUI), or provides security protections for the systems that do.

That second condition is where most contractors get the analysis wrong. The IdP question is arguably the most argued-about scoping decision in CMMC 2.0 Level 2 preparation, because an identity provider almost never holds CUI directly, yet it controls access to everything that does. This article works through the regulatory requirement, the actual FedRAMP status of JumpCloud, Okta, and Microsoft Entra ID, and how to choose based on your CUI architecture rather than vendor marketing.

Understanding the CMMC Level 2 + FedRAMP Requirement

What CMMC Level 2 Requires for Cloud Services Handling CUI

CMMC 2.0 Level 2 requires contractors to implement the 110 security requirements of NIST SP 800-171 Rev. 2 and, for most contracts, pass a third-party assessment by a Certified Third-Party Assessor Organization (C3PAO). The 48 CFR acquisition rule took effect on November 10, 2025, which means CMMC clauses now appear in new Department of Defense (DoD) solicitations, with third-party assessment requirements expanding through the phased rollout in 2026 and beyond.

The cloud piece comes from the CMMC program rule at 32 CFR Part 170. If an Organization Seeking Certification uses a Cloud Service Provider (CSP) to process, store, or transmit CUI, that cloud service offering must be either FedRAMP Authorized at the Moderate baseline or higher or must meet security requirements equivalent to the FedRAMP Moderate baseline. Your C3PAO verifies this during the assessment. If your in-scope CSP fails the test, you fail the assessment.

The DFARS 252.204-7012 “FedRAMP Moderate or Equivalent” Clause

The requirement predates CMMC. DFARS 252.204-7012 has required since 2016 that any external CSP used to store, process, or transmit covered defense information meet security requirements “equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline.”

For years, “equivalent” was undefined, and contractors interpreted it loosely. The DoD CIO closed that door with its December 2023 equivalency memo. To be FedRAMP Moderate Equivalent, a CSP must now demonstrate 100% compliance with the FedRAMP Moderate baseline, validated by a FedRAMP-recognized Third-Party Assessment Organization (3PAO), and hand over a full Body of Evidence to the contractor. No open Plans of Action and Milestones (POA&Ms) against the baseline are permitted. In some ways, it’s stricter than authorization itself, since authorized CSPs are allowed to carry POA&Ms.

Important: A vendor telling you they are “NIST 800-171 compliant” or “aligned to FedRAMP controls” does not satisfy DFARS 7012 or the CMMC rule. Either the offering appears on the FedRAMP Marketplace at Moderate or higher, or the vendor gives you a 3PAO-attested Body of Evidence demonstrating full equivalency. Anything else is a gap your C3PAO will find.

When an Identity Provider Falls Under This Requirement

An IdP is a cloud service. The question is whether it processes, stores, or transmits CUI. In a typical SSO flow, the IdP handles credentials, authentication tokens, session data, and directory attributes. None of that is CUI in most environments. So a literal reading says the FedRAMP mandate doesn’t apply.

The complication is the CMMC scoping guidance, which defines Security Protection Assets (SPAs): assets that provide security functions to the CMMC assessment scope even if they never touch CUI. An IdP enforcing multi-factor authentication (MFA), conditional access, and session policy over your CUI enclave is the textbook SPA. SPAs are in scope for your assessment and get evaluated against the relevant NIST SP 800-171 requirements they help satisfy.

Let Axipro help you build a business continuity plan that's practical, compliant, and audit-ready.

Schedule Your Free Assessment Today

Does Your Identity Provider Actually Need to Be FedRAMP Authorized?

When the IdP Processes, Stores, or Transmits CUI

Some architectures do push CUI through the identity layer. If usernames or directory attributes contain CUI (think program names or export-controlled project identifiers), if your IdP proxies application traffic through a gateway that carries CUI payloads, or if CUI-bearing documents get attached to identity workflows, the IdP is now a CSP handling CUI. FedRAMP Moderate or equivalent becomes non-negotiable.

When the IdP Provides Security Protections for CUI (SPA Role)

This is the common case, and it’s genuinely gray. The FedRAMP requirement in the rule text attaches to CSPs that process, store, or transmit CUI. A pure-play authentication service that does neither is an SPA, not a CUI-handling CSP. Under the final CMMC rule, External Service Providers (ESPs) that handle only Security Protection Data, such as configuration data, logs, and credentials, do not themselves require FedRAMP authorization or a separate CMMC certification. Their services get assessed as part of your assessment.

In practice, C3PAOs are not uniform on this. Some accept a well-documented System Security Plan (SSP) showing the IdP never touches CUI. Others take a conservative view that authentication data for CUI systems is sensitive enough that they want FedRAMP-grade assurance behind it, and they will probe hard. DIBCAC’s historical position, given publicly by officials as far back as 2020, is that clouds with management access to CUI systems don’t need FedRAMP unless CUI actually moves into them. That position helps, but you carry the burden of proving CUI never transits the service.

Cases Where a Commercial IdP May Be Acceptable

A commercial, non-FedRAMP IdP can survive a CMMC Level 2 assessment when all three of the following are true: CUI demonstrably never touches the IdP, the IdP is documented as an SPA with the specific 800-171 requirements it supports, and the data flows in your SSP prove the boundary. This is exactly how many contractors run enclave strategies, keeping a commercial identity stack for the corporate network while the CUI enclave uses its own FedRAMP-authorized identity.

The “External Service Provider” (ESP) Classification Under CMMC

The final rule distinguishes CSPs from other ESPs, like managed service providers. If your MSP administers your environment but the cloud tenancy is yours, the MSP is not a CSP and the FedRAMP requirement doesn’t attach to them, though their people and tools enter your assessment scope. If the provider hosts the service itself and CUI flows into it, they’re a CSP and the FedRAMP test applies. Where your IdP vendor sits in that taxonomy should be written into your SSP before your C3PAO asks.

 

Pro Tip: Write a One-page Data Flow Narrative

Write a one-page data flow narrative for your identity layer: what the IdP stores (identifiers, hashes, tokens, device posture), what it never stores, and how CUI systems consume authentication. Assessors respond far better to a clear negative claim with evidence than to a shrug. This single artifact resolves most IdP scoping debates before they start.

JumpCloud for CMMC Level 2

JumpCloud’s Current FedRAMP Status

JumpCloud is not FedRAMP authorized at any baseline, does not appear on the FedRAMP Marketplace, and has not published a 3PAO-attested FedRAMP Moderate equivalency Body of Evidence. The JumpCloud Directory Platform carries SOC 2 Type 2 attestation and ISO 27001 certification, which are credible commercial trust signals and irrelevant to the DFARS 7012 test.

JumpCloud Government vs. Commercial Offering

There is no JumpCloud government cloud. Unlike Okta and Microsoft, JumpCloud sells a single multi-tenant commercial platform. Its own CMMC positioning is about helping you satisfy control families like Access Control (AC), Identification and Authentication (IA), and Audit and Accountability (AU), not about the platform meeting CSP requirements for CUI.

Gaps to Address When Using JumpCloud for CUI Environments

If CUI touches JumpCloud, you have a finding you cannot remediate with configuration. Beyond the missing authorization, contractors should press JumpCloud on FIPS 140-2/140-3 validated cryptography for data in transit and at rest, US data residency guarantees, and personnel access controls, because your C3PAO will ask even in the SPA scenario.

Best-Fit Scenarios for JumpCloud

JumpCloud makes sense for small and mid-sized contractors running an enclave strategy: JumpCloud handles identity and device management for the general corporate environment, while the CUI enclave (commonly Microsoft GCC High or a managed enclave product) uses its own FedRAMP-authorized identity. It’s a cost-effective way to get MFA, SSO, and cross-OS device management for the 90% of your company that never sees CUI. It is not a candidate for the CUI path itself.

Okta for CMMC Level 2

Okta IDaaS Government High Cloud (GHC) FedRAMP High Authorization

Okta for Government High, listed on the FedRAMP Marketplace as Okta IDaaS Government High Cloud, achieved FedRAMP High authorization in March 2023. It runs on AWS GovCloud and covers 420+ NIST SP 800-53 controls at the High baseline, with support for phishing-resistant MFA including PIV, FIDO2/WebAuthn, and Okta FastPass. Okta has since extended the High authorization to Okta Identity Governance and Okta Workflows, which matters if you want lifecycle automation inside the authorization boundary rather than bolted on outside it.

Okta IDaaS Regulated Cloud (FedRAMP Moderate)

Okta’s Moderate-baseline offering (Okta for Government Moderate, listed as Okta IDaaS Regulated Cloud) has held FedRAMP Moderate authorization since 2017 and has accumulated well over 250 agency authorizations, making it one of the most reused identity packages on the Marketplace. For CMMC Level 2, Moderate is the floor the rule requires, so this tier is sufficient for most CUI Basic scenarios. Contractors handling CUI specified categories or wanting headroom often go straight to the High cell.

Okta Commercial vs. Okta for Government: Which You Need

Commercial Okta tenants are not covered by either authorization. The authorization attaches to specific cells and environments, not to the Okta brand. If your subscription lives in a commercial cell, you inherit nothing. Migrating between commercial and government cells is a real project involving re-federation of every application, MFA re-enrollment, and workflow rebuilds, so contractors should pick the right cell before rollout, not after.

Licensing and Cost Considerations

Expect the government cells to price meaningfully above the commercial list, with procurement through government-oriented contract vehicles or resellers. Okta prices per user per product (SSO, MFA, Lifecycle Management, Identity Governance, each stack), so a full CMMC-supporting deployment for a 200-person contractor routinely lands in the tens of thousands of dollars annually before professional services. Against that, Okta is the strongest option when your CUI systems are heterogeneous, spanning AWS GovCloud workloads, on-prem applications, and non-Microsoft SaaS.

Microsoft Entra ID for CMMC Level 2

Entra ID in Microsoft 365 GCC High (FedRAMP High Equivalent)

For Defense Industrial Base (DIB) contractors, the default answer is Entra ID inside Microsoft 365 GCC High. The GCC High directory service is provided by Azure Government, assessed at FedRAMP High, operated by screened US persons within US data residency, and it demonstrates DoD SRG IL4/IL5 equivalency. Critically, GCC High is the Microsoft environment where the DFARS 7012 paragraph (c) through (g) incident reporting and forensics flow-down is contractually supported. Microsoft also completed a Joint Surveillance Voluntary Assessment (JSVA) of its own federal environment with a perfect 110 score in SPRS terms, which is the strongest shared-responsibility evidence any of the three vendors can hand you.

Entra ID in GCC vs. Commercial M365

Here’s a nuance most comparison articles miss: Azure Commercial, including commercial Entra ID, actually holds a FedRAMP High provisional authorization. On paper, that reads like a pass. The problem is everything around it. Commercial M365 doesn’t support the DFARS 7012 (c)-(g) flow-down, doesn’t guarantee US-person administration, and can’t hold export-controlled CUI categories like ITAR data. GCC (standard) sits in between: fine for Federal Contract Information and workable for some CUI Basic scenarios, but Microsoft itself steers CMMC Level 2 contractors with CUI toward GCC High. So the Entra question is less “is it FedRAMP” and more “which cloud does your whole Microsoft stack live in,” because Entra follows the tenant.

Insider Note: The FedRAMP status of the identity service is rarely what disqualifies a Microsoft architecture. What disqualifies it is CUI sitting in Exchange, SharePoint, and Teams in a commercial tenant. The IdP inherits the decision you make about the productivity stack. If email and files must be in GCC High, your Entra ID is in GCC High by definition, and the IdP debate resolves itself.

Entra ID P1/P2 Feature Availability Across Tenants

Conditional Access, the workhorse for CMMC access control requirements, needs Entra ID P1. Privileged Identity Management and risk-based policies (your PAM-adjacent and 3.1.x/3.5.x helpers) need P2. Both are available in GCC High, usually bundled through M365 G3/G5 licensing, though some features ship to government clouds months behind commercial. GCC High licensing typically runs a 25-50% premium over commercial equivalents and requires validation of your eligibility before Microsoft will even provision the tenant.

Integration with Azure Government

If your engineering workloads run in Azure Government, Entra ID in GCC High is the native control plane: same identity backbone, Conditional Access spanning M365 and Azure workloads, and a single audit trail feeding Sentinel. That integration story is the main reason Entra wins by default in Microsoft-centric DIB environments.

Choosing the Right IdP Based on Your CUI Architecture

Ultimately, choosing the right IdP based on your CUI architecture comes down to where your data lives and moves. The paths below map the three most common scenarios.

If CUI Never Touches the IdP Authentication Flow

Document the IdP as a Security Protection Asset, keep the data-flow evidence tight, and any of the three can technically work, including JumpCloud. Your risk here is assessor variance, not the rule itself. Budget-conscious contractors with a hard enclave boundary take this path deliberately.

If the IdP Enforces Access Controls Over CUI Systems

Once the IdP is the enforcement point for your CUI systems’ access control and MFA requirements, most contractors and a growing share of C3PAOs treat FedRAMP-grade identity as the safe harbor. That means Okta’s government cells or Entra ID in GCC/GCC High. The cost delta is smaller than the cost of a contested assessment finding.

Hybrid Scenarios and Enclave Strategies

The pattern we see most at Axipro among mid-sized DIB contractors: GCC High (with Entra ID) as the CUI enclave, JumpCloud or commercial Okta running the rest of the company, and no federation between the two identity planes. Two directories are annoying. It’s also dramatically cheaper than moving 400 people into GCC High to protect the 40 who touch CUI, and it shrinks your assessment scope in the bargain.

Decision Framework: Which IdP Should You Choose?

Ask four questions in order.

  • One: Does CUI transit the identity layer in any flow? If yes, only FedRAMP Moderate-or-higher offerings qualify, which eliminates JumpCloud.
  • Two: Is your CUI stack Microsoft-centric? If yes, Entra ID in the matching tenant wins on integration and total cost, since you’re already paying for it.
  • Three: Is your CUI estate heterogeneous across clouds and on-prem? Okta’s government cells earn their premium there.
  • Four: Are you running an enclave to shrink scope? Then split the decision: FedRAMP-authorized identity inside the enclave, and the best value platform (often JumpCloud) outside it.

The bottom line across all of this: the rule cares about where CUI lives and moves, not about logos. JumpCloud is a capable platform with no lane into the CUI path. Okta gives you purpose-built FedRAMP Moderate and High identity clouds at a price. Entra ID rides whichever Microsoft tenant your data already demands. Architecture first, vendor second.

Worth Knowing: Phase 2 of the CMMC

With Phase 2 of the CMMC rollout bringing C3PAO assessments to more Level 2 contracts through 2026, assessment calendars at reputable C3PAOs are filling up months out. If your IdP decision forces a migration, the migration timeline, not the license negotiation, is usually what threatens your assessment date. Cell-to-cell Okta migrations and commercial-to-GCC High moves both routinely run one to two quarters.

Final Recommendation Based on Contractor Profile

For a Microsoft-centric DIB contractor handling CUI in email and files, choose Entra ID in GCC High. You need the tenant anyway; the identity comes with it, and the shared-responsibility evidence trail is the most mature in the market.

For a contractor with CUI spread across AWS GovCloud, on-prem systems, and non-Microsoft SaaS, choose Okta IDaaS Regulated Cloud (or Government High Cloud for CUI Specified and ITAR contexts) and budget for the government-cell premium.

For a small contractor pursuing an enclave strategy, run JumpCloud as the corporate identity and device platform outside the boundary and let the enclave’s native FedRAMP-authorized identity handle CUI access.

And whichever way you go, settle the IdP scoping question in your SSP before your C3PAO settles it for you.

Frequently Asked Questions

Does Microsoft Entra ID Commercial meet CMMC Level 2 requirements?

Partially, and that’s the trap. Commercial Azure (including Entra ID) holds a FedRAMP High provisional authorization, but commercial M365 doesn’t support the DFARS 252.204-7012 (c)-(g) flow-down and can’t hold export-controlled CUI. If your CUI lives in Microsoft services, Microsoft’s own guidance points Level 2 contractors to GCC High, and your Entra tenant follows that decision.

No. JumpCloud holds SOC 2 Type 2 and ISO 27001 for its directory platform but has no FedRAMP authorization at any baseline and no published Moderate-equivalency Body of Evidence. It cannot be used to process, store, or transmit CUI under DFARS 7012 or the CMMC rule.

Yes, in an enclave architecture where commercial Okta serves only the non-CUI environment and never federates into the enclave. Document it as out of scope or as a Security Protection Asset for the corporate side, and keep the identity planes separated in your SSP and network diagrams.

FedRAMP Moderate means the offering holds an actual authorization and appears on the FedRAMP Marketplace. Equivalent, per the DoD’s December 2023 memo, means the CSP proves 100% compliance with the Moderate baseline through a 3PAO assessment and supplies the contractor a Body of Evidence, with no open POA&Ms. Equivalency has no marketplace listing and no government sponsor; you hold the evidence and the risk.

Under a strict reading of the rule, no: the FedRAMP requirement attaches to CSPs that process, store, or transmit CUI, and an authentication-only IdP is a Security Protection Asset assessed within your scope instead. In practice, be ready to prove the negative with data-flow documentation, and expect some C3PAOs to push toward FedRAMP-grade identity anyway when the IdP gates CUI systems.

Three ways. They check scoping: is the IdP a CUI asset, an SPA, or out of scope, and does the evidence support that classification. They check the CSP test where it applies: marketplace listing or Body of Evidence. And they assess the 800-171 requirements the IdP helps satisfy, such as MFA (3.5.3), session controls, and account management, against your actual tenant configuration, not the vendor’s data sheet.

You have a compliance gap against DFARS 7012 the moment CUI keeps flowing through a no-longer-qualified service. Practically, you’d document the deviation, open a POA&M, notify affected primes where required, and execute a migration. This is a reason to favor offerings with long authorization track records and multiple agency reuses, and to write exit rights into the vendor contract.

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

One in five breached organizations last year traced the incident to shadow AI, and those breaches cost an average of $670,000 more than standard incidents, according to IBM’s 2025 Cost of a Data Breach Report. The worst part is that most of those organizations already ran a CASB, a DLP program, or both. The tools were on, but the traffic still got through. That’s the visibility gap this article is about. AI tool usage tracking isn’t the same problem as SaaS discovery, and the security stack built for the SaaS era misses most of what matters about AI. Below, we break down what tracking actually requires, where CASB and DLP fail, which categories of AI usage slip through, and what a stack that works looks like in 2026. What AI Tool Usage Tracking Actually Means Most teams that say they “track AI usage” mean they can see that someone visited chat.openai.com. That is app discovery, and it answers almost none of the questions a security or governance team actually needs answered. Beyond App Discovery: Tracking Prompts, Data Flows, and Model Interactions Real tracking covers three layers. First, which tools are in use: chatbots, copilots, coding assistants, embedded SaaS features, agents. Second, what data moves: the content of prompts, uploaded files, and pasted context, mapped against data classifications. Third, how models behave in your environment: which endpoints get called, which OAuth grants exist, which agents hold standing permissions. Seeing that an employee opened ChatGPT gets you nowhere. What you actually need to know is whether they pasted a customer contract into a personal account while they were there. The Difference Between Detection, Monitoring, and Continuous Tracking Detection is a point-in-time answer to “what AI is here?” Monitoring watches known tools on an ongoing basis. Continuous tracking is broader: it assumes the inventory changes weekly, correlates identity, data, and endpoint signals over time, and feeds a governance program rather than a one-off report. Frameworks such as the NIST AI Risk Management Framework and ISO 42001 assume the third mode. A discovery scan from last quarter won’t satisfy an auditor, and it certainly won’t slow down an attacker. Why Traditional SaaS Monitoring Falls Short for AI SaaS monitoring was built around a stable premise: an app is a destination with a domain, a login, and an admin console. AI breaks that premise in several ways at once. The risky activity is the content of an interaction, not the visit. The tool often isn’t a destination at all but a feature inside an app you already sanctioned. And increasingly the “user” isn’t a person but an agent acting on delegated credentials. Why CASB Misses Shadow AI Usage The Cloud Access Security Broker sits between users and cloud services to enforce policy, and for classic SaaS governance it still earns its keep. AI has structural blind spots that no amount of tuning can fix. CASBs Were Built for SaaS Apps, Not Model Endpoints A CASB catalog maps domains to applications with risk scores. AI usage doesn’t resolve neatly to a domain. The same api.openai.com endpoint serves a sanctioned enterprise deployment, a developer’s weekend experiment, and a data-leaking browser extension, and the catalog sees one “app”. Meanwhile, new model endpoints, wrappers, and niche AI tools appear faster than any vendor catalog can keep up with. Gartner research from late 2025 found 69% of organizations already suspect or have evidence that employees use prohibited public generative AI tools, catalog or no catalog. Blind Spots in Encrypted API Traffic to LLM Providers Prompt content travels over TLS. Without full TLS inspection, a CASB sees connection metadata: destination, volume, timing. It can’t see that the payload contained source code or patient records. And full TLS inspection is harder than the datasheet implies. Certificate pinning breaks it for many native apps and CLI tools, legal and works-council constraints limit it in the EU, and most organizations carve out broad exemption lists that AI traffic happily rides through. The OAuth and Embedded AI Problem CASBs Can’t See When an employee grants an AI meeting-notes tool access to their calendar and mailbox via OAuth, no proxy is involved at all. The vendor’s servers communicate directly with Microsoft’s or Google’s APIs using a persistent token. The same applies to AI features embedded inside sanctioned SaaS, think Notion AI, Slack AI, or Salesforce Einstein. The CASB sees approved traffic to an approved app, while the AI processing happening inside it, and whichever sub-processor it forwards data to, stays invisible. Personal Accounts and BYO-AI Bypass CASB Proxies Netskope’s 2026 Cloud and Threat Report found that nearly half of employees who use generative AI at work do so through personal accounts. Personal accounts on managed devices are hard enough; personal accounts on personal devices, home networks, and mobile connections never touch the corporate proxy path at all. Tenant restrictions help for a handful of major providers and do nothing for the long tail. Browser-Based and Extension-Delivered AI Escape Network Inspection AI browser extensions read page content and form inputs locally, then exfiltrate via their own backend, often to generic cloud infrastructure that categorizes as “technology” rather than “AI”. From the network’s view, it is routine HTTPS to a CDN. The riskiest interaction, an extension scraping everything an employee views, produces the most boring traffic signature. Insider Note: In AI governance readiness assessments, the OAuth grant review is where clients get the biggest surprise. We routinely find dozens of AI tools holding live mail, calendar, or drive scopes that nobody in IT ever approved, granted by employees who abandoned the tool (and sometimes the company) months earlier. The tokens keep working anyway. Why DLP Fails to Catch Shadow AI Data Exposure DLP has the opposite problem. It can sometimes see content, but it doesn’t understand it, and AI interactions defeat the pattern matching it depends on. Prompt-Based Data Loss Doesn’t Match DLP Signature Patterns DLP fires on signatures: credit card regexes, SSN formats, keyword dictionaries, file fingerprints. Sensitive prompts rarely look like that. “Summarize why we’re losing

Most SOC 2 preparation effort goes into access controls, encryption, and vendor reviews. Then the auditor’s first evidence request arrives, and item one has nothing to do with technology: show us your board charter, your meeting minutes, and proof that your board operates independently from management. That’s CC1.2, and it causes more last-minute scrambling than almost any technical control in the framework. This guide explains what CC1.2 requires, provides a board charter template with sample language that auditors accept, and covers the situation most startups actually face: satisfying the criterion without a traditional board of directors. What Is a SOC 2 Board Charter and Why It Matters for CC1.2 A board charter is a formal document that defines your board’s purpose, composition, authority, meeting procedures, and oversight responsibilities. Outside of compliance, it’s a corporate governance tool and a good idea in general for companies with shareholders.  Inside a SOC 2 audit, it’s the primary design evidence for CC1.2, the criterion that asks whether an independent body oversees management and the internal control environment. The charter matters because CC1.2 is one of the few criteria where the control is a document plus behavior. The charter establishes the structure. The auditor then tests whether the structure operates: did the board actually meet, did it review the security program, did it challenge management? A beautifully drafted charter with no meeting minutes behind it fails just as surely as no charter at all. If you’re earlier in your preparation, our complete SOC 2 guide covers how the full audit fits together. Understanding CC1.2: The Board Independence Criterion CC1.2 is part of the Trust Services Criteria published by the AICPA (American Institute of Certified Public Accountants). The criterion requires that the board of directors, in the AICPA’s words, “demonstrates independence from management and exercises oversight” of how internal control is developed and how it performs. That sentence hides two separate tests. Independence means the board isn’t just management wearing a second hat. Active oversight means the board actually reviews and challenges the control environment instead of existing on paper. Plenty of companies pass one and fail the other. How CC1.2 Fits Within the CC1 Control Environment The Common Criteria run from CC1 through CC9, and the CC1 series covers the control environment: the governance and people layer everything else rests on. CC1.1 addresses integrity and ethical values, CC1.2 addresses board independence and oversight, CC1.3 covers organizational structure and reporting lines, CC1.4 covers competence and hiring, and CC1.5 covers accountability. CC1.2 is the layer that makes the other four credible. A code of conduct means little if nobody independent of management ever checks whether leadership follows it. The COSO Principle 2 Connection The Trust Services Criteria are built directly on the COSO Internal Control—Integrated Framework and its 17 principles. CC1.2 maps to COSO Principle 2, which carries four points of focus: the board establishes oversight responsibilities, applies relevant expertise, operates independently of management, and provides oversight of the system of internal control. Those four phrases are worth memorizing, because they’re effectively the outline of a good board charter. Why Auditors Prioritize Board Charter Evidence Auditors test the control environment first because failures there cascade. If governance is weak, every other control claim gets harder to trust: who approved the risk assessment, who reviewed the incident report, who held management accountable when a control slipped? An exception at CC1.2 tells the auditor that nobody independent was watching, and they’ll read the rest of your evidence with that in mind. That’s why board charter requests sit near the top of almost every evidence list. Worth Knowing: Points of Focus Points of focus are not pass/fail requirements. The AICPA describes them as characteristics that assist evaluation, and the 2022 revisions changed points of focus without changing any criteria. In practice, though, they function as the auditor’s mental checklist, so drafting your charter against them is the safest move. What Auditors Actually Look For in a Board Charter Auditors don’t grade prose style. They scan for specific, verifiable commitments. Here’s what they check, roughly in order. Documented Board Independence from Management The charter must state how many members are independent, define what independence means (no operational role, no material financial relationship beyond board compensation or equity), and describe how independence is maintained. “The board includes members independent of management” without a definition is boilerplate; auditors want criteria they can test against actual member profiles. Defined Oversight Responsibilities This is the heart of CC1.2. The charter should explicitly assign the board oversight of internal control, information security, and risk management. If the charter only mentions financial oversight and strategy, it wasn’t written with SOC 2 in mind, and the auditor will notice the gap. Clear Authority and Decision-Making Powers What can the board approve, veto, or demand? Typical provisions include approving the risk management framework, reviewing audit results, approving executive appointments, and requiring management to report on control deficiencies. Authority without teeth reads as decorative. Meeting Cadence and Quorum Requirements The charter should commit to a minimum meeting frequency (quarterly is the common standard) and define a quorum. This clause matters more than founders expect, because it’s the one auditors test directly against your calendar: if the charter says quarterly and you met twice last year, that’s an exception you wrote for yourself. Committee Structures Larger organizations delegate through audit, risk, and compensation committees, each with its own mini-charter. Smaller companies don’t need committees, but if your charter mentions them, they must exist and produce minutes. Never copy a public-company template with a phantom audit committee. Conflict of Interest Provisions A disclosure and recusal process for conflicts, usually paired with an annual attestation. This clause supports the independence claim: independence isn’t a one-time status, it’s maintained through disclosed and managed conflicts. Evidence of Board Member Expertise and Qualifications COSO’s “applies relevant expertise” point of focus means the board should be able to ask probing questions about security and risk, not just finance. Charters increasingly include a skills expectation clause, and

Most Drata reviews are written by Drata’s competitors. Scroll the first page of Google and you’ll find review posts from rival compliance platforms, each one ending with a pitch for their own tool. This one is different, and the bias runs the other way, so let’s put it on the table: Axipro is a Drata Gold Partner, and our consultants configure the platform for clients every week. That means we profit when companies choose Drata. It also means we know exactly where it saves you months, where the invoice grows faster than you planned, and when you should pick something else. This review covers all three. What Is Drata?​ Drata is a compliance automation platform (the industry calls the category GRC, for governance, risk, and compliance) founded in 2020 in San Diego by Adam Markowitz, Daniel Marashlian, and Troy Markowitz. Its core job: connect to your cloud infrastructure, identity provider, HR system, and code repositories, then continuously test your security controls against frameworks like SOC 2 and ISO 27001, collecting timestamped evidence as it goes. When your auditor shows up, most of the evidence is already packaged. Funding, Valuation, and Market Position Drata has raised $328 million, most recently a $200 million Series C in late 2022 that valued the company at $2 billion. It passed $100 million in annual recurring revenue in early 2025, acquired the trust center platform SafeBase for $250 million the same year, and now serves more than 8,000 customers. In late 2025 it earned a FedRAMP 20x Low Pilot Authorization, which puts it in a small group of compliance platforms cleared through the U.S. government’s modernized FedRAMP review track. Together with Vanta, it’s one of the two platforms almost every compliance buyer shortlists. Who Drata Is Built For The sweet spot is cloud-native companies from seed stage to mid-market: SaaS businesses pursuing their first SOC 2 or ISO 27001, and scaling teams juggling three or four frameworks at once. If your infrastructure lives in AWS, Azure, or GCP and your team uses standard tools like Okta, GitHub, and a mainstream HRIS, Drata’s automation covers a large share of your evidence collection out of the box. The further you drift from that profile (heavy on-prem systems, exotic tooling, air-gapped environments), the more manual work remains. How Drata Works: From Connection to Audit The workflow runs in five stages. First, you connect your tech stack through more than 270 native integrations covering cloud providers, identity, version control, HRIS, MDM, and ticketing. Second, continuous control monitoring kicks in: automated tests run around the clock against your connected systems, checking things like MFA enforcement, encryption settings, and access reviews. Third, automated evidence collection captures timestamped proof each time a test passes, building the evidence library your auditor will draw from. Fourth, when a test fails, remediation workflows and alerts route the issue to an owner through Slack, Jira, or email, with guidance on how to fix it. Fifth, the Audit Hub gives your auditor a scoped login to review evidence directly in the platform instead of trading spreadsheets and screenshots over email. In our client engagements, that last piece cuts back and forth more than any other feature. Auditors ask fewer clarifying questions when they can trace evidence to its source themselves. Drata’s Core Features Reviewed Overview of the Drata platform and compliance management dashboard. Multi-Framework Control Mapping Drata maintains a single control set mapped across every framework you activate. Pass an encryption control once, and it satisfies the corresponding requirements in SOC 2, ISO 27001, and HIPAA simultaneously. For multi-framework programs, this is the feature that pays for the platform. Adding ISO 27001 to an existing SOC 2 program typically starts you at 60 to 80 percent complete rather than zero. The Drata Agent The Drata Agent is a lightweight application installed on employee laptops. It checks device posture: screen lock, disk encryption, password manager, antivirus, OS updates. It reads configuration states, not files, browsing history, or keystrokes. Employees sometimes push back on installing it anyway, which is why we advise clients to communicate what it does and doesn’t see before rollout, not after the first complaint. Companies with an existing MDM like Jamf or Intune can often pull device evidence from that integration instead. Risk Management, Vendor Risk, and the Trust Center The built-in risk register lets you score risks by likelihood and impact and tie them to controls and remediation tasks. Vendor risk management got a genuine upgrade with the August 2025 agentic AI release, which now collects vendor evidence, reviews SOC 2 reports, and drafts risk summaries with far less manual chasing. The Trust Center, built on the acquired SafeBase product, gives you a public page where prospects can review your certifications and policies under NDA. Clients in active enterprise sales cycles tell us it measurably shortens security review, though note it’s a paid add-on at most tiers, not a bundled feature. Policies, Training, and the Rest Drata ships editable policy templates for every major framework, embedded security awareness training with completion tracking, and an API for anything the native integrations miss. The policy templates are a real accelerator for first-time programs, with one caveat we see constantly: teams accept templates wholesale without adapting them, then get flagged in audit when their actual practice doesn’t match their written policy. A template you don’t follow is worse than no template. Supported Compliance Frameworks Drata supports more than 30 frameworks. The ones that matter for most buyers: SOC 2 (Type I and Type II) against the AICPA Trust Services Criteria, ISO 27001, HIPAA (where Drata operationalizes safeguards, since no formal HIPAA certification exists), GDPR under the EU data protection rules, and PCI DSS. Coverage extends to CMMC, NIS2, DORA, FedRAMP, and various NIST standards. You can also build custom frameworks by mapping your own control set, useful for internal standards or customer-specific requirements. What Users Really Say Drata holds a 4.8 out of 5 on G2 across more than 1,100 reviews, the highest score among the