[{"data":1,"prerenderedAt":1902},["ShallowReactive",2],{"\u002Fblog\u002Fcmmc-phase-2":3,"blog-surround-cmmc-phase-2":340,"explore-glossary-none-\u002Fblog\u002Fcmmc-phase-2":351,"explore-topics-none-\u002Fblog\u002Fcmmc-phase-2":1092,"explore-hub-none":6,"explore-compare-vs-\u002Fblog\u002Fcmmc-phase-2":1093,"explore-compare-\u002Fblog\u002Fcmmc-phase-2":1387,"explore-blog-none-\u002Fblog\u002Fcmmc-phase-2":1560,"explore-industry-none":1817},{"id":4,"title":5,"api":6,"authors":7,"body":13,"category":328,"date":329,"description":330,"extension":331,"faq":6,"features":6,"fixes":6,"highlight":6,"image":332,"improvements":6,"meta":334,"navigation":335,"path":336,"seo":337,"stem":338,"summary":6,"updated":6,"__hash__":339},"posts\u002F3.blog\u002Fcmmc-phase-2.md","CMMC Phase 2 Was Supposed to Start This Month. Here's What Actually Changed.",null,[8],{"name":9,"to":10,"avatar":11},"Justin Leapline","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fjustinleapline\u002F",{"src":12},"\u002Fimages\u002Fjustinleapline.png",{"type":14,"value":15,"toc":314},"minimark",[16,20,23,26,29,34,42,51,54,58,61,64,86,89,92,95,99,102,108,114,120,126,129,133,136,139,147,151,159,162,177,188,191,195,198,201,219,222,230,234,237,282,286,289,292,296,304,308,311],[17,18,19],"p",{},"For a year, November 10, 2026 was circled on every defense contractor's calendar.",[17,21,22],{},"That was the day CMMC Phase 2 was supposed to begin. Third-party Level 2 certification from a C3PAO would start showing up as a condition of award in contracts that touch Controlled Unclassified Information (CUI).",[17,24,25],{},"Then the date came and went, and nothing new took effect.",[17,27,28],{},"Here is where things actually stand, what you still owe, and what I would do with the next 90 days.",[30,31,33],"h2",{"id":32},"what-phase-2-was-supposed-to-be","What Phase 2 was supposed to be",[17,35,36,37,41],{},"The CMMC program rule (32 CFR Part 170) lays out four phases. Phase 1 started on November 10, 2025, the day the DFARS acquisition rule took effect. Phase 1 let DoD require Level 1 and Level 2 ",[38,39,40],"em",{},"self","-assessments as a condition of award.",[17,43,44,45,50],{},"Phase 2 was written to begin \"one calendar year following the start date of Phase 1.\" It kept the Phase 1 requirements and added Level 2 (C3PAO) certification as a condition of award for applicable contracts, with the option to defer it to an option period. Phase 3 and Phase 4 would follow a year apart. Our ",[46,47,49],"a",{"href":48},"\u002Fframeworks\u002Fcmmc\u002Fimplementation-timeline","CMMC implementation timeline"," walks through the original schedule.",[17,52,53],{},"That is still the text of the rule. It's just not what is happening.",[30,55,57],{"id":56},"what-happened-instead","What happened instead",[17,59,60],{},"On July 13, 2026, DoD CIO Kirsten Davies announced the department was \"suspending the CMMC Phase II requirements and initiating a 60-day study of the future of this program.\" Phase 3 and Phase 4 were suspended with it. Her explanation, as reported by DefenseScoop, was that \"the math just simply doesn't math\" for small and mid-sized businesses to get compliant by the transition date, given assessor capacity and cost.",[17,62,63],{},"The implementing guidance was blunt:",[65,66,67,80,83],"ul",{},[68,69,70,71,75,76,79],"li",{},"Program offices can only require ",[72,73,74],"strong",{},"Level 1 (Self)"," or ",[72,77,78],{},"Level 2 (Self)"," in procurement documents. No C3PAO or DIBCAC designations during the review.",[68,81,82],{},"Active solicitations that already included Level 2 (C3PAO) or Level 3 requirements get amended to remove them \"as soon as practicable.\"",[68,84,85],{},"Existing contracts with those requirements get modified before the next option period or at the next scheduled administrative modification.",[17,87,88],{},"On September 3, a DFARS class deviation (2026-O0025, Revision 3) told contracting officers to strip third-party assessment requirements out of contracts. That turned a policy pause into binding contracting direction, which makes it harder to reverse quickly.",[17,90,91],{},"A CMMC Reform Task Force took industry comments through an RFI that closed August 14. On October 27, Federal News Network reported on a summary of its recommendations. The headline items: restart Phase 2 with a narrower population, extend the POA&M closeout window to 270 days through rulemaking, give explicit credit for comparable ISO 27001 requirements, and finalize the move to NIST SP 800-171 Revision 3. DoD declined to comment, and none of it has been adopted as of this writing.",[17,93,94],{},"So on November 10, the honest status was: Phase 2 is suspended, no restart date has been announced, and the task force recommendations are just recommendations.",[30,96,98],{"id":97},"what-did-not-change","What did not change",[17,100,101],{},"This is the part people skip, and it's the part that matters.",[17,103,104,107],{},[72,105,106],{},"Phase 1 is fully in force."," Solicitations can still require Level 1 (Self) for Federal Contract Information (FCI) and Level 2 (Self) for CUI. Level 2 (Self) means you assess yourself against all 110 NIST SP 800-171 Rev 2 requirements, post the score in SPRS, reassess every three years, and have an affirming official affirm compliance every year.",[17,109,110,113],{},[72,111,112],{},"DFARS 252.204-7012 still applies."," If you handle covered defense information, you are contractually obligated to implement NIST SP 800-171 and report incidents, and have been since long before CMMC. The suspension didn't touch that.",[17,115,116,119],{},[72,117,118],{},"DFARS 252.204-7021 still applies where it's in your contract."," It requires you to \"have and maintain for the duration of the contract\" a current CMMC status at the required level, and to complete an annual affirmation in SPRS.",[17,121,122,125],{},[72,123,124],{},"False Claims Act exposure got worse, not better."," DOJ's Civil Cyber-Fraud Initiative goes after contractors who knowingly misrepresent cybersecurity compliance. With C3PAO certification off the table, nobody independent checks most contractors' scores before award, so your self-assessment and your affirming official's signature carry the weight. DoD's own scrutiny didn't go away, either: DFARS 252.204-7020 still lets it run a Medium or High assessment of your environment, typically through DIBCAC. A 110 you can't defend is a liability, not an asset.",[17,127,128],{},"Pausing a certification requirement is not the same as pausing a security requirement. The controls were always the obligation. The C3PAO was just the person checking.",[30,130,132],{"id":131},"self-assessment-vs-c3pao-right-now","Self-assessment vs. C3PAO right now",[17,134,135],{},"For now, self-assessment is the ceiling of what a DoD solicitation can require. That doesn't make C3PAO assessments pointless.",[17,137,138],{},"You can still get one voluntarily. A Level 2 (C3PAO) certification also satisfies Level 2 (Self) for the same assessment scope, so it isn't wasted if the requirement stays at self-assessment. And some primes will want independent assurance from their critical suppliers no matter what the rule says. If your biggest customer is asking, that's your real requirement.",[17,140,141,142,146],{},"If nobody is asking, don't rush to book an assessment you aren't ready for. Spend the money on controls and evidence first. Our ",[46,143,145],{"href":144},"\u002Fframeworks\u002Fcmmc\u002Fself-assessment-vs-third-party","self-assessment vs. third-party breakdown"," covers the trade-offs in more detail.",[30,148,150],{"id":149},"sprs-scores-and-the-poam-rules","SPRS scores and the POA&M rules",[17,152,153,154,158],{},"Your SPRS score follows the DoD Assessment Methodology. You start at 110 and subtract 5, 3, or 1 point for each requirement that isn't met. If you haven't scored yourself recently, our free ",[46,155,157],{"href":156},"\u002Ftools\u002Fsprs-calculator","SPRS score calculator"," does the math the same way.",[17,160,161],{},"For CMMC Level 2, Part 170 sets firm rules on what you can leave open on a Plan of Action and Milestones (POA&M):",[65,163,164,171,174],{},[68,165,166,167,170],{},"Your score has to be at least 80% of the maximum. On a 110-point scale, that's ",[72,168,169],{},"88",".",[68,172,173],{},"Only requirements worth 1 point can go on the POA&M, with one exception: CUI encryption (3.13.11) when you use encryption that isn't FIPS-validated.",[68,175,176],{},"Some requirements can never be on a POA&M, including your System Security Plan (3.12.4), external connections (3.1.20), control of publicly posted information (3.1.22), and the physical access requirements for escorting visitors, keeping access logs, and managing physical access devices (3.10.3 through 3.10.5).",[17,178,179,180,183,184,187],{},"Meet those conditions and you get ",[72,181,182],{},"Conditional"," status. Then the clock starts. The POA&M has to be closed and confirmed by a closeout assessment within ",[72,185,186],{},"180 days"," of the Conditional status date, or the Conditional status expires. For Level 2 (Self), you perform that closeout yourself. For Level 2 (C3PAO), the C3PAO does.",[17,189,190],{},"The task force floated 270 days. That would take rulemaking. Plan for 180.",[30,192,194],{"id":193},"how-flow-down-works","How flow-down works",[17,196,197],{},"DFARS 252.204-7021 has to be flowed down to any subcontract (excluding COTS) where the sub will process, store, or transmit FCI or CUI. Before awarding that subcontract, the prime has to make sure the sub has a current CMMC status at the right level.",[17,199,200],{},"The right level comes from 32 CFR 170.23:",[65,202,203,208,213],{},[68,204,205,206,170],{},"Sub handles only FCI: ",[72,207,74],{},[68,209,210,211,170],{},"Sub handles CUI and the prime's requirement is Level 1 or Level 2 (Self): at least ",[72,212,78],{},[68,214,215,216,170],{},"Sub handles CUI and the prime's requirement is Level 2 (C3PAO) or Level 3: at least ",[72,217,218],{},"Level 2 (C3PAO)",[17,220,221],{},"With C3PAO designations off the table during the suspension, the practical floor for a CUI subcontractor is Level 2 (Self). Expect primes to ask for your SPRS score, affirmation, and CMMC unique identifier before they send you anything sensitive.",[17,223,224,225,229],{},"The other lever is sending less CUI in the first place. If a sub doesn't need the drawing, don't flow the drawing. The task force recommendations called this out too. Our ",[46,226,228],{"href":227},"\u002Fframeworks\u002Fcmmc\u002Fsubcontractor-requirements","subcontractor requirements page"," goes deeper on how primes can reduce the burden.",[30,231,233],{"id":232},"if-youre-not-ready-the-next-90-days","If you're not ready: the next 90 days",[17,235,236],{},"Treat the suspension as found time, not a reprieve. Here's how I'd spend it.",[238,239,240,246,252,258,264,270,276],"ol",{},[68,241,242,245],{},[72,243,244],{},"Read your contracts."," Find every 7012 and 7021 clause and every CMMC level in open solicitations. If something still calls for a C3PAO assessment, ask your contracting officer in writing when it will be modified.",[68,247,248,251],{},[72,249,250],{},"Draw your CUI boundary."," Where does CUI actually live? Which systems, which people, which suppliers? A smaller scope, like an enclave, is often the cheapest control you'll ever buy.",[68,253,254,257],{},[72,255,256],{},"Write or fix your System Security Plan."," It can't go on a POA&M. No SSP means no Conditional status.",[68,259,260,263],{},[72,261,262],{},"Do an honest self-assessment."," Score all 110 requirements. Mark anything you can't prove as not met. A lower true score beats a higher fictional one.",[68,265,266,269],{},[72,267,268],{},"Fix the items that can't be deferred first."," SSP, external connections, public information, physical access, and anything worth 3 or 5 points.",[68,271,272,275],{},[72,273,274],{},"Post an accurate score and keep it current."," Your affirming official should be able to explain every point.",[68,277,278,281],{},[72,279,280],{},"Keep evidence as you go."," Screenshots, configs, tickets, training records, POA&M closures. If an assessor, a prime, or a DIBCAC team ever asks, you want to pull it up, not recreate it.",[30,283,285],{"id":284},"realistic-expectations-on-c3pao-timing","Realistic expectations on C3PAO timing",[17,287,288],{},"I won't pretend to know when Phase 2 restarts. Nobody outside the Pentagon does, and anyone giving you a date is guessing.",[17,290,291],{},"What I'm confident of is this: assessor capacity was one of the reasons DoD gave for pausing in the first place, and the task force recommended publishing assessor availability statistics and growing the assessor ecosystem. When third-party requirements come back, even for a narrower population, the companies that waited will all call C3PAOs at the same time. The ones with a defensible SSP, a real score, and organized evidence will move through faster. Everyone else will be in a queue.",[30,293,295],{"id":294},"where-episki-fits","Where episki fits",[17,297,298,299,303],{},"episki tracks your CMMC and NIST SP 800-171 controls, evidence, and POA&Ms in one place, with 180-day closeout reminders so a Conditional status doesn't quietly expire. If you're rebuilding your self-assessment during the pause, the ",[46,300,302],{"href":301},"\u002Fframeworks\u002Fcmmc","CMMC framework overview"," shows how it's set up.",[30,305,307],{"id":306},"the-bottom-line","The bottom line",[17,309,310],{},"November 10 didn't bring a new requirement. It also didn't remove any of the old ones.",[17,312,313],{},"Self-assessments, SPRS scores, annual affirmations, 7012, and flow-down are all still live, and a self-attested score now carries more weight than it did a year ago. Use the pause to make your score true and your evidence easy to find. Whenever Phase 2 comes back, and in whatever form, that work carries over.",{"title":315,"searchDepth":316,"depth":316,"links":317},"",2,[318,319,320,321,322,323,324,325,326,327],{"id":32,"depth":316,"text":33},{"id":56,"depth":316,"text":57},{"id":97,"depth":316,"text":98},{"id":131,"depth":316,"text":132},{"id":149,"depth":316,"text":150},{"id":193,"depth":316,"text":194},{"id":232,"depth":316,"text":233},{"id":284,"depth":316,"text":285},{"id":294,"depth":316,"text":295},{"id":306,"depth":316,"text":307},"practices","2026-11-19","November 10, 2026 was the day Level 2 C3PAO certification was meant to hit defense contracts. It didn't. What the suspension changed, what you still owe, how SPRS scores, POA&Ms and flow-down work now, and what to do in the next 90 days.","md",{"src":333},"\u002Fimages\u002Fblog\u002Fcmmc-for-government.webp",{},true,"\u002Fblog\u002Fcmmc-phase-2",{"title":5,"description":330},"3.blog\u002Fcmmc-phase-2","NdodtPK6i50kJiWXTC4NHRCSycAK9x_UYpNuDd1iwPQ",[341,346],{"title":342,"path":343,"stem":344,"description":345,"children":-1},"CMMC Compliance for Government Contractors (2026)","\u002Fblog\u002Fcmmc-for-government","3.blog\u002Fcmmc-for-government","A practical CMMC 2.0 guide for defense industrial base contractors in 2026 — level selection, NIST 800-171 mapping, CUI handling, and preparing for C3PAO assessment.",{"title":347,"path":348,"stem":349,"description":350,"children":-1},"How to Prepare for a Compliance Audit: The 60-Day Countdown","\u002Fblog\u002Fcompliance-audit-preparation","3.blog\u002Fcompliance-audit-preparation","A week-by-week guide to preparing for a compliance audit — from scoping and evidence review through audit week and post-audit follow-up.",[352,931],{"id":353,"title":354,"body":355,"description":315,"extension":331,"lastUpdated":911,"meta":912,"navigation":335,"path":913,"relatedFrameworks":914,"relatedTerms":921,"seo":925,"slug":928,"stem":929,"term":360,"__hash__":930},"glossary\u002F8.glossary\u002Faccess-control.md","Access Control",{"type":14,"value":356,"toc":896},[357,361,364,369,372,398,402,408,414,420,426,430,433,439,456,462,476,482,493,497,500,557,561,564,578,582,585,608,612,615,664,668,671,791,794,797,826,830,836,839,876,879,882,885,889],[30,358,360],{"id":359},"what-is-access-control","What is Access Control?",[17,362,363],{},"Access control is the set of policies, procedures, and technical mechanisms that regulate who can access systems, data, and resources within an organization. It ensures that only authorized individuals can view, modify, or interact with sensitive information and critical systems. Access control is one of the most fundamental and universally required security controls across every major compliance framework.",[365,366,368],"h3",{"id":367},"what-are-the-core-principles-of-access-control","What are the core principles of access control?",[17,370,371],{},"Access control is built on several foundational principles:",[65,373,374,380,386,392],{},[68,375,376,379],{},[72,377,378],{},"Least privilege"," — users are granted only the minimum access necessary to perform their job functions",[68,381,382,385],{},[72,383,384],{},"Separation of duties"," — critical tasks are divided among multiple individuals to prevent any single person from having unchecked authority",[68,387,388,391],{},[72,389,390],{},"Need to know"," — access to information is restricted to those who require it for a specific purpose",[68,393,394,397],{},[72,395,396],{},"Default deny"," — access is denied by default unless explicitly granted",[365,399,401],{"id":400},"what-are-the-types-of-access-control","What are the types of access control?",[17,403,404,407],{},[72,405,406],{},"Role-Based Access Control (RBAC)"," — access is determined by the user's role within the organization. Roles are defined with specific permissions, and users are assigned to roles. This is the most common model in enterprise environments.",[17,409,410,413],{},[72,411,412],{},"Attribute-Based Access Control (ABAC)"," — access decisions are based on attributes of the user, the resource, and the environment (e.g., department, location, time of day, device type).",[17,415,416,419],{},[72,417,418],{},"Discretionary Access Control (DAC)"," — resource owners decide who can access their resources. Common in file systems where owners set permissions.",[17,421,422,425],{},[72,423,424],{},"Mandatory Access Control (MAC)"," — access is controlled by the system based on security labels and clearance levels. Common in government and military environments.",[365,427,429],{"id":428},"what-are-access-control-components","What are access control components?",[17,431,432],{},"A complete access control program addresses:",[17,434,435,438],{},[72,436,437],{},"Authentication"," — verifying the identity of users:",[65,440,441,444,447,450,453],{},[68,442,443],{},"Passwords and passphrases",[68,445,446],{},"Multi-factor authentication (MFA)",[68,448,449],{},"Single sign-on (SSO)",[68,451,452],{},"Biometric authentication",[68,454,455],{},"Certificate-based authentication",[17,457,458,461],{},[72,459,460],{},"Authorization"," — determining what authenticated users can do:",[65,463,464,467,470,473],{},[68,465,466],{},"Permission assignments",[68,468,469],{},"Role definitions",[68,471,472],{},"Access control lists",[68,474,475],{},"Policy enforcement points",[17,477,478,481],{},[72,479,480],{},"Access lifecycle management"," — managing access throughout the user lifecycle:",[65,483,484,487,490],{},[68,485,486],{},"Provisioning (granting access when hired or role changes)",[68,488,489],{},"Review (periodic access certification)",[68,491,492],{},"Deprovisioning (revoking access upon termination or role change)",[365,494,496],{"id":495},"how-do-compliance-frameworks-address-access-control","How do compliance frameworks address access control?",[17,498,499],{},"Every major framework requires access control:",[65,501,502,511,525,539,548],{},[68,503,504,510],{},[72,505,506],{},[46,507,509],{"href":508},"\u002Fframeworks\u002Fsoc2","SOC 2"," — CC6.1 through CC6.8 cover logical and physical access controls",[68,512,513,519,520,524],{},[72,514,515],{},[46,516,518],{"href":517},"\u002Fframeworks\u002Fiso27001","ISO 27001"," — ",[46,521,523],{"href":522},"\u002Fglossary\u002Fannex-a","Annex A"," controls A.5.15 through A.5.18 and A.8.2 through A.8.5 address access management",[68,526,527,533,534,538],{},[72,528,529],{},[46,530,532],{"href":531},"\u002Fframeworks\u002Fhipaa","HIPAA"," — the ",[46,535,537],{"href":536},"\u002Fframeworks\u002Fhipaa\u002Fsecurity-rule","Security Rule"," requires access controls for ePHI (45 CFR 164.312(a))",[68,540,541,547],{},[72,542,543],{},[46,544,546],{"href":545},"\u002Fframeworks\u002Fpci","PCI DSS"," — Requirements 7 and 8 address access restriction and user identification",[68,549,550,556],{},[72,551,552],{},[46,553,555],{"href":554},"\u002Fframeworks\u002Fnistcsf","NIST CSF"," — PR.AC covers identity management, authentication, and access control",[365,558,560],{"id":559},"what-are-access-reviews","What are access reviews?",[17,562,563],{},"Regular access reviews (also called access certifications) are a critical control:",[65,565,566,569,572,575],{},[68,567,568],{},"Review user access rights periodically (quarterly is common for sensitive systems)",[68,570,571],{},"Verify that access aligns with current job responsibilities",[68,573,574],{},"Identify and remove excessive or unnecessary access",[68,576,577],{},"Document review results and remediation actions",[365,579,581],{"id":580},"what-are-common-access-control-weaknesses","What are common access control weaknesses?",[17,583,584],{},"Even well-designed access control programs can degrade over time without ongoing attention. Watch for these common issues:",[65,586,587,590,593,596,599,602,605],{},[68,588,589],{},"Excessive permissions that accumulate over time (privilege creep)",[68,591,592],{},"Shared or generic accounts that prevent individual accountability",[68,594,595],{},"Delayed deprovisioning when employees leave or change roles",[68,597,598],{},"Lack of MFA on critical systems and remote access paths",[68,600,601],{},"Inconsistent access review processes with no documented remediation",[68,603,604],{},"Service accounts with standing privileged access and no rotation schedule",[68,606,607],{},"Lack of visibility into SaaS application access outside the corporate IdP",[365,609,611],{"id":610},"how-do-you-implement-access-control-in-practice","How do you implement access control in practice?",[17,613,614],{},"Effective access control programs start with planning and build toward automation. The following steps provide a practical roadmap for organizations at any maturity level:",[238,616,617,623,629,635,641,647,658],{},[68,618,619,622],{},[72,620,621],{},"Map your environment"," — inventory all systems, applications, and data repositories that require access controls. You cannot protect what you have not identified. Include SaaS applications, cloud infrastructure, on-premises servers, databases, file shares, and third-party integrations.",[68,624,625,628],{},[72,626,627],{},"Define roles based on job functions"," — create roles that reflect organizational responsibilities, not individual users. Align roles to the principle of least privilege so each role includes only the permissions required for that function. Review role definitions annually and whenever organizational structure changes.",[68,630,631,634],{},[72,632,633],{},"Centralize authentication with SSO"," — implement single sign-on using SAML 2.0 or OpenID Connect (OIDC) to unify identity across cloud and on-premises systems. Centralized authentication reduces password sprawl and gives security teams a single point of enforcement. Ensure all business-critical applications are integrated with your SSO provider before considering the rollout complete.",[68,636,637,640],{},[72,638,639],{},"Layer MFA on all critical systems"," — require multi-factor authentication for remote access, privileged accounts, email, cloud consoles, and any system that touches sensitive data. Phishing-resistant methods such as FIDO2 hardware keys are preferred over SMS-based codes. At a minimum, enforce MFA on identity providers, admin consoles, and VPN access.",[68,642,643,646],{},[72,644,645],{},"Automate provisioning and deprovisioning"," — connect your HR system to your identity provider (IdP) and use SCIM or directory sync to automate account creation, role assignment, and account removal. When an employee is terminated in the HR system, access should be revoked within minutes, not days. Automation eliminates the human error that leads to orphaned accounts and privilege creep.",[68,648,649,652,653,657],{},[72,650,651],{},"Build an access request and approval workflow"," — establish a formal process where users request access with documented business justification, managers approve, and the request is logged for audit. This creates an ",[46,654,656],{"href":655},"\u002Fglossary\u002Faudit-trail","audit trail"," that satisfies compliance requirements.",[68,659,660,663],{},[72,661,662],{},"Monitor and log access events"," — collect authentication and authorization logs centrally. Monitor for anomalies such as failed login attempts, access from unusual locations, and privilege escalation. Logs are essential for incident response and audit evidence.",[365,665,667],{"id":666},"what-are-the-access-control-requirements","What are the access control requirements?",[17,669,670],{},"Different frameworks address the same access control concepts with different control references. The table below maps common requirements to their framework-specific identifiers:",[672,673,674,694],"table",{},[675,676,677],"thead",{},[678,679,680,684,686,688,690,692],"tr",{},[681,682,683],"th",{},"Requirement",[681,685,509],{},[681,687,518],{},[681,689,532],{},[681,691,546],{},[681,693,555],{},[695,696,697,718,737,757,774],"tbody",{},[678,698,699,703,706,709,712,715],{},[700,701,702],"td",{},"Unique user IDs",[700,704,705],{},"CC6.1",[700,707,708],{},"A.5.16",[700,710,711],{},"§164.312(a)(2)(i)",[700,713,714],{},"Req 8.2.1",[700,716,717],{},"PR.AC-1",[678,719,720,723,725,728,731,734],{},[700,721,722],{},"MFA",[700,724,705],{},[700,726,727],{},"A.8.5",[700,729,730],{},"Addressable",[700,732,733],{},"Req 8.4",[700,735,736],{},"PR.AC-7",[678,738,739,742,745,748,751,754],{},[700,740,741],{},"Access reviews",[700,743,744],{},"CC6.2",[700,746,747],{},"A.5.18",[700,749,750],{},"§164.312(a)(1)",[700,752,753],{},"Req 7.2",[700,755,756],{},"PR.AC-4",[678,758,759,761,764,767,769,772],{},[700,760,378],{},[700,762,763],{},"CC6.3",[700,765,766],{},"A.5.15",[700,768,750],{},[700,770,771],{},"Req 7.1",[700,773,756],{},[678,775,776,779,781,783,786,789],{},[700,777,778],{},"Deprovisioning",[700,780,744],{},[700,782,747],{},[700,784,785],{},"§164.312(a)(2)(ii)",[700,787,788],{},"Req 8.2.6",[700,790,717],{},[17,792,793],{},"Organizations subject to multiple frameworks can use this mapping to build a unified access control program that satisfies overlapping requirements without duplicating effort.",[17,795,796],{},"A few notes on framework-specific nuances:",[65,798,799,804,812,819],{},[68,800,801,803],{},[72,802,532],{}," treats MFA as an \"addressable\" implementation specification, meaning covered entities must implement it or document why an equivalent alternative is reasonable. In practice, most organizations implement MFA because the risk of not doing so is difficult to justify.",[68,805,806,811],{},[72,807,808,810],{},[46,809,546],{"href":545}," v4.0"," expanded MFA requirements (Req 8.4) to include all access into the cardholder data environment, not just remote access. Organizations processing card data should verify their MFA coverage meets the updated scope.",[68,813,814,818],{},[72,815,816],{},[46,817,509],{"href":508}," does not prescribe specific technologies but evaluates whether the controls in place are suitably designed and operating effectively. Auditors will look for evidence that access control policies are enforced consistently.",[68,820,821,825],{},[72,822,823],{},[46,824,555],{"href":554}," provides a flexible, risk-based approach. The PR.AC subcategory identifiers map to more detailed controls in NIST SP 800-53, which organizations can reference for implementation guidance.",[365,827,829],{"id":828},"how-does-zero-trust-relate-to-access-control","How does zero trust relate to access control?",[17,831,832,833,170],{},"Traditional access control models assume that users inside the network perimeter can be trusted. Zero trust architecture rejects that assumption entirely: ",[72,834,835],{},"never trust, always verify",[17,837,838],{},"In a zero trust model, every access request is authenticated, authorized, and encrypted regardless of where it originates. Key principles include:",[65,840,841,847,853,864,870],{},[68,842,843,846],{},[72,844,845],{},"Continuous verification"," — access decisions are re-evaluated throughout a session, not just at login. Changes in user behavior, location, or risk score can trigger step-up authentication or session termination.",[68,848,849,852],{},[72,850,851],{},"Micro-segmentation"," — network resources are divided into small, isolated zones so that compromising one segment does not grant lateral access to others.",[68,854,855,858,859,863],{},[72,856,857],{},"Device posture checks"," — the security state of the connecting device (patch level, endpoint protection status, disk ",[46,860,862],{"href":861},"\u002Fglossary\u002Fencryption","encryption",") is evaluated before access is granted.",[68,865,866,869],{},[72,867,868],{},"Identity-centric perimeter"," — the network perimeter is replaced by identity as the primary security boundary. Every user, device, and workload must prove its identity before accessing any resource.",[68,871,872,875],{},[72,873,874],{},"Least privilege enforcement at the session level"," — access grants are scoped to the specific resource and action needed, and they expire when the session ends or conditions change.",[17,877,878],{},"NIST SP 800-207 defines the zero trust architecture and provides guidance on implementation. Many compliance frameworks are increasingly aligning their access control requirements with zero trust principles, making it a forward-looking strategy for organizations building or modernizing their access control programs.",[17,880,881],{},"Zero trust is not a single product but an architectural approach that spans identity, network, endpoints, and data.",[17,883,884],{},"Adopting zero trust does not require replacing your existing access control infrastructure overnight. Most organizations begin by enforcing MFA universally, segmenting their most sensitive assets, and adding device posture checks to their conditional access policies. Over time, these incremental improvements compound into a mature zero trust posture.",[365,886,888],{"id":887},"how-does-episki-help-with-access-control","How does episki help with access control?",[17,890,891,892,170],{},"episki evaluates access rather than inventorying it. Identity evidence from Google, Microsoft, and AWS IAM across multiple accounts is collected and then checked, writing pass, fail, or inconclusive against the control — and a check that finds over-broad access raises a finding naming the specific principals. An unreadable or empty response returns inconclusive rather than passing, so an access control is never attested by a collection that failed. Learn more on our ",[46,893,895],{"href":894},"\u002Fframeworks","compliance platform",{"title":315,"searchDepth":316,"depth":316,"links":897},[898],{"id":359,"depth":316,"text":360,"children":899},[900,902,903,904,905,906,907,908,909,910],{"id":367,"depth":901,"text":368},3,{"id":400,"depth":901,"text":401},{"id":428,"depth":901,"text":429},{"id":495,"depth":901,"text":496},{"id":559,"depth":901,"text":560},{"id":580,"depth":901,"text":581},{"id":610,"depth":901,"text":611},{"id":666,"depth":901,"text":667},{"id":828,"depth":901,"text":829},{"id":887,"depth":901,"text":888},"2026-08-31",{},"\u002Fglossary\u002Faccess-control",[915,916,917,918,919,920],"cmmc","soc2","iso27001","hipaa","pci","nistcsf",[922,923,862,924],"minimum-necessary-rule","audit-trail","user-entity-controls",{"title":926,"description":927},"Access Control in Compliance: RBAC, MFA & Least Privilege","Access control restricts system and data access to authorized users. Learn RBAC, MFA, least privilege, and requirements across SOC 2, ISO 27001, HIPAA, and PCI DSS.","access-control","8.glossary\u002Faccess-control","9s8m0GbTkTfzK-1ANXSdpQhsVk3cqHqMcU4xDE8iDn0",{"id":932,"title":523,"body":933,"description":315,"extension":331,"lastUpdated":911,"meta":1079,"navigation":335,"path":522,"relatedFrameworks":1080,"relatedTerms":1081,"seo":1086,"slug":1089,"stem":1090,"term":938,"__hash__":1091},"glossary\u002F8.glossary\u002Fannex-a.md",{"type":14,"value":934,"toc":1069},[935,939,950,954,957,983,987,990,1007,1010,1014,1017,1021,1024,1038,1041,1045,1058,1062],[30,936,938],{"id":937},"what-is-iso-27001-annex-a","What is ISO 27001 Annex A?",[17,940,941,942,944,945,949],{},"ISO 27001 Annex A is the normative annex to the ",[46,943,518],{"href":517}," standard that provides a reference list of information security controls. Organizations use Annex A as a checklist to ensure their ",[46,946,948],{"href":947},"\u002Fframeworks\u002Fiso27001\u002Fisms-implementation","Information Security Management System (ISMS)"," addresses a comprehensive range of security topics. As of the 2022 revision, Annex A contains 93 controls organized into four themes.",[365,951,953],{"id":952},"what-are-the-four-themes","What are the four themes?",[17,955,956],{},"The 2022 revision reorganized controls from the previous 14 categories into four themes:",[65,958,959,965,971,977],{},[68,960,961,964],{},[72,962,963],{},"Organizational controls (37 controls)"," — policies, roles and responsibilities, threat intelligence, information security in project management, supplier relationships, and more",[68,966,967,970],{},[72,968,969],{},"People controls (8 controls)"," — screening, terms and conditions of employment, security awareness training, disciplinary processes, and responsibilities after termination",[68,972,973,976],{},[72,974,975],{},"Physical controls (14 controls)"," — physical security perimeters, entry controls, securing offices and facilities, equipment protection, and clear desk policies",[68,978,979,982],{},[72,980,981],{},"Technological controls (34 controls)"," — user endpoint devices, privileged access management, access restrictions, secure authentication, malware protection, logging, encryption, and secure development",[365,984,986],{"id":985},"how-does-annex-a-fit-into-iso-27001","How does Annex A fit into ISO 27001?",[17,988,989],{},"Annex A is not a standalone list of mandatory controls. Instead, it works in conjunction with the risk assessment process defined in clauses 6 and 8 of ISO 27001:",[238,991,992,995,998,1001,1004],{},[68,993,994],{},"The organization performs a risk assessment to identify information security risks",[68,996,997],{},"The organization determines how to treat each risk (mitigate, accept, transfer, or avoid)",[68,999,1000],{},"For risks being mitigated, the organization selects appropriate controls",[68,1002,1003],{},"The organization compares selected controls against Annex A to ensure nothing has been overlooked",[68,1005,1006],{},"The results are documented in the Statement of Applicability",[17,1008,1009],{},"This approach ensures that control selection is risk-driven rather than checkbox-driven. An organization may determine that certain Annex A controls are not applicable based on their specific risk profile, and this is acceptable as long as the justification is documented.",[365,1011,1013],{"id":1012},"how-does-annex-a-relate-to-iso-27002","How does Annex A relate to ISO 27002?",[17,1015,1016],{},"ISO 27002 provides detailed implementation guidance for each Annex A control. While Annex A lists the controls with brief descriptions, ISO 27002 explains the purpose, guidance, and other information for each control. Think of Annex A as the \"what\" and ISO 27002 as the \"how.\"",[365,1018,1020],{"id":1019},"what-changed-in-the-2022-revision-of-annex-a","What changed in the 2022 revision of Annex A?",[17,1022,1023],{},"The 2022 update introduced several changes from the 2013 version:",[65,1025,1026,1029,1032,1035],{},[68,1027,1028],{},"Controls were consolidated from 114 to 93",[68,1030,1031],{},"The 14 categories were replaced with 4 themes",[68,1033,1034],{},"11 new controls were added, including threat intelligence, information security for cloud services, ICT readiness for business continuity, and data masking",[68,1036,1037],{},"Each control now includes attributes (control type, cybersecurity concept, operational capability, and security domain) to aid in filtering and mapping",[17,1039,1040],{},"Organizations certified under the 2013 version had a transition period to update their ISMS to align with the 2022 revision.",[365,1042,1044],{"id":1043},"what-is-the-statement-of-applicability","What is the Statement of Applicability?",[17,1046,1047,1048,1052,1053,1057],{},"The ",[46,1049,1051],{"href":1050},"\u002Fframeworks\u002Fiso27001\u002Fstatement-of-applicability","Statement of Applicability (SoA)"," is the document where an organization records which Annex A controls are applicable, which are not, and the justification for each decision. The SoA is a mandatory document for ",[46,1054,1056],{"href":1055},"\u002Fframeworks\u002Fiso27001\u002Fcertification-process","ISO 27001 certification"," and is a key artifact reviewed during certification audits.",[365,1059,1061],{"id":1060},"how-does-episki-help-with-annex-a","How does episki help with Annex A?",[17,1063,1064,1065,170],{},"episki maps Annex A to controls evaluated on every sync across your connected estate, with evidence reused by every other framework that claims the same control. A check whose evidence comes back empty or unreadable returns inconclusive and attests nothing, so an Annex A control is never marked satisfied by a collection that silently failed. Learn more about the ",[46,1066,1068],{"href":1067},"\u002Fframeworks\u002Fiso27001\u002Fannex-a-controls","Annex A controls",{"title":315,"searchDepth":316,"depth":316,"links":1070},[1071],{"id":937,"depth":316,"text":938,"children":1072},[1073,1074,1075,1076,1077,1078],{"id":952,"depth":901,"text":953},{"id":985,"depth":901,"text":986},{"id":1012,"depth":901,"text":1013},{"id":1019,"depth":901,"text":1020},{"id":1043,"depth":901,"text":1044},{"id":1060,"depth":901,"text":1061},{},[917],[917,1082,1083,1084,1085],"statement-of-applicability","iso-27002","control-objectives","isms",{"title":1087,"description":1088},"ISO 27001 Annex A: All 93 Controls Explained (2022)","ISO 27001 Annex A lists 93 security controls in 4 themes. Learn each control category, how they map to your Statement of Applicability, and implementation tips.","annex-a","8.glossary\u002Fannex-a","ninWoLuGbIvkJx3djy7wTT090WPcFjANjfzM_i_lOn4",[],{"id":1094,"title":1095,"body":1096,"comparison":1288,"competitorA":1189,"competitorB":1201,"cta":1336,"description":315,"extension":331,"faq":1339,"hero":1357,"lastUpdated":911,"meta":1373,"navigation":335,"path":1374,"seo":1375,"slug":1378,"slugA":1379,"slugB":1380,"stem":1381,"verdict":1382,"__hash__":1386},"compareVs\u002F7.compare\u002Fvs\u002Fdrata-vs-secureframe.md","Drata Vs Secureframe",{"type":14,"value":1097,"toc":1278},[1098,1102,1105,1109,1112,1118,1121,1125,1128,1131,1134,1138,1141,1144,1148,1151,1223,1226,1229,1233,1236,1239,1243,1246,1249,1252],[30,1099,1101],{"id":1100},"drata-vs-secureframe-the-closest-comparison-in-compliance","Drata vs Secureframe: the closest comparison in compliance",[17,1103,1104],{},"If Vanta is the 800-pound gorilla, Drata and Secureframe are the two challengers most often compared against each other. They target similar buyers, cover similar frameworks, and offer similar automation. The differences are real but subtle — and they matter most in how your team experiences the platform day to day.",[365,1106,1108],{"id":1107},"feature-parity-with-different-emphasis","Feature parity with different emphasis",[17,1110,1111],{},"On paper, Drata and Secureframe look nearly identical. Both automate evidence collection, monitor your compliance posture continuously, support 15+ frameworks, and provide auditor-facing portals. The overlap is so significant that choosing between them often comes down to three factors: onboarding style, dashboard experience, and pricing.",[17,1113,1114,1117],{},[72,1115,1116],{},"Onboarding style"," is the clearest differentiator. Drata leans toward self-serve. The platform guides you through integration setup, control mapping, and evidence configuration with in-app workflows. For teams with compliance experience, this speed is an advantage — you can be operational in 1–2 weeks without waiting for a human to walk you through every step.",[17,1119,1120],{},"Secureframe takes the opposite approach. Every customer gets access to dedicated compliance managers who help interpret requirements, map controls to your environment, and prepare for audit. This white-glove model adds a week or two to implementation but dramatically reduces the learning curve for first-time audit teams.",[365,1122,1124],{"id":1123},"the-dashboard-question","The dashboard question",[17,1126,1127],{},"Drata's compliance dashboard is one of its signature features. The real-time posture view shows passing and failing controls across every framework, with compliance percentages and trend data. For compliance leads who report to a CISO or board, this visual layer simplifies status updates and makes it easy to demonstrate progress.",[17,1129,1130],{},"Secureframe also provides dashboards, but they feel more functional than visual. The platform surfaces actionable items — controls that need attention, evidence that's expiring, gaps to remediate — in a task-oriented format. It's effective, but it doesn't deliver the same at-a-glance executive view that Drata provides.",[17,1132,1133],{},"For teams that need board-ready compliance reporting, Drata has the edge. For teams that care more about daily workflow and task management, Secureframe's approach may feel more productive.",[365,1135,1137],{"id":1136},"integration-depth","Integration depth",[17,1139,1140],{},"Both platforms now connect to hundreds of tools: Secureframe advertises 300+ integrations, and Drata says it integrates with hundreds. At that scale, raw counts rarely decide it. Check that the specific CI\u002FCD pipelines, vulnerability scanners, and endpoint management tools in your stack are covered natively, because any gap there becomes manual evidence collection.",[17,1142,1143],{},"Drata's integrations, while fewer in number, tend to offer deeper configuration options for the platforms they do support. If your stack is standard — AWS or GCP, Okta or Google Workspace, GitHub, and a common HR tool — both platforms will serve you equally well.",[365,1145,1147],{"id":1146},"pricing-opacity","Pricing opacity",[17,1149,1150],{},"Neither Drata nor Secureframe publishes pricing. Both require a sales conversation to get a quote, and both scale based on team size, framework count, and contract terms. Here's how the major platforms compare on 2026 pricing, based on market data:",[672,1152,1153,1169],{},[675,1154,1155],{},[678,1156,1157,1160,1163,1166],{},[681,1158,1159],{},"Platform",[681,1161,1162],{},"Typical entry price (2026)",[681,1164,1165],{},"Pricing model",[681,1167,1168],{},"Published?",[695,1170,1171,1185,1197,1209],{},[678,1172,1173,1176,1179,1182],{},[700,1174,1175],{},"Vanta",[700,1177,1178],{},"~$11,000–$15,000\u002Fyr",[700,1180,1181],{},"Per-seat + framework, custom quote",[700,1183,1184],{},"No",[678,1186,1187,1190,1193,1195],{},[700,1188,1189],{},"Drata",[700,1191,1192],{},"~$10,000–$15,000\u002Fyr",[700,1194,1181],{},[700,1196,1184],{},[678,1198,1199,1202,1205,1207],{},[700,1200,1201],{},"Secureframe",[700,1203,1204],{},"~$8,000–$12,000\u002Fyr",[700,1206,1181],{},[700,1208,1184],{},[678,1210,1211,1214,1217,1220],{},[700,1212,1213],{},"episki",[700,1215,1216],{},"$750\u002Fmo ($7,500\u002Fyr)",[700,1218,1219],{},"Flat platform + modules, unlimited seats",[700,1221,1222],{},"Yes",[17,1224,1225],{},"At scale, Vanta, Drata, and Secureframe all reach $30,000–$50,000\u002Fyr for larger organizations. Secureframe usually starts slightly cheaper than Drata at the entry tier, but because both scale on seats and frameworks, the gap narrows quickly as your team grows.",[17,1227,1228],{},"This pricing opacity creates a frustrating buying experience. You can't model costs internally before engaging sales. You can't easily compare options. And renewal conversations often involve price increases that are hard to predict at the time of initial purchase.",[365,1230,1232],{"id":1231},"where-both-platforms-struggle","Where both platforms struggle",[17,1234,1235],{},"The irony of comparing Drata and Secureframe is that their most significant limitations are shared. Both use pricing models that punish team growth. Both rely on templated control libraries that resist customization. Both treat policy documentation as a secondary concern — something generated through forms rather than crafted through a proper writing experience.",[17,1237,1238],{},"And both lock you into their workflow assumptions. If your compliance program doesn't map cleanly to their templates — if you run hybrid frameworks, need custom controls, or want to structure programs differently than the default — you'll spend time working around the platform instead of working within it.",[365,1240,1242],{"id":1241},"the-case-for-a-different-approach","The case for a different approach",[17,1244,1245],{},"When two products are this similar, the deciding factor often isn't which one is better — it's whether either one is the right category of tool for your needs. If you want maximum automation and are comfortable with enterprise pricing, Drata and Secureframe both deliver.",[17,1247,1248],{},"But if you want GRC that runs itself, episki offers something neither Drata nor Secureframe provides. Where legacy GRC automates evidence, episki automates the program: agents draft policies, answer security questionnaires, map controls, manage vendors, and keep evidence evergreen — while your team approves the work that matters. The AI authors deterministic recipes that then run without AI in the loop, so output is reproducible and auditor-acceptable. A dedicated AI Governance module (agent and use-case registry, ISO 42001, NIST AI RMF, EU AI Act) covers the governance work neither competitor was built for.",[17,1250,1251],{},"It comes with flat pricing at $750\u002Fmo plus optional modules, unlimited seats, and a Notion-like editor for the documentation your team owns. No per-seat scaling. No opaque quotes. No templated policies that read like every other company's — just a program that runs itself, at a price that doesn't make your CFO wince.",[17,1253,1254,1257,1258,1262,1263,1267,1268,1272,1273,1277],{},[72,1255,1256],{},"Related reading:"," dig deeper into each platform's competitors in our ",[46,1259,1261],{"href":1260},"\u002Fblog\u002Fdrata-alternatives","Drata alternatives"," and ",[46,1264,1266],{"href":1265},"\u002Fblog\u002Fsecureframe-alternatives","Secureframe alternatives"," guides, see where both rank in the ",[46,1269,1271],{"href":1270},"\u002Fblog\u002Fbest-grc-tools-2026","best GRC tools of 2026",", or compare ",[46,1274,1276],{"href":1275},"\u002Fcompare\u002Fvs\u002Fvanta-vs-drata","Vanta vs Drata"," if Vanta is also on your shortlist.",{"title":315,"searchDepth":316,"depth":316,"links":1279},[1280],{"id":1100,"depth":316,"text":1101,"children":1281},[1282,1283,1284,1285,1286,1287],{"id":1107,"depth":901,"text":1108},{"id":1123,"depth":901,"text":1124},{"id":1136,"depth":901,"text":1137},{"id":1146,"depth":901,"text":1147},{"id":1231,"depth":901,"text":1232},{"id":1241,"depth":901,"text":1242},[1289,1293,1297,1302,1307,1311,1316,1321,1326,1331],{"feature":1165,"competitorA":1290,"competitorB":1291,"episki":1292},"Custom pricing, typically starting around $10,000–$15,000\u002Fyr","Custom pricing, typically starting around $8,000–$12,000\u002Fyr","Flat $750\u002Fmo ($7,500\u002Fyr) platform + optional modules; unlimited users, frameworks, and vendors",{"feature":1294,"competitorA":1295,"competitorB":1295,"episki":1296},"Framework coverage","SOC 2, ISO 27001, HIPAA, PCI DSS, GDPR, and 15+ frameworks","34+ pre-built frameworks (SOC 2, ISO 27001, HIPAA, PCI DSS, NIST CSF, CMMC, FedRAMP, ISO 42001) plus custom",{"feature":1298,"competitorA":1299,"competitorB":1300,"episki":1301},"Automation depth","Automated evidence collection with real-time compliance dashboards","Automated monitoring with continuous evidence collection and alerts","Autonomous GRC — agents draft, answer, and map across the program; humans approve",{"feature":1303,"competitorA":1304,"competitorB":1305,"episki":1306},"Integration count","Hundreds of integrations covering major cloud and SaaS platforms","300+ integrations covering cloud, identity, HR, and developer tools","AWS (multi-account and Organizations), GitHub, Google, Microsoft, Slack, Teams, Jira, Linear, Supabase, Vercel, Netlify — each writing evaluated control coverage",{"feature":1308,"competitorA":1309,"competitorB":1309,"episki":1310},"Control verdicts","Continuous monitoring with pass\u002Ffail tests on a posture dashboard","Every check writes pass, fail, or inconclusive against the control and raises a finding when it fails — empty or unreadable evidence attests nothing, and an approved exception that expires can satisfy a check for named records",{"feature":1312,"competitorA":1313,"competitorB":1314,"episki":1315},"Auditor collaboration","Auditor-facing portal with read-only access and evidence downloads","Auditor-ready evidence rooms with structured access controls","Built-in auditor portal with scoped access and Q&A threads",{"feature":1317,"competitorA":1318,"competitorB":1319,"episki":1320},"AI features","AI-assisted control mapping and compliance recommendations","AI-driven compliance recommendations and automated risk scoring","Agents draft policies, answer questionnaires, map controls, and recommend tasks — AI authors deterministic recipes auditors can accept",{"feature":1322,"competitorA":1323,"competitorB":1324,"episki":1325},"Implementation time","1–3 weeks with self-serve setup and optional guided onboarding","2–3 weeks with guided onboarding and compliance expertise","Same-day setup with self-serve onboarding and optional demo",{"feature":1327,"competitorA":1328,"competitorB":1329,"episki":1330},"Support model","In-app chat, email support, and dedicated CSM for larger accounts","Dedicated compliance managers, email, and in-app support","Self-serve by design, in-app chat, plus vetted Operator Partners (vCISO\u002FvGRC) for advisory",{"feature":1332,"competitorA":1333,"competitorB":1334,"episki":1335},"Free trial","Demo-based sales process, limited free trial availability","Demo-based sales process, no public free trial","14-day free trial with full access, no credit card required",{"title":1337,"description":1338},"Skip the comparison. Try episki free.","14-day trial with full access. No credit card required.",{"title":1340,"items":1341},"Drata vs Secureframe pricing FAQ (2026)",[1342,1345,1348,1351,1354],{"label":1343,"content":1344},"How much does Drata cost in 2026?","Drata does not publish pricing. Based on 2026 market data, plans typically start around $10,000–$15,000\u002Fyr and scale with team size and framework count, reaching $30,000–$50,000\u002Fyr for larger organizations. You need a sales conversation to get a firm quote.",{"label":1346,"content":1347},"How much does Secureframe cost in 2026?","Secureframe also keeps pricing private. In 2026 it typically starts slightly lower than Drata, around $8,000–$12,000\u002Fyr, and scales with seats and frameworks. Expect $30,000–$50,000\u002Fyr at enterprise scale.",{"label":1349,"content":1350},"How do Vanta, Drata, and Secureframe pricing compare in 2026?","All three use custom, per-seat-plus-framework pricing and none publish rates. Rough 2026 entry points: Vanta ~$11,000–$15,000\u002Fyr, Drata ~$10,000–$15,000\u002Fyr, Secureframe ~$8,000–$12,000\u002Fyr. The common thread is that costs rise as your team grows. episki is the outlier at a flat $750\u002Fmo ($7,500\u002Fyr) for the platform plus optional modules, with unlimited seats and published pricing.",{"label":1352,"content":1353},"Which is cheaper, Drata or Secureframe?","At the entry tier, Secureframe is usually slightly cheaper than Drata. But both scale on seats and frameworks, so the gap narrows or reverses depending on your team size and contract. Neither is predictable without a quote — which is why some teams choose a flat-priced platform instead.",{"label":1355,"content":1356},"Do Drata or Secureframe offer a free trial?","Neither offers a true public free trial — both run a demo-led sales process. If you want to evaluate hands-on before committing, episki offers a 14-day free trial with full access and no credit card.",{"headline":1358,"title":1359,"description":1360,"links":1361},"Drata vs Secureframe","Similar features, different approaches to compliance automation","Compare Drata and Secureframe across pricing, onboarding, and compliance workflows. Two closely matched platforms with subtle but important differences for your team.",[1362,1367],{"label":1363,"icon":1364,"to":1365,"target":1366},"Book a demo","i-lucide-calendar","\u002Fdemo","_blank",{"label":1368,"icon":1369,"color":1370,"variant":1371,"to":1372},"Try episki free","i-lucide-rocket","neutral","subtle","https:\u002F\u002Fapp.episki.com\u002Fauth\u002Fregister",{},"\u002Fcompare\u002Fvs\u002Fdrata-vs-secureframe",{"title":1376,"description":1377},"Drata vs Secureframe: Pricing & Evidence Automation","Drata vs Secureframe on pricing, automated evidence collection, onboarding, and framework coverage. A side-by-side table and which team each one fits.","drata-vs-secureframe","drata","secureframe","7.compare\u002Fvs\u002Fdrata-vs-secureframe",{"chooseA":1383,"chooseB":1384,"chooseEpiski":1385},"Choose Drata if you value self-serve speed and visual compliance dashboards. Drata gets you operational faster and provides the clearest real-time view of your compliance posture — ideal for teams with in-house compliance knowledge.","Choose Secureframe if you want more hands-on guidance from dedicated compliance managers. Secureframe's human-led onboarding is better for teams running their first audit without experienced GRC staff.","Choose episki if you want GRC that runs itself — agents draft policies, answer questionnaires, and keep evidence evergreen while your team approves the work that matters. You get transparent flat pricing ($750\u002Fmo plus optional modules, unlimited seats) and a dedicated AI Governance module.","l-c3Qw1KfFCqWQlH82pSvFRHsRkvIaxScWlhnZbmUMI",{"id":1388,"title":1389,"advantages":1390,"body":1412,"comparison":1475,"competitor":1389,"cta":1523,"description":315,"extension":331,"faq":1526,"hero":1544,"lastUpdated":911,"meta":1552,"navigation":335,"path":1553,"seo":1554,"slug":1557,"stem":1558,"__hash__":1559},"compare\u002F7.compare\u002Farcher.md","Archer",[1391,1398,1405],{"title":1392,"description":1393,"bullets":1394},"Start this afternoon, not next quarter","Archer's power comes from configurability, and configurability has to be configured. episki is opinionated on purpose — sensible defaults, self-serve onboarding, and an agent drafting your first policy in minutes.",[1395,1396,1397],"Self-serve signup with no implementation project and no onboarding fee","34+ frameworks pre-built, adopted through a wizard rather than modeled by a consultant","Same-day setup, with a 14-day free trial and no credit card",{"title":1399,"description":1400,"bullets":1401},"A program that advances without a risk department","Archer assumes a staffed risk function operating it. episki assumes you do not have one — the agents draft the work and a human approves it.",[1402,1403,1404],"Agents draft policies, narratives, and questionnaire answers from your own evidence","Vendor reviews advance over email, with inbound attachments triaged and linked with provenance","AI authors deterministic recipes; the recipes then run without AI in the loop, so auditors can trust the output",{"title":1406,"description":1407,"bullets":1408},"A verdict you can defend, not just a green check","episki evaluates the evidence it collects and writes an explicit verdict, closing the failure modes that let a check pass without proving anything.",[1409,1410,1411],"Empty, undecodable, or partially collected evidence returns inconclusive and attests nothing","A failing check raises a finding with the offending records attached","An approved exception can satisfy a check for named records — but it needs an approver and it expires",{"type":14,"value":1413,"toc":1470},[1414,1418,1421,1424,1427,1447,1451,1454,1457,1460,1463,1467],[30,1415,1417],{"id":1416},"why-teams-evaluate-archer-alternatives","Why teams evaluate Archer alternatives",[17,1419,1420],{},"Archer is one of the originals in integrated risk management, and at the top of the market it earns its position: operational risk, IT risk, third-party risk, and regulatory compliance modeled together, configurable to almost any taxonomy, deployable on-premises where that is mandatory.",[17,1422,1423],{},"That power has a shape. Deployments are configuration projects measured in months, frequently with a partner. Pricing is modular and custom, commonly reported from $75,000 into the hundreds of thousands per year. And reviewers consistently describe the interface as dated with a steep learning curve — which matters when the people who need to file evidence are engineers, not risk analysts.",[17,1425,1426],{},"Most teams evaluating Archer alongside episki are not choosing between equals. They are asking whether they need an enterprise IRM platform at all, or whether they need the compliance program to run itself.",[65,1428,1429,1435,1441],{},[68,1430,1431,1434],{},[72,1432,1433],{},"No implementation project"," — self-serve signup, sensible defaults, first policy drafted in minutes",[68,1436,1437,1440],{},[72,1438,1439],{},"A published price"," — $7,500\u002Fyr for the platform, unlimited users and frameworks",[68,1442,1443,1446],{},[72,1444,1445],{},"Agents that do the drafting"," — instead of workflows that route it to a person",[30,1448,1450],{"id":1449},"where-episki-is-different","Where episki is different",[17,1452,1453],{},"episki does not try to be Archer. It makes the opposite bet: rather than configurability for a risk department, opinionated defaults plus agents that do the work.",[17,1455,1456],{},"Those agents draft policies, answer security questionnaires, map controls across frameworks, and advance vendor reviews over email between audits. The AI authors deterministic recipes — plain, inspectable procedures — that then run without a model in the loop, so an auditor reads how an artifact was gathered rather than trusting a generation.",[17,1458,1459],{},"And every control check produces a verdict. Each integration operation decodes its response, evaluates its assertions, and writes pass, fail, or inconclusive. Empty evidence attests nothing. An incomplete sync cannot mark a control clean. A failing check raises a finding with the offending records attached. An approved exception, bound to an approver and an expiry, can satisfy a check for named records without pretending the condition changed.",[17,1461,1462],{},"Boundaries are real: programs report against individual scopes with rules on cloud account, region, resource, and tag — enough to define a PCI cardholder data environment precisely, without modeling a taxonomy first.",[30,1464,1466],{"id":1465},"when-archer-might-still-be-the-better-fit","When Archer might still be the better fit",[17,1468,1469],{},"If you are a large enterprise with a staffed risk function, need operational and regulatory risk modeled alongside IT risk, or have a hard on-premises requirement, Archer is the more capable platform and episki is not a substitute. The honest dividing line is whether you are buying a risk modeling system for a department, or an operator for a small team.",{"title":315,"searchDepth":316,"depth":316,"links":1471},[1472,1473,1474],{"id":1416,"depth":316,"text":1417},{"id":1449,"depth":316,"text":1450},{"id":1465,"depth":316,"text":1466},[1476,1480,1484,1487,1491,1495,1499,1503,1507,1511,1515,1519],{"feature":1477,"episki":1478,"competitor":1479},"Approach","Autonomous GRC — agents run the program; humans approve the work that matters","Integrated risk management — a configurable enterprise platform spanning operational, IT, third-party, and regulatory risk",{"feature":1481,"episki":1482,"competitor":1483},"Built for","Security and compliance teams from one person to a few hundred employees, who need the program to advance without headcount","Large enterprises with a staffed risk function and a multi-year GRC roadmap",{"feature":1165,"episki":1485,"competitor":1486},"Published — platform $750\u002Fmo (or $7,500\u002Fyr) + optional modules; unlimited users and frameworks, with AI tokens the only metered resource","Custom enterprise licensing, modular by use case, commonly reported from $75,000 to $300,000+ per year depending on modules, users, and deployment",{"feature":1488,"episki":1489,"competitor":1490},"Time to value","Same-day — self-serve signup, connect a cloud account, and an agent drafts your first policy in minutes","A configuration and implementation project, frequently measured in months and often involving a partner",{"feature":1492,"episki":1493,"competitor":1494},"Deployment","Cloud, with optional regional data residency for US, EU, or Canada","On-premises or SaaS, which is a genuine advantage where on-prem is mandatory",{"feature":1496,"episki":1497,"competitor":1498},"Who does the work","Agents draft policies, narratives, questionnaire answers, and control mappings; a human approves","Your risk and compliance team, inside highly configurable workflows",{"feature":1500,"episki":1501,"competitor":1502},"Risk management","Risk module — qualitative and quantitative scoring, treatments, and acceptance wired to controls and evidence","The deepest integrated risk model in the category, connecting operational, IT, third-party, and regulatory risk in one framework",{"feature":1504,"episki":1505,"competitor":1506},"Controls & evidence","Continuous controls that produce a verdict — every check evaluates the evidence it collected and writes pass, fail, or inconclusive, and a failing check raises a finding. Empty or undecodable evidence attests nothing","Control and assessment management, with automated technical evidence collection depending on configuration and add-ons",{"feature":1508,"episki":1509,"competitor":1510},"AI capabilities","Agents draft, answer, and map — and the AI authors deterministic recipes that then run without a model in the loop, so output is reproducible","AI features layered onto an established enterprise platform",{"feature":1512,"episki":1513,"competitor":1514},"Integrations","AWS (multi-account, multi-region, and Organizations), GitHub, Google, Microsoft, Slack, Teams, Jira, Linear, Supabase, Vercel, and Netlify — each writing evaluated control coverage out of the box","Extensive integration capability, typically realized through configuration and professional services",{"feature":1516,"episki":1517,"competitor":1518},"User experience","Notion-like, keyboard-first editor, a global command palette, and a desktop app with tabs","A mature interface that reviewers consistently describe as dated, with a steep learning curve",{"feature":1520,"episki":1521,"competitor":1522},"API & agent access","REST API, a published entity-ontology catalog with a drift checksum, and a hosted MCP server whose writes route through the same API as the UI","REST API and enterprise integration tooling",{"title":1524,"description":1525},"Enterprise-grade, without the enterprise project","Start a free trial and let an agent draft your first policy in under five minutes. No credit card required.",{"title":1527,"items":1528},"episki vs Archer — frequently asked questions",[1529,1532,1535,1538,1541],{"label":1530,"content":1531},"Is episki a realistic alternative to Archer?","For a large enterprise running a mature, multi-domain integrated risk program, generally no — Archer's risk model is deeper and its configurability is the reason organizations buy it. For the far more common case of a security or compliance team that has been quoted six figures for capability they will not use, episki covers the compliance, risk, vendor, trust, and AI governance ground at a published $7,500\u002Fyr and requires no implementation project.",{"label":1533,"content":1534},"How different is the cost really?","Substantially. Archer deployments are commonly reported between $75,000 and $300,000+ per year depending on modules, users, and deployment model, before implementation services. episki's platform is $7,500\u002Fyr with unlimited users and unlimited frameworks, with optional modules published on the pricing page and no onboarding or implementation fee.",{"label":1536,"content":1537},"What does Archer do that episki does not?","Three things worth naming honestly. Archer's integrated risk model connects operational, IT, third-party, and regulatory risk more deeply than episki's Risk module. Archer supports on-premises deployment, which episki does not. And Archer's configurability lets a large organization model risk taxonomies and workflows that episki deliberately keeps opinionated.",{"label":1539,"content":1540},"What does episki do that Archer does not?","The work. episki's agents draft policies, answer security questionnaires, map controls across frameworks, and advance vendor reviews between audits, with humans approving what matters. Every control check evaluates its own evidence and writes an explicit pass, fail, or inconclusive verdict, and connectors for AWS, GitHub, Supabase, Vercel, Netlify, Jira, and Linear write evaluated control coverage out of the box rather than through configuration.",{"label":1542,"content":1543},"When is Archer the better choice?","When you are a large enterprise — typically financial services, healthcare, or critical infrastructure — with a staffed risk function, a requirement to model operational and regulatory risk alongside IT risk, or a hard on-premises deployment requirement. Those are real needs and Archer is built for them.",{"headline":1545,"title":1546,"description":1547,"links":1548},"episki vs Archer","Two different weight classes, and that is the point","Archer is deep integrated risk management for large enterprises, deployed over months and priced accordingly. episki is Autonomous GRC you can start this afternoon — agents run the program, and the price is on the website.",[1549,1550],{"label":1363,"icon":1364,"to":1365,"target":1366},{"label":1551,"icon":1369,"color":1370,"variant":1371,"to":1372},"Start free trial",{},"\u002Fcompare\u002Farcher",{"title":1555,"description":1556},"episki vs Archer (2026): Autonomous GRC vs Enterprise Risk Management","episki vs Archer: flat $750\u002Fmo self-serve vs Archer's six-figure enterprise IRM deployments. Compare implementation, autonomy, and who each is actually built for.","archer","7.compare\u002Farcher","X-XyGkrH428bktnKyiu-R4eTwNtfC5e4fPwZSHDxMVo",{"id":1561,"title":1562,"api":6,"authors":1563,"body":1566,"category":328,"date":1808,"description":1809,"extension":331,"faq":6,"features":6,"fixes":6,"highlight":6,"image":1810,"improvements":6,"meta":1812,"navigation":335,"path":1813,"seo":1814,"stem":1815,"summary":6,"updated":6,"__hash__":1816},"posts\u002F3.blog\u002Fsecurity-questionnaires.md","Security Questionnaires: Stop Starting From Scratch",[1564],{"name":9,"to":10,"avatar":1565},{"src":12},{"type":14,"value":1567,"toc":1799},[1568,1571,1574,1577,1580,1584,1587,1590,1619,1622,1625,1629,1632,1638,1644,1650,1656,1659,1663,1666,1669,1672,1691,1694,1697,1701,1704,1710,1716,1722,1728,1734,1738,1741,1767,1770,1774,1777,1780,1782,1785,1788,1796],[17,1569,1570],{},"It always shows up on a Thursday.",[17,1572,1573],{},"A sales rep forwards an email with a spreadsheet attached and one line on top: \"Customer needs this back by Monday to keep the deal moving.\" You open it. Fourteen tabs. 312 questions. Column F says \"Comments (required).\" Somewhere around row 40 you realize you answered this exact questionnaire eight months ago, for a different customer, in a different format, and nobody knows where that file went.",[17,1575,1576],{},"So the weekend goes to retyping answers about encryption at rest.",[17,1578,1579],{},"Questionnaires look very different depending on whether you are the buyer sending them or the vendor answering them. Here is my honest take: security questionnaires are not hard. They are repetitive, and most companies treat every single one like it's the first one they have ever seen. That's the real problem, and it's very fixable.",[30,1581,1583],{"id":1582},"every-questionnaire-is-the-same-questionnaire","Every questionnaire is the same questionnaire",[17,1585,1586],{},"The SIG has hundreds of questions. The CAIQ is built on the CSA Cloud Controls Matrix. The HECVAT is the higher ed version. And then there's your customer's own custom spreadsheet, which is usually a remix of all three plus a few questions their legal team added after reading a headline.",[17,1588,1589],{},"Different logos, same core topics:",[65,1591,1592,1595,1598,1601,1604,1607,1610,1613,1616],{},[68,1593,1594],{},"Access control and MFA",[68,1596,1597],{},"Encryption in transit and at rest",[68,1599,1600],{},"Logging and monitoring",[68,1602,1603],{},"Vulnerability management and penetration testing",[68,1605,1606],{},"Incident response",[68,1608,1609],{},"Business continuity and backups",[68,1611,1612],{},"Vendor management",[68,1614,1615],{},"Policies, training, and HR security",[68,1617,1618],{},"Data handling, retention, and privacy",[17,1620,1621],{},"Once you have answered three or four questionnaires, you have answered roughly 80% of every future questionnaire. The wording changes. The underlying question does not. \"Do you encrypt customer data at rest?\" and \"Describe the cryptographic controls protecting stored data\" want the same answer, with the same evidence behind it.",[17,1623,1624],{},"If your team is writing that answer from scratch every time, you're not doing security work. You're doing data entry with extra anxiety.",[30,1626,1628],{"id":1627},"why-it-still-eats-your-week","Why it still eats your week",[17,1630,1631],{},"If the questions repeat, why does every questionnaire still feel like a fire drill? In my experience, it comes down to four things.",[17,1633,1634,1637],{},[72,1635,1636],{},"The answers live in people's heads."," The person who knows how backups work is in engineering. The person who knows the incident response process is in security. The person who knows the vendor review process left in March. So the questionnaire turns into a scavenger hunt across Slack.",[17,1639,1640,1643],{},[72,1641,1642],{},"Last time's answers are lost."," They're in someone's downloads folder, in an email thread, or uploaded to a customer portal you can't log into anymore. You know you have answered this before. You just can't prove it.",[17,1645,1646,1649],{},[72,1647,1648],{},"Nobody owns it."," Sales owns the deadline. Security owns the truth. Neither owns the process. So it lands on whoever is most responsible and least able to say no.",[17,1651,1652,1655],{},[72,1653,1654],{},"Every format is different."," One customer sends Excel. One sends a fillable PDF. One sends a portal with a 30 minute session timeout. Even when you have good answers, moving them into a new format takes hours.",[17,1657,1658],{},"None of this is a security problem. It's an operations problem wearing a security costume.",[30,1660,1662],{"id":1661},"the-real-risk-is-not-the-time","The real risk is not the time",[17,1664,1665],{},"Here's the part people skip. Speed is nice, but accuracy is what matters.",[17,1667,1668],{},"Your questionnaire answers are not a marketing brochure. In a lot of deals, they get attached to the contract, referenced in the security addendum, or relied on during a vendor risk review. If you answer \"Yes, MFA is enforced for all users\" and it's actually enforced for 90% of users, you have made a promise you're not keeping. When something goes wrong, that answer will be the first document someone pulls.",[17,1670,1671],{},"The pressure of a Monday deadline pushes teams toward two bad habits:",[238,1673,1674,1680],{},[68,1675,1676,1679],{},[72,1677,1678],{},"Optimistic yes."," \"We're rolling that out next quarter, so... yes.\" It's not yes. It's \"partially, with a plan,\" and you should say exactly that.",[68,1681,1682,1685,1686,1690],{},[72,1683,1684],{},"Copying someone else's answers."," Template answers from the internet, or from a previous employer, that describe a program you don't run. I've written about where that road ends in ",[46,1687,1689],{"href":1688},"\u002Fblog\u002Ffake-compliance-as-a-service","Fake Compliance as a Service",". It's the same problem at a smaller scale.",[17,1692,1693],{},"A good answer is boring, specific, and true. \"MFA is enforced for all workforce accounts through our identity provider. Service accounts are excluded and are restricted by IP allowlist and key rotation every 90 days.\" That's an answer a reviewer trusts, because it sounds like someone actually runs it.",[17,1695,1696],{},"And here's a secret from the buyer side: reviewers can smell a canned answer. A clear \"No, but here's our compensating control and our target date\" builds more trust than a wall of yeses that don't match your SOC 2 report.",[30,1698,1700],{"id":1699},"build-an-answer-library-not-a-filing-cabinet","Build an answer library, not a filing cabinet",[17,1702,1703],{},"The fix is not heroic. It's a library.",[17,1705,1706,1709],{},[72,1707,1708],{},"Start with your strongest sources."," Pull answers from documents that have already been reviewed: your SOC 2 report, your ISO 27001 Statement of Applicability, your policies, your last penetration test summary. If an answer traces back to an audited document, it's defensible.",[17,1711,1712,1715],{},[72,1713,1714],{},"Write 50 to 100 standard answers."," Cover the core topics above. Keep each one short, specific, and written in plain English. Add the evidence that backs it up and the control it maps to.",[17,1717,1718,1721],{},[72,1719,1720],{},"Give every answer an owner and a review date."," Encryption answers belong to engineering. Incident response answers belong to security. Review the library at least quarterly, and any time something real changes, like a new identity provider or a new data center region. An answer library that is two years old is just a nicer way to be wrong.",[17,1723,1724,1727],{},[72,1725,1726],{},"Mark the gaps honestly."," When a question isn't covered by your documents, flag it for a human decision. Don't let anyone, human or tool, invent an answer to fill the cell.",[17,1729,1730,1733],{},[72,1731,1732],{},"Save every finished questionnaire back into the library."," Each one you answer should make the next one faster. If it doesn't, the library isn't really a library.",[30,1735,1737],{"id":1736},"give-it-one-owner-and-a-simple-process","Give it one owner and a simple process",[17,1739,1740],{},"You don't need a committee. You need one owner and four steps:",[238,1742,1743,1749,1755,1761],{},[68,1744,1745,1748],{},[72,1746,1747],{},"Intake."," Sales sends the questionnaire to one place, with the due date and the deal size. Not a DM to whoever answered last time.",[68,1750,1751,1754],{},[72,1752,1753],{},"Draft."," The owner drafts answers from the library and marks anything new or uncertain.",[68,1756,1757,1760],{},[72,1758,1759],{},"Review."," Subject matter experts review only the marked items. Engineering should spend 20 minutes on the five questions that need them, not three hours on all 312.",[68,1762,1763,1766],{},[72,1764,1765],{},"Send and save."," The final version goes back to the customer in their format, and the new answers go back into the library.",[17,1768,1769],{},"Bonus points for publishing what you can up front. A trust page with your SOC 2 report available under NDA, your policies summary, and your subprocessor list will head off a surprising number of questionnaires before they're ever sent. The best questionnaire is the one the buyer decides they don't need.",[30,1771,1773],{"id":1772},"where-ai-helps-and-where-it-doesnt","Where AI helps, and where it doesn't",[17,1775,1776],{},"AI is genuinely good at this job when it works from your documents. Matching a new question to an answer you already approved, drafting from your policies and audit reports, and filling the original spreadsheet in place: that's exactly the kind of repetitive work machines should do.",[17,1778,1779],{},"It is genuinely bad at this job when it works from general knowledge. A model that \"knows\" what a typical company does will happily tell your customer that you have a 24\u002F7 SOC. Drafts should come from your sources, gaps should be flagged instead of guessed, and a human who knows the environment should approve every answer before it leaves the building. Agents draft. Humans own the answers.",[30,1781,307],{"id":306},[17,1783,1784],{},"Security questionnaires aren't going away. If anything, every new AI regulation and vendor risk program is adding questions. But the work doesn't have to grow with them.",[17,1786,1787],{},"Treat questionnaires as a repeatable process, not a weekend emergency. Answer from your real documents. Say no when the answer is no. Save everything so the next one is faster.",[17,1789,1790,1791,1795],{},"And if one is holding up a deal right now, ",[46,1792,1794],{"href":1793},"\u002Ftools\u002Fsecurity-questionnaire","send us your security questionnaire",". We'll draft the answers from your own documents and send it back in the original file, with the gaps marked for you. Your first one is free.",[17,1797,1798],{},"Your weekend will thank you.",{"title":315,"searchDepth":316,"depth":316,"links":1800},[1801,1802,1803,1804,1805,1806,1807],{"id":1582,"depth":316,"text":1583},{"id":1627,"depth":316,"text":1628},{"id":1661,"depth":316,"text":1662},{"id":1699,"depth":316,"text":1700},{"id":1736,"depth":316,"text":1737},{"id":1772,"depth":316,"text":1773},{"id":306,"depth":316,"text":307},"2026-11-17","SIG, CAIQ, HECVAT, or your customer's own 300 question spreadsheet. Why security questionnaires eat your week, how to answer them faster without overpromising, and the answer library every growing company should build.",{"src":1811},"\u002Fimages\u002Fblog\u002Fsecurity-questionnaires.webp",{},"\u002Fblog\u002Fsecurity-questionnaires",{"title":1562,"description":1809},"3.blog\u002Fsecurity-questionnaires","2faHkFfdYqeKwayD0BvLpf3eK7VQIlVrkrUdgpJUbFo",{"id":1818,"title":1819,"advantages":1820,"body":1842,"checklist":1849,"cta":1858,"description":1846,"extension":331,"faq":6,"hero":1861,"lastUpdated":911,"meta":1870,"name":1871,"navigation":335,"path":1872,"resources":1873,"seo":1886,"slug":1889,"stats":1890,"stem":1900,"__hash__":1901},"industries\u002F6.industry\u002F1.healthcare.md","Healthcare",[1821,1828,1835],{"title":1822,"description":1823,"bullets":1824},"PHI-aware control mapping","Map administrative, technical, and physical safeguards to your stack without rebuilding every audit.",[1825,1826,1827],"Track EHR, identity, and cloud evidence with structured ownership","Track segmentation, backups, and log retention against HIPAA safeguards","Map once for HIPAA and reuse for HITRUST or regional requirements",{"title":1829,"description":1830,"bullets":1831},"Clinician-friendly workflows","Keep nurses, clinicians, and ops aligned without burying them in tickets.",[1832,1833,1834],"Role-aware tasks routed to the right owner with due dates","Playbooks show “what good looks like” for PHI handling","Attestations and approvals captured inline for auditors",{"title":1836,"description":1837,"bullets":1838},"Auditor and partner collaboration","Give regulators, payers, and partners scoped access instead of email threads.",[1839,1840,1841],"Auditor portal with threaded Q&A per safeguard","Secure uploads with expirations and access controls","Exports for SOC 2, PCI, or privacy questionnaires",{"type":14,"value":1843,"toc":1847},[1844],[17,1845,1846],{},"Healthcare buyers move fast when they trust your safeguards. episki keeps PHI protections documented, monitored, and shareable without slowing product or patient care.",{"title":315,"searchDepth":316,"depth":316,"links":1848},[],{"title":1850,"description":1851,"items":1852},"Healthtech compliance checklist","Use this inside your trial to assign owners, attach evidence, and track renewals.",[1853,1854,1855,1856,1857],"HIPAA safeguard library mapped to your systems","BAA tracker with renewal reminders and risk scoring","Incident response runbooks with timelines and owners","Access, logging, and backup verification tasks","Third-party risk reviews tied to PHI data flows",{"title":1859,"description":1860},"Launch a healthtech-ready workspace","Connect your stack, invite stakeholders, and show PHI protections the same day.",{"headline":1862,"title":1863,"description":1864,"links":1865},"HIPAA-grade governance without slowing clinicians","Keep PHI protections provable across cloud apps, clinics, and vendors","episki maps safeguards, automates evidence, and gives auditors scoped access so healthtech teams can keep shipping.",[1866,1868],{"label":1867,"icon":1369,"to":1372},"Start healthtech trial",{"label":1363,"icon":1869,"color":1370,"variant":1371,"to":1365,"target":1366},"i-lucide-message-circle",{},"healthcare and healthtech","\u002Findustry\u002Fhealthcare",{"headline":1874,"title":1874,"description":1875,"items":1876},"Healthcare enablement kit","Keep leadership, clinicians, and auditors aligned on the same story.",[1877,1880,1883],{"title":1878,"description":1879},"PHI data flow deck","Share sanitized diagrams plus segmentation notes for customers and partners.",{"title":1881,"description":1882},"Board + payer brief","Summarize control health, incidents, and remediation in plain language.",{"title":1884,"description":1885},"Auditor-ready workspace","Prebuilt template for requests, evidence, and walkthrough scheduling.",{"title":1887,"description":1888},"Healthcare Compliance Software","HIPAA-ready GRC for healthtech teams. Map safeguards, track PHI evidence, and collaborate with auditors in one secure workspace. Start your free trial.","healthcare",[1891,1894,1897],{"value":1892,"description":1893},"30-day rollout","Move from baseline controls to monitored safeguards in under a month.",{"value":1895,"description":1896},"PHI-safe sharing","Role-based portals keep BAAs, policies, and diagrams organized and protected.",{"value":1898,"description":1899},"Continuous watch","Drift detection across access, logging, vendors, and incidents.","6.industry\u002F1.healthcare","u08a7hidKILzMlQgEwXI8WBgv7i08HXpMKdsEpMA3Tw",1795055229407]