[{"data":1,"prerenderedAt":1959},["ShallowReactive",2],{"\u002Fblog\u002F2026-09-03-pipeline":3,"blog-surround-2026-09-03-pipeline":167,"explore-glossary-none-\u002Fblog\u002F2026-09-03-pipeline":178,"explore-topics-none-\u002Fblog\u002F2026-09-03-pipeline":923,"explore-hub-none":6,"explore-compare-vs-\u002Fblog\u002F2026-09-03-pipeline":924,"explore-compare-\u002Fblog\u002F2026-09-03-pipeline":1218,"explore-blog-none-\u002Fblog\u002F2026-09-03-pipeline":1391,"explore-industry-none":1874},{"id":4,"title":5,"api":6,"authors":7,"body":13,"category":155,"date":156,"description":157,"extension":158,"faq":6,"features":6,"fixes":6,"highlight":6,"image":159,"improvements":6,"meta":161,"navigation":162,"path":163,"seo":164,"stem":165,"__hash__":166},"posts\u002F3.blog\u002F2026-09-03- Pipeline.md","Securing the Pipeline: Why DevSecOps Is No Longer Optional",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":146},"minimark",[16,20,23,26,29,34,37,40,43,47,50,57,63,69,75,81,85,88,91,94,98,101,104,107,111,114,117,122,133,140],[17,18,19],"p",{},"Speed is the default setting of modern software development.",[17,21,22],{},"Code ships daily. Infrastructure spins up on demand. Features move from idea to production in days, not months. And somewhere in that velocity, security is supposed to keep up — reviewing changes, catching vulnerabilities, approving deployments — without slowing anything down.",[17,24,25],{},"For most organizations, that's where the model breaks. Security becomes a gate at the end of the process rather than a guardrail throughout it. Vulnerabilities get caught late, when they're expensive to fix. Controls get added after deployment, when they're harder to enforce. And the security team spends most of its time reacting to problems that could have been prevented earlier.",[17,27,28],{},"Securing the pipeline is the answer to that problem. Here's what it actually takes.",[30,31,33],"h2",{"id":32},"the-cost-of-bolting-security-on-at-the-end","The Cost of Bolting Security On at the End",[17,35,36],{},"The traditional software delivery model puts security at the end of the process — a final review before release, a penetration test before launch, a compliance check before the product goes live. It made sense when releases happened quarterly and teams had time to slow down. It doesn't make sense anymore.",[17,38,39],{},"When security is a final gate, several things happen predictably. Vulnerabilities discovered late are more expensive to fix — estimates consistently put the cost of remediating a security issue in production at ten to a hundred times the cost of catching it during development. Developers experience security as a blocker rather than a partner, which creates the adversarial dynamic that makes everything harder. And the security team is always playing catch-up, reviewing work that's already done rather than shaping work that's in progress.",[17,41,42],{},"The organizations that have solved this problem didn't do it by making the final gate bigger. They moved security earlier — into the pipeline itself.",[30,44,46],{"id":45},"what-securing-the-pipeline-actually-means","What Securing the Pipeline Actually Means",[17,48,49],{},"DevSecOps — the integration of security into DevOps practices — is the framework most organizations use to describe this shift. But the term has become generic enough to mean almost anything, so it's worth being precise about what actually needs to happen.",[17,51,52,56],{},[53,54,55],"strong",{},"Static analysis in the development environment."," Developers should be getting security feedback while they write code, not after they've committed it. Tools that run in the IDE or as part of the commit process — scanning for known vulnerability patterns, insecure configurations, hardcoded secrets — catch issues at the point where they're cheapest and easiest to fix.",[17,58,59,62],{},[53,60,61],{},"Automated security testing in CI\u002FCD."," Every code change that moves through the pipeline should trigger automated security checks — dependency scanning, container image scanning, infrastructure-as-code analysis, SAST and DAST where appropriate. These checks should be fast enough to not meaningfully slow the pipeline and clear enough that developers know exactly what failed and why.",[17,64,65,68],{},[53,66,67],{},"Secrets management integrated into the build process."," Hardcoded credentials and API keys in source code remain one of the most common and most avoidable causes of security incidents. A mature pipeline enforces secrets management — pulling credentials from a vault at runtime rather than baking them into the code or the image.",[17,70,71,74],{},[53,72,73],{},"Policy as code."," Security and compliance requirements that are manually reviewed before deployment will be inconsistently applied and will create bottlenecks. Encoding those requirements as automated policies — infrastructure configurations that must meet certain standards before they can deploy, images that must pass certain checks before they can run — makes compliance continuous rather than periodic.",[17,76,77,80],{},[53,78,79],{},"Security gates that are proportionate to risk."," Not every deployment carries the same risk profile. A pipeline that applies the same level of scrutiny to a frontend copy change and a change to authentication logic will create friction in the wrong places and miss risk in the right ones. Effective pipeline security is risk-proportionate — more rigorous checks for higher-risk changes, lighter-touch automation for lower-risk ones.",[30,82,84],{"id":83},"the-cultural-shift-is-harder-than-the-technical-one","The Cultural Shift Is Harder Than the Technical One",[17,86,87],{},"Organizations that struggle with DevSecOps usually don't fail because of the tools. They fail because of the model.",[17,89,90],{},"Shifting security left requires security teams to operate differently — less as auditors reviewing finished work, more as enablers helping developers ship securely. It requires developers to take ownership of security outcomes in their own code, not hand them off to a separate team. And it requires leadership to align on the idea that security and speed are not fundamentally in tension — that a well-secured pipeline is actually faster over time, because it catches problems before they become incidents.",[17,92,93],{},"That cultural alignment doesn't happen by installing a scanner. It happens through deliberate relationship-building between security and engineering teams, through security champions embedded in development teams, through metrics that measure security outcomes rather than security activities, and through leadership that reinforces the message that security is everyone's job.",[30,95,97],{"id":96},"where-to-start","Where to Start",[17,99,100],{},"For security leaders who want to move in this direction but aren't sure where to begin, the temptation is to try to transform everything at once. That rarely works.",[17,102,103],{},"A more effective approach starts with a specific team or a specific pipeline — one where the engineering relationship is strong enough to absorb some friction during the transition, and where the risk profile makes the investment clearly worthwhile. Instrument that pipeline, measure what you find, demonstrate the value, and use that proof of concept to drive adoption across the organization.",[17,105,106],{},"The goal isn't a perfect pipeline on day one. It's a pipeline that gets measurably more secure over time, without getting measurably slower — and a security team that's seen as a partner in shipping, not an obstacle to it.",[30,108,110],{"id":109},"security-that-ships-with-the-code","Security That Ships With the Code",[17,112,113],{},"The organizations that are best at software security aren't the ones with the most rigorous pre-release reviews. They're the ones where security is embedded so deeply in how software gets built that it's hard to separate from the development process itself.",[17,115,116],{},"That's the goal of securing the pipeline — not more checkpoints, but better defaults. Not more gates, but smarter guardrails. Security that ships with the code, because it was part of how the code was written.",[17,118,119],{},[53,120,121],{},"Ready to build a pipeline where security and speed work together?",[17,123,124,125,132],{},"At ",[126,127,131],"a",{"href":128,"rel":129},"https:\u002F\u002Fepiski.com",[130],"nofollow","Episki",", we help security leaders design and implement DevSecOps programs that fit the way their engineering teams actually work — reducing risk without creating friction. If you're ready to stop bolting security on at the end, let's talk.",[17,134,135],{},[126,136,139],{"href":137,"rel":138},"https:\u002F\u002Fepiski.com\u002Fcontact",[130],"Let's talk →",[17,141,142],{},[143,144,145],"em",{},"The best time to catch a vulnerability is before it ships. The best way to do that is to build security into how you ship.",{"title":147,"searchDepth":148,"depth":148,"links":149},"",2,[150,151,152,153,154],{"id":32,"depth":148,"text":33},{"id":45,"depth":148,"text":46},{"id":83,"depth":148,"text":84},{"id":96,"depth":148,"text":97},{"id":109,"depth":148,"text":110},"craft","2026-09-03","Security can't afford to wait until after deployment. Here's how forward-thinking security leaders are embedding controls directly into the development pipeline — and why it matters more than ever.","md",{"src":160},"public\u002Fimages\u002Fchangelog\u002FPotential.jpg",{},true,"\u002Fblog\u002F2026-09-03-pipeline",{"title":5,"description":157},"3.blog\u002F2026-09-03- Pipeline","UpGamvS014RDc6U2dJsxo1cjOJLGfbYcwn5-ytr6sBM",[168,173],{"title":169,"path":170,"stem":171,"description":172,"children":-1},"Cloud Evidence That Actually Evaluates","\u002Fblog\u002F2026-08-31-cloud-evidence-agent-skills","3.blog\u002F2026-08-31-cloud-evidence-agent-skills","Multi-account AWS, Supabase, Vercel, Netlify, and GitHub connectors now write real control verdicts — and a failing check raises a finding instead of quietly passing. Plus agent skills, approved exceptions that satisfy a check, per-boundary program reporting, and a desktop app with tabs.",{"title":174,"path":175,"stem":176,"description":177,"children":-1},"Turning Security into a Core Competency","\u002Fblog\u002F2026-09-03-security","3.blog\u002F2026-09-03-Security","Security stops being a cost center the moment it becomes something the organization is genuinely good at. Here's what it takes to move from reactive to exceptional.",[179,762],{"id":180,"title":181,"body":182,"description":147,"extension":158,"lastUpdated":742,"meta":743,"navigation":162,"path":744,"relatedFrameworks":745,"relatedTerms":752,"seo":756,"slug":759,"stem":760,"term":187,"__hash__":761},"glossary\u002F8.glossary\u002Faccess-control.md","Access Control",{"type":14,"value":183,"toc":727},[184,188,191,196,199,227,231,237,243,249,255,259,262,268,285,291,305,311,322,326,329,386,390,393,407,411,414,437,441,444,494,498,501,621,624,627,656,660,667,670,707,710,713,716,720],[30,185,187],{"id":186},"what-is-access-control","What is Access Control?",[17,189,190],{},"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.",[192,193,195],"h3",{"id":194},"what-are-the-core-principles-of-access-control","What are the core principles of access control?",[17,197,198],{},"Access control is built on several foundational principles:",[200,201,202,209,215,221],"ul",{},[203,204,205,208],"li",{},[53,206,207],{},"Least privilege"," — users are granted only the minimum access necessary to perform their job functions",[203,210,211,214],{},[53,212,213],{},"Separation of duties"," — critical tasks are divided among multiple individuals to prevent any single person from having unchecked authority",[203,216,217,220],{},[53,218,219],{},"Need to know"," — access to information is restricted to those who require it for a specific purpose",[203,222,223,226],{},[53,224,225],{},"Default deny"," — access is denied by default unless explicitly granted",[192,228,230],{"id":229},"what-are-the-types-of-access-control","What are the types of access control?",[17,232,233,236],{},[53,234,235],{},"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,238,239,242],{},[53,240,241],{},"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,244,245,248],{},[53,246,247],{},"Discretionary Access Control (DAC)"," — resource owners decide who can access their resources. Common in file systems where owners set permissions.",[17,250,251,254],{},[53,252,253],{},"Mandatory Access Control (MAC)"," — access is controlled by the system based on security labels and clearance levels. Common in government and military environments.",[192,256,258],{"id":257},"what-are-access-control-components","What are access control components?",[17,260,261],{},"A complete access control program addresses:",[17,263,264,267],{},[53,265,266],{},"Authentication"," — verifying the identity of users:",[200,269,270,273,276,279,282],{},[203,271,272],{},"Passwords and passphrases",[203,274,275],{},"Multi-factor authentication (MFA)",[203,277,278],{},"Single sign-on (SSO)",[203,280,281],{},"Biometric authentication",[203,283,284],{},"Certificate-based authentication",[17,286,287,290],{},[53,288,289],{},"Authorization"," — determining what authenticated users can do:",[200,292,293,296,299,302],{},[203,294,295],{},"Permission assignments",[203,297,298],{},"Role definitions",[203,300,301],{},"Access control lists",[203,303,304],{},"Policy enforcement points",[17,306,307,310],{},[53,308,309],{},"Access lifecycle management"," — managing access throughout the user lifecycle:",[200,312,313,316,319],{},[203,314,315],{},"Provisioning (granting access when hired or role changes)",[203,317,318],{},"Review (periodic access certification)",[203,320,321],{},"Deprovisioning (revoking access upon termination or role change)",[192,323,325],{"id":324},"how-do-compliance-frameworks-address-access-control","How do compliance frameworks address access control?",[17,327,328],{},"Every major framework requires access control:",[200,330,331,340,354,368,377],{},[203,332,333,339],{},[53,334,335],{},[126,336,338],{"href":337},"\u002Fframeworks\u002Fsoc2","SOC 2"," — CC6.1 through CC6.8 cover logical and physical access controls",[203,341,342,348,349,353],{},[53,343,344],{},[126,345,347],{"href":346},"\u002Fframeworks\u002Fiso27001","ISO 27001"," — ",[126,350,352],{"href":351},"\u002Fglossary\u002Fannex-a","Annex A"," controls A.5.15 through A.5.18 and A.8.2 through A.8.5 address access management",[203,355,356,362,363,367],{},[53,357,358],{},[126,359,361],{"href":360},"\u002Fframeworks\u002Fhipaa","HIPAA"," — the ",[126,364,366],{"href":365},"\u002Fframeworks\u002Fhipaa\u002Fsecurity-rule","Security Rule"," requires access controls for ePHI (45 CFR 164.312(a))",[203,369,370,376],{},[53,371,372],{},[126,373,375],{"href":374},"\u002Fframeworks\u002Fpci","PCI DSS"," — Requirements 7 and 8 address access restriction and user identification",[203,378,379,385],{},[53,380,381],{},[126,382,384],{"href":383},"\u002Fframeworks\u002Fnistcsf","NIST CSF"," — PR.AC covers identity management, authentication, and access control",[192,387,389],{"id":388},"what-are-access-reviews","What are access reviews?",[17,391,392],{},"Regular access reviews (also called access certifications) are a critical control:",[200,394,395,398,401,404],{},[203,396,397],{},"Review user access rights periodically (quarterly is common for sensitive systems)",[203,399,400],{},"Verify that access aligns with current job responsibilities",[203,402,403],{},"Identify and remove excessive or unnecessary access",[203,405,406],{},"Document review results and remediation actions",[192,408,410],{"id":409},"what-are-common-access-control-weaknesses","What are common access control weaknesses?",[17,412,413],{},"Even well-designed access control programs can degrade over time without ongoing attention. Watch for these common issues:",[200,415,416,419,422,425,428,431,434],{},[203,417,418],{},"Excessive permissions that accumulate over time (privilege creep)",[203,420,421],{},"Shared or generic accounts that prevent individual accountability",[203,423,424],{},"Delayed deprovisioning when employees leave or change roles",[203,426,427],{},"Lack of MFA on critical systems and remote access paths",[203,429,430],{},"Inconsistent access review processes with no documented remediation",[203,432,433],{},"Service accounts with standing privileged access and no rotation schedule",[203,435,436],{},"Lack of visibility into SaaS application access outside the corporate IdP",[192,438,440],{"id":439},"how-do-you-implement-access-control-in-practice","How do you implement access control in practice?",[17,442,443],{},"Effective access control programs start with planning and build toward automation. The following steps provide a practical roadmap for organizations at any maturity level:",[445,446,447,453,459,465,471,477,488],"ol",{},[203,448,449,452],{},[53,450,451],{},"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.",[203,454,455,458],{},[53,456,457],{},"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.",[203,460,461,464],{},[53,462,463],{},"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.",[203,466,467,470],{},[53,468,469],{},"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.",[203,472,473,476],{},[53,474,475],{},"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.",[203,478,479,482,483,487],{},[53,480,481],{},"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 ",[126,484,486],{"href":485},"\u002Fglossary\u002Faudit-trail","audit trail"," that satisfies compliance requirements.",[203,489,490,493],{},[53,491,492],{},"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.",[192,495,497],{"id":496},"what-are-the-access-control-requirements","What are the access control requirements?",[17,499,500],{},"Different frameworks address the same access control concepts with different control references. The table below maps common requirements to their framework-specific identifiers:",[502,503,504,524],"table",{},[505,506,507],"thead",{},[508,509,510,514,516,518,520,522],"tr",{},[511,512,513],"th",{},"Requirement",[511,515,338],{},[511,517,347],{},[511,519,361],{},[511,521,375],{},[511,523,384],{},[525,526,527,548,567,587,604],"tbody",{},[508,528,529,533,536,539,542,545],{},[530,531,532],"td",{},"Unique user IDs",[530,534,535],{},"CC6.1",[530,537,538],{},"A.5.16",[530,540,541],{},"§164.312(a)(2)(i)",[530,543,544],{},"Req 8.2.1",[530,546,547],{},"PR.AC-1",[508,549,550,553,555,558,561,564],{},[530,551,552],{},"MFA",[530,554,535],{},[530,556,557],{},"A.8.5",[530,559,560],{},"Addressable",[530,562,563],{},"Req 8.4",[530,565,566],{},"PR.AC-7",[508,568,569,572,575,578,581,584],{},[530,570,571],{},"Access reviews",[530,573,574],{},"CC6.2",[530,576,577],{},"A.5.18",[530,579,580],{},"§164.312(a)(1)",[530,582,583],{},"Req 7.2",[530,585,586],{},"PR.AC-4",[508,588,589,591,594,597,599,602],{},[530,590,207],{},[530,592,593],{},"CC6.3",[530,595,596],{},"A.5.15",[530,598,580],{},[530,600,601],{},"Req 7.1",[530,603,586],{},[508,605,606,609,611,613,616,619],{},[530,607,608],{},"Deprovisioning",[530,610,574],{},[530,612,577],{},[530,614,615],{},"§164.312(a)(2)(ii)",[530,617,618],{},"Req 8.2.6",[530,620,547],{},[17,622,623],{},"Organizations subject to multiple frameworks can use this mapping to build a unified access control program that satisfies overlapping requirements without duplicating effort.",[17,625,626],{},"A few notes on framework-specific nuances:",[200,628,629,634,642,649],{},[203,630,631,633],{},[53,632,361],{}," 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.",[203,635,636,641],{},[53,637,638,640],{},[126,639,375],{"href":374}," 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.",[203,643,644,648],{},[53,645,646],{},[126,647,338],{"href":337}," 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.",[203,650,651,655],{},[53,652,653],{},[126,654,384],{"href":383}," 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.",[192,657,659],{"id":658},"how-does-zero-trust-relate-to-access-control","How does zero trust relate to access control?",[17,661,662,663,666],{},"Traditional access control models assume that users inside the network perimeter can be trusted. Zero trust architecture rejects that assumption entirely: ",[53,664,665],{},"never trust, always verify",".",[17,668,669],{},"In a zero trust model, every access request is authenticated, authorized, and encrypted regardless of where it originates. Key principles include:",[200,671,672,678,684,695,701],{},[203,673,674,677],{},[53,675,676],{},"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.",[203,679,680,683],{},[53,681,682],{},"Micro-segmentation"," — network resources are divided into small, isolated zones so that compromising one segment does not grant lateral access to others.",[203,685,686,689,690,694],{},[53,687,688],{},"Device posture checks"," — the security state of the connecting device (patch level, endpoint protection status, disk ",[126,691,693],{"href":692},"\u002Fglossary\u002Fencryption","encryption",") is evaluated before access is granted.",[203,696,697,700],{},[53,698,699],{},"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.",[203,702,703,706],{},[53,704,705],{},"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,708,709],{},"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,711,712],{},"Zero trust is not a single product but an architectural approach that spans identity, network, endpoints, and data.",[17,714,715],{},"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.",[192,717,719],{"id":718},"how-does-episki-help-with-access-control","How does episki help with access control?",[17,721,722,723,666],{},"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 ",[126,724,726],{"href":725},"\u002Fframeworks","compliance platform",{"title":147,"searchDepth":148,"depth":148,"links":728},[729],{"id":186,"depth":148,"text":187,"children":730},[731,733,734,735,736,737,738,739,740,741],{"id":194,"depth":732,"text":195},3,{"id":229,"depth":732,"text":230},{"id":257,"depth":732,"text":258},{"id":324,"depth":732,"text":325},{"id":388,"depth":732,"text":389},{"id":409,"depth":732,"text":410},{"id":439,"depth":732,"text":440},{"id":496,"depth":732,"text":497},{"id":658,"depth":732,"text":659},{"id":718,"depth":732,"text":719},"2026-08-31",{},"\u002Fglossary\u002Faccess-control",[746,747,748,749,750,751],"cmmc","soc2","iso27001","hipaa","pci","nistcsf",[753,754,693,755],"minimum-necessary-rule","audit-trail","user-entity-controls",{"title":757,"description":758},"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":763,"title":352,"body":764,"description":147,"extension":158,"lastUpdated":742,"meta":910,"navigation":162,"path":351,"relatedFrameworks":911,"relatedTerms":912,"seo":917,"slug":920,"stem":921,"term":769,"__hash__":922},"glossary\u002F8.glossary\u002Fannex-a.md",{"type":14,"value":765,"toc":900},[766,770,781,785,788,814,818,821,838,841,845,848,852,855,869,872,876,889,893],[30,767,769],{"id":768},"what-is-iso-27001-annex-a","What is ISO 27001 Annex A?",[17,771,772,773,775,776,780],{},"ISO 27001 Annex A is the normative annex to the ",[126,774,347],{"href":346}," standard that provides a reference list of information security controls. Organizations use Annex A as a checklist to ensure their ",[126,777,779],{"href":778},"\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.",[192,782,784],{"id":783},"what-are-the-four-themes","What are the four themes?",[17,786,787],{},"The 2022 revision reorganized controls from the previous 14 categories into four themes:",[200,789,790,796,802,808],{},[203,791,792,795],{},[53,793,794],{},"Organizational controls (37 controls)"," — policies, roles and responsibilities, threat intelligence, information security in project management, supplier relationships, and more",[203,797,798,801],{},[53,799,800],{},"People controls (8 controls)"," — screening, terms and conditions of employment, security awareness training, disciplinary processes, and responsibilities after termination",[203,803,804,807],{},[53,805,806],{},"Physical controls (14 controls)"," — physical security perimeters, entry controls, securing offices and facilities, equipment protection, and clear desk policies",[203,809,810,813],{},[53,811,812],{},"Technological controls (34 controls)"," — user endpoint devices, privileged access management, access restrictions, secure authentication, malware protection, logging, encryption, and secure development",[192,815,817],{"id":816},"how-does-annex-a-fit-into-iso-27001","How does Annex A fit into ISO 27001?",[17,819,820],{},"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:",[445,822,823,826,829,832,835],{},[203,824,825],{},"The organization performs a risk assessment to identify information security risks",[203,827,828],{},"The organization determines how to treat each risk (mitigate, accept, transfer, or avoid)",[203,830,831],{},"For risks being mitigated, the organization selects appropriate controls",[203,833,834],{},"The organization compares selected controls against Annex A to ensure nothing has been overlooked",[203,836,837],{},"The results are documented in the Statement of Applicability",[17,839,840],{},"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.",[192,842,844],{"id":843},"how-does-annex-a-relate-to-iso-27002","How does Annex A relate to ISO 27002?",[17,846,847],{},"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.\"",[192,849,851],{"id":850},"what-changed-in-the-2022-revision-of-annex-a","What changed in the 2022 revision of Annex A?",[17,853,854],{},"The 2022 update introduced several changes from the 2013 version:",[200,856,857,860,863,866],{},[203,858,859],{},"Controls were consolidated from 114 to 93",[203,861,862],{},"The 14 categories were replaced with 4 themes",[203,864,865],{},"11 new controls were added, including threat intelligence, information security for cloud services, ICT readiness for business continuity, and data masking",[203,867,868],{},"Each control now includes attributes (control type, cybersecurity concept, operational capability, and security domain) to aid in filtering and mapping",[17,870,871],{},"Organizations certified under the 2013 version had a transition period to update their ISMS to align with the 2022 revision.",[192,873,875],{"id":874},"what-is-the-statement-of-applicability","What is the Statement of Applicability?",[17,877,878,879,883,884,888],{},"The ",[126,880,882],{"href":881},"\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 ",[126,885,887],{"href":886},"\u002Fframeworks\u002Fiso27001\u002Fcertification-process","ISO 27001 certification"," and is a key artifact reviewed during certification audits.",[192,890,892],{"id":891},"how-does-episki-help-with-annex-a","How does episki help with Annex A?",[17,894,895,896,666],{},"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 ",[126,897,899],{"href":898},"\u002Fframeworks\u002Fiso27001\u002Fannex-a-controls","Annex A controls",{"title":147,"searchDepth":148,"depth":148,"links":901},[902],{"id":768,"depth":148,"text":769,"children":903},[904,905,906,907,908,909],{"id":783,"depth":732,"text":784},{"id":816,"depth":732,"text":817},{"id":843,"depth":732,"text":844},{"id":850,"depth":732,"text":851},{"id":874,"depth":732,"text":875},{"id":891,"depth":732,"text":892},{},[748],[748,913,914,915,916],"statement-of-applicability","iso-27002","control-objectives","isms",{"title":918,"description":919},"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":925,"title":926,"body":927,"comparison":1119,"competitorA":1020,"competitorB":1032,"cta":1167,"description":147,"extension":158,"faq":1170,"hero":1188,"lastUpdated":742,"meta":1204,"navigation":162,"path":1205,"seo":1206,"slug":1209,"slugA":1210,"slugB":1211,"stem":1212,"verdict":1213,"__hash__":1217},"compareVs\u002F7.compare\u002Fvs\u002Fdrata-vs-secureframe.md","Drata Vs Secureframe",{"type":14,"value":928,"toc":1109},[929,933,936,940,943,949,952,956,959,962,965,969,972,975,979,982,1054,1057,1060,1064,1067,1070,1074,1077,1080,1083],[30,930,932],{"id":931},"drata-vs-secureframe-the-closest-comparison-in-compliance","Drata vs Secureframe: the closest comparison in compliance",[17,934,935],{},"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.",[192,937,939],{"id":938},"feature-parity-with-different-emphasis","Feature parity with different emphasis",[17,941,942],{},"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,944,945,948],{},[53,946,947],{},"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,950,951],{},"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.",[192,953,955],{"id":954},"the-dashboard-question","The dashboard question",[17,957,958],{},"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,960,961],{},"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,963,964],{},"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.",[192,966,968],{"id":967},"integration-depth","Integration depth",[17,970,971],{},"Secureframe holds a slight advantage in integration count, with 150+ connections compared to Drata's 100+. The extra integrations primarily cover developer tools, identity providers, and security platforms. For teams running complex stacks with multiple CI\u002FCD pipelines, vulnerability scanners, and endpoint management tools, Secureframe's broader integration library means less manual evidence collection.",[17,973,974],{},"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.",[192,976,978],{"id":977},"pricing-opacity","Pricing opacity",[17,980,981],{},"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:",[502,983,984,1000],{},[505,985,986],{},[508,987,988,991,994,997],{},[511,989,990],{},"Platform",[511,992,993],{},"Typical entry price (2026)",[511,995,996],{},"Pricing model",[511,998,999],{},"Published?",[525,1001,1002,1016,1028,1040],{},[508,1003,1004,1007,1010,1013],{},[530,1005,1006],{},"Vanta",[530,1008,1009],{},"~$11,000–$15,000\u002Fyr",[530,1011,1012],{},"Per-seat + framework, custom quote",[530,1014,1015],{},"No",[508,1017,1018,1021,1024,1026],{},[530,1019,1020],{},"Drata",[530,1022,1023],{},"~$10,000–$15,000\u002Fyr",[530,1025,1012],{},[530,1027,1015],{},[508,1029,1030,1033,1036,1038],{},[530,1031,1032],{},"Secureframe",[530,1034,1035],{},"~$8,000–$12,000\u002Fyr",[530,1037,1012],{},[530,1039,1015],{},[508,1041,1042,1045,1048,1051],{},[530,1043,1044],{},"episki",[530,1046,1047],{},"$750\u002Fmo ($7,500\u002Fyr)",[530,1049,1050],{},"Flat platform + modules, unlimited seats",[530,1052,1053],{},"Yes",[17,1055,1056],{},"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,1058,1059],{},"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.",[192,1061,1063],{"id":1062},"where-both-platforms-struggle","Where both platforms struggle",[17,1065,1066],{},"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,1068,1069],{},"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.",[192,1071,1073],{"id":1072},"the-case-for-a-different-approach","The case for a different approach",[17,1075,1076],{},"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,1078,1079],{},"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,1081,1082],{},"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,1084,1085,1088,1089,1093,1094,1098,1099,1103,1104,1108],{},[53,1086,1087],{},"Related reading:"," dig deeper into each platform's competitors in our ",[126,1090,1092],{"href":1091},"\u002Fblog\u002Fdrata-alternatives","Drata alternatives"," and ",[126,1095,1097],{"href":1096},"\u002Fblog\u002Fsecureframe-alternatives","Secureframe alternatives"," guides, see where both rank in the ",[126,1100,1102],{"href":1101},"\u002Fblog\u002Fbest-grc-tools-2026","best GRC tools of 2026",", or compare ",[126,1105,1107],{"href":1106},"\u002Fcompare\u002Fvs\u002Fvanta-vs-drata","Vanta vs Drata"," if Vanta is also on your shortlist.",{"title":147,"searchDepth":148,"depth":148,"links":1110},[1111],{"id":931,"depth":148,"text":932,"children":1112},[1113,1114,1115,1116,1117,1118],{"id":938,"depth":732,"text":939},{"id":954,"depth":732,"text":955},{"id":967,"depth":732,"text":968},{"id":977,"depth":732,"text":978},{"id":1062,"depth":732,"text":1063},{"id":1072,"depth":732,"text":1073},[1120,1124,1128,1133,1138,1142,1147,1152,1157,1162],{"feature":996,"competitorA":1121,"competitorB":1122,"episki":1123},"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":1125,"competitorA":1126,"competitorB":1126,"episki":1127},"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":1129,"competitorA":1130,"competitorB":1131,"episki":1132},"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":1134,"competitorA":1135,"competitorB":1136,"episki":1137},"Integration count","100+ integrations covering major cloud and SaaS platforms","150+ 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":1139,"competitorA":1140,"competitorB":1140,"episki":1141},"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":1143,"competitorA":1144,"competitorB":1145,"episki":1146},"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":1148,"competitorA":1149,"competitorB":1150,"episki":1151},"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":1153,"competitorA":1154,"competitorB":1155,"episki":1156},"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":1158,"competitorA":1159,"competitorB":1160,"episki":1161},"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":1163,"competitorA":1164,"competitorB":1165,"episki":1166},"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":1168,"description":1169},"Skip the comparison. Try episki free.","14-day trial with full access. No credit card required.",{"title":1171,"items":1172},"Drata vs Secureframe pricing FAQ (2026)",[1173,1176,1179,1182,1185],{"label":1174,"content":1175},"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":1177,"content":1178},"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":1180,"content":1181},"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":1183,"content":1184},"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":1186,"content":1187},"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":1189,"title":1190,"description":1191,"links":1192},"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.",[1193,1198],{"label":1194,"icon":1195,"to":1196,"target":1197},"Book a demo","i-lucide-calendar","\u002Fdemo","_blank",{"label":1199,"icon":1200,"color":1201,"variant":1202,"to":1203},"Try episki free","i-lucide-rocket","neutral","subtle","https:\u002F\u002Fapp.episki.com\u002Fauth\u002Fregister",{},"\u002Fcompare\u002Fvs\u002Fdrata-vs-secureframe",{"title":1207,"description":1208},"Drata vs Secureframe (2026): Pricing, Features & Honest Comparison","Drata vs Secureframe compared on pricing, onboarding, framework coverage, and compliance automation. See which platform fits your team — or if neither does.","drata-vs-secureframe","drata","secureframe","7.compare\u002Fvs\u002Fdrata-vs-secureframe",{"chooseA":1214,"chooseB":1215,"chooseEpiski":1216},"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.","ZFhZug7YeFTwHWW7ofP4DEaTqpwuaS47YBVKAJnxU-U",{"id":1219,"title":1220,"advantages":1221,"body":1243,"comparison":1306,"competitor":1220,"cta":1354,"description":147,"extension":158,"faq":1357,"hero":1375,"lastUpdated":742,"meta":1383,"navigation":162,"path":1384,"seo":1385,"slug":1388,"stem":1389,"__hash__":1390},"compare\u002F7.compare\u002Farcher.md","Archer",[1222,1229,1236],{"title":1223,"description":1224,"bullets":1225},"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.",[1226,1227,1228],"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":1230,"description":1231,"bullets":1232},"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.",[1233,1234,1235],"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":1237,"description":1238,"bullets":1239},"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.",[1240,1241,1242],"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":1244,"toc":1301},[1245,1249,1252,1255,1258,1278,1282,1285,1288,1291,1294,1298],[30,1246,1248],{"id":1247},"why-teams-evaluate-archer-alternatives","Why teams evaluate Archer alternatives",[17,1250,1251],{},"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,1253,1254],{},"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,1256,1257],{},"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.",[200,1259,1260,1266,1272],{},[203,1261,1262,1265],{},[53,1263,1264],{},"No implementation project"," — self-serve signup, sensible defaults, first policy drafted in minutes",[203,1267,1268,1271],{},[53,1269,1270],{},"A published price"," — $7,500\u002Fyr for the platform, unlimited users and frameworks",[203,1273,1274,1277],{},[53,1275,1276],{},"Agents that do the drafting"," — instead of workflows that route it to a person",[30,1279,1281],{"id":1280},"where-episki-is-different","Where episki is different",[17,1283,1284],{},"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,1286,1287],{},"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,1289,1290],{},"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,1292,1293],{},"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,1295,1297],{"id":1296},"when-archer-might-still-be-the-better-fit","When Archer might still be the better fit",[17,1299,1300],{},"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":147,"searchDepth":148,"depth":148,"links":1302},[1303,1304,1305],{"id":1247,"depth":148,"text":1248},{"id":1280,"depth":148,"text":1281},{"id":1296,"depth":148,"text":1297},[1307,1311,1315,1318,1322,1326,1330,1334,1338,1342,1346,1350],{"feature":1308,"episki":1309,"competitor":1310},"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":1312,"episki":1313,"competitor":1314},"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":996,"episki":1316,"competitor":1317},"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":1319,"episki":1320,"competitor":1321},"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":1323,"episki":1324,"competitor":1325},"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":1327,"episki":1328,"competitor":1329},"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":1331,"episki":1332,"competitor":1333},"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":1335,"episki":1336,"competitor":1337},"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":1339,"episki":1340,"competitor":1341},"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":1343,"episki":1344,"competitor":1345},"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":1347,"episki":1348,"competitor":1349},"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":1351,"episki":1352,"competitor":1353},"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":1355,"description":1356},"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":1358,"items":1359},"episki vs Archer — frequently asked questions",[1360,1363,1366,1369,1372],{"label":1361,"content":1362},"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":1364,"content":1365},"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":1367,"content":1368},"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":1370,"content":1371},"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":1373,"content":1374},"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":1376,"title":1377,"description":1378,"links":1379},"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.",[1380,1381],{"label":1194,"icon":1195,"to":1196,"target":1197},{"label":1382,"icon":1200,"color":1201,"variant":1202,"to":1203},"Start free trial",{},"\u002Fcompare\u002Farcher",{"title":1386,"description":1387},"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":1392,"title":1393,"api":6,"authors":1394,"body":1397,"category":1864,"date":1865,"description":1866,"extension":158,"faq":6,"features":6,"fixes":6,"highlight":6,"image":1867,"improvements":6,"meta":1869,"navigation":162,"path":1870,"seo":1871,"stem":1872,"__hash__":1873},"posts\u002F3.blog\u002Fpci-faq-1331-saq-scope.md","PCI FAQ #1331: SAQ Eligibility Criteria Can No Longer Set Your ROC Scope",[1395],{"name":9,"to":10,"avatar":1396},{"src":12},{"type":14,"value":1398,"toc":1852},[1399,1402,1410,1418,1424,1427,1432,1435,1439,1442,1458,1468,1471,1478,1491,1495,1498,1508,1511,1514,1517,1521,1524,1527,1530,1533,1540,1550,1554,1557,1570,1577,1580,1584,1587,1594,1600,1603,1606,1610,1613,1616,1636,1639,1649,1652,1655,1659,1662,1667,1687,1692,1725,1730,1738,1742,1749,1756,1771,1775,1822,1825,1828],[17,1400,1401],{},"The PCI Security Standards Council just made scoping worse.",[17,1403,1404,1409],{},[126,1405,1408],{"href":1406,"rel":1407},"https:\u002F\u002Fwww.pcisecuritystandards.org\u002Ffaqs\u002F1331\u002F",[130],"FAQ #1331"," was updated this month. If you're not familiar with it, it's the one that let a QSA performing a merchant Report on Compliance reference the control set from the SAQs when the merchant met the eligibility criteria. So if a channel was just an iframe to a compliant payment processor, it was clear which controls should be tested. That clarity is what's gone.",[17,1411,1412,1413,1417],{},"The question the FAQ answers is one that every ",[126,1414,1416],{"href":1415},"\u002Fglossary\u002Fqsa","QSA"," and every Level 1 merchant assessment team has relied on for years:",[1419,1420,1421],"blockquote",{},[17,1422,1423],{},"Can SAQ eligibility criteria be used as a guide for determining applicability of PCI DSS requirements for merchant assessments documented in a Report on Compliance?",[17,1425,1426],{},"The updated answer:",[1419,1428,1429],{},[17,1430,1431],{},"Self-Assessment Questionnaires are compliance tools designed for merchants under specific conditions and use cases. They should not serve as a \"guide\" for determining PCI DSS requirement applicability unless the merchant's compliance-accepting entity (such as payment brands or acquirers) explicitly reviews and agrees to this approach.",[17,1433,1434],{},"Scope is now a negotiation. And it creates two problems the Council hasn't addressed.",[30,1436,1438],{"id":1437},"what-actually-changed-and-what-didnt","🎯 What Actually Changed (and What Didn't)",[17,1440,1441],{},"Let's be precise, because this update is getting summarized badly.",[17,1443,1444,1447,1448,1452,1453,1457],{},[53,1445,1446],{},"What didn't change:"," whether you file an ",[126,1449,1451],{"href":1450},"\u002Fglossary\u002Fsaq","SAQ"," or a Report on Compliance was never your call. That's always been determined by your acquirer or payment brand based on transaction volume and ",[126,1454,1456],{"href":1455},"\u002Fframeworks\u002Fpci\u002Fcompliance-levels","merchant level",". Nobody lost that freedom, because nobody had it.",[17,1459,1460,1463,1464,1467],{},[53,1461,1462],{},"What changed:"," using SAQ eligibility criteria as a scoping reference ",[143,1465,1466],{},"inside"," a ROC. This is how a lot of e-commerce merchants with a redirect or a hosted iframe ended up with a ROC that, functionally, looked like SAQ A. The SAQ told you which requirements were \"in play.\" The ROC followed along. The assessor documented the rest as Not Applicable and everyone moved on.",[17,1469,1470],{},"That door is now closed unless the compliance-accepting entity has explicitly reviewed, discussed, and agreed to the approach.",[17,1472,1473,1474,1477],{},"Worth being honest about what that practice was actually delivering: ",[53,1475,1476],{},"consistency",". Two assessors looking at the same iframe-to-a-compliant-processor channel would land in roughly the same place, because they were both reasoning from the same published control set. That's the thing being removed. Not a loophole — a shared reference point.",[17,1479,1480,1481,1486,1487,1490],{},"The Council also points to ",[126,1482,1485],{"href":1483,"rel":1484},"https:\u002F\u002Fwww.pcisecuritystandards.org\u002Ffaqs\u002F1473\u002F",[130],"FAQ #1473",", which is the more consequential half of the story. Read them together and the division of labor is unambiguous: compliance-accepting entities determine validation and reporting methods and ",[143,1488,1489],{},"may direct which specific requirements are included",". Assessors are responsible for validating that scope and applicability are accurately defined — and must confirm through testing that a requirement genuinely doesn't apply before marking it Not Applicable.",[30,1492,1494],{"id":1493},"️-the-not-tested-trap-nobody-is-talking-about","⚠️ The \"Not Tested\" Trap Nobody Is Talking About",[17,1496,1497],{},"Here's the part that will bite programs in the next assessment cycle.",[17,1499,1500,1501,1504,1505,666],{},"Under FAQ #1473, if a compliance-accepting entity directs that requirements be excluded from the assessment, the assessor does ",[53,1502,1503],{},"not"," mark them Not Applicable. They mark them ",[53,1506,1507],{},"Not Tested",[17,1509,1510],{},"Those are not the same thing on an Attestation of Compliance. Not Applicable means the assessor tested and confirmed the requirement legitimately doesn't apply to this environment. Not Tested means nobody looked. An Attestation of Compliance carrying Not Tested entries is a materially weaker document — and one that a customer's third-party risk team, a downstream service provider, or a future acquirer will read very differently.",[17,1512,1513],{},"So the \"win\" of getting your acquirer to agree to a narrowed scope may hand you an AOC with visible holes in it. Meanwhile, \"SAQ A doesn't include Requirement 6\" is not evidence that Requirement 6 is inapplicable. It's evidence that a different document, built for a different validation path, didn't ask. Your assessor still owes a testing rationale.",[17,1515,1516],{},"That distinction is the whole ballgame, and almost nobody has priced it into their program yet.",[30,1518,1520],{"id":1519},"problem-one-why-is-a-control-set-acceptable-for-one-merchant-and-not-another","🤔 Problem One: Why Is a Control Set Acceptable for One Merchant and Not Another?",[17,1522,1523],{},"Take two e-commerce merchants. Same redirect to a third-party payment page. Same architecture. Same cardholder data footprint, which is to say essentially none. One does 500 transactions a year and files SAQ A. The other does 8 million and gets a ROC.",[17,1525,1526],{},"SAQ A does not ask the small merchant to demonstrate a secure development lifecycle. Its entire Requirement 6 coverage in v4.0 was three items — 6.3.1, 6.3.3, and 6.4.3 — and 6.4.3 was pulled out in the January 2025 revision. Nothing from 6.2 (secure software development, secure coding training, code review). Nothing from 6.5 (change management). Twenty-odd questions in total, against a standard that runs to hundreds of requirements. The Council has effectively said: for this payment channel, those controls don't move the needle on cardholder data risk.",[17,1528,1529],{},"So is development in scope for the big one?",[17,1531,1532],{},"Not according to the model. Maybe according to the acquirer. Definitely according to whoever is feeling cautious that quarter.",[17,1534,1535,1536,1539],{},"Either the SAQ A control set is a ",[53,1537,1538],{},"risk-based statement about what matters for that payment channel"," — in which case a Level 1 merchant with the identical channel should be able to reason from it — or it isn't, and we are quietly telling small merchants that a thinner control set is good enough for them because nobody is watching.",[17,1541,1542,1543,1546,1547,666],{},"It can't be both. Volume should drive ",[53,1544,1545],{},"validation rigor",": who assesses, how much evidence, how deeply it's tested. It shouldn't silently redefine which controls are ",[143,1548,1549],{},"relevant to the same risk",[192,1551,1553],{"id":1552},"the-council-already-made-eligibility-criteria-do-control-work","The Council Already Made Eligibility Criteria Do Control Work",[17,1555,1556],{},"If you think that's an unfair reading, look at what happened to SAQ A in January 2025.",[17,1558,1559,1560,1565,1566,1569],{},"The Council ",[126,1561,1564],{"href":1562,"rel":1563},"https:\u002F\u002Fblog.pcisecuritystandards.org\u002Fimportant-updates-announced-for-merchants-validating-to-self-assessment-questionnaire-a",[130],"removed Requirements 6.4.3, 11.6.1, and 12.3.1 from SAQ A"," — the payment page script management, tamper detection, and supporting targeted risk analysis items — and replaced them with an ",[53,1567,1568],{},"eligibility criterion",": the merchant confirms their site is not susceptible to attacks from scripts that could affect their e-commerce systems.",[17,1571,1572,1573,1576],{},"Read that again. Three PCI DSS requirements were converted into a self-attested eligibility condition. The eligibility criteria are not a neutral gate that sits outside the control set; in SAQ A they ",[143,1574,1575],{},"are"," part of how the Council decided script risk gets addressed for that channel.",[17,1578,1579],{},"Which makes FAQ #1331's position awkward. Eligibility criteria are apparently substantive enough to stand in for three requirements when a small merchant self-assesses, but not substantive enough to inform an applicability discussion when a QSA assesses the same architecture at scale.",[30,1581,1583],{"id":1582},"problem-two-why-is-this-the-acquirers-call-at-all","🏦 Problem Two: Why Is This the Acquirer's Call at All?",[17,1585,1586],{},"If the merchant meets the eligibility criteria, the criteria are the criteria. They were published by the Council, not invented by the assessor.",[17,1588,1589,1590,1593],{},"Requiring acquirer sign-off doesn't add technical rigor. Most acquirers are not staffed to make architecture-level scoping determinations — their PCI function is a portfolio compliance-tracking operation, not a payments security engineering group. The ones that ",[143,1591,1592],{},"can"," engage at that level will take months to do it. What you get back is a signature, not an answer.",[17,1595,1596,1597],{},"For the veteran QSAs reading this: how many times have we been on that call and heard, ",[53,1598,1599],{},"\"What does your QSA think?\"",[17,1601,1602],{},"That's the part the FAQ doesn't reckon with. Acquirers routinely defer to the assessor on-site, because the assessor is the one who has seen the network diagrams, walked the data flows, and knows the specific conditions in the environment. The acquirer hasn't. Naming them the deciding party in an FAQ does not give them that knowledge, and it does not change the dynamic on the call. The question comes right back to the QSA — except now with a formal expectation attached to it.",[17,1604,1605],{},"There's also a structural asymmetry. The acquirer bears the fine risk, so their rational move on any ambiguous scoping question is to say \"assess everything\" or to say nothing at all. Neither response is a risk determination. One is a cost transfer to the merchant; the other is silence that the merchant has to interpret.",[30,1607,1609],{"id":1608},"where-this-actually-lands-division","🧩 Where This Actually Lands: Division",[17,1611,1612],{},"Push a decision to a party that can't or won't make it, and the decision doesn't disappear. It gets made anyway, less visibly, by whoever is holding the pen.",[17,1614,1615],{},"Here's how this plays out. A QSA will do one of three things:",[445,1617,1618,1624,1630],{},[203,1619,1620,1623],{},[53,1621,1622],{},"Agree with the merchant and scope to the SAQ control set."," Defensible if the acquirer signs off. A problem if the merchant never got that in writing.",[203,1625,1626,1629],{},[53,1627,1628],{},"Disagree and push essentially the full ROC where applicable."," The defensible-by-default posture. Expensive, slow, and it generates evidence for controls with no bearing on the merchant's actual card data risk.",[203,1631,1632,1635],{},[53,1633,1634],{},"Pick and choose a smattering of controls they think apply."," No consistent rationale, no published reference point. I've seen all three of these implemented by QSAs firsthand — and the third was already happening before this update. The FAQ change doesn't fix it. It removes the one shared reference the other two were anchored to.",[17,1637,1638],{},"And now the merchant has to go to their processor to clear scope if they want to use the controls in an already defined and approved SAQ. So they're left with two real options: chase an approval from an acquirer who may never respond, or accept whatever scope their QSA decided on.",[17,1640,1641,1642,1645,1646,666],{},"Most will take option two. Which means the decision didn't move ",[53,1643,1644],{},"up"," a level. It moved ",[53,1647,1648],{},"out of sight",[17,1650,1651],{},"So we end up with division. Some Level 1 merchants will test every applicable control in the ROC. Some will get approval and test the SAQ-scoped set. Some will get whatever their QSA decided was applicable that week. Two merchants with identical architecture, materially different assessments — depending on which QSA they hired and how engaged their acquirer happens to be.",[17,1653,1654],{},"That's worse for comparability, worse for merchants trying to budget, and — the part that should bother the Council most — worse for actual security, because effort gets allocated by liability anxiety instead of by risk.",[30,1656,1658],{"id":1657},"what-to-do-about-it-this-quarter","✅ What to Do About It This Quarter",[17,1660,1661],{},"Setting aside whether the policy is right, it's the policy. Here's the practical response.",[17,1663,1664],{},[53,1665,1666],{},"If you have a ROC in flight that leaned on SAQ criteria to narrow requirements:",[200,1668,1669,1672,1679],{},[203,1670,1671],{},"Raise it with your acquirer now, not at report writing. Scoping questions that arrive alongside a draft ROC get answered with \"assess everything.\"",[203,1673,1674,1675,1678],{},"Ask specifically whether they will agree to the approach ",[53,1676,1677],{},"in writing",", and whether excluded requirements will be documented as Not Applicable (with assessor testing) or Not Tested (at their direction). Make sure you understand which AOC you're going to end up holding.",[203,1680,1681,1682,1686],{},"If they won't engage, get their non-response documented and make a deliberate, defensible applicability decision with your assessor — with a written rationale tied to your actual ",[126,1683,1685],{"href":1684},"\u002Fglossary\u002Fcardholder-data-environment","cardholder data environment",", not to an SAQ table of contents.",[17,1688,1689],{},[53,1690,1691],{},"If you're scoping next year's assessment:",[200,1693,1694,1707,1710,1713],{},[203,1695,1696,1697,1701,1702,1706],{},"Build your applicability position from first principles. Data flows, system component inventory, ",[126,1698,1700],{"href":1699},"\u002Fframeworks\u002Fpci\u002Fnetwork-segmentation","segmentation"," boundaries, and a documented rationale per requirement. That work survives any FAQ revision. See our guide to ",[126,1703,1705],{"href":1704},"\u002Fframeworks\u002Fpci\u002Fscope-reduction","PCI scope reduction"," for how to shrink the environment rather than argue about it.",[203,1708,1709],{},"Open the acquirer conversation early in the cycle, not 60 days out. Budget real calendar time for it.",[203,1711,1712],{},"Assume your applicability rationale will be re-litigated by the next QSA you hire. Write it so it holds up without you in the room.",[203,1714,1715,1716,1720,1721,1724],{},"Genuinely reduce scope where you can. ",[126,1717,1719],{"href":1718},"\u002Fglossary\u002Ftokenization","Tokenization"," and hosted payment fields don't just narrow requirements — they narrow the ",[143,1722,1723],{},"argument",", which is now the expensive part.",[17,1726,1727],{},[53,1728,1729],{},"If you're a QSA:",[200,1731,1732,1735],{},[203,1733,1734],{},"Stop treating \"the merchant qualifies for SAQ A\" as a scoping input. It's an interesting data point about architecture, not a determination.",[203,1736,1737],{},"Get the compliance-accepting entity's position in the ROC, in writing, including silence. Document what you asked and when.",[30,1739,1741],{"id":1740},"️-how-episki-helps","🛠️ How episki Helps",[17,1743,1744,1745,1748],{},"The uncomfortable truth of this update is that ",[53,1746,1747],{},"your applicability rationale is now a first-class deliverable",", not an implicit byproduct of picking the right questionnaire. It has to be written down, defended per requirement, and durable across assessor changes.",[17,1750,1751,1755],{},[126,1752,1044],{"href":1753,"rel":1754},"https:\u002F\u002Fapp.episki.com",[130]," is built for that: requirement-level applicability status with a documented rationale and full audit trail, evidence linked to the specific requirement it supports, and a shared workspace where your assessor and your team see the same scoping decisions instead of reconstructing them from email. When a control is scoped out, the reason is recorded next to it — so next year's assessor reads your reasoning rather than inventing their own.",[17,1757,1758,1759,1762,1763,1093,1767,666],{},"Explore the ",[126,1760,1761],{"href":374},"PCI DSS framework on episki"," to see how requirements, applicability, and evidence connect, or read our breakdown of ",[126,1764,1766],{"href":1765},"\u002Fframeworks\u002Fpci\u002Fsaq-types-explained","SAQ types",[126,1768,1770],{"href":1769},"\u002Fframeworks\u002Fpci\u002Fv4-changes","what changed in v4",[30,1772,1774],{"id":1773},"key-takeaways","📝 Key Takeaways",[200,1776,1777,1783,1792,1798,1804,1810,1816],{},[203,1778,1779,1782],{},[53,1780,1781],{},"FAQ #1331 (updated August 2026)"," closes the practice of using SAQ eligibility criteria to determine requirement applicability in a ROC without explicit acquirer or payment brand agreement.",[203,1784,1785,1788,1789,1791],{},[53,1786,1787],{},"Read it with FAQ #1473."," Requirements excluded at the compliance-accepting entity's direction are marked ",[53,1790,1507],{},", not Not Applicable — a visibly weaker AOC.",[203,1793,1794,1797],{},[53,1795,1796],{},"The inconsistency is real."," The same architecture gets a thinner control set at 500 transactions than at 8 million. Volume should drive validation rigor, not which risks are considered relevant.",[203,1799,1800,1803],{},[53,1801,1802],{},"Eligibility criteria already do control work."," SAQ A's January 2025 revision replaced 6.4.3, 11.6.1, and 12.3.1 with a self-attested eligibility criterion.",[203,1805,1806,1809],{},[53,1807,1808],{},"Acquirer sign-off adds a signature, not a determination."," Most aren't staffed for architecture-level scoping, their incentive is to say \"everything\" or nothing, and on the call they'll ask what your QSA thinks.",[203,1811,1812,1815],{},[53,1813,1814],{},"Practice will divide."," Some Level 1 merchants will test everything, some will get approval and test the SAQ-scoped set, some will get whatever their QSA decided that week.",[203,1817,1818,1821],{},[53,1819,1820],{},"Do the work anyway."," A first-principles, documented applicability rationale is the only artifact that holds up regardless of how the Council words this next.",[1823,1824],"hr",{},[17,1826,1827],{},"Curious on thoughts from my QSA peeps and the broader community. Am I right that this is going in the wrong direction, or am I missing something?",[17,1829,1830,1833,1834,1838,1839,1838,1843,1838,1847],{},[53,1831,1832],{},"Sources:"," ",[126,1835,1837],{"href":1406,"rel":1836},[130],"PCI SSC FAQ #1331"," · ",[126,1840,1842],{"href":1483,"rel":1841},[130],"PCI SSC FAQ #1473",[126,1844,1846],{"href":1562,"rel":1845},[130],"Important Updates Announced for Merchants Validating to SAQ A",[126,1848,1851],{"href":1849,"rel":1850},"https:\u002F\u002Fblog.pcisecuritystandards.org\u002Ffaq-clarifies-new-saq-a-eligibility-criteria-for-e-commerce-merchants",[130],"FAQ Clarifies New SAQ A Eligibility Criteria for E-Commerce Merchants",{"title":147,"searchDepth":148,"depth":148,"links":1853},[1854,1855,1856,1859,1860,1861,1862,1863],{"id":1437,"depth":148,"text":1438},{"id":1493,"depth":148,"text":1494},{"id":1519,"depth":148,"text":1520,"children":1857},[1858],{"id":1552,"depth":732,"text":1553},{"id":1582,"depth":148,"text":1583},{"id":1608,"depth":148,"text":1609},{"id":1657,"depth":148,"text":1658},{"id":1740,"depth":148,"text":1741},{"id":1773,"depth":148,"text":1774},"news","2026-08-05","The PCI Council updated FAQ #1331 in August 2026. You can no longer use SAQ eligibility criteria to determine which PCI DSS requirements apply in a Report on Compliance without acquirer agreement. Here's what breaks.",{"src":1868},"\u002Fimages\u002Fblog\u002Fpci-faq-1331-saq-scope.webp",{},"\u002Fblog\u002Fpci-faq-1331-saq-scope",{"title":1393,"description":1866},"3.blog\u002Fpci-faq-1331-saq-scope","Qy7jrphPcuHhcgiLvIRaUbg56-o84BEX8DnxNfgVnYs",{"id":1875,"title":1876,"advantages":1877,"body":1899,"checklist":1906,"cta":1915,"description":1903,"extension":158,"faq":6,"hero":1918,"lastUpdated":742,"meta":1927,"name":1928,"navigation":162,"path":1929,"resources":1930,"seo":1943,"slug":1946,"stats":1947,"stem":1957,"__hash__":1958},"industries\u002F6.industry\u002F1.healthcare.md","Healthcare",[1878,1885,1892],{"title":1879,"description":1880,"bullets":1881},"PHI-aware control mapping","Map administrative, technical, and physical safeguards to your stack without rebuilding every audit.",[1882,1883,1884],"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":1886,"description":1887,"bullets":1888},"Clinician-friendly workflows","Keep nurses, clinicians, and ops aligned without burying them in tickets.",[1889,1890,1891],"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":1893,"description":1894,"bullets":1895},"Auditor and partner collaboration","Give regulators, payers, and partners scoped access instead of email threads.",[1896,1897,1898],"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":1900,"toc":1904},[1901],[17,1902,1903],{},"Healthcare buyers move fast when they trust your safeguards. episki keeps PHI protections documented, monitored, and shareable without slowing product or patient care.",{"title":147,"searchDepth":148,"depth":148,"links":1905},[],{"title":1907,"description":1908,"items":1909},"Healthtech compliance checklist","Use this inside your trial to assign owners, attach evidence, and track renewals.",[1910,1911,1912,1913,1914],"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":1916,"description":1917},"Launch a healthtech-ready workspace","Connect your stack, invite stakeholders, and show PHI protections the same day.",{"headline":1919,"title":1920,"description":1921,"links":1922},"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.",[1923,1925],{"label":1924,"icon":1200,"to":1203},"Start healthtech trial",{"label":1194,"icon":1926,"color":1201,"variant":1202,"to":1196,"target":1197},"i-lucide-message-circle",{},"healthcare and healthtech","\u002Findustry\u002Fhealthcare",{"headline":1931,"title":1931,"description":1932,"items":1933},"Healthcare enablement kit","Keep leadership, clinicians, and auditors aligned on the same story.",[1934,1937,1940],{"title":1935,"description":1936},"PHI data flow deck","Share sanitized diagrams plus segmentation notes for customers and partners.",{"title":1938,"description":1939},"Board + payer brief","Summarize control health, incidents, and remediation in plain language.",{"title":1941,"description":1942},"Auditor-ready workspace","Prebuilt template for requests, evidence, and walkthrough scheduling.",{"title":1944,"description":1945},"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",[1948,1951,1954],{"value":1949,"description":1950},"30-day rollout","Move from baseline controls to monitored safeguards in under a month.",{"value":1952,"description":1953},"PHI-safe sharing","Role-based portals keep BAAs, policies, and diagrams organized and protected.",{"value":1955,"description":1956},"Continuous watch","Drift detection across access, logging, vendors, and incidents.","6.industry\u002F1.healthcare","u08a7hidKILzMlQgEwXI8WBgv7i08HXpMKdsEpMA3Tw",1788458838847]