[{"data":1,"prerenderedAt":3493},["ShallowReactive",2],{"\u002Fglossary\u002Fsoc-report":3,"glossary-related-terms-soc-report":291,"explore-glossary-soc2-\u002Fglossary\u002Fsoc-report":310,"explore-topics-soc2-\u002Fglossary\u002Fsoc-report":1112,"explore-hub-soc2":2011,"explore-compare-vs-\u002Fglossary\u002Fsoc-report":2605,"explore-compare-\u002Fglossary\u002Fsoc-report":2890,"explore-blog-soc2-\u002Fglossary\u002Fsoc-report":3063,"explore-industry-soc2":3409},{"id":4,"title":5,"body":6,"description":258,"extension":271,"lastUpdated":272,"meta":273,"navigation":274,"path":275,"relatedFrameworks":276,"relatedTerms":278,"seo":285,"slug":288,"stem":289,"term":13,"__hash__":290},"glossary\u002F8.glossary\u002Fsoc-report.md","Soc Report",{"type":7,"value":8,"toc":257},"minimark",[9,14,18,21,30,35,38,103,106,110,113,142,145,149,152,155,159,172,175,179,182,235,239,242,245,249],[10,11,13],"h2",{"id":12},"what-is-a-soc-report","What is a SOC report?",[15,16,17],"p",{},"A SOC report (System and Organization Controls report) is the document a licensed CPA firm issues at the end of a SOC examination. It describes a service organization's system, lists the controls that were tested, and gives the auditor's opinion on them.",[15,19,20],{},"The word \"report\" does a lot of work here. A SOC report is not a certificate and not a pass\u002Ffail score. It is a narrative document -- commonly 30 to 100+ pages -- that a reader is expected to work through and form their own judgement about. That is why buyers ask for the report itself rather than a badge.",[15,22,23,24,29],{},"Three reports share the name. SOC 1 covers controls relevant to a customer's financial reporting, SOC 2 covers security, availability, processing integrity, confidentiality, and privacy, and SOC 3 is a short public-use summary of a SOC 2. For help choosing between them, see ",[25,26,28],"a",{"href":27},"\u002Fframeworks\u002Fsoc2\u002Fsoc1-vs-soc2","SOC 1 vs SOC 2 vs SOC 3",".",[31,32,34],"h3",{"id":33},"what-sections-does-a-soc-report-contain","What sections does a SOC report contain?",[15,36,37],{},"The AICPA publishes an illustrative SOC 2 report, and real reports follow its shape. It contains management's assertion, the description of the system, the service auditor's report, and the tests of controls and their results. In practice you will see them ordered like this:",[39,40,41,57],"table",{},[42,43,44],"thead",{},[45,46,47,51,54],"tr",{},[48,49,50],"th",{},"Section",[48,52,53],{},"What it contains",[48,55,56],{},"Who writes it",[58,59,60,72,83,93],"tbody",{},[45,61,62,66,69],{},[63,64,65],"td",{},"Independent service auditor's report",[63,67,68],{},"The scope, the period covered, and the opinion",[63,70,71],{},"The CPA firm",[45,73,74,77,80],{},[63,75,76],{},"Management's assertion",[63,78,79],{},"Management's formal statement that the system description is accurate and the controls are suitably designed",[63,81,82],{},"The service organization",[45,84,85,88,91],{},[63,86,87],{},"Description of the system",[63,89,90],{},"Infrastructure, software, people, procedures, data, subservice organizations, and what was scoped out",[63,92,82],{},[45,94,95,98,101],{},[63,96,97],{},"Tests of controls and results",[63,99,100],{},"Each control, how the auditor tested it, and what the test found",[63,102,71],{},[15,104,105],{},"Many reports add a fifth section, usually titled \"other information\". It is outside the scope of the examination and is not covered by the auditor's opinion -- management's response to an exception typically sits here. Read it, but weigh it differently from the four audited sections.",[31,107,109],{"id":108},"what-does-the-auditors-opinion-mean","What does the auditor's opinion mean?",[15,111,112],{},"The opinion sits in the first section and is the fastest read in the document. Four outcomes are possible:",[114,115,116,124,130,136],"ul",{},[117,118,119,123],"li",{},[120,121,122],"strong",{},"Unqualified"," -- the controls were suitably designed and, in a Type 2, operated effectively. This is the normal good result.",[117,125,126,129],{},[120,127,128],{},"Qualified"," -- one or more controls were not designed or not operating effectively, and the auditor is naming the exception.",[117,131,132,135],{},[120,133,134],{},"Adverse"," -- the problems are pervasive enough that the auditor cannot stand behind the system description or the controls.",[117,137,138,141],{},[120,139,140],{},"Disclaimer"," -- the auditor could not gather enough evidence to form an opinion at all.",[15,143,144],{},"An unqualified opinion does not mean there were no exceptions. Exceptions are listed control by control in the tests-of-controls section, so read that section as well as the opinion.",[31,146,148],{"id":147},"is-there-a-soc-report-example-you-can-look-at","Is there a SOC report example you can look at?",[15,150,151],{},"The AICPA publishes an illustrative SOC 2 report with an illustrative system description, which is the reference the audit profession works from. It is the closest thing to a canonical example and it shows the assertion, the description, the auditor's report, and the tests of controls in full.",[15,153,154],{},"Vendors' own reports are restricted-use documents, so you will not find a real one published openly. Ask the service organization directly and expect to sign an NDA first. A SOC 3 report, by contrast, is written for public distribution, so a vendor's SOC 3 is often available on request without one -- it is a useful shape reference even though it omits the detailed testing results.",[31,156,158],{"id":157},"what-is-the-difference-between-a-type-1-and-a-type-2-report","What is the difference between a Type 1 and a Type 2 report?",[15,160,161,162,166,167,171],{},"A ",[25,163,165],{"href":164},"\u002Fglossary\u002Fsoc2-type-1","Type 1"," report covers whether controls were suitably designed as of a single date. A ",[25,168,170],{"href":169},"\u002Fglossary\u002Fsoc2-type-2","Type 2"," report covers whether those controls also operated effectively across a period, commonly three to twelve months.",[15,173,174],{},"The practical consequence is in the tests-of-controls section. A Type 1 has no operating-effectiveness testing to report, so that section is far thinner. Enterprise buyers generally want Type 2 because a snapshot says little about whether a control survives contact with a normal quarter.",[31,176,178],{"id":177},"how-do-you-review-a-vendors-soc-report","How do you review a vendor's SOC report?",[15,180,181],{},"Most people meet a SOC report because procurement handed them one. Six checks cover most of the risk:",[183,184,185,191,197,203,209,219],"ol",{},[117,186,187,190],{},[120,188,189],{},"Read the opinion first."," Unqualified, qualified, adverse, or disclaimer.",[117,192,193,196],{},[120,194,195],{},"Check the period."," A Type 2 covers a window, and that window has an end date. If it closed more than a few months ago, ask for a bridge letter covering the gap.",[117,198,199,202],{},[120,200,201],{},"Confirm the service you buy is in scope."," The system description names the products and services examined. A company-wide report does not automatically cover the specific product in your contract.",[117,204,205,208],{},[120,206,207],{},"Read the exceptions, not just the opinion."," Work through the tests of controls and look at what failed and how management responded.",[117,210,211,214,215,29],{},[120,212,213],{},"Check which criteria were included."," Security is the baseline; availability, processing integrity, confidentiality, and privacy are included only if the service organization chose them. See ",[25,216,218],{"href":217},"\u002Fglossary\u002Ftrust-services-criteria","Trust Services Criteria",[117,220,221,224,225,229,230,234],{},[120,222,223],{},"Find your own obligations."," Reports list complementary ",[25,226,228],{"href":227},"\u002Fglossary\u002Fuser-entity-controls","user entity controls"," -- things the report assumes ",[231,232,233],"em",{},"you"," do. If you do not do them, the vendor's controls do not work as described.",[31,236,238],{"id":237},"how-long-is-a-soc-report-good-for","How long is a SOC report good for?",[15,240,241],{},"A SOC report does not carry a formal expiry date. What it carries is a period, and the report says nothing about what happened after that period ended.",[15,243,244],{},"Convention in buyer security reviews is to treat a report as current for about twelve months from the end of the audit period, and to expect an annual refresh. Where there is a gap between the last period end and today, service organizations issue a bridge letter -- a short statement from management that nothing material changed in the interval. A bridge letter is management's word, not audited work, so it carries less weight than the report.",[31,246,248],{"id":247},"how-does-episki-help-with-soc-reports","How does episki help with SOC reports?",[15,250,251,252,256],{},"episki holds the material a SOC examination runs on: controls with explicit pass, fail, or inconclusive verdicts rather than filed screenshots, evidence that carries provenance showing how it was gathered, and complementary user entity controls kept as structured records instead of a paragraph someone rewrites each year. The system description and the control narratives your auditor needs are drafted in the platform and approved by your team. Service auditors get guest access scoped to a single assessment, and it is not billed per seat. See the ",[25,253,255],{"href":254},"\u002Fframeworks\u002Fsoc2\u002Faudit-process","SOC 2 audit process"," for how a full engagement runs.",{"title":258,"searchDepth":259,"depth":259,"links":260},"",2,[261],{"id":12,"depth":259,"text":13,"children":262},[263,265,266,267,268,269,270],{"id":33,"depth":264,"text":34},3,{"id":108,"depth":264,"text":109},{"id":147,"depth":264,"text":148},{"id":157,"depth":264,"text":158},{"id":177,"depth":264,"text":178},{"id":237,"depth":264,"text":238},{"id":247,"depth":264,"text":248},"md","2026-10-19",{},true,"\u002Fglossary\u002Fsoc-report",[277],"soc2",[277,279,280,281,282,283,284],"soc2-type-1","soc2-type-2","ssae-18","service-auditor","trust-services-criteria","user-entity-controls",{"title":286,"description":287},"What is a SOC Report? Sections, Example Structure & How to Read One","A SOC report is the attestation a CPA firm issues after a SOC examination. What the four sections contain, what the auditor's opinion means, and the checks to run on a vendor's report.","soc-report","8.glossary\u002Fsoc-report","kUHer412F0wH2oMepoB17GmbGLLJaMhvqJBt-n0xKmQ",{"terms":292,"frameworks":307},[293,295,297,299,301,303,305],{"slug":282,"term":294},"What is a Service Auditor?",{"slug":277,"term":296},"What is SOC 2?",{"slug":279,"term":298},"What is SOC 2 Type I?",{"slug":280,"term":300},"What is SOC 2 Type II?",{"slug":281,"term":302},"What is SSAE 18?",{"slug":283,"term":304},"What is Trust Services Criteria?",{"slug":284,"term":306},"What are User Entity Controls?",[308],{"slug":277,"name":309},"SOC 2 Type I\u002FII",[311,880],{"id":312,"title":313,"body":314,"description":258,"extension":271,"lastUpdated":862,"meta":863,"navigation":274,"path":864,"relatedFrameworks":865,"relatedTerms":871,"seo":874,"slug":877,"stem":878,"term":319,"__hash__":879},"glossary\u002F8.glossary\u002Faccess-control.md","Access Control",{"type":7,"value":315,"toc":848},[316,320,323,327,330,356,360,366,372,378,384,388,391,397,414,420,434,440,451,455,458,515,519,522,536,540,543,566,570,573,622,626,629,743,746,749,778,782,788,791,828,831,834,837,841],[10,317,319],{"id":318},"what-is-access-control","What is Access Control?",[15,321,322],{},"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.",[31,324,326],{"id":325},"what-are-the-core-principles-of-access-control","What are the core principles of access control?",[15,328,329],{},"Access control is built on several foundational principles:",[114,331,332,338,344,350],{},[117,333,334,337],{},[120,335,336],{},"Least privilege"," — users are granted only the minimum access necessary to perform their job functions",[117,339,340,343],{},[120,341,342],{},"Separation of duties"," — critical tasks are divided among multiple individuals to prevent any single person from having unchecked authority",[117,345,346,349],{},[120,347,348],{},"Need to know"," — access to information is restricted to those who require it for a specific purpose",[117,351,352,355],{},[120,353,354],{},"Default deny"," — access is denied by default unless explicitly granted",[31,357,359],{"id":358},"what-are-the-types-of-access-control","What are the types of access control?",[15,361,362,365],{},[120,363,364],{},"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.",[15,367,368,371],{},[120,369,370],{},"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).",[15,373,374,377],{},[120,375,376],{},"Discretionary Access Control (DAC)"," — resource owners decide who can access their resources. Common in file systems where owners set permissions.",[15,379,380,383],{},[120,381,382],{},"Mandatory Access Control (MAC)"," — access is controlled by the system based on security labels and clearance levels. Common in government and military environments.",[31,385,387],{"id":386},"what-are-access-control-components","What are access control components?",[15,389,390],{},"A complete access control program addresses:",[15,392,393,396],{},[120,394,395],{},"Authentication"," — verifying the identity of users:",[114,398,399,402,405,408,411],{},[117,400,401],{},"Passwords and passphrases",[117,403,404],{},"Multi-factor authentication (MFA)",[117,406,407],{},"Single sign-on (SSO)",[117,409,410],{},"Biometric authentication",[117,412,413],{},"Certificate-based authentication",[15,415,416,419],{},[120,417,418],{},"Authorization"," — determining what authenticated users can do:",[114,421,422,425,428,431],{},[117,423,424],{},"Permission assignments",[117,426,427],{},"Role definitions",[117,429,430],{},"Access control lists",[117,432,433],{},"Policy enforcement points",[15,435,436,439],{},[120,437,438],{},"Access lifecycle management"," — managing access throughout the user lifecycle:",[114,441,442,445,448],{},[117,443,444],{},"Provisioning (granting access when hired or role changes)",[117,446,447],{},"Review (periodic access certification)",[117,449,450],{},"Deprovisioning (revoking access upon termination or role change)",[31,452,454],{"id":453},"how-do-compliance-frameworks-address-access-control","How do compliance frameworks address access control?",[15,456,457],{},"Every major framework requires access control:",[114,459,460,469,483,497,506],{},[117,461,462,468],{},[120,463,464],{},[25,465,467],{"href":466},"\u002Fframeworks\u002Fsoc2","SOC 2"," — CC6.1 through CC6.8 cover logical and physical access controls",[117,470,471,477,478,482],{},[120,472,473],{},[25,474,476],{"href":475},"\u002Fframeworks\u002Fiso27001","ISO 27001"," — ",[25,479,481],{"href":480},"\u002Fglossary\u002Fannex-a","Annex A"," controls A.5.15 through A.5.18 and A.8.2 through A.8.5 address access management",[117,484,485,491,492,496],{},[120,486,487],{},[25,488,490],{"href":489},"\u002Fframeworks\u002Fhipaa","HIPAA"," — the ",[25,493,495],{"href":494},"\u002Fframeworks\u002Fhipaa\u002Fsecurity-rule","Security Rule"," requires access controls for ePHI (45 CFR 164.312(a))",[117,498,499,505],{},[120,500,501],{},[25,502,504],{"href":503},"\u002Fframeworks\u002Fpci","PCI DSS"," — Requirements 7 and 8 address access restriction and user identification",[117,507,508,514],{},[120,509,510],{},[25,511,513],{"href":512},"\u002Fframeworks\u002Fnistcsf","NIST CSF"," — PR.AC covers identity management, authentication, and access control",[31,516,518],{"id":517},"what-are-access-reviews","What are access reviews?",[15,520,521],{},"Regular access reviews (also called access certifications) are a critical control:",[114,523,524,527,530,533],{},[117,525,526],{},"Review user access rights periodically (quarterly is common for sensitive systems)",[117,528,529],{},"Verify that access aligns with current job responsibilities",[117,531,532],{},"Identify and remove excessive or unnecessary access",[117,534,535],{},"Document review results and remediation actions",[31,537,539],{"id":538},"what-are-common-access-control-weaknesses","What are common access control weaknesses?",[15,541,542],{},"Even well-designed access control programs can degrade over time without ongoing attention. Watch for these common issues:",[114,544,545,548,551,554,557,560,563],{},[117,546,547],{},"Excessive permissions that accumulate over time (privilege creep)",[117,549,550],{},"Shared or generic accounts that prevent individual accountability",[117,552,553],{},"Delayed deprovisioning when employees leave or change roles",[117,555,556],{},"Lack of MFA on critical systems and remote access paths",[117,558,559],{},"Inconsistent access review processes with no documented remediation",[117,561,562],{},"Service accounts with standing privileged access and no rotation schedule",[117,564,565],{},"Lack of visibility into SaaS application access outside the corporate IdP",[31,567,569],{"id":568},"how-do-you-implement-access-control-in-practice","How do you implement access control in practice?",[15,571,572],{},"Effective access control programs start with planning and build toward automation. The following steps provide a practical roadmap for organizations at any maturity level:",[183,574,575,581,587,593,599,605,616],{},[117,576,577,580],{},[120,578,579],{},"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.",[117,582,583,586],{},[120,584,585],{},"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.",[117,588,589,592],{},[120,590,591],{},"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.",[117,594,595,598],{},[120,596,597],{},"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.",[117,600,601,604],{},[120,602,603],{},"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.",[117,606,607,610,611,615],{},[120,608,609],{},"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 ",[25,612,614],{"href":613},"\u002Fglossary\u002Faudit-trail","audit trail"," that satisfies compliance requirements.",[117,617,618,621],{},[120,619,620],{},"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.",[31,623,625],{"id":624},"what-are-the-access-control-requirements","What are the access control requirements?",[15,627,628],{},"Different frameworks address the same access control concepts with different control references. The table below maps common requirements to their framework-specific identifiers:",[39,630,631,648],{},[42,632,633],{},[45,634,635,638,640,642,644,646],{},[48,636,637],{},"Requirement",[48,639,467],{},[48,641,476],{},[48,643,490],{},[48,645,504],{},[48,647,513],{},[58,649,650,670,689,709,726],{},[45,651,652,655,658,661,664,667],{},[63,653,654],{},"Unique user IDs",[63,656,657],{},"CC6.1",[63,659,660],{},"A.5.16",[63,662,663],{},"§164.312(a)(2)(i)",[63,665,666],{},"Req 8.2.1",[63,668,669],{},"PR.AC-1",[45,671,672,675,677,680,683,686],{},[63,673,674],{},"MFA",[63,676,657],{},[63,678,679],{},"A.8.5",[63,681,682],{},"Addressable",[63,684,685],{},"Req 8.4",[63,687,688],{},"PR.AC-7",[45,690,691,694,697,700,703,706],{},[63,692,693],{},"Access reviews",[63,695,696],{},"CC6.2",[63,698,699],{},"A.5.18",[63,701,702],{},"§164.312(a)(1)",[63,704,705],{},"Req 7.2",[63,707,708],{},"PR.AC-4",[45,710,711,713,716,719,721,724],{},[63,712,336],{},[63,714,715],{},"CC6.3",[63,717,718],{},"A.5.15",[63,720,702],{},[63,722,723],{},"Req 7.1",[63,725,708],{},[45,727,728,731,733,735,738,741],{},[63,729,730],{},"Deprovisioning",[63,732,696],{},[63,734,699],{},[63,736,737],{},"§164.312(a)(2)(ii)",[63,739,740],{},"Req 8.2.6",[63,742,669],{},[15,744,745],{},"Organizations subject to multiple frameworks can use this mapping to build a unified access control program that satisfies overlapping requirements without duplicating effort.",[15,747,748],{},"A few notes on framework-specific nuances:",[114,750,751,756,764,771],{},[117,752,753,755],{},[120,754,490],{}," 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.",[117,757,758,763],{},[120,759,760,762],{},[25,761,504],{"href":503}," 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.",[117,765,766,770],{},[120,767,768],{},[25,769,467],{"href":466}," 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.",[117,772,773,777],{},[120,774,775],{},[25,776,513],{"href":512}," 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.",[31,779,781],{"id":780},"how-does-zero-trust-relate-to-access-control","How does zero trust relate to access control?",[15,783,784,785,29],{},"Traditional access control models assume that users inside the network perimeter can be trusted. Zero trust architecture rejects that assumption entirely: ",[120,786,787],{},"never trust, always verify",[15,789,790],{},"In a zero trust model, every access request is authenticated, authorized, and encrypted regardless of where it originates. Key principles include:",[114,792,793,799,805,816,822],{},[117,794,795,798],{},[120,796,797],{},"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.",[117,800,801,804],{},[120,802,803],{},"Micro-segmentation"," — network resources are divided into small, isolated zones so that compromising one segment does not grant lateral access to others.",[117,806,807,810,811,815],{},[120,808,809],{},"Device posture checks"," — the security state of the connecting device (patch level, endpoint protection status, disk ",[25,812,814],{"href":813},"\u002Fglossary\u002Fencryption","encryption",") is evaluated before access is granted.",[117,817,818,821],{},[120,819,820],{},"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.",[117,823,824,827],{},[120,825,826],{},"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.",[15,829,830],{},"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.",[15,832,833],{},"Zero trust is not a single product but an architectural approach that spans identity, network, endpoints, and data.",[15,835,836],{},"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.",[31,838,840],{"id":839},"how-does-episki-help-with-access-control","How does episki help with access control?",[15,842,843,844,29],{},"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 ",[25,845,847],{"href":846},"\u002Fframeworks","compliance platform",{"title":258,"searchDepth":259,"depth":259,"links":849},[850],{"id":318,"depth":259,"text":319,"children":851},[852,853,854,855,856,857,858,859,860,861],{"id":325,"depth":264,"text":326},{"id":358,"depth":264,"text":359},{"id":386,"depth":264,"text":387},{"id":453,"depth":264,"text":454},{"id":517,"depth":264,"text":518},{"id":538,"depth":264,"text":539},{"id":568,"depth":264,"text":569},{"id":624,"depth":264,"text":625},{"id":780,"depth":264,"text":781},{"id":839,"depth":264,"text":840},"2026-08-31",{},"\u002Fglossary\u002Faccess-control",[866,277,867,868,869,870],"cmmc","iso27001","hipaa","pci","nistcsf",[872,873,814,284],"minimum-necessary-rule","audit-trail",{"title":875,"description":876},"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":881,"title":882,"body":883,"description":258,"extension":271,"lastUpdated":862,"meta":1101,"navigation":274,"path":613,"relatedFrameworks":1102,"relatedTerms":1103,"seo":1107,"slug":873,"stem":1110,"term":888,"__hash__":1111},"glossary\u002F8.glossary\u002Faudit-trail.md","Audit Trail",{"type":7,"value":884,"toc":1091},[885,889,892,896,899,937,940,960,964,967,989,993,996,1040,1044,1047,1061,1065,1082,1086],[10,886,888],{"id":887},"what-is-an-audit-trail","What is an Audit Trail?",[15,890,891],{},"An audit trail is a chronological record of activities, events, and changes within a system or process that provides documentary evidence of the sequence of actions performed. Audit trails answer the fundamental questions: who did what, when did they do it, where did it happen, and what was the result. They are essential for security monitoring, incident investigation, compliance demonstration, and accountability.",[31,893,895],{"id":894},"what-do-audit-trails-capture","What do audit trails capture?",[15,897,898],{},"Effective audit trails typically record:",[114,900,901,907,913,919,925,931],{},[117,902,903,906],{},[120,904,905],{},"User actions"," — logins, logouts, data access, data modifications, privilege changes",[117,908,909,912],{},[120,910,911],{},"System events"," — configuration changes, service starts and stops, errors, failures",[117,914,915,918],{},[120,916,917],{},"Administrative actions"," — user account creation and deletion, permission changes, policy updates",[117,920,921,924],{},[120,922,923],{},"Data changes"," — creation, modification, and deletion of records, including before and after values where applicable",[117,926,927,930],{},[120,928,929],{},"Access attempts"," — both successful and failed authentication and authorization attempts",[117,932,933,936],{},[120,934,935],{},"Security events"," — firewall rule changes, intrusion detection alerts, malware detections",[15,938,939],{},"Each audit trail entry should include:",[114,941,942,945,948,951,954,957],{},[117,943,944],{},"Timestamp (synchronized across systems)",[117,946,947],{},"User or system identity",[117,949,950],{},"Action performed",[117,952,953],{},"Target resource or data",[117,955,956],{},"Outcome (success or failure)",[117,958,959],{},"Source (IP address, device, or location)",[31,961,963],{"id":962},"what-are-the-audit-trail-requirements","What are the audit trail requirements?",[15,965,966],{},"Multiple compliance frameworks require audit trails:",[114,968,969,974,979,984],{},[117,970,971,973],{},[120,972,467],{}," — CC7.2 requires monitoring of system components for anomalies, and CC6.1 requires logical access controls with logging",[117,975,976,978],{},[120,977,476],{}," — control A.8.15 addresses logging, and A.8.17 addresses clock synchronization for accurate audit trails",[117,980,981,983],{},[120,982,490],{}," — the Security Rule requires audit controls that record and examine activity in systems containing ePHI (45 CFR 164.312(b))",[117,985,986,988],{},[120,987,504],{}," — Requirement 10 mandates logging and monitoring all access to network resources and cardholder data",[31,990,992],{"id":991},"how-do-you-implement-audit-trails","How do you implement audit trails?",[15,994,995],{},"To implement effective audit trails:",[183,997,998,1004,1010,1016,1022,1028,1034],{},[117,999,1000,1003],{},[120,1001,1002],{},"Enable logging"," — activate audit logging on all in-scope systems including applications, databases, operating systems, and network devices",[117,1005,1006,1009],{},[120,1007,1008],{},"Centralize logs"," — aggregate logs into a central platform (SIEM) for correlation and analysis",[117,1011,1012,1015],{},[120,1013,1014],{},"Protect integrity"," — ensure logs cannot be modified or deleted by users, including administrators",[117,1017,1018,1021],{},[120,1019,1020],{},"Synchronize time"," — use NTP to ensure timestamps are consistent across all systems",[117,1023,1024,1027],{},[120,1025,1026],{},"Define retention"," — establish retention periods aligned with compliance and business requirements",[117,1029,1030,1033],{},[120,1031,1032],{},"Monitor actively"," — review audit trails for suspicious activity, not just for compliance evidence",[117,1035,1036,1039],{},[120,1037,1038],{},"Automate alerts"," — configure alerts for critical events such as failed login attempts, privilege escalation, and unauthorized access",[31,1041,1043],{"id":1042},"how-long-should-audit-trails-be-retained","How long should audit trails be retained?",[15,1045,1046],{},"Retention requirements vary by framework and jurisdiction:",[114,1048,1049,1052,1055,1058],{},[117,1050,1051],{},"PCI DSS requires at least 12 months of audit trail history, with the most recent 3 months immediately available",[117,1053,1054],{},"HIPAA requires documentation retention for 6 years",[117,1056,1057],{},"ISO 27001 does not specify a fixed period but requires organizations to define and follow their own retention policy",[117,1059,1060],{},"SOC 2 audit periods typically require evidence covering the observation period",[31,1062,1064],{"id":1063},"what-are-common-pitfalls-with-audit-trails","What are common pitfalls with audit trails?",[114,1066,1067,1070,1073,1076,1079],{},[117,1068,1069],{},"Insufficient logging — missing critical events or systems",[117,1071,1072],{},"Log overload — logging too much without meaningful analysis",[117,1074,1075],{},"No log protection — allowing administrators to modify or delete logs",[117,1077,1078],{},"Inconsistent timestamps — making it impossible to correlate events across systems",[117,1080,1081],{},"No review process — collecting logs but never analyzing them",[31,1083,1085],{"id":1084},"how-does-episki-help-with-audit-trails","How does episki help with audit trails?",[15,1087,1088,1089,29],{},"episki records who did what, when, and on whose behalf — including agents. Every action carries provenance, and because writes made through the API and the hosted MCP server route through the same path as the UI, an agent's write is indistinguishable from a hand-made one in the audit log rather than landing in a side channel. Approvals record the approver and the rationale, and decisions that carry weight — accepting a risk, approving an exception — require one. Learn more on our ",[25,1090,847],{"href":846},{"title":258,"searchDepth":259,"depth":259,"links":1092},[1093],{"id":887,"depth":259,"text":888,"children":1094},[1095,1096,1097,1098,1099,1100],{"id":894,"depth":264,"text":895},{"id":962,"depth":264,"text":963},{"id":991,"depth":264,"text":992},{"id":1042,"depth":264,"text":1043},{"id":1063,"depth":264,"text":1064},{"id":1084,"depth":264,"text":1085},{},[277,867,868,869],[1104,877,1105,1106],"evidence-collection","continuous-monitoring","incident-response",{"title":1108,"description":1109},"What is an Audit Trail? Definition & Compliance Guide","An audit trail is a chronological record of system activities that provides evidence of who did what, when, and where for security and compliance purposes.","8.glossary\u002Faudit-trail","gwbZn86OgTUUVaArFZbCZPDIA20zQUGUIpEJLc1kzRg",[1113,1623],{"id":1114,"title":1115,"body":1116,"description":1609,"extension":271,"faq":1610,"frameworkSlug":277,"lastUpdated":862,"meta":1611,"navigation":274,"path":254,"relatedTerms":1612,"relatedTopics":1614,"seo":1618,"stem":1621,"__hash__":1622},"frameworkTopics\u002F5.frameworks\u002Fsoc2\u002Faudit-process.md","SOC 2 Audit Process",{"type":7,"value":1117,"toc":1585},[1118,1122,1131,1135,1138,1142,1166,1170,1178,1192,1195,1199,1202,1222,1230,1234,1237,1274,1277,1281,1288,1292,1330,1334,1391,1395,1398,1401,1439,1443,1489,1493,1496,1500,1503,1507,1510,1513,1516,1530,1533,1537,1567,1571],[10,1119,1121],{"id":1120},"how-the-soc-2-audit-process-works","How the SOC 2 audit process works",[15,1123,1124,1125,1127,1128,1130],{},"The ",[25,1126,467],{"href":466}," audit process can feel opaque if you have never been through one. Unlike a certification like ",[25,1129,476],{"href":475}," where a registrar issues a certificate, SOC 2 produces an auditor's report — a detailed opinion letter from a licensed CPA firm. Understanding each phase removes surprises and keeps your team on track.",[10,1132,1134],{"id":1133},"phase-1-scoping-and-readiness-assessment","Phase 1: Scoping and readiness assessment",[15,1136,1137],{},"Before engaging an auditor, define what is in scope and evaluate how ready you are.",[31,1139,1141],{"id":1140},"define-scope","Define scope",[114,1143,1144,1150,1160],{},[117,1145,1146,1149],{},[120,1147,1148],{},"Systems",": Identify the applications, infrastructure, databases, and third-party services that store, process, or transmit customer data.",[117,1151,1152,1154,1155,1159],{},[120,1153,218],{},": Security is required. Add availability, processing integrity, confidentiality, or privacy based on customer commitments and the nature of your service. See the ",[25,1156,1158],{"href":1157},"\u002Fframeworks\u002Fsoc2\u002Ftrust-services-criteria","Trust Services Criteria deep dive"," for guidance.",[117,1161,1162,1165],{},[120,1163,1164],{},"Service commitments",": Review your terms of service, SLAs, and data processing agreements. Auditors will test controls against these commitments.",[31,1167,1169],{"id":1168},"conduct-a-gap-analysis","Conduct a gap analysis",[15,1171,1172,1173,1177],{},"Compare your current controls against ",[25,1174,1176],{"href":1175},"\u002Fframeworks\u002Fsoc2\u002Frequirements","SOC 2 requirements",". A readiness assessment identifies:",[114,1179,1180,1183,1186,1189],{},[117,1181,1182],{},"Controls that already satisfy criteria",[117,1184,1185],{},"Gaps where controls are missing or undocumented",[117,1187,1188],{},"Evidence that exists versus evidence you still need to collect",[117,1190,1191],{},"Policies that need to be written or updated",[15,1193,1194],{},"Many organizations perform this internally or hire a consultant. The output should be a remediation plan with owners and deadlines.",[31,1196,1198],{"id":1197},"remediate-gaps","Remediate gaps",[15,1200,1201],{},"Address the findings from your gap analysis before the audit begins. Common remediation items include:",[114,1203,1204,1207,1210,1213,1216,1219],{},[117,1205,1206],{},"Writing or formalizing information security policies",[117,1208,1209],{},"Enabling multi-factor authentication across all critical systems",[117,1211,1212],{},"Implementing centralized logging and monitoring",[117,1214,1215],{},"Establishing a vendor risk management process",[117,1217,1218],{},"Conducting security awareness training for all employees",[117,1220,1221],{},"Documenting an incident response plan and running a tabletop exercise",[15,1223,1224,1225,1229],{},"Budget four to twelve weeks for remediation depending on the size of your gap list. Use the ",[25,1226,1228],{"href":1227},"\u002Fframeworks\u002Fsoc2\u002Fchecklist","SOC 2 compliance checklist"," to track progress systematically.",[10,1231,1233],{"id":1232},"phase-2-selecting-an-auditor","Phase 2: Selecting an auditor",[15,1235,1236],{},"SOC 2 audits must be performed by a CPA firm licensed to issue SOC reports. Not all CPA firms are equal — look for:",[114,1238,1239,1245,1251,1257,1268],{},[117,1240,1241,1244],{},[120,1242,1243],{},"SOC 2 experience",": Ask how many SOC 2 engagements they complete per year and whether they have experience with companies at your stage and in your industry.",[117,1246,1247,1250],{},[120,1248,1249],{},"Technology alignment",": Firms that understand cloud-native architectures, CI\u002FCD pipelines, and modern SaaS stacks will ask better questions and move faster.",[117,1252,1253,1256],{},[120,1254,1255],{},"Communication style",": You will work closely with the audit team for weeks or months. Clear, responsive communication matters.",[117,1258,1259,1262,1263,1267],{},[120,1260,1261],{},"Pricing transparency",": Request a fixed-fee quote or a detailed estimate. Understand what triggers additional fees. See our ",[25,1264,1266],{"href":1265},"\u002Fframeworks\u002Fsoc2\u002Fcost","SOC 2 cost breakdown"," for benchmarks.",[117,1269,1270,1273],{},[120,1271,1272],{},"Timeline availability",": Popular audit firms book up quarters in advance. Start the selection process early.",[15,1275,1276],{},"Request proposals from two to four firms, compare scope and pricing, and check references from companies similar to yours.",[10,1278,1280],{"id":1279},"phase-3-the-type-i-audit","Phase 3: The Type I audit",[15,1282,161,1283,1287],{},[25,1284,1286],{"href":1285},"\u002Fframeworks\u002Fsoc2\u002Ftype-1-vs-type-2","SOC 2 Type I"," audit evaluates whether controls are suitably designed and implemented as of a specific date — a point-in-time assessment.",[31,1289,1291],{"id":1290},"what-to-expect","What to expect",[183,1293,1294,1300,1306,1312,1318,1324],{},[117,1295,1296,1299],{},[120,1297,1298],{},"Kickoff meeting",": The auditor reviews scope, systems, and criteria with your team. They will share a request list detailing the evidence and documentation they need.",[117,1301,1302,1305],{},[120,1303,1304],{},"Evidence collection",": Your team gathers policies, configurations, screenshots, access lists, and other artifacts. This is typically the most time-consuming step.",[117,1307,1308,1311],{},[120,1309,1310],{},"Walkthroughs and inquiries",": The auditor conducts interviews with control owners to understand how processes work. They may ask for live demonstrations.",[117,1313,1314,1317],{},[120,1315,1316],{},"Testing",": The auditor inspects evidence to confirm controls are designed to meet the criteria. For Type I, they are validating design — not operating effectiveness over time.",[117,1319,1320,1323],{},[120,1321,1322],{},"Issue identification",": If the auditor finds control gaps or design deficiencies, they will flag them. You may have an opportunity to remediate before the report is finalized.",[117,1325,1326,1329],{},[120,1327,1328],{},"Report drafting and delivery",": The auditor produces a report containing their opinion, a description of your system, the criteria tested, and any exceptions noted.",[31,1331,1333],{"id":1332},"type-i-timeline","Type I timeline",[39,1335,1336,1346],{},[42,1337,1338],{},[45,1339,1340,1343],{},[48,1341,1342],{},"Step",[48,1344,1345],{},"Duration",[58,1347,1348,1356,1364,1372,1379],{},[45,1349,1350,1353],{},[63,1351,1352],{},"Readiness and remediation",[63,1354,1355],{},"4–12 weeks",[45,1357,1358,1361],{},[63,1359,1360],{},"Auditor selection and contracting",[63,1362,1363],{},"2–4 weeks",[45,1365,1366,1369],{},[63,1367,1368],{},"Evidence collection and fieldwork",[63,1370,1371],{},"3–6 weeks",[45,1373,1374,1377],{},[63,1375,1376],{},"Report drafting and review",[63,1378,1363],{},[45,1380,1381,1386],{},[63,1382,1383],{},[120,1384,1385],{},"Total",[63,1387,1388],{},[120,1389,1390],{},"11–26 weeks",[10,1392,1394],{"id":1393},"phase-4-the-type-ii-audit","Phase 4: The Type II audit",[15,1396,1397],{},"A SOC 2 Type II audit tests whether controls operated effectively over a defined observation period, typically three to twelve months. Most organizations choose a six-month or twelve-month window.",[31,1399,1291],{"id":1400},"what-to-expect-1",[183,1402,1403,1409,1415,1421,1427,1433],{},[117,1404,1405,1408],{},[120,1406,1407],{},"Observation period begins",": The clock starts on the agreed date. All controls must be operating from this point forward.",[117,1410,1411,1414],{},[120,1412,1413],{},"Ongoing evidence collection",": Unlike Type I, you need to collect evidence continuously throughout the observation period — access reviews, change approvals, incident logs, monitoring alerts.",[117,1416,1417,1420],{},[120,1418,1419],{},"Midpoint check-in"," (optional but recommended): Some auditors offer an interim review partway through the observation period to catch issues early.",[117,1422,1423,1426],{},[120,1424,1425],{},"Fieldwork",": After the observation period ends, the auditor performs detailed testing. They sample transactions, review logs, and verify that controls operated consistently.",[117,1428,1429,1432],{},[120,1430,1431],{},"Exception handling",": If a control failed during the period, the auditor documents the exception. A few exceptions do not automatically mean a qualified opinion, but patterns of failure will.",[117,1434,1435,1438],{},[120,1436,1437],{},"Final report",": The Type II report includes everything from Type I plus the auditor's testing results and opinion on operating effectiveness.",[31,1440,1442],{"id":1441},"type-ii-timeline","Type II timeline",[39,1444,1445,1453],{},[42,1446,1447],{},[45,1448,1449,1451],{},[48,1450,1342],{},[48,1452,1345],{},[58,1454,1455,1463,1471,1477],{},[45,1456,1457,1460],{},[63,1458,1459],{},"Observation period",[63,1461,1462],{},"3–12 months",[45,1464,1465,1468],{},[63,1466,1467],{},"Fieldwork after period ends",[63,1469,1470],{},"4–8 weeks",[45,1472,1473,1475],{},[63,1474,1376],{},[63,1476,1363],{},[45,1478,1479,1484],{},[63,1480,1481],{},[120,1482,1483],{},"Total (after readiness)",[63,1485,1486],{},[120,1487,1488],{},"5–15 months",[10,1490,1492],{"id":1491},"phase-5-report-delivery-and-beyond","Phase 5: Report delivery and beyond",[15,1494,1495],{},"Once you receive your SOC 2 report, the process does not end.",[31,1497,1499],{"id":1498},"distribute-the-report","Distribute the report",[15,1501,1502],{},"SOC 2 reports are restricted-use documents. Share them under NDA with customers, prospects, and partners who request them. Many companies set up a trust center or compliance portal to manage requests.",[31,1504,1506],{"id":1505},"plan-for-the-next-period","Plan for the next period",[15,1508,1509],{},"SOC 2 Type II reports cover a specific window. To maintain continuous coverage, plan the next observation period to begin immediately after the current one ends. Auditors call this a \"bridge period\" — any gap between periods means you have a coverage lapse that buyers may question.",[31,1511,1512],{"id":1105},"Continuous monitoring",[15,1514,1515],{},"The most efficient SOC 2 programs do not treat the audit as a seasonal event. Instead, they:",[114,1517,1518,1521,1524,1527],{},[117,1519,1520],{},"Monitor control health in real time",[117,1522,1523],{},"Collect evidence automatically where possible",[117,1525,1526],{},"Review and update policies on a regular cadence",[117,1528,1529],{},"Track remediation items from previous audit exceptions",[15,1531,1532],{},"This continuous approach reduces the scramble before each audit and catches issues before they become exceptions.",[10,1534,1536],{"id":1535},"common-pitfalls-in-the-soc-2-audit-process","Common pitfalls in the SOC 2 audit process",[114,1538,1539,1545,1551,1557],{},[117,1540,1541,1544],{},[120,1542,1543],{},"Starting evidence collection too late",": Begin during readiness, not after the auditor's first request list arrives.",[117,1546,1547,1550],{},[120,1548,1549],{},"Single-threaded ownership",": SOC 2 touches engineering, IT, HR, and legal. Assign control owners across teams and give them visibility into the timeline.",[117,1552,1553,1556],{},[120,1554,1555],{},"Ignoring the observation period",": For Type II, controls must operate every day of the period. A policy that exists but is not followed will result in exceptions.",[117,1558,1559,1562,1563,1566],{},[120,1560,1561],{},"Choosing the wrong auditor",": A mismatched firm can slow the process and increase ",[25,1564,1565],{"href":1265},"costs",". Do your diligence upfront.",[10,1568,1570],{"id":1569},"how-episki-helps","How episki helps",[15,1572,1573,1574,1580,1581,29],{},"episki shortens the audit by making the evidence self-describing. Your auditor gets scoped guest access per assessment — auditor seats are not billed — plus a portal with Q&A threads so requests and responses stay attached to the evidence they concern. Because collection runs as deterministic recipes rather than model output, an auditor can read exactly how each artifact was gathered, and every check carries an explicit verdict with the records behind it. ",[25,1575,1579],{"href":1576,"rel":1577},"https:\u002F\u002Fapp.episki.com\u002Fauth\u002Fregister",[1578],"nofollow","Start a free trial"," or review the ",[25,1582,1584],{"href":1583},"\u002Fframeworks\u002Fsoc2\u002Freadiness-assessment","readiness assessment",{"title":258,"searchDepth":259,"depth":259,"links":1586},[1587,1588,1593,1594,1598,1602,1607,1608],{"id":1120,"depth":259,"text":1121},{"id":1133,"depth":259,"text":1134,"children":1589},[1590,1591,1592],{"id":1140,"depth":264,"text":1141},{"id":1168,"depth":264,"text":1169},{"id":1197,"depth":264,"text":1198},{"id":1232,"depth":259,"text":1233},{"id":1279,"depth":259,"text":1280,"children":1595},[1596,1597],{"id":1290,"depth":264,"text":1291},{"id":1332,"depth":264,"text":1333},{"id":1393,"depth":259,"text":1394,"children":1599},[1600,1601],{"id":1400,"depth":264,"text":1291},{"id":1441,"depth":264,"text":1442},{"id":1491,"depth":259,"text":1492,"children":1603},[1604,1605,1606],{"id":1498,"depth":264,"text":1499},{"id":1505,"depth":264,"text":1506},{"id":1105,"depth":264,"text":1512},{"id":1535,"depth":259,"text":1536},{"id":1569,"depth":259,"text":1570},"A step-by-step guide to the SOC 2 audit process, from readiness assessment through final report delivery, including timelines for Type I and Type II engagements.",null,{},[277,1613],"grc",[1615,1616,1617],"type-1-vs-type-2","requirements","cost",{"title":1619,"description":1620},"SOC 2 Audit Process — Step-by-Step Guide for 2026","Walk through the SOC 2 audit process step by step. Learn about readiness assessments, auditor selection, Type I vs Type II timelines, and what to expect.","5.frameworks\u002Fsoc2\u002Faudit-process","LfOEI1nM_ecArjeS2Hd3b9u595Ev756EhnPBXdoWlb0",{"id":1624,"title":1625,"body":1626,"description":1981,"extension":271,"faq":1982,"frameworkSlug":277,"lastUpdated":862,"meta":1999,"navigation":274,"path":2000,"relatedTerms":2001,"relatedTopics":2005,"seo":2006,"stem":2009,"__hash__":2010},"frameworkTopics\u002F5.frameworks\u002Fsoc2\u002Favailability-criteria.md","SOC 2 Availability Criteria",{"type":7,"value":1627,"toc":1960},[1628,1632,1638,1641,1645,1650,1670,1673,1677,1680,1684,1704,1708,1722,1725,1729,1732,1735,1758,1761,1778,1781,1785,1788,1791,1808,1811,1825,1838,1842,1845,1871,1882,1886,1889,1892,1896,1928,1932,1949,1951],[10,1629,1631],{"id":1630},"availability-is-the-soc-2-criterion-most-visible-to-customers","Availability is the SOC 2 criterion most visible to customers",[15,1633,1634,1635,1637],{},"When a customer's application goes down and they cannot log in, they blame your uptime. The availability Trust Services Criterion is where ",[25,1636,467],{"href":466}," turns that reality into a structured set of controls. The criterion applies when an organization commits to specific uptime levels or recovery capabilities — typically through published SLAs, status pages, or contractual obligations. If your customers rely on your service being up, availability belongs in your audit scope.",[15,1639,1640],{},"Availability is optional in SOC 2, but for SaaS companies selling into enterprise or mid-market, it is often the first additional criterion added beyond security. Enterprise procurement teams expect it because their risk frameworks treat vendor availability as a top-tier concern.",[10,1642,1644],{"id":1643},"what-the-availability-criterion-covers","What the availability criterion covers",[15,1646,1124,1647,1649],{},[25,1648,218],{"href":1157}," define availability as \"the accessibility of the system, products, or services as stipulated by a contract or service level agreement.\" Availability has three dedicated control categories in the A1 series, plus overlap with several Common Criteria.",[114,1651,1652,1658,1664],{},[117,1653,1654,1657],{},[120,1655,1656],{},"A1.1"," — The entity maintains, monitors, and evaluates current processing capacity and use of system components to manage capacity demand and to enable the implementation of additional capacity.",[117,1659,1660,1663],{},[120,1661,1662],{},"A1.2"," — The entity authorizes, designs, develops or acquires, implements, operates, approves, maintains, and monitors environmental protections, software, data backup processes, and recovery infrastructure to meet its availability objectives.",[117,1665,1666,1669],{},[120,1667,1668],{},"A1.3"," — The entity tests recovery plan procedures supporting system recovery to meet its availability objectives.",[15,1671,1672],{},"A1 is short but dense. Each control generates operational evidence across the observation period.",[10,1674,1676],{"id":1675},"a11-capacity-planning-and-monitoring","A1.1 — Capacity planning and monitoring",[15,1678,1679],{},"A1.1 requires that you know how much capacity your system has, how much it is using, and how you will add more when demand grows. Auditors look for a capacity management process that operates continuously, not a one-time analysis.",[31,1681,1683],{"id":1682},"typical-controls","Typical controls",[114,1685,1686,1689,1692,1695,1698,1701],{},[117,1687,1688],{},"Real-time capacity monitoring dashboards (CPU, memory, storage, network, database connections)",[117,1690,1691],{},"Defined thresholds for capacity alerts",[117,1693,1694],{},"Scheduled capacity reviews with documented outcomes",[117,1696,1697],{},"Forecasting based on growth assumptions",[117,1699,1700],{},"Auto-scaling for elastic workloads",[117,1702,1703],{},"Procurement lead time built into capacity forecasting",[31,1705,1707],{"id":1706},"evidence-expectations","Evidence expectations",[114,1709,1710,1713,1716,1719],{},[117,1711,1712],{},"Capacity dashboards with historical data spanning the observation period",[117,1714,1715],{},"Capacity review meeting notes or tickets",[117,1717,1718],{},"Alert history showing capacity thresholds being monitored",[117,1720,1721],{},"Procurement or provisioning records when capacity was added",[15,1723,1724],{},"Organizations running in public cloud typically have strong A1.1 posture out of the box because auto-scaling and managed services remove much of the manual capacity work. Organizations running colocated hardware have more evidence to produce.",[10,1726,1728],{"id":1727},"a12-environmental-protections-and-recovery-infrastructure","A1.2 — Environmental protections and recovery infrastructure",[15,1730,1731],{},"A1.2 covers the infrastructure that supports availability — redundancy, backups, and environmental controls. The term \"environmental\" is broader than physical environment; it includes software resilience as well.",[31,1733,1683],{"id":1734},"typical-controls-1",[114,1736,1737,1740,1743,1746,1749,1752,1755],{},[117,1738,1739],{},"Multi-region or multi-AZ deployment architecture",[117,1741,1742],{},"Redundant components (load balancers, databases, caches)",[117,1744,1745],{},"Automated failover mechanisms",[117,1747,1748],{},"Backup and recovery procedures with defined retention",[117,1750,1751],{},"Data replication strategy",[117,1753,1754],{},"Physical environmental controls for on-premises facilities (power, cooling, fire suppression)",[117,1756,1757],{},"Network isolation and DDoS protections",[31,1759,1707],{"id":1760},"evidence-expectations-1",[114,1762,1763,1766,1769,1772,1775],{},[117,1764,1765],{},"Architecture diagrams showing redundancy",[117,1767,1768],{},"Backup job logs confirming successful backups",[117,1770,1771],{},"Backup restoration test records",[117,1773,1774],{},"Failover test results if applicable",[117,1776,1777],{},"Data center certifications (for colocated hardware)",[15,1779,1780],{},"A common gap in A1.2 is backup coverage. Teams have backups but do not test restoration until an incident forces it. Auditors look for proactive restoration tests.",[10,1782,1784],{"id":1783},"a13-recovery-testing","A1.3 — Recovery testing",[15,1786,1787],{},"A1.3 is where availability and business continuity meet. The control requires that recovery procedures be tested so they work when a real disruption occurs.",[31,1789,1683],{"id":1790},"typical-controls-2",[114,1792,1793,1796,1799,1802,1805],{},[117,1794,1795],{},"Documented disaster recovery plan with defined RPO and RTO",[117,1797,1798],{},"Annual or more frequent DR tests",[117,1800,1801],{},"Scenario-based testing (region failure, database failure, application failure)",[117,1803,1804],{},"Post-test reviews with remediation items",[117,1806,1807],{},"Business continuity plan integration",[31,1809,1707],{"id":1810},"evidence-expectations-2",[114,1812,1813,1816,1819,1822],{},[117,1814,1815],{},"Current DR plan document with approval evidence",[117,1817,1818],{},"DR test reports from the observation period",[117,1820,1821],{},"Remediation tracking for issues identified during tests",[117,1823,1824],{},"Evidence that lessons were incorporated into the plan",[15,1826,1827,1828,1832,1833,1837],{},"See ",[25,1829,1831],{"href":1830},"\u002Fglossary\u002Fbusiness-continuity","business continuity"," and ",[25,1834,1836],{"href":1835},"\u002Fglossary\u002Fdisaster-recovery","disaster recovery"," for related terms.",[10,1839,1841],{"id":1840},"overlap-with-other-trust-services-criteria","Overlap with other Trust Services Criteria",[15,1843,1844],{},"Availability does not exist in isolation. Several Common Criteria contribute to the picture.",[114,1846,1847,1853,1859,1865],{},[117,1848,1849,1852],{},[120,1850,1851],{},"CC7"," (system operations) — monitoring that detects availability events feeds the availability controls directly",[117,1854,1855,1858],{},[120,1856,1857],{},"CC9.1"," (business continuity) — overlaps heavily with A1.3",[117,1860,1861,1864],{},[120,1862,1863],{},"CC2"," (communication) — customer and internal communication during outages",[117,1866,1867,1870],{},[120,1868,1869],{},"CC8"," (change management) — poorly managed changes cause outages",[15,1872,1873,1874,1832,1878,29],{},"A well-designed SOC 2 program maps controls once and applies them to every applicable criterion. For example, a failover test may satisfy A1.2, A1.3, and CC9.1 simultaneously. The same mapping applies in ",[25,1875,1877],{"href":1876},"\u002Fframeworks\u002Fsoc2\u002Fcontinuous-monitoring","continuous monitoring",[25,1879,1881],{"href":1880},"\u002Fframeworks\u002Fsoc2\u002Fincident-response","incident response",[10,1883,1885],{"id":1884},"how-this-fits-into-soc-2","How this fits into SOC 2",[15,1887,1888],{},"Availability is the most visible criterion for customers — outages generate status page updates, incident reports, and sometimes contractual credits. Auditors know this, so they examine availability controls against both the design and real operational outcomes during the observation period. If you had an outage during the period, the auditor will typically request the incident record and verify that A1.3 controls — recovery procedures — were executed and effective.",[15,1890,1891],{},"This also means availability has the clearest connection between control effectiveness and business impact. A clean availability section in a SOC 2 report supports sales conversations about enterprise reliability in a way that the security criterion alone cannot.",[10,1893,1895],{"id":1894},"common-mistakes","Common mistakes",[114,1897,1898,1904,1910,1916,1922],{},[117,1899,1900,1903],{},[120,1901,1902],{},"SLA without monitoring."," A published uptime commitment that nobody measures is a recipe for exceptions. If you commit to 99.9%, measure it and report it.",[117,1905,1906,1909],{},[120,1907,1908],{},"Backups without restoration tests."," Untested backups are hope, not controls. Run periodic restorations.",[117,1911,1912,1915],{},[120,1913,1914],{},"DR plan in a drawer."," A plan that has not been updated in two years is a design problem even if no disaster happened. Review annually.",[117,1917,1918,1921],{},[120,1919,1920],{},"No RPO or RTO."," \"We'll figure it out\" is not an acceptable answer to what data loss you can tolerate. Define the numbers.",[117,1923,1924,1927],{},[120,1925,1926],{},"Single-region deployments with availability criterion."," If your architecture cannot survive a regional failure and you are claiming availability, the auditor will note the gap. Match the criterion to reality.",[10,1929,1931],{"id":1930},"implementation-tips","Implementation tips",[114,1933,1934,1937,1940,1943,1946],{},[117,1935,1936],{},"Publish a status page that reflects real uptime. Auditors sometimes check it against your internal incident records.",[117,1938,1939],{},"Define RPO and RTO per system tier. Not every service needs the same recovery targets, and differentiating them makes the plan credible.",[117,1941,1942],{},"Test DR quarterly with different scenarios rotating across the year. Document each test.",[117,1944,1945],{},"Treat capacity alerts as first-class signals. If capacity thresholds are consistently breached with no action, A1.1 is weak.",[117,1947,1948],{},"Integrate capacity planning with business forecasts. Sales pipeline can predict capacity demand if the signal is used.",[10,1950,1570],{"id":1569},[15,1952,1953,1954,1957,1958,29],{},"Availability evidence lives in your platform stack, and episki now reads it there. The Supabase connector evaluates point-in-time recovery and SSL enforcement; Vercel and Netlify connectors evaluate deployment protection and forced HTTPS; AWS sweeps across multiple accounts and regions with per-account failure isolation. Each check writes a verdict rather than filing a config dump, and a backup or recovery setting that is absent — not merely set to false — is treated as unprotected rather than assumed fine. ",[25,1955,1579],{"href":1576,"rel":1956},[1578]," or see the ",[25,1959,218],{"href":1157},{"title":258,"searchDepth":259,"depth":259,"links":1961},[1962,1963,1964,1968,1972,1976,1977,1978,1979,1980],{"id":1630,"depth":259,"text":1631},{"id":1643,"depth":259,"text":1644},{"id":1675,"depth":259,"text":1676,"children":1965},[1966,1967],{"id":1682,"depth":264,"text":1683},{"id":1706,"depth":264,"text":1707},{"id":1727,"depth":259,"text":1728,"children":1969},[1970,1971],{"id":1734,"depth":264,"text":1683},{"id":1760,"depth":264,"text":1707},{"id":1783,"depth":259,"text":1784,"children":1973},[1974,1975],{"id":1790,"depth":264,"text":1683},{"id":1810,"depth":264,"text":1707},{"id":1840,"depth":259,"text":1841},{"id":1884,"depth":259,"text":1885},{"id":1894,"depth":259,"text":1895},{"id":1930,"depth":259,"text":1931},{"id":1569,"depth":259,"text":1570},"Deep dive on the SOC 2 Availability Trust Services Criterion. A1 series controls, uptime commitments, capacity planning, and disaster recovery.",{"items":1983},[1984,1987,1990,1993,1996],{"label":1985,"content":1986},"When should I include the availability criterion in my SOC 2?","Include availability when you have published SLAs, customers depend on continuous uptime, or contracts include availability commitments with penalties. Many SaaS companies add availability in their first SOC 2 if they sell into enterprise or mid-market.",{"label":1988,"content":1989},"Does the availability criterion require 99.99% uptime?","No. SOC 2 does not set a specific uptime number. It requires that you have defined availability commitments, measure against them, and have controls that support those commitments. The number is whatever you commit to in SLAs or customer contracts.",{"label":1991,"content":1992},"What is the difference between availability and business continuity?","Availability in SOC 2 covers day-to-day operation of the system — capacity, redundancy, monitoring. Business continuity covers response to disruptive events — the ability to recover when something goes wrong. Both are tested under availability controls (A1.3 specifically).",{"label":1994,"content":1995},"Do I need to test disaster recovery annually?","Yes. Auditors expect documented DR tests at least annually, with defined scenarios, results, and corrective actions. Many mature SOC 2 programs test quarterly, rotating scenarios.",{"label":1997,"content":1998},"What evidence do auditors expect for availability?","Auditors typically review published SLAs, capacity monitoring dashboards, incident history for outages, DR test results, and evidence that the DR plan was executed or simulated during the observation period.",{},"\u002Fframeworks\u002Fsoc2\u002Favailability-criteria",[2002,2003,2004,277],"business-continuity","disaster-recovery","monitoring",[283,1105,1106],{"title":2007,"description":2008},"SOC 2 Availability Criteria (2026): A1 Controls Deep Dive","Master the SOC 2 Availability criterion. A1.1 capacity planning, A1.2 environmental protections, A1.3 recovery, and common audit evidence.","5.frameworks\u002Fsoc2\u002Favailability-criteria","avp3L1fdKIB8H1eC0EtAZLjtreRSNUhv9pJRpcoXh44",{"id":2012,"title":2013,"advantages":2014,"body":2036,"checklist":2533,"cta":2542,"description":258,"extension":271,"faq":2545,"hero":2562,"lastUpdated":862,"meta":2576,"name":309,"navigation":274,"path":466,"resources":2577,"seo":2590,"slug":277,"stats":2593,"stem":2603,"__hash__":2604},"frameworks\u002F5.frameworks\u002Fsoc2.md","Soc2",[2015,2022,2029],{"title":2016,"description":2017,"bullets":2018},"Mapped once, reused forever","Applies Trust Service Criteria to your existing controls and keeps overlaps synced.",[2019,2020,2021],"Control graph highlights reuse across security, availability, and confidentiality","AI suggests narratives and testing procedures","Version history shows every update for auditors",{"title":2023,"description":2024,"bullets":2025},"Evidence organized by control","Upload and track screenshots, configs, and exports in a structured evidence locker.",[2026,2027,2028],"Organized screenshots, configs, and test exports","Alerting when evidence expires or SLAs slip","Immutable locker with reviewer threads",{"title":2030,"description":2031,"bullets":2032},"Auditor collaboration hub","Invite your auditor with scoped access and keep Q&A right next to each control.",[2033,2034,2035],"Bulk requests & fulfillment tracking","Redacted file sharing with access controls","One-click SOC 2 summaries for customers",{"type":7,"value":2037,"toc":2514},[2038,2041,2044,2052,2058,2064,2068,2071,2076,2082,2094,2098,2103,2107,2110,2114,2121,2125,2128,2132,2140,2144,2151,2155,2158,2161,2178,2186,2190,2195,2233,2236,2240,2243,2246,2284,2290,2294,2297,2353,2356,2360,2363,2370,2377,2384,2398,2406,2410,2417,2449,2452,2456,2459,2462,2500,2502],[10,2039,296],{"id":2040},"what-is-soc-2",[15,2042,2043],{},"SOC 2 (System and Organization Controls 2) is an auditing standard developed by the American Institute of Certified Public Accountants (AICPA) that evaluates how a service organization manages customer data. A SOC 2 report is the de facto security credential for modern SaaS companies — enterprise buyers request it before signing, procurement teams rely on it during vendor reviews, and auditors consult it when assessing outsourced systems. Unlike a prescriptive standard, SOC 2 is principle-based. It does not tell you which tools to deploy; it tells you which outcomes you must demonstrate and leaves the implementation details to you.",[15,2045,2046,2047,2051],{},"SOC 2 evolved from SAS 70, an older attestation framework used primarily for financial reporting systems. As technology service providers increased their role in handling sensitive data, the AICPA introduced the SOC reporting suite. SOC 1 continued to address controls relevant to financial reporting. SOC 2 and SOC 3 shifted attention to information security, availability, and related commitments. Today, SOC 2 is issued under the AICPA's AT-C 105 and AT-C 205 attestation standards, following the ",[25,2048,2050],{"href":2049},"\u002Fglossary\u002Fssae-18","SSAE 18"," framework.",[15,2053,2054,2055,2057],{},"A SOC 2 engagement produces an opinion letter from a licensed CPA firm. That letter is the report buyers ask for. It documents the system under audit, the ",[25,2056,218],{"href":1157}," selected, the controls in place, the testing the auditor performed, and any exceptions noted. A clean SOC 2 opinion signals to the market that a third party examined your controls and found them suitable — or in the case of Type II, found them operating effectively across a defined window.",[15,2059,2060,2061,2063],{},"SOC 2 is built on five ",[120,2062,218],{},": security, availability, processing integrity, confidentiality, and privacy. Security is mandatory. The other four are optional and chosen based on your service commitments and customer expectations. Most first-time SOC 2 audits cover security alone or security plus one or two additional criteria. Scope expansion happens later, as the program matures.",[10,2065,2067],{"id":2066},"soc-2-type-i-vs-type-ii","SOC 2 Type I vs Type II",[15,2069,2070],{},"Every SOC 2 engagement is either Type I or Type II, and the difference matters.",[15,2072,161,2073,2075],{},[120,2074,1286],{}," report evaluates whether controls are suitably designed and implemented as of a single date. Think of it as a design review. The auditor confirms your policies exist, your technical controls are configured, and your processes are in place. Type I is the fastest path to a SOC 2 report and is useful when a deal is on the line, but it does not prove your controls work day after day.",[15,2077,161,2078,2081],{},[120,2079,2080],{},"SOC 2 Type II"," report evaluates whether controls operated effectively across an observation period, typically three to twelve months. The auditor samples evidence from throughout the period — access reviews, change approvals, incident tickets, monitoring alerts — to confirm that controls were not just designed but consistently executed. Most enterprise buyers require a Type II, and many will not accept a Type I at all.",[15,2083,2084,2085,2088,2089,1832,2092,29],{},"For a full comparison including cost benchmarks, observation period tradeoffs, and decision frameworks, see ",[25,2086,2087],{"href":1285},"SOC 2 Type 1 vs Type 2",". Related glossary terms: ",[25,2090,2091],{"href":169},"SOC 2 Type 2",[25,2093,218],{"href":217},[10,2095,2097],{"id":2096},"the-five-trust-services-criteria","The five Trust Services Criteria",[15,2099,1124,2100,2102],{},[25,2101,218],{"href":1157}," define the principles your controls must satisfy. Each criterion addresses a different aspect of how a service organization protects and manages customer data.",[31,2104,2106],{"id":2105},"security-common-criteria-required","Security (Common Criteria) — required",[15,2108,2109],{},"The security criterion, also called the Common Criteria, is required for every SOC 2 engagement. It evaluates whether the system is protected against unauthorized access — both logical and physical. The Common Criteria are organized into nine categories (CC1 through CC9) that map to the COSO internal control framework and cover governance, communication, risk assessment, monitoring, access control, system operations, change management, and vendor risk. Every SOC 2 report includes testing against these categories.",[31,2111,2113],{"id":2112},"availability","Availability",[15,2115,2116,2117,2120],{},"The availability criterion applies when an organization commits to specific uptime levels or recovery capabilities. It covers environmental protections, capacity planning, disaster recovery, and incident management for availability-impacting events. If your product has published SLAs or customers rely on continuous uptime, include availability. Read the ",[25,2118,2119],{"href":2000},"availability criteria deep dive"," for common controls and implementation patterns.",[31,2122,2124],{"id":2123},"processing-integrity","Processing integrity",[15,2126,2127],{},"Processing integrity focuses on whether the system processes data completely, validly, accurately, timely, and with proper authorization. This criterion is relevant for platforms that perform calculations, process financial transactions, or transform customer data. It is less common in first-time SOC 2 audits but important for fintech, billing platforms, and data pipelines that customers rely on for operational decisions.",[31,2129,2131],{"id":2130},"confidentiality","Confidentiality",[15,2133,2134,2135,2139],{},"The confidentiality criterion addresses information designated as confidential — distinct from personal information. It covers data classification, access restrictions, encryption, and secure disposal of confidential data. If you handle intellectual property, business plans, or other sensitive non-personal information on behalf of clients, include confidentiality. See the ",[25,2136,2138],{"href":2137},"\u002Fframeworks\u002Fsoc2\u002Fconfidentiality-criteria","confidentiality criteria deep dive"," for details.",[31,2141,2143],{"id":2142},"privacy","Privacy",[15,2145,2146,2147,29],{},"The privacy criterion applies to personal information — data that can identify an individual. It evaluates whether your data practices match your stated privacy commitments across notice, choice, collection, use, retention, disclosure, security, and accuracy. Privacy aligns closely with regulations like GDPR and CCPA and is the most demanding criterion in terms of control coverage. For a full walkthrough, see the ",[25,2148,2150],{"href":2149},"\u002Fframeworks\u002Fsoc2\u002Fprivacy-criteria","privacy criteria deep dive",[10,2152,2154],{"id":2153},"who-needs-soc-2-compliance","Who needs SOC 2 compliance?",[15,2156,2157],{},"SOC 2 is not legally mandated, but the market treats it as a cost of doing business. Any SaaS company, cloud service provider, managed service provider, or data processor that handles customer data is a likely SOC 2 candidate. If your customers are businesses and their security teams will scrutinize your controls before signing, SOC 2 is almost certainly on your roadmap.",[15,2159,2160],{},"Companies typically pursue SOC 2 when one or more of the following is true:",[114,2162,2163,2166,2169,2172,2175],{},[117,2164,2165],{},"Enterprise prospects are asking for a report during procurement or vendor reviews.",[117,2167,2168],{},"Sales cycles are slowing because buyers are blocking deals on security questionnaires.",[117,2170,2171],{},"Existing customers are requesting a current SOC 2 report during annual reviews.",[117,2173,2174],{},"Investors or partners are asking about the company's security posture.",[117,2176,2177],{},"The business is entering regulated verticals like financial services, healthcare, or government.",[15,2179,2180,2181,2185],{},"Industries that almost always require SOC 2 from their vendors include financial services, healthcare, legal technology, HR technology, martech that handles PII, and any B2B SaaS selling into enterprise accounts. For SaaS companies specifically, SOC 2 has become table stakes — see ",[25,2182,2184],{"href":2183},"\u002Fblog\u002Fsoc2-for-saas","SOC 2 for SaaS"," for a deeper discussion.",[10,2187,2189],{"id":2188},"the-soc-2-audit-process-overview","The SOC 2 audit process overview",[15,2191,1124,2192,2194],{},[25,2193,255],{"href":254}," follows a predictable sequence. Understanding each phase prevents surprises and helps you set realistic timelines with your team and auditor.",[183,2196,2197,2209,2215,2221,2227],{},[117,2198,2199,2202,2203,2205,2206,2208],{},[120,2200,2201],{},"Scoping and readiness assessment."," Define what systems and Trust Services Criteria are in scope, then perform a ",[25,2204,1584],{"href":1583}," to compare current controls against ",[25,2207,1176],{"href":1175},". The output is a prioritized remediation plan.",[117,2210,2211,2214],{},[120,2212,2213],{},"Remediation."," Close the gaps identified during readiness. Common items include formalizing policies, enabling MFA everywhere, centralizing logging, documenting vendor risk processes, and running tabletop exercises.",[117,2216,2217,2220],{},[120,2218,2219],{},"Auditor selection."," SOC 2 audits must be performed by a CPA firm licensed to issue SOC reports. Request proposals from two to four firms, compare scope and pricing, and check references from similar companies.",[117,2222,2223,2226],{},[120,2224,2225],{},"Audit fieldwork."," For Type I, the auditor validates control design at a point in time. For Type II, the auditor samples evidence from across the observation period and tests operating effectiveness.",[117,2228,2229,2232],{},[120,2230,2231],{},"Report delivery and ongoing operation."," Once the report is issued, plan the next observation period so you maintain continuous coverage with no bridge gaps that buyers might question.",[15,2234,2235],{},"Most organizations complete their first Type I in three to six months and their first Type II in six to eighteen months, depending on starting maturity and observation period length.",[10,2237,2239],{"id":2238},"what-does-soc-2-cost","What does SOC 2 cost?",[15,2241,2242],{},"SOC 2 cost varies widely based on scope, starting maturity, and whether you pursue Type I, Type II, or both. Auditor fees are the largest line item, but they are not the only cost. You should budget for readiness consulting, compliance tooling, internal staff time, remediation work, and penetration testing.",[15,2244,2245],{},"Typical benchmarks for a first-time SOC 2 engagement:",[114,2247,2248,2254,2260,2266,2272,2278],{},[117,2249,2250,2253],{},[120,2251,2252],{},"Type I auditor fees",": $15,000 to $40,000",[117,2255,2256,2259],{},[120,2257,2258],{},"Type II auditor fees",": $25,000 to $80,000",[117,2261,2262,2265],{},[120,2263,2264],{},"Readiness consulting"," (optional): $10,000 to $40,000",[117,2267,2268,2271],{},[120,2269,2270],{},"Compliance platform",": $6,000 to $60,000 annually depending on vendor",[117,2273,2274,2277],{},[120,2275,2276],{},"Penetration testing",": $8,000 to $30,000 per test",[117,2279,2280,2283],{},[120,2281,2282],{},"Internal staff time",": 200 to 600 hours across the first cycle",[15,2285,2286,2287,2289],{},"Total first-year cost for most growth-stage SaaS companies lands between $40,000 and $200,000. See the full ",[25,2288,1266],{"href":1265}," for detailed ranges and cost-reduction strategies.",[10,2291,2293],{"id":2292},"common-soc-2-challenges","Common SOC 2 challenges",[15,2295,2296],{},"SOC 2 programs rarely fail because the audit is unfair. They fail because organizations underestimate the operational discipline required. The challenges show up in predictable places.",[114,2298,2299,2305,2311,2317,2323,2334,2345],{},[117,2300,2301,2304],{},[120,2302,2303],{},"Scope creep."," Teams add new systems mid-audit or expand Trust Services Criteria without revisiting the control set. Every addition extends timelines and evidence requirements.",[117,2306,2307,2310],{},[120,2308,2309],{},"Evidence gaps."," Screenshots expire. Configurations change. Ownership drifts between quarters. By the time the auditor asks, the evidence trail is broken.",[117,2312,2313,2316],{},[120,2314,2315],{},"Cross-team coordination."," SOC 2 touches engineering, IT, HR, legal, and finance. Without a single source of truth for control status, teams duplicate work or miss handoffs.",[117,2318,2319,2322],{},[120,2320,2321],{},"Policy drift."," Policies written for the audit do not match how the team actually operates. Auditors detect this quickly during interviews and walkthroughs.",[117,2324,2325,2328,2329,2333],{},[120,2326,2327],{},"Vendor oversight."," Third-party vendors handle critical data but are rarely monitored with the same rigor as internal systems. See ",[25,2330,2332],{"href":2331},"\u002Fframeworks\u002Fsoc2\u002Fvendor-management","vendor management"," for how to close this gap.",[117,2335,2336,2339,2340,2344],{},[120,2337,2338],{},"Change management."," Production changes bypass approval workflows, leaving no audit trail. ",[25,2341,2343],{"href":2342},"\u002Fframeworks\u002Fsoc2\u002Fchange-management","Change management"," is a frequent source of Type II exceptions.",[117,2346,2347,2350,2351,29],{},[120,2348,2349],{},"Incident response immaturity."," Teams have an incident response plan but have never tested it. Auditors look for evidence of real incidents handled end to end. See ",[25,2352,1881],{"href":1880},[15,2354,2355],{},"A structured approach — mapping controls, evidence, and owners from day one — removes most of these friction points before they become audit findings.",[10,2357,2359],{"id":2358},"how-soc-2-compares-to-other-frameworks","How SOC 2 compares to other frameworks",[15,2361,2362],{},"SOC 2 is not the only security framework buyers may request. Understanding how SOC 2 relates to other standards helps you plan a cohesive compliance strategy rather than running parallel audits with overlapping work.",[15,2364,2365,2369],{},[120,2366,2367],{},[25,2368,476],{"href":475}," is an international certification focused on information security management systems. Unlike SOC 2, which produces an auditor's opinion letter, ISO 27001 results in a certificate issued by an accredited registrar. ISO 27001 is prescriptive about building an ISMS but the control set in Annex A overlaps heavily with the SOC 2 Common Criteria. Many mature companies pursue both and reuse evidence across them. ISO 27001 tends to be preferred by European and international buyers; SOC 2 is the North American standard.",[15,2371,2372,2376],{},[120,2373,2374],{},[25,2375,490],{"href":489}," is a US healthcare law that mandates specific safeguards for protected health information. HIPAA is a regulatory requirement rather than a voluntary attestation — there is no HIPAA certificate, but business associates and covered entities must comply. SOC 2 controls address many HIPAA administrative and technical safeguards, and a SOC 2 Type II report is often used as evidence of HIPAA compliance in vendor due diligence.",[15,2378,2379,2383],{},[120,2380,2381],{},[25,2382,504],{"href":503}," is the payment card industry's prescriptive standard for any organization that stores, processes, or transmits cardholder data. Unlike SOC 2, PCI DSS specifies exact controls down to firewall rules and encryption key rotation cadences. SOC 2 and PCI DSS share concepts like encryption, access control, and monitoring, but PCI DSS scope is narrower (cardholder data environment) and the requirements are more specific. Companies that process payments typically need both.",[15,2385,2386,2389,2390,2393,2394,2397],{},[120,2387,2388],{},"NIST Cybersecurity Framework",", ",[120,2391,2392],{},"FedRAMP",", and ",[120,2395,2396],{},"CMMC"," address additional specialized audiences — federal contractors, defense industrial base, and government-adjacent systems. These are out of scope for most commercial SaaS but worth mapping if your buyer base includes public sector.",[15,2399,2400,2401,2405],{},"If you are comparing SOC 2 tooling options, our ",[25,2402,2404],{"href":2403},"\u002Fcompare\u002Fvs\u002Fvanta-vs-drata","Vanta vs Drata comparison"," covers the leading compliance automation platforms.",[10,2407,2409],{"id":2408},"soc-2-readiness-checklist","SOC 2 readiness checklist",[15,2411,2412,2413,2416],{},"A readiness checklist keeps your team focused during the months before the audit begins. The ",[25,2414,2415],{"href":1227},"full SOC 2 checklist"," covers every category, but at a high level expect to address:",[114,2418,2419,2422,2425,2428,2431,2434,2437,2440,2443,2446],{},[117,2420,2421],{},"Governance and policies (information security policy, acceptable use, code of conduct)",[117,2423,2424],{},"Access control (SSO, MFA, role-based access, quarterly access reviews)",[117,2426,2427],{},"Change management (code review, deployment approvals, production change logs)",[117,2429,2430],{},"Vendor risk management (inventory, assessments, monitoring)",[117,2432,2433],{},"Incident response (documented plan, tested at least annually)",[117,2435,2436],{},"Business continuity and disaster recovery (plan with defined RPO\u002FRTO, tested)",[117,2438,2439],{},"Logging and monitoring (centralized logs, alerting, incident tickets)",[117,2441,2442],{},"Security awareness training (annual minimum, tracked completion)",[117,2444,2445],{},"HR controls (background checks, onboarding, offboarding, confidentiality agreements)",[117,2447,2448],{},"Risk assessment (annual risk review, risk register, treatment plans)",[15,2450,2451],{},"Most companies find that the readiness phase surfaces gaps they did not know existed. That is the point — better to discover them before the auditor arrives.",[10,2453,2455],{"id":2454},"getting-started-with-soc-2","Getting started with SOC 2",[15,2457,2458],{},"The best time to start a SOC 2 program is before the first buyer demands it. The second best time is now.",[15,2460,2461],{},"A reasonable starting sequence:",[183,2463,2464,2470,2476,2482,2488,2494],{},[117,2465,2466,2469],{},[120,2467,2468],{},"Pick your Trust Services Criteria."," Security is required. Add others only if you have customer commitments that map to them.",[117,2471,2472,2475],{},[120,2473,2474],{},"Decide Type I vs Type II."," If you need a report fast for a specific deal, start with Type I. If you have time and buyer pressure is general, skip straight to Type II.",[117,2477,2478,2481],{},[120,2479,2480],{},"Run a readiness assessment."," Either internally or with a consultant. The goal is a prioritized remediation list, not a polished report.",[117,2483,2484,2487],{},[120,2485,2486],{},"Remediate in priority order."," Address policy gaps, access control weaknesses, and logging first — these are the most common sources of findings.",[117,2489,2490,2493],{},[120,2491,2492],{},"Select an auditor."," Get proposals from two to four CPA firms. Check references from similar companies. Book early — good auditors are scheduled quarters in advance.",[117,2495,2496,2499],{},[120,2497,2498],{},"Operate, collect, and iterate."," Run your controls, collect evidence continuously, and prepare for fieldwork. Do not treat the audit as a one-time event.",[10,2501,1570],{"id":1569},[15,2503,2504,2505,2508,2509,2513],{},"episki maps your controls to the Trust Services Criteria and then evaluates them continuously. Connected systems — AWS across multiple accounts and regions, plus GitHub, Google, Microsoft, Slack, Supabase, Vercel, and Netlify — collect evidence and write an explicit pass, fail, or inconclusive verdict against each criterion, with a failing check raising a finding that syncs bi-directionally into Jira, Linear, or GitHub. Change management evidence comes from branch protection and git-only deploy checks rather than screenshots; availability evidence from point-in-time recovery and deployment protection. Your auditor gets scoped guest access per assessment at no extra cost. ",[25,2506,1579],{"href":1576,"rel":2507},[1578]," or ",[25,2510,2512],{"href":2511},"\u002Fdemo","book a demo"," to see how SOC 2 looks with the scramble removed.",{"title":258,"searchDepth":259,"depth":259,"links":2515},[2516,2517,2518,2525,2526,2527,2528,2529,2530,2531,2532],{"id":2040,"depth":259,"text":296},{"id":2066,"depth":259,"text":2067},{"id":2096,"depth":259,"text":2097,"children":2519},[2520,2521,2522,2523,2524],{"id":2105,"depth":264,"text":2106},{"id":2112,"depth":264,"text":2113},{"id":2123,"depth":264,"text":2124},{"id":2130,"depth":264,"text":2131},{"id":2142,"depth":264,"text":2143},{"id":2153,"depth":259,"text":2154},{"id":2188,"depth":259,"text":2189},{"id":2238,"depth":259,"text":2239},{"id":2292,"depth":259,"text":2293},{"id":2358,"depth":259,"text":2359},{"id":2408,"depth":259,"text":2409},{"id":2454,"depth":259,"text":2455},{"id":1569,"depth":259,"text":1570},{"title":2534,"description":2535,"items":2536},"SOC 2 readiness checklist inside episki","Everything is preloaded in your free trial so you can start assigning ownership and collecting proof immediately.",[2537,2538,2539,2540,2541],"Trust Service Criteria library with mapped controls","Policy templates and AI drafting assistant","Evidence library with structured ownership and review cadences","Emulated auditor workspace with sample requests","Customer-facing compliance portal template",{"title":2543,"description":2544},"Launch your SOC 2 workspace today","Import your controls, connect evidence, and invite your auditor in under an hour.",{"title":2546,"items":2547},"SOC 2 frequently asked questions",[2548,2551,2554,2557,2559],{"label":2549,"content":2550},"How long does a SOC 2 audit take?","A SOC 2 Type I audit typically takes 4-8 weeks of preparation plus the audit itself. Type II requires a 3-12 month observation period followed by the assessment. episki's automation can cut preparation time by up to 45 days.",{"label":2552,"content":2553},"What is the difference between SOC 2 Type I and Type II?","SOC 2 Type I evaluates whether controls are suitably designed at a single point in time. Type II tests whether those controls operated effectively over a sustained period, usually 3-12 months. Most enterprise buyers require a Type II report.",{"label":2555,"content":2556},"How much does SOC 2 compliance cost?","Total costs typically range from $20,000 to $100,000+ depending on scope, readiness, and auditor fees. episki covers the platform side at a flat $750\u002Fmonth with no per-seat charges, significantly reducing the software portion of that budget.",{"label":2154,"content":2558},"Any SaaS company, cloud service provider, or data processor handling customer data is a likely candidate. Enterprise buyers in financial services, healthcare, and technology frequently require a current SOC 2 report before signing contracts.",{"label":2560,"content":2561},"What are the SOC 2 Trust Services Criteria?","The five Trust Services Criteria are security (required), availability, processing integrity, confidentiality, and privacy. Security is mandatory for every SOC 2 audit; the other four are optional and selected based on the services you provide.",{"headline":2563,"title":2564,"description":2565,"links":2566},"SOC 2 without the scramble","Ship SOC 2 audits without slowing product velocity","episki maps Trust Service Criteria, automates evidence, and keeps auditors in sync so your team can focus on building.",[2567,2570],{"label":2568,"icon":2569,"to":1576},"Start SOC 2 trial","i-lucide-rocket",{"label":2571,"icon":2572,"color":2573,"variant":2574,"to":2511,"target":2575},"Book a demo","i-lucide-message-circle","neutral","subtle","_blank",{},{"headline":2578,"title":2578,"description":2579,"items":2580},"SOC 2 acceleration resources","Give execs and customers visibility into progress at every stage.",[2581,2584,2587],{"title":2582,"description":2583},"Executive scorecard","Summaries translate control work into risk reduction and deals unlocked.",{"title":2585,"description":2586},"Sales enablement kit","SOC 2 FAQ answers and trust collateral ready for GTM teams.",{"title":2588,"description":2589},"Audit retro template","Capture what worked, track remediations, and prep the next period.",{"title":2591,"description":2592},"SOC 2 Compliance Software","Get SOC 2 Type I and Type II audit-ready faster with episki's automated controls, evidence tracking, and auditor collaboration. Start your free 14-day trial.",[2594,2597,2600],{"value":2595,"description":2596},"45 days faster","Average time saved reaching Type II readiness with episki’s automation.",{"value":2598,"description":2599},"120+ controls","Pre-mapped control narratives with owners, evidence, and review cadences.",{"value":2601,"description":2602},"100% coverage","Auditor portal with control health dashboards and SOC 2 exports.","5.frameworks\u002Fsoc2","UexUtE1HJiFtSL7wv59EdqPVMfsoQCTKsPLQUzdOCwM",{"id":2606,"title":2607,"body":2608,"comparison":2798,"competitorA":2701,"competitorB":2713,"cta":2846,"description":258,"extension":271,"faq":2849,"hero":2867,"lastUpdated":862,"meta":2876,"navigation":274,"path":2877,"seo":2878,"slug":2881,"slugA":2882,"slugB":2883,"stem":2884,"verdict":2885,"__hash__":2889},"compareVs\u002F7.compare\u002Fvs\u002Fdrata-vs-secureframe.md","Drata Vs Secureframe",{"type":7,"value":2609,"toc":2788},[2610,2614,2617,2621,2624,2630,2633,2637,2640,2643,2646,2650,2653,2656,2660,2663,2735,2738,2741,2745,2748,2751,2755,2758,2761,2764],[10,2611,2613],{"id":2612},"drata-vs-secureframe-the-closest-comparison-in-compliance","Drata vs Secureframe: the closest comparison in compliance",[15,2615,2616],{},"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.",[31,2618,2620],{"id":2619},"feature-parity-with-different-emphasis","Feature parity with different emphasis",[15,2622,2623],{},"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.",[15,2625,2626,2629],{},[120,2627,2628],{},"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.",[15,2631,2632],{},"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.",[31,2634,2636],{"id":2635},"the-dashboard-question","The dashboard question",[15,2638,2639],{},"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.",[15,2641,2642],{},"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.",[15,2644,2645],{},"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.",[31,2647,2649],{"id":2648},"integration-depth","Integration depth",[15,2651,2652],{},"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.",[15,2654,2655],{},"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.",[31,2657,2659],{"id":2658},"pricing-opacity","Pricing opacity",[15,2661,2662],{},"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:",[39,2664,2665,2681],{},[42,2666,2667],{},[45,2668,2669,2672,2675,2678],{},[48,2670,2671],{},"Platform",[48,2673,2674],{},"Typical entry price (2026)",[48,2676,2677],{},"Pricing model",[48,2679,2680],{},"Published?",[58,2682,2683,2697,2709,2721],{},[45,2684,2685,2688,2691,2694],{},[63,2686,2687],{},"Vanta",[63,2689,2690],{},"~$11,000–$15,000\u002Fyr",[63,2692,2693],{},"Per-seat + framework, custom quote",[63,2695,2696],{},"No",[45,2698,2699,2702,2705,2707],{},[63,2700,2701],{},"Drata",[63,2703,2704],{},"~$10,000–$15,000\u002Fyr",[63,2706,2693],{},[63,2708,2696],{},[45,2710,2711,2714,2717,2719],{},[63,2712,2713],{},"Secureframe",[63,2715,2716],{},"~$8,000–$12,000\u002Fyr",[63,2718,2693],{},[63,2720,2696],{},[45,2722,2723,2726,2729,2732],{},[63,2724,2725],{},"episki",[63,2727,2728],{},"$750\u002Fmo ($7,500\u002Fyr)",[63,2730,2731],{},"Flat platform + modules, unlimited seats",[63,2733,2734],{},"Yes",[15,2736,2737],{},"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.",[15,2739,2740],{},"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.",[31,2742,2744],{"id":2743},"where-both-platforms-struggle","Where both platforms struggle",[15,2746,2747],{},"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.",[15,2749,2750],{},"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.",[31,2752,2754],{"id":2753},"the-case-for-a-different-approach","The case for a different approach",[15,2756,2757],{},"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.",[15,2759,2760],{},"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.",[15,2762,2763],{},"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.",[15,2765,2766,2769,2770,1832,2774,2778,2779,2783,2784,2787],{},[120,2767,2768],{},"Related reading:"," dig deeper into each platform's competitors in our ",[25,2771,2773],{"href":2772},"\u002Fblog\u002Fdrata-alternatives","Drata alternatives",[25,2775,2777],{"href":2776},"\u002Fblog\u002Fsecureframe-alternatives","Secureframe alternatives"," guides, see where both rank in the ",[25,2780,2782],{"href":2781},"\u002Fblog\u002Fbest-grc-tools-2026","best GRC tools of 2026",", or compare ",[25,2785,2786],{"href":2403},"Vanta vs Drata"," if Vanta is also on your shortlist.",{"title":258,"searchDepth":259,"depth":259,"links":2789},[2790],{"id":2612,"depth":259,"text":2613,"children":2791},[2792,2793,2794,2795,2796,2797],{"id":2619,"depth":264,"text":2620},{"id":2635,"depth":264,"text":2636},{"id":2648,"depth":264,"text":2649},{"id":2658,"depth":264,"text":2659},{"id":2743,"depth":264,"text":2744},{"id":2753,"depth":264,"text":2754},[2799,2803,2807,2812,2817,2821,2826,2831,2836,2841],{"feature":2677,"competitorA":2800,"competitorB":2801,"episki":2802},"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":2804,"competitorA":2805,"competitorB":2805,"episki":2806},"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":2808,"competitorA":2809,"competitorB":2810,"episki":2811},"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":2813,"competitorA":2814,"competitorB":2815,"episki":2816},"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":2818,"competitorA":2819,"competitorB":2819,"episki":2820},"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":2822,"competitorA":2823,"competitorB":2824,"episki":2825},"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":2827,"competitorA":2828,"competitorB":2829,"episki":2830},"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":2832,"competitorA":2833,"competitorB":2834,"episki":2835},"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":2837,"competitorA":2838,"competitorB":2839,"episki":2840},"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":2842,"competitorA":2843,"competitorB":2844,"episki":2845},"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":2847,"description":2848},"Skip the comparison. Try episki free.","14-day trial with full access. No credit card required.",{"title":2850,"items":2851},"Drata vs Secureframe pricing FAQ (2026)",[2852,2855,2858,2861,2864],{"label":2853,"content":2854},"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":2856,"content":2857},"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":2859,"content":2860},"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":2862,"content":2863},"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":2865,"content":2866},"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":2868,"title":2869,"description":2870,"links":2871},"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.",[2872,2874],{"label":2571,"icon":2873,"to":2511,"target":2575},"i-lucide-calendar",{"label":2875,"icon":2569,"color":2573,"variant":2574,"to":1576},"Try episki free",{},"\u002Fcompare\u002Fvs\u002Fdrata-vs-secureframe",{"title":2879,"description":2880},"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":2886,"chooseB":2887,"chooseEpiski":2888},"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.","_gy5xGoS3mNTVVSLgAHu1fxopUUE6K2hbndBLv_SwzI",{"id":2891,"title":2892,"advantages":2893,"body":2915,"comparison":2978,"competitor":2892,"cta":3026,"description":258,"extension":271,"faq":3029,"hero":3047,"lastUpdated":862,"meta":3055,"navigation":274,"path":3056,"seo":3057,"slug":3060,"stem":3061,"__hash__":3062},"compare\u002F7.compare\u002Farcher.md","Archer",[2894,2901,2908],{"title":2895,"description":2896,"bullets":2897},"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.",[2898,2899,2900],"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":2902,"description":2903,"bullets":2904},"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.",[2905,2906,2907],"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":2909,"description":2910,"bullets":2911},"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.",[2912,2913,2914],"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":7,"value":2916,"toc":2973},[2917,2921,2924,2927,2930,2950,2954,2957,2960,2963,2966,2970],[10,2918,2920],{"id":2919},"why-teams-evaluate-archer-alternatives","Why teams evaluate Archer alternatives",[15,2922,2923],{},"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.",[15,2925,2926],{},"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.",[15,2928,2929],{},"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.",[114,2931,2932,2938,2944],{},[117,2933,2934,2937],{},[120,2935,2936],{},"No implementation project"," — self-serve signup, sensible defaults, first policy drafted in minutes",[117,2939,2940,2943],{},[120,2941,2942],{},"A published price"," — $7,500\u002Fyr for the platform, unlimited users and frameworks",[117,2945,2946,2949],{},[120,2947,2948],{},"Agents that do the drafting"," — instead of workflows that route it to a person",[10,2951,2953],{"id":2952},"where-episki-is-different","Where episki is different",[15,2955,2956],{},"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.",[15,2958,2959],{},"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.",[15,2961,2962],{},"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.",[15,2964,2965],{},"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.",[10,2967,2969],{"id":2968},"when-archer-might-still-be-the-better-fit","When Archer might still be the better fit",[15,2971,2972],{},"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":258,"searchDepth":259,"depth":259,"links":2974},[2975,2976,2977],{"id":2919,"depth":259,"text":2920},{"id":2952,"depth":259,"text":2953},{"id":2968,"depth":259,"text":2969},[2979,2983,2987,2990,2994,2998,3002,3006,3010,3014,3018,3022],{"feature":2980,"episki":2981,"competitor":2982},"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":2984,"episki":2985,"competitor":2986},"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":2677,"episki":2988,"competitor":2989},"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":2991,"episki":2992,"competitor":2993},"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":2995,"episki":2996,"competitor":2997},"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":2999,"episki":3000,"competitor":3001},"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":3003,"episki":3004,"competitor":3005},"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":3007,"episki":3008,"competitor":3009},"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":3011,"episki":3012,"competitor":3013},"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":3015,"episki":3016,"competitor":3017},"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":3019,"episki":3020,"competitor":3021},"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":3023,"episki":3024,"competitor":3025},"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":3027,"description":3028},"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":3030,"items":3031},"episki vs Archer — frequently asked questions",[3032,3035,3038,3041,3044],{"label":3033,"content":3034},"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":3036,"content":3037},"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":3039,"content":3040},"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":3042,"content":3043},"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":3045,"content":3046},"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":3048,"title":3049,"description":3050,"links":3051},"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.",[3052,3053],{"label":2571,"icon":2873,"to":2511,"target":2575},{"label":3054,"icon":2569,"color":2573,"variant":2574,"to":1576},"Start free trial",{},"\u002Fcompare\u002Farcher",{"title":3058,"description":3059},"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":3064,"title":3065,"api":1610,"authors":3066,"body":3072,"category":3400,"date":272,"description":3401,"extension":271,"faq":1610,"features":1610,"fixes":1610,"highlight":1610,"image":3402,"improvements":1610,"meta":3404,"navigation":274,"path":3405,"seo":3406,"stem":3407,"summary":1610,"updated":1610,"__hash__":3408},"posts\u002F3.blog\u002Fmonitoring-csp.md","Monitoring for CSP (PCI DSS 11.6.1)",[3067],{"name":3068,"to":3069,"avatar":3070},"Justin Leapline","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fjustinleapline\u002F",{"src":3071},"\u002Fimages\u002Fjustinleapline.png",{"type":7,"value":3073,"toc":3390},[3074,3077,3080,3083,3086,3090,3093,3104,3107,3110,3117,3120,3124,3127,3130,3152,3155,3158,3176,3179,3182,3186,3189,3195,3201,3207,3213,3219,3229,3233,3236,3239,3253,3256,3260,3263,3305,3308,3312,3315,3318,3322,3325,3345,3348,3352,3373,3376,3379],[15,3075,3076],{},"Your checkout page has seventeen scripts. Marketing added three through the tag manager last quarter. Nobody owns the inventory. Someone says \"we have CSP\" in the audit call, and then cannot show a single alert from the last ninety days.",[15,3078,3079],{},"That is not monitoring. That is hope with a header.",[15,3081,3082],{},"PCI DSS 11.6.1 is the requirement that closes that gap. It sits next to 6.4.3 (script inventory, authorization, integrity, and justification) and asks a harder question: if something unauthorized shows up on the payment page as the customer's browser receives it, will you know, and will someone get alerted in time to act?",[15,3084,3085],{},"For mid-sized merchants, that question is practical, not academic. E-skimming does not wait for your annual ROC. It waits for a forgotten third-party script.",[10,3087,3089],{"id":3088},"what-1161-actually-requires","What 11.6.1 Actually Requires",[15,3091,3092],{},"Requirement 11.6.1 calls for a change- and tamper-detection mechanism that alerts personnel to unauthorized modification, including indicators of compromise, changes, additions, and deletions, to:",[114,3094,3095,3098],{},[117,3096,3097],{},"Security-impacting HTTP headers on payment pages",[117,3099,3100,3101],{},"Script contents of those payment pages ",[120,3102,3103],{},"as received by the consumer browser",[15,3105,3106],{},"The mechanism must evaluate what the browser actually gets, and it must run at least weekly, or at a frequency defined by a targeted risk analysis under 12.3.1.",[15,3108,3109],{},"Read that carefully. Server-side file hashes alone are not enough if scripts assemble in the browser from CDNs, tag managers, and third-party widgets. The control cares about the consumer's view of the page.",[15,3111,3112,3113,3116],{},"Also note what it does ",[231,3114,3115],{},"not"," say: prevent every bad change forever. 11.6.1 is detection and alerting. Prevention and authorization live with 6.4.3. You need both.",[15,3118,3119],{},"CSP is useful in this story. It is not the whole story. If your plan is \"we shipped a CSP header, so we're done,\" you will struggle when your QSA asks how you detect, alert, and respond.",[10,3121,3123],{"id":3122},"where-csp-fits-and-where-it-doesnt","Where CSP Fits, and Where It Doesn't",[15,3125,3126],{},"Content Security Policy is useful. It is not a complete 11.6.1 program by itself.",[15,3128,3129],{},"A solid CSP can:",[114,3131,3132,3140,3143],{},[117,3133,3134,3135,3139],{},"Limit which origins may load scripts (",[3136,3137,3138],"code",{},"script-src",")",[117,3141,3142],{},"Prefer hashes or nonces over wildcards",[117,3144,3145,3146,2508,3149],{},"Report violations via ",[3136,3147,3148],{},"report-to",[3136,3150,3151],{},"report-uri",[15,3153,3154],{},"That reporting path is how CSP becomes monitoring instead of silent blocking. Without violation collection, ownership, and follow-up, CSP is just a filter nobody watches.",[15,3156,3157],{},"CSP still leaves gaps mid-market teams hit every week:",[114,3159,3160,3163,3166,3173],{},[117,3161,3162],{},"Dynamic payment scripts that resist clean Subresource Integrity (SRI) hashes",[117,3164,3165],{},"Tag managers that rewrite the allowlist faster than GRC can document it",[117,3167,3168,3169,3172],{},"Changes ",[231,3170,3171],{},"to"," the CSP header itself, which can be an attack signal and must be monitored",[117,3174,3175],{},"\"Report-only\" policies that never graduate to enforcement because nobody owned the cleanup",[15,3177,3178],{},"Treat CSP as a preventive baseline plus a signal source. Pair it with browser-perspective monitoring of scripts and security headers, alongside Subresource Integrity and a living 6.4.3 inventory. That combination maps to how QSAs are reading 6.4.3 and 11.6.1 together.",[15,3180,3181],{},"If you embed a payment processor iframe, 11.6.1 still applies to your parent page. Scripts inside the processor's embedded form are generally the processor's responsibility, but your surrounding page, tags, analytics, and widgets remain in scope.",[10,3183,3185],{"id":3184},"a-practical-stack-for-mid-sized-merchants","A Practical Stack for Mid-Sized Merchants",[15,3187,3188],{},"You do not need a Fortune-500 security engineering org. You need a stack you can run every week.",[15,3190,3191,3194],{},[120,3192,3193],{},"1. Know your payment pages.","\nList every URL where card data is entered or scripts can touch the payment flow, including iframes and hosted fields you still influence. Cart, checkout, confirmation, and promo checkouts all count. If marketing runs a promo checkout, it is in scope.",[15,3196,3197,3200],{},[120,3198,3199],{},"2. Finish the 6.4.3 homework.","\nInventory scripts. Authorize them. Justify business need. Apply an integrity method (SRI where it holds, approved vendor controls, or equivalent). 11.6.1 alerts are noisy and useless without a baseline of what is supposed to be there. Monitoring a mess just creates a louder mess.",[15,3202,3203,3206],{},[120,3204,3205],{},"3. Deploy CSP with reporting.","\nStart report-only if you must, but set a date to enforce. Send violations to a destination someone actually reviews. Alert on unexpected script hosts and on CSP header drift.",[15,3208,3209,3212],{},[120,3210,3211],{},"4. Add browser-perspective change detection.","\nOptions include synthetic monitoring that fetches pages like a customer, client-side tamper detection, CDN or reverse-proxy change alerts, or a purpose-built payment-page integrity tool. Prefer live payment-flow checks over a cached server copy alone. Pick what matches your architecture, and prove it sees what the browser sees.",[15,3214,3215,3218],{},[120,3216,3217],{},"5. Alert people who can act.","\nName an owner. Define severity. Route to Slack, ticket, or on-call. A weekly PDF nobody opens is not a control. The requirement is detection plus alerting, not silent logs.",[15,3220,3221,3224,3225,3228],{},[120,3222,3223],{},"6. Evidence on a cadence.","\nKeep samples of baselines, alerts, investigations, false-positive tuning, CSP violation summaries, and TRA rationale if you are not on a strict weekly schedule. Name an owner. Timestamp everything. Auditors ask for the mechanism ",[231,3226,3227],{},"and"," the operating proof.",[10,3230,3232],{"id":3231},"operating-cadence-that-survives-an-audit","Operating Cadence That Survives an Audit",[15,3234,3235],{},"Weekly is the default. If you choose a different frequency, document the targeted risk analysis: threat landscape, payment-page change rate, detection capability, and compensating factors. With frequent tag releases, weekly is a floor, not a goal.",[15,3237,3238],{},"Each cycle, ask:",[114,3240,3241,3244,3247,3250],{},[117,3242,3243],{},"Did any new script appear on an in-scope page?",[117,3245,3246],{},"Did any authorized script's content or source change without a change ticket?",[117,3248,3249],{},"Did security headers (CSP, HSTS, framing controls, and peers you treat as security-impacting) drift?",[117,3251,3252],{},"Were alerts acknowledged and closed with a disposition?",[15,3254,3255],{},"Tie script changes to change management. Marketing should not be able to drop a new analytics tag on checkout without GRC and security seeing it the same week, preferably before production. Unauthorized changes should also trigger a 6.4.3 script-control review.",[10,3257,3259],{"id":3258},"common-failure-modes","Common Failure Modes",[15,3261,3262],{},"Mid-sized programs usually stumble in the same places:",[114,3264,3265,3271,3277,3283,3293,3299],{},[117,3266,3267,3270],{},[120,3268,3269],{},"CSP with no report pipeline."," Blocks (or would block) but never alerts. A header without alerts, owners, and review evidence is configuration, not monitoring.",[117,3272,3273,3276],{},[120,3274,3275],{},"Inventory that is a one-time spreadsheet."," Drift starts the day after the assessment.",[117,3278,3279,3282],{},[120,3280,3281],{},"Server-only FIM."," Misses CDN and tag-manager payloads the browser executes. Magecart-style attacks often inject scripts dynamically; if you ignore the live DOM during payment, you can miss what 11.6.1 cares about.",[117,3284,3285,3288,3289,3292],{},[120,3286,3287],{},"Vendor \"we handle PCI\" assumptions."," Embedded forms help, but your SAQ or ROC still needs ",[231,3290,3291],{},"your"," evidence for pages you control.",[117,3294,3295,3298],{},[120,3296,3297],{},"Alerts with no owner."," Detection without response is theater.",[117,3300,3301,3304],{},[120,3302,3303],{},"Weekly in theory, never in practice."," Teams document the cadence, then cannot show tickets or reports proving the check ran and someone reviewed results.",[15,3306,3307],{},"Fix those before you buy another dashboard.",[10,3309,3311],{"id":3310},"how-this-ties-to-day-to-day-grc","How This Ties to Day-to-Day GRC",[15,3313,3314],{},"11.6.1 is not a one-off project. It is an operating control: inventory, detect, alert, investigate, evidence.",[15,3316,3317],{},"Keep the script inventory, exceptions, TRA, and alert tickets connected to the same compliance workflow you already use for PCI, so the control shows up in weekly work, not only in the ROC binder. Platforms like episki help when they keep requirements, owners, and evidence in one place instead of three SharePoint sites and a forgotten CSP report bucket.",[10,3319,3321],{"id":3320},"what-good-enough-looks-like","What \"Good Enough\" Looks Like",[15,3323,3324],{},"For a mid-sized merchant, good enough usually looks like this:",[114,3326,3327,3330,3333,3336,3339,3342],{},[117,3328,3329],{},"Payment pages and parent pages are identified and owned",[117,3331,3332],{},"Scripts are inventoried and authorized under 6.4.3",[117,3334,3335],{},"CSP is implemented thoughtfully, with reporting turned on",[117,3337,3338],{},"A change and tamper detection mechanism compares browser-received scripts and security-impacting headers against baseline",[117,3340,3341],{},"Alerts reach a human on a defined schedule",[117,3343,3344],{},"Evidence of weekly (or TRA-defined) operation is retained for assessment",[15,3346,3347],{},"You can buy parts of this, build parts, or combine both. PCI guidance allows a mix. What is not acceptable is hoping a single header equals continuous assurance.",[10,3349,3351],{"id":3350},"key-takeaways","Key Takeaways",[114,3353,3354,3361,3364,3367,3370],{},[117,3355,3356,3357,3360],{},"PCI DSS 11.6.1 requires change and tamper detection and alerting for payment-page scripts and security-impacting headers ",[120,3358,3359],{},"as the consumer browser receives them",", at least weekly or per TRA",[117,3362,3363],{},"CSP helps constrain unauthorized loads and can feed monitoring via violation reports, but CSP alone is not a complete 11.6.1 answer",[117,3365,3366],{},"Pair CSP with browser-perspective monitoring, a living 6.4.3 inventory, and named alert owners",[117,3368,3369],{},"Mid-sized merchants win with a simple weekly stack and evidence, not with an unread policy header",[117,3371,3372],{},"Common failures: no reporting, stale inventories, server-only checks, and orphaned alerts",[15,3374,3375],{},"Skimmers live in the gap between \"we set a header\" and \"we watch what customers actually load.\" Close that gap on purpose.",[3377,3378],"hr",{},[15,3380,3381,3384,3385],{},[120,3382,3383],{},"Are you detecting unauthorized changes on payment pages the way PCI DSS 11.6.1 expects, or only shipping a CSP header?"," episki helps teams keep script inventories, control ownership, alert evidence, and PCI DSS workflows in one place your team will actually use. ",[25,3386,3389],{"href":3387,"rel":3388},"https:\u002F\u002Fapp.episki.com",[1578],"Get started free",{"title":258,"searchDepth":259,"depth":259,"links":3391},[3392,3393,3394,3395,3396,3397,3398,3399],{"id":3088,"depth":259,"text":3089},{"id":3122,"depth":259,"text":3123},{"id":3184,"depth":259,"text":3185},{"id":3231,"depth":259,"text":3232},{"id":3258,"depth":259,"text":3259},{"id":3310,"depth":259,"text":3311},{"id":3320,"depth":259,"text":3321},{"id":3350,"depth":259,"text":3351},"practices","PCI DSS 11.6.1 for mid-sized merchants: how CSP monitoring, payment-page script integrity, and weekly change detection actually work without theater.",{"src":3403},"\u002Fimages\u002Fblog\u002Fepiskimage.png",{},"\u002Fblog\u002Fmonitoring-csp",{"title":3065,"description":3401},"3.blog\u002Fmonitoring-csp","Lx-uqeVqcVcfJc23kbOX_z_VIwvMf8Y2NeIj6UCloYk",{"id":3410,"title":3411,"advantages":3412,"body":3434,"checklist":3441,"cta":3450,"description":3438,"extension":271,"faq":1610,"hero":3453,"lastUpdated":862,"meta":3461,"name":3462,"navigation":274,"path":3463,"resources":3464,"seo":3477,"slug":3480,"stats":3481,"stem":3491,"__hash__":3492},"industries\u002F6.industry\u002F1.healthcare.md","Healthcare",[3413,3420,3427],{"title":3414,"description":3415,"bullets":3416},"PHI-aware control mapping","Map administrative, technical, and physical safeguards to your stack without rebuilding every audit.",[3417,3418,3419],"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":3421,"description":3422,"bullets":3423},"Clinician-friendly workflows","Keep nurses, clinicians, and ops aligned without burying them in tickets.",[3424,3425,3426],"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":3428,"description":3429,"bullets":3430},"Auditor and partner collaboration","Give regulators, payers, and partners scoped access instead of email threads.",[3431,3432,3433],"Auditor portal with threaded Q&A per safeguard","Secure uploads with expirations and access controls","Exports for SOC 2, PCI, or privacy questionnaires",{"type":7,"value":3435,"toc":3439},[3436],[15,3437,3438],{},"Healthcare buyers move fast when they trust your safeguards. episki keeps PHI protections documented, monitored, and shareable without slowing product or patient care.",{"title":258,"searchDepth":259,"depth":259,"links":3440},[],{"title":3442,"description":3443,"items":3444},"Healthtech compliance checklist","Use this inside your trial to assign owners, attach evidence, and track renewals.",[3445,3446,3447,3448,3449],"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":3451,"description":3452},"Launch a healthtech-ready workspace","Connect your stack, invite stakeholders, and show PHI protections the same day.",{"headline":3454,"title":3455,"description":3456,"links":3457},"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.",[3458,3460],{"label":3459,"icon":2569,"to":1576},"Start healthtech trial",{"label":2571,"icon":2572,"color":2573,"variant":2574,"to":2511,"target":2575},{},"healthcare and healthtech","\u002Findustry\u002Fhealthcare",{"headline":3465,"title":3465,"description":3466,"items":3467},"Healthcare enablement kit","Keep leadership, clinicians, and auditors aligned on the same story.",[3468,3471,3474],{"title":3469,"description":3470},"PHI data flow deck","Share sanitized diagrams plus segmentation notes for customers and partners.",{"title":3472,"description":3473},"Board + payer brief","Summarize control health, incidents, and remediation in plain language.",{"title":3475,"description":3476},"Auditor-ready workspace","Prebuilt template for requests, evidence, and walkthrough scheduling.",{"title":3478,"description":3479},"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",[3482,3485,3488],{"value":3483,"description":3484},"30-day rollout","Move from baseline controls to monitored safeguards in under a month.",{"value":3486,"description":3487},"PHI-safe sharing","Role-based portals keep BAAs, policies, and diagrams organized and protected.",{"value":3489,"description":3490},"Continuous watch","Drift detection across access, logging, vendors, and incidents.","6.industry\u002F1.healthcare","u08a7hidKILzMlQgEwXI8WBgv7i08HXpMKdsEpMA3Tw",1792416025988]