[{"data":1,"prerenderedAt":1901},["ShallowReactive",2],{"\u002Fblog\u002Fshadow-it":3,"blog-surround-shadow-it":255,"explore-glossary-none-\u002Fblog\u002Fshadow-it":266,"explore-topics-none-\u002Fblog\u002Fshadow-it":1008,"explore-hub-none":6,"explore-compare-vs-\u002Fblog\u002Fshadow-it":1009,"explore-compare-\u002Fblog\u002Fshadow-it":1303,"explore-blog-none-\u002Fblog\u002Fshadow-it":1476,"explore-industry-none":1816},{"id":4,"title":5,"api":6,"authors":7,"body":13,"category":243,"date":244,"description":245,"extension":246,"faq":6,"features":6,"fixes":6,"highlight":6,"image":247,"improvements":6,"meta":249,"navigation":250,"path":251,"seo":252,"stem":253,"summary":6,"updated":6,"__hash__":254},"posts\u002F3.blog\u002Fshadow-it.md","Dealing with Shadow IT",null,[8],{"name":9,"to":10,"avatar":11},"Justin Leapline","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fjustinleapline\u002F",{"src":12},"\u002Fimages\u002Fjustinleapline.png",{"type":14,"value":15,"toc":233},"minimark",[16,20,23,26,31,34,37,60,63,66,70,73,79,85,91,94,98,101,104,137,144,148,154,160,163,167,170,190,193,197,214,217,220],[17,18,19],"p",{},"It's Monday morning. Finance just forwarded an invoice for an \"AI writing assistant\" nobody in IT approved. Marketing has been running campaigns out of a personal Notion workspace for six months. Sales closed three deals last quarter using a browser extension that scrapes LinkedIn—and nobody can tell you where that data lands.",[17,21,22],{},"Welcome to Shadow IT. Not a scandal. A symptom.",[17,24,25],{},"Mid-sized organizations don't lose to Shadow IT because employees are reckless. They lose because approved tools are slow, rigid, or missing—and people still have to ship. The practical response isn't a witch hunt. It's discover without shame, triage by real risk, and decide: bring it into the fold, or block it for a clear reason.",[27,28,30],"h2",{"id":29},"shadow-it-is-a-gap-not-a-character-flaw","Shadow IT Is a Gap, Not a Character Flaw",[17,32,33],{},"Shadow IT is any technology used for work outside the organization's approved inventory—SaaS apps, browser extensions, personal cloud drives, no-code automations, AI copilots, even a contractor's preferred project board.",[17,35,36],{},"In mid-market companies, it usually shows up for three reasons:",[38,39,40,48,54],"ul",{},[41,42,43,47],"li",{},[44,45,46],"strong",{},"Speed"," — Procurement takes weeks; the quarter ends Friday.",[41,49,50,53],{},[44,51,52],{},"Fit"," — The \"standard\" tool doesn't match how a team actually works.",[41,55,56,59],{},[44,57,58],{},"Awareness"," — People don't know a sanctioned alternative exists.",[17,61,62],{},"Treat every discovery as a requirements signal. If half of Customer Success is paying for the same chatbot out of pocket, you don't have a compliance problem first—you have a product gap.",[17,64,65],{},"Shame culture makes the inventory worse. When discovery equals punishment, tools go underground. You get less visibility, not more control.",[27,67,69],{"id":68},"discover-without-turning-it-into-a-manhunt","Discover Without Turning It Into a Manhunt",[17,71,72],{},"You need an inventory. You don't need a tribunal.",[17,74,75,78],{},[44,76,77],{},"Start with passive signals."," Expense reports and corporate card spend surface paid SaaS. Identity logs (SSO, email OAuth grants) show what people connect with work credentials. DNS\u002Fproxy and CASB-style egress data catch high-volume destinations. MDM and browser management reveal extensions and unmanaged devices. None of this requires accusing anyone in Slack.",[17,80,81,84],{},[44,82,83],{},"Add a safe intake path."," A short \"tools we use\" form—anonymous if needed—beats surprise audits. Promise (and keep) a no-blame window: report what you're using, help us evaluate it, keep working while we decide.",[17,86,87,90],{},[44,88,89],{},"Talk to teams, not just dashboards."," Ask ops, sales, and engineering leads: \"What would break if we took away the tools IT doesn't know about?\" That conversation surfaces process debt faster than a spreadsheet of domains.",[17,92,93],{},"Document owners, data types, and business purpose as you go. An inventory without context is just a longer to-do list.",[27,95,97],{"id":96},"risk-triage-not-everything-deserves-the-same-heat","Risk Triage: Not Everything Deserves the Same Heat",[17,99,100],{},"Once something is visible, sort it. Mid-sized GRC teams don't have time to run full vendor diligence on every Chrome extension.",[17,102,103],{},"Use a simple triage that leadership can understand:",[105,106,107,113,119,125,131],"ol",{},[41,108,109,112],{},[44,110,111],{},"What data is involved?"," Public marketing copy is not the same as customer PII, source code, or production credentials.",[41,114,115,118],{},[44,116,117],{},"Who has access?"," One power user vs. an entire department sharing a login.",[41,120,121,124],{},[44,122,123],{},"Where does data go?"," Retention, subprocessors, training on customer content, residency.",[41,126,127,130],{},[44,128,129],{},"What's the blast radius?"," Can a compromise of this tool reach SSO, email, or critical systems?",[41,132,133,136],{},[44,134,135],{},"Is there a contract and an owner?"," Orphan tools with no budget owner are higher risk than a managed exception.",[17,138,139,140,143],{},"Bucket findings into ",[44,141,142],{},"accept \u002F fold \u002F replace \u002F block",". Most items land in fold or replace. Only a minority need a hard block—and those should be explainable in one sentence to the people using them.",[27,145,147],{"id":146},"bring-into-the-fold-vs-block","Bring Into the Fold vs. Block",[17,149,150,153],{},[44,151,152],{},"Bring into the fold"," when the tool solves a real job and risk is manageable. That means: add it to the approved catalog, run proportionate vendor review, connect SSO if available, define who owns renewals, and set data-handling rules the team can actually follow. Sometimes \"fold\" means a short-term exception with an expiry date while you evaluate a sanctioned alternative.",[17,155,156,159],{},[44,157,158],{},"Block"," when the risk is disproportionate and there's no credible control path—cleartext handling of regulated data, known-abusive extensions, tools that force broad mailbox or drive scopes with no business need, or anything that creates an uninsurable gap. Blocking without a replacement plan just recreates Shadow IT under a new name. Pair every block with: what to use instead, how to migrate, and who helps.",[17,161,162],{},"The goal is a catalog people prefer because it's faster to ask than to hide—not a fortress of \"no\" that trains workarounds.",[27,164,166],{"id":165},"a-90-day-path-mid-sized-orgs-can-actually-run","A 90-Day Path Mid-Sized Orgs Can Actually Run",[17,168,169],{},"Don't announce a transformation. Run a contained program:",[105,171,172,178,184],{},[41,173,174,177],{},[44,175,176],{},"Days 1–30 — Visibility."," Stand up spend + identity + egress signals. Open a no-blame intake. Publish a one-page Shadow IT stance: discover, triage, fold or block with reasons.",[41,179,180,183],{},[44,181,182],{},"Days 31–60 — Triage the top 20."," Score by data sensitivity and blast radius. Fold the easy wins (SSO + owner + DPA). Queue replacements for medium risk. Block only the obvious.",[41,185,186,189],{},[44,187,188],{},"Days 61–90 — Make approved the path of least resistance."," Shorten procurement for low-risk SaaS. Publish the catalog where people already look. Assign a human who answers \"can I use X?\" in two business days.",[17,191,192],{},"Tools help when they keep inventory, vendors, exceptions, and evidence connected. Platforms like episki tie approvals and risk decisions to the same workflow your compliance program already runs—so Shadow IT stops living in a side spreadsheet.",[27,194,196],{"id":195},"key-takeaways","Key Takeaways",[38,198,199,202,205,208,211],{},[41,200,201],{},"Shadow IT is usually a speed or fit gap, not malice—shame culture hides risk",[41,203,204],{},"Discover with spend, identity, and egress signals plus a safe intake path",[41,206,207],{},"Triage by data, access, destination, blast radius, and ownership—not by vibes",[41,209,210],{},"Prefer bring-into-the-fold with SSO, owners, and proportionate review; block only with a replacement",[41,212,213],{},"Run a 90-day visibility → triage → catalog loop mid-market teams can staff",[17,215,216],{},"Shadow IT won't disappear. Competitive teams will always find tools. Your job is to make the honest path the easy path—and to reserve hard blocks for risks you can explain without theater.",[218,219],"hr",{},[17,221,222,225,226],{},[44,223,224],{},"Do you know which tools your teams are actually using for work, and who owns the risk decision on each one?"," episki helps teams keep tool inventories, vendor reviews, exceptions, and compliance evidence connected in one place your team will actually use. ",[227,228,232],"a",{"href":229,"rel":230},"https:\u002F\u002Fapp.episki.com",[231],"nofollow","Get started free",{"title":234,"searchDepth":235,"depth":235,"links":236},"",2,[237,238,239,240,241,242],{"id":29,"depth":235,"text":30},{"id":68,"depth":235,"text":69},{"id":96,"depth":235,"text":97},{"id":146,"depth":235,"text":147},{"id":165,"depth":235,"text":166},{"id":195,"depth":235,"text":196},"practices","2026-10-22","A practical approach to Shadow IT for mid-sized orgs—discover without shame culture, triage real risk, and choose bring-into-the-fold vs block.","md",{"src":248},"\u002Fimages\u002Fblog\u002Fshadow-it.webp",{},true,"\u002Fblog\u002Fshadow-it",{"title":5,"description":245},"3.blog\u002Fshadow-it","XllImPhANbMinYFCsPVSjlTeZcykJIGEgGoXkqdokGI",[256,261],{"title":257,"path":258,"stem":259,"description":260,"children":-1},"Strategies in a Shrinking Resource Economy: Building a Resilient Security Program","\u002Fblog\u002Fsecurity-shrinking-resources","3.blog\u002Fsecurity-shrinking-resources","Practical strategies for security leaders to maintain impact and resilience even when budgets and resources are shrinking.",{"title":262,"path":263,"stem":264,"description":265,"children":-1},"The Real Cost of SOC 2 in 2026: A Complete Breakdown","\u002Fblog\u002Fsoc2-cost-breakdown","3.blog\u002Fsoc2-cost-breakdown","A transparent breakdown of SOC 2 costs in 2026 — auditor fees, tooling, internal time, and practical ways to reduce your total compliance spend.",[267,847],{"id":268,"title":269,"body":270,"description":234,"extension":246,"lastUpdated":827,"meta":828,"navigation":250,"path":829,"relatedFrameworks":830,"relatedTerms":837,"seo":841,"slug":844,"stem":845,"term":275,"__hash__":846},"glossary\u002F8.glossary\u002Faccess-control.md","Access Control",{"type":14,"value":271,"toc":812},[272,276,279,284,287,313,317,323,329,335,341,345,348,354,371,377,391,397,408,412,415,472,476,479,493,497,500,523,527,530,579,583,586,706,709,712,741,745,752,755,792,795,798,801,805],[27,273,275],{"id":274},"what-is-access-control","What is Access Control?",[17,277,278],{},"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.",[280,281,283],"h3",{"id":282},"what-are-the-core-principles-of-access-control","What are the core principles of access control?",[17,285,286],{},"Access control is built on several foundational principles:",[38,288,289,295,301,307],{},[41,290,291,294],{},[44,292,293],{},"Least privilege"," — users are granted only the minimum access necessary to perform their job functions",[41,296,297,300],{},[44,298,299],{},"Separation of duties"," — critical tasks are divided among multiple individuals to prevent any single person from having unchecked authority",[41,302,303,306],{},[44,304,305],{},"Need to know"," — access to information is restricted to those who require it for a specific purpose",[41,308,309,312],{},[44,310,311],{},"Default deny"," — access is denied by default unless explicitly granted",[280,314,316],{"id":315},"what-are-the-types-of-access-control","What are the types of access control?",[17,318,319,322],{},[44,320,321],{},"Role-Based Access Control (RBAC)"," — access is determined by the user's role within the organization. Roles are defined with specific permissions, and users are assigned to roles. This is the most common model in enterprise environments.",[17,324,325,328],{},[44,326,327],{},"Attribute-Based Access Control (ABAC)"," — access decisions are based on attributes of the user, the resource, and the environment (e.g., department, location, time of day, device type).",[17,330,331,334],{},[44,332,333],{},"Discretionary Access Control (DAC)"," — resource owners decide who can access their resources. Common in file systems where owners set permissions.",[17,336,337,340],{},[44,338,339],{},"Mandatory Access Control (MAC)"," — access is controlled by the system based on security labels and clearance levels. Common in government and military environments.",[280,342,344],{"id":343},"what-are-access-control-components","What are access control components?",[17,346,347],{},"A complete access control program addresses:",[17,349,350,353],{},[44,351,352],{},"Authentication"," — verifying the identity of users:",[38,355,356,359,362,365,368],{},[41,357,358],{},"Passwords and passphrases",[41,360,361],{},"Multi-factor authentication (MFA)",[41,363,364],{},"Single sign-on (SSO)",[41,366,367],{},"Biometric authentication",[41,369,370],{},"Certificate-based authentication",[17,372,373,376],{},[44,374,375],{},"Authorization"," — determining what authenticated users can do:",[38,378,379,382,385,388],{},[41,380,381],{},"Permission assignments",[41,383,384],{},"Role definitions",[41,386,387],{},"Access control lists",[41,389,390],{},"Policy enforcement points",[17,392,393,396],{},[44,394,395],{},"Access lifecycle management"," — managing access throughout the user lifecycle:",[38,398,399,402,405],{},[41,400,401],{},"Provisioning (granting access when hired or role changes)",[41,403,404],{},"Review (periodic access certification)",[41,406,407],{},"Deprovisioning (revoking access upon termination or role change)",[280,409,411],{"id":410},"how-do-compliance-frameworks-address-access-control","How do compliance frameworks address access control?",[17,413,414],{},"Every major framework requires access control:",[38,416,417,426,440,454,463],{},[41,418,419,425],{},[44,420,421],{},[227,422,424],{"href":423},"\u002Fframeworks\u002Fsoc2","SOC 2"," — CC6.1 through CC6.8 cover logical and physical access controls",[41,427,428,434,435,439],{},[44,429,430],{},[227,431,433],{"href":432},"\u002Fframeworks\u002Fiso27001","ISO 27001"," — ",[227,436,438],{"href":437},"\u002Fglossary\u002Fannex-a","Annex A"," controls A.5.15 through A.5.18 and A.8.2 through A.8.5 address access management",[41,441,442,448,449,453],{},[44,443,444],{},[227,445,447],{"href":446},"\u002Fframeworks\u002Fhipaa","HIPAA"," — the ",[227,450,452],{"href":451},"\u002Fframeworks\u002Fhipaa\u002Fsecurity-rule","Security Rule"," requires access controls for ePHI (45 CFR 164.312(a))",[41,455,456,462],{},[44,457,458],{},[227,459,461],{"href":460},"\u002Fframeworks\u002Fpci","PCI DSS"," — Requirements 7 and 8 address access restriction and user identification",[41,464,465,471],{},[44,466,467],{},[227,468,470],{"href":469},"\u002Fframeworks\u002Fnistcsf","NIST CSF"," — PR.AC covers identity management, authentication, and access control",[280,473,475],{"id":474},"what-are-access-reviews","What are access reviews?",[17,477,478],{},"Regular access reviews (also called access certifications) are a critical control:",[38,480,481,484,487,490],{},[41,482,483],{},"Review user access rights periodically (quarterly is common for sensitive systems)",[41,485,486],{},"Verify that access aligns with current job responsibilities",[41,488,489],{},"Identify and remove excessive or unnecessary access",[41,491,492],{},"Document review results and remediation actions",[280,494,496],{"id":495},"what-are-common-access-control-weaknesses","What are common access control weaknesses?",[17,498,499],{},"Even well-designed access control programs can degrade over time without ongoing attention. Watch for these common issues:",[38,501,502,505,508,511,514,517,520],{},[41,503,504],{},"Excessive permissions that accumulate over time (privilege creep)",[41,506,507],{},"Shared or generic accounts that prevent individual accountability",[41,509,510],{},"Delayed deprovisioning when employees leave or change roles",[41,512,513],{},"Lack of MFA on critical systems and remote access paths",[41,515,516],{},"Inconsistent access review processes with no documented remediation",[41,518,519],{},"Service accounts with standing privileged access and no rotation schedule",[41,521,522],{},"Lack of visibility into SaaS application access outside the corporate IdP",[280,524,526],{"id":525},"how-do-you-implement-access-control-in-practice","How do you implement access control in practice?",[17,528,529],{},"Effective access control programs start with planning and build toward automation. The following steps provide a practical roadmap for organizations at any maturity level:",[105,531,532,538,544,550,556,562,573],{},[41,533,534,537],{},[44,535,536],{},"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.",[41,539,540,543],{},[44,541,542],{},"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.",[41,545,546,549],{},[44,547,548],{},"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.",[41,551,552,555],{},[44,553,554],{},"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.",[41,557,558,561],{},[44,559,560],{},"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.",[41,563,564,567,568,572],{},[44,565,566],{},"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 ",[227,569,571],{"href":570},"\u002Fglossary\u002Faudit-trail","audit trail"," that satisfies compliance requirements.",[41,574,575,578],{},[44,576,577],{},"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.",[280,580,582],{"id":581},"what-are-the-access-control-requirements","What are the access control requirements?",[17,584,585],{},"Different frameworks address the same access control concepts with different control references. The table below maps common requirements to their framework-specific identifiers:",[587,588,589,609],"table",{},[590,591,592],"thead",{},[593,594,595,599,601,603,605,607],"tr",{},[596,597,598],"th",{},"Requirement",[596,600,424],{},[596,602,433],{},[596,604,447],{},[596,606,461],{},[596,608,470],{},[610,611,612,633,652,672,689],"tbody",{},[593,613,614,618,621,624,627,630],{},[615,616,617],"td",{},"Unique user IDs",[615,619,620],{},"CC6.1",[615,622,623],{},"A.5.16",[615,625,626],{},"§164.312(a)(2)(i)",[615,628,629],{},"Req 8.2.1",[615,631,632],{},"PR.AC-1",[593,634,635,638,640,643,646,649],{},[615,636,637],{},"MFA",[615,639,620],{},[615,641,642],{},"A.8.5",[615,644,645],{},"Addressable",[615,647,648],{},"Req 8.4",[615,650,651],{},"PR.AC-7",[593,653,654,657,660,663,666,669],{},[615,655,656],{},"Access reviews",[615,658,659],{},"CC6.2",[615,661,662],{},"A.5.18",[615,664,665],{},"§164.312(a)(1)",[615,667,668],{},"Req 7.2",[615,670,671],{},"PR.AC-4",[593,673,674,676,679,682,684,687],{},[615,675,293],{},[615,677,678],{},"CC6.3",[615,680,681],{},"A.5.15",[615,683,665],{},[615,685,686],{},"Req 7.1",[615,688,671],{},[593,690,691,694,696,698,701,704],{},[615,692,693],{},"Deprovisioning",[615,695,659],{},[615,697,662],{},[615,699,700],{},"§164.312(a)(2)(ii)",[615,702,703],{},"Req 8.2.6",[615,705,632],{},[17,707,708],{},"Organizations subject to multiple frameworks can use this mapping to build a unified access control program that satisfies overlapping requirements without duplicating effort.",[17,710,711],{},"A few notes on framework-specific nuances:",[38,713,714,719,727,734],{},[41,715,716,718],{},[44,717,447],{}," 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.",[41,720,721,726],{},[44,722,723,725],{},[227,724,461],{"href":460}," 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.",[41,728,729,733],{},[44,730,731],{},[227,732,424],{"href":423}," 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.",[41,735,736,740],{},[44,737,738],{},[227,739,470],{"href":469}," 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.",[280,742,744],{"id":743},"how-does-zero-trust-relate-to-access-control","How does zero trust relate to access control?",[17,746,747,748,751],{},"Traditional access control models assume that users inside the network perimeter can be trusted. Zero trust architecture rejects that assumption entirely: ",[44,749,750],{},"never trust, always verify",".",[17,753,754],{},"In a zero trust model, every access request is authenticated, authorized, and encrypted regardless of where it originates. Key principles include:",[38,756,757,763,769,780,786],{},[41,758,759,762],{},[44,760,761],{},"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.",[41,764,765,768],{},[44,766,767],{},"Micro-segmentation"," — network resources are divided into small, isolated zones so that compromising one segment does not grant lateral access to others.",[41,770,771,774,775,779],{},[44,772,773],{},"Device posture checks"," — the security state of the connecting device (patch level, endpoint protection status, disk ",[227,776,778],{"href":777},"\u002Fglossary\u002Fencryption","encryption",") is evaluated before access is granted.",[41,781,782,785],{},[44,783,784],{},"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.",[41,787,788,791],{},[44,789,790],{},"Least privilege enforcement at the session level"," — access grants are scoped to the specific resource and action needed, and they expire when the session ends or conditions change.",[17,793,794],{},"NIST SP 800-207 defines the zero trust architecture and provides guidance on implementation. Many compliance frameworks are increasingly aligning their access control requirements with zero trust principles, making it a forward-looking strategy for organizations building or modernizing their access control programs.",[17,796,797],{},"Zero trust is not a single product but an architectural approach that spans identity, network, endpoints, and data.",[17,799,800],{},"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.",[280,802,804],{"id":803},"how-does-episki-help-with-access-control","How does episki help with access control?",[17,806,807,808,751],{},"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 ",[227,809,811],{"href":810},"\u002Fframeworks","compliance platform",{"title":234,"searchDepth":235,"depth":235,"links":813},[814],{"id":274,"depth":235,"text":275,"children":815},[816,818,819,820,821,822,823,824,825,826],{"id":282,"depth":817,"text":283},3,{"id":315,"depth":817,"text":316},{"id":343,"depth":817,"text":344},{"id":410,"depth":817,"text":411},{"id":474,"depth":817,"text":475},{"id":495,"depth":817,"text":496},{"id":525,"depth":817,"text":526},{"id":581,"depth":817,"text":582},{"id":743,"depth":817,"text":744},{"id":803,"depth":817,"text":804},"2026-08-31",{},"\u002Fglossary\u002Faccess-control",[831,832,833,834,835,836],"cmmc","soc2","iso27001","hipaa","pci","nistcsf",[838,839,778,840],"minimum-necessary-rule","audit-trail","user-entity-controls",{"title":842,"description":843},"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":848,"title":438,"body":849,"description":234,"extension":246,"lastUpdated":827,"meta":995,"navigation":250,"path":437,"relatedFrameworks":996,"relatedTerms":997,"seo":1002,"slug":1005,"stem":1006,"term":854,"__hash__":1007},"glossary\u002F8.glossary\u002Fannex-a.md",{"type":14,"value":850,"toc":985},[851,855,866,870,873,899,903,906,923,926,930,933,937,940,954,957,961,974,978],[27,852,854],{"id":853},"what-is-iso-27001-annex-a","What is ISO 27001 Annex A?",[17,856,857,858,860,861,865],{},"ISO 27001 Annex A is the normative annex to the ",[227,859,433],{"href":432}," standard that provides a reference list of information security controls. Organizations use Annex A as a checklist to ensure their ",[227,862,864],{"href":863},"\u002Fframeworks\u002Fiso27001\u002Fisms-implementation","Information Security Management System (ISMS)"," addresses a comprehensive range of security topics. As of the 2022 revision, Annex A contains 93 controls organized into four themes.",[280,867,869],{"id":868},"what-are-the-four-themes","What are the four themes?",[17,871,872],{},"The 2022 revision reorganized controls from the previous 14 categories into four themes:",[38,874,875,881,887,893],{},[41,876,877,880],{},[44,878,879],{},"Organizational controls (37 controls)"," — policies, roles and responsibilities, threat intelligence, information security in project management, supplier relationships, and more",[41,882,883,886],{},[44,884,885],{},"People controls (8 controls)"," — screening, terms and conditions of employment, security awareness training, disciplinary processes, and responsibilities after termination",[41,888,889,892],{},[44,890,891],{},"Physical controls (14 controls)"," — physical security perimeters, entry controls, securing offices and facilities, equipment protection, and clear desk policies",[41,894,895,898],{},[44,896,897],{},"Technological controls (34 controls)"," — user endpoint devices, privileged access management, access restrictions, secure authentication, malware protection, logging, encryption, and secure development",[280,900,902],{"id":901},"how-does-annex-a-fit-into-iso-27001","How does Annex A fit into ISO 27001?",[17,904,905],{},"Annex A is not a standalone list of mandatory controls. Instead, it works in conjunction with the risk assessment process defined in clauses 6 and 8 of ISO 27001:",[105,907,908,911,914,917,920],{},[41,909,910],{},"The organization performs a risk assessment to identify information security risks",[41,912,913],{},"The organization determines how to treat each risk (mitigate, accept, transfer, or avoid)",[41,915,916],{},"For risks being mitigated, the organization selects appropriate controls",[41,918,919],{},"The organization compares selected controls against Annex A to ensure nothing has been overlooked",[41,921,922],{},"The results are documented in the Statement of Applicability",[17,924,925],{},"This approach ensures that control selection is risk-driven rather than checkbox-driven. An organization may determine that certain Annex A controls are not applicable based on their specific risk profile, and this is acceptable as long as the justification is documented.",[280,927,929],{"id":928},"how-does-annex-a-relate-to-iso-27002","How does Annex A relate to ISO 27002?",[17,931,932],{},"ISO 27002 provides detailed implementation guidance for each Annex A control. While Annex A lists the controls with brief descriptions, ISO 27002 explains the purpose, guidance, and other information for each control. Think of Annex A as the \"what\" and ISO 27002 as the \"how.\"",[280,934,936],{"id":935},"what-changed-in-the-2022-revision-of-annex-a","What changed in the 2022 revision of Annex A?",[17,938,939],{},"The 2022 update introduced several changes from the 2013 version:",[38,941,942,945,948,951],{},[41,943,944],{},"Controls were consolidated from 114 to 93",[41,946,947],{},"The 14 categories were replaced with 4 themes",[41,949,950],{},"11 new controls were added, including threat intelligence, information security for cloud services, ICT readiness for business continuity, and data masking",[41,952,953],{},"Each control now includes attributes (control type, cybersecurity concept, operational capability, and security domain) to aid in filtering and mapping",[17,955,956],{},"Organizations certified under the 2013 version had a transition period to update their ISMS to align with the 2022 revision.",[280,958,960],{"id":959},"what-is-the-statement-of-applicability","What is the Statement of Applicability?",[17,962,963,964,968,969,973],{},"The ",[227,965,967],{"href":966},"\u002Fframeworks\u002Fiso27001\u002Fstatement-of-applicability","Statement of Applicability (SoA)"," is the document where an organization records which Annex A controls are applicable, which are not, and the justification for each decision. The SoA is a mandatory document for ",[227,970,972],{"href":971},"\u002Fframeworks\u002Fiso27001\u002Fcertification-process","ISO 27001 certification"," and is a key artifact reviewed during certification audits.",[280,975,977],{"id":976},"how-does-episki-help-with-annex-a","How does episki help with Annex A?",[17,979,980,981,751],{},"episki maps Annex A to controls evaluated on every sync across your connected estate, with evidence reused by every other framework that claims the same control. A check whose evidence comes back empty or unreadable returns inconclusive and attests nothing, so an Annex A control is never marked satisfied by a collection that silently failed. Learn more about the ",[227,982,984],{"href":983},"\u002Fframeworks\u002Fiso27001\u002Fannex-a-controls","Annex A controls",{"title":234,"searchDepth":235,"depth":235,"links":986},[987],{"id":853,"depth":235,"text":854,"children":988},[989,990,991,992,993,994],{"id":868,"depth":817,"text":869},{"id":901,"depth":817,"text":902},{"id":928,"depth":817,"text":929},{"id":935,"depth":817,"text":936},{"id":959,"depth":817,"text":960},{"id":976,"depth":817,"text":977},{},[833],[833,998,999,1000,1001],"statement-of-applicability","iso-27002","control-objectives","isms",{"title":1003,"description":1004},"ISO 27001 Annex A: All 93 Controls Explained (2022)","ISO 27001 Annex A lists 93 security controls in 4 themes. Learn each control category, how they map to your Statement of Applicability, and implementation tips.","annex-a","8.glossary\u002Fannex-a","ninWoLuGbIvkJx3djy7wTT090WPcFjANjfzM_i_lOn4",[],{"id":1010,"title":1011,"body":1012,"comparison":1204,"competitorA":1105,"competitorB":1117,"cta":1252,"description":234,"extension":246,"faq":1255,"hero":1273,"lastUpdated":827,"meta":1289,"navigation":250,"path":1290,"seo":1291,"slug":1294,"slugA":1295,"slugB":1296,"stem":1297,"verdict":1298,"__hash__":1302},"compareVs\u002F7.compare\u002Fvs\u002Fdrata-vs-secureframe.md","Drata Vs Secureframe",{"type":14,"value":1013,"toc":1194},[1014,1018,1021,1025,1028,1034,1037,1041,1044,1047,1050,1054,1057,1060,1064,1067,1139,1142,1145,1149,1152,1155,1159,1162,1165,1168],[27,1015,1017],{"id":1016},"drata-vs-secureframe-the-closest-comparison-in-compliance","Drata vs Secureframe: the closest comparison in compliance",[17,1019,1020],{},"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.",[280,1022,1024],{"id":1023},"feature-parity-with-different-emphasis","Feature parity with different emphasis",[17,1026,1027],{},"On paper, Drata and Secureframe look nearly identical. Both automate evidence collection, monitor your compliance posture continuously, support 15+ frameworks, and provide auditor-facing portals. The overlap is so significant that choosing between them often comes down to three factors: onboarding style, dashboard experience, and pricing.",[17,1029,1030,1033],{},[44,1031,1032],{},"Onboarding style"," is the clearest differentiator. Drata leans toward self-serve. The platform guides you through integration setup, control mapping, and evidence configuration with in-app workflows. For teams with compliance experience, this speed is an advantage — you can be operational in 1–2 weeks without waiting for a human to walk you through every step.",[17,1035,1036],{},"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.",[280,1038,1040],{"id":1039},"the-dashboard-question","The dashboard question",[17,1042,1043],{},"Drata's compliance dashboard is one of its signature features. The real-time posture view shows passing and failing controls across every framework, with compliance percentages and trend data. For compliance leads who report to a CISO or board, this visual layer simplifies status updates and makes it easy to demonstrate progress.",[17,1045,1046],{},"Secureframe also provides dashboards, but they feel more functional than visual. The platform surfaces actionable items — controls that need attention, evidence that's expiring, gaps to remediate — in a task-oriented format. It's effective, but it doesn't deliver the same at-a-glance executive view that Drata provides.",[17,1048,1049],{},"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.",[280,1051,1053],{"id":1052},"integration-depth","Integration depth",[17,1055,1056],{},"Both platforms now connect to hundreds of tools: Secureframe advertises 300+ integrations, and Drata says it integrates with hundreds. At that scale, raw counts rarely decide it. Check that the specific CI\u002FCD pipelines, vulnerability scanners, and endpoint management tools in your stack are covered natively, because any gap there becomes manual evidence collection.",[17,1058,1059],{},"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.",[280,1061,1063],{"id":1062},"pricing-opacity","Pricing opacity",[17,1065,1066],{},"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:",[587,1068,1069,1085],{},[590,1070,1071],{},[593,1072,1073,1076,1079,1082],{},[596,1074,1075],{},"Platform",[596,1077,1078],{},"Typical entry price (2026)",[596,1080,1081],{},"Pricing model",[596,1083,1084],{},"Published?",[610,1086,1087,1101,1113,1125],{},[593,1088,1089,1092,1095,1098],{},[615,1090,1091],{},"Vanta",[615,1093,1094],{},"~$11,000–$15,000\u002Fyr",[615,1096,1097],{},"Per-seat + framework, custom quote",[615,1099,1100],{},"No",[593,1102,1103,1106,1109,1111],{},[615,1104,1105],{},"Drata",[615,1107,1108],{},"~$10,000–$15,000\u002Fyr",[615,1110,1097],{},[615,1112,1100],{},[593,1114,1115,1118,1121,1123],{},[615,1116,1117],{},"Secureframe",[615,1119,1120],{},"~$8,000–$12,000\u002Fyr",[615,1122,1097],{},[615,1124,1100],{},[593,1126,1127,1130,1133,1136],{},[615,1128,1129],{},"episki",[615,1131,1132],{},"$750\u002Fmo ($7,500\u002Fyr)",[615,1134,1135],{},"Flat platform + modules, unlimited seats",[615,1137,1138],{},"Yes",[17,1140,1141],{},"At scale, Vanta, Drata, and Secureframe all reach $30,000–$50,000\u002Fyr for larger organizations. Secureframe usually starts slightly cheaper than Drata at the entry tier, but because both scale on seats and frameworks, the gap narrows quickly as your team grows.",[17,1143,1144],{},"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.",[280,1146,1148],{"id":1147},"where-both-platforms-struggle","Where both platforms struggle",[17,1150,1151],{},"The irony of comparing Drata and Secureframe is that their most significant limitations are shared. Both use pricing models that punish team growth. Both rely on templated control libraries that resist customization. Both treat policy documentation as a secondary concern — something generated through forms rather than crafted through a proper writing experience.",[17,1153,1154],{},"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.",[280,1156,1158],{"id":1157},"the-case-for-a-different-approach","The case for a different approach",[17,1160,1161],{},"When two products are this similar, the deciding factor often isn't which one is better — it's whether either one is the right category of tool for your needs. If you want maximum automation and are comfortable with enterprise pricing, Drata and Secureframe both deliver.",[17,1163,1164],{},"But if you want GRC that runs itself, episki offers something neither Drata nor Secureframe provides. Where legacy GRC automates evidence, episki automates the program: agents draft policies, answer security questionnaires, map controls, manage vendors, and keep evidence evergreen — while your team approves the work that matters. The AI authors deterministic recipes that then run without AI in the loop, so output is reproducible and auditor-acceptable. A dedicated AI Governance module (agent and use-case registry, ISO 42001, NIST AI RMF, EU AI Act) covers the governance work neither competitor was built for.",[17,1166,1167],{},"It comes with flat pricing at $750\u002Fmo plus optional modules, unlimited seats, and a Notion-like editor for the documentation your team owns. No per-seat scaling. No opaque quotes. No templated policies that read like every other company's — just a program that runs itself, at a price that doesn't make your CFO wince.",[17,1169,1170,1173,1174,1178,1179,1183,1184,1188,1189,1193],{},[44,1171,1172],{},"Related reading:"," dig deeper into each platform's competitors in our ",[227,1175,1177],{"href":1176},"\u002Fblog\u002Fdrata-alternatives","Drata alternatives"," and ",[227,1180,1182],{"href":1181},"\u002Fblog\u002Fsecureframe-alternatives","Secureframe alternatives"," guides, see where both rank in the ",[227,1185,1187],{"href":1186},"\u002Fblog\u002Fbest-grc-tools-2026","best GRC tools of 2026",", or compare ",[227,1190,1192],{"href":1191},"\u002Fcompare\u002Fvs\u002Fvanta-vs-drata","Vanta vs Drata"," if Vanta is also on your shortlist.",{"title":234,"searchDepth":235,"depth":235,"links":1195},[1196],{"id":1016,"depth":235,"text":1017,"children":1197},[1198,1199,1200,1201,1202,1203],{"id":1023,"depth":817,"text":1024},{"id":1039,"depth":817,"text":1040},{"id":1052,"depth":817,"text":1053},{"id":1062,"depth":817,"text":1063},{"id":1147,"depth":817,"text":1148},{"id":1157,"depth":817,"text":1158},[1205,1209,1213,1218,1223,1227,1232,1237,1242,1247],{"feature":1081,"competitorA":1206,"competitorB":1207,"episki":1208},"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":1210,"competitorA":1211,"competitorB":1211,"episki":1212},"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":1214,"competitorA":1215,"competitorB":1216,"episki":1217},"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":1219,"competitorA":1220,"competitorB":1221,"episki":1222},"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":1224,"competitorA":1225,"competitorB":1225,"episki":1226},"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":1228,"competitorA":1229,"competitorB":1230,"episki":1231},"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":1233,"competitorA":1234,"competitorB":1235,"episki":1236},"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":1238,"competitorA":1239,"competitorB":1240,"episki":1241},"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":1243,"competitorA":1244,"competitorB":1245,"episki":1246},"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":1248,"competitorA":1249,"competitorB":1250,"episki":1251},"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":1253,"description":1254},"Skip the comparison. Try episki free.","14-day trial with full access. No credit card required.",{"title":1256,"items":1257},"Drata vs Secureframe pricing FAQ (2026)",[1258,1261,1264,1267,1270],{"label":1259,"content":1260},"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":1262,"content":1263},"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":1265,"content":1266},"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":1268,"content":1269},"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":1271,"content":1272},"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":1274,"title":1275,"description":1276,"links":1277},"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.",[1278,1283],{"label":1279,"icon":1280,"to":1281,"target":1282},"Book a demo","i-lucide-calendar","\u002Fdemo","_blank",{"label":1284,"icon":1285,"color":1286,"variant":1287,"to":1288},"Try episki free","i-lucide-rocket","neutral","subtle","https:\u002F\u002Fapp.episki.com\u002Fauth\u002Fregister",{},"\u002Fcompare\u002Fvs\u002Fdrata-vs-secureframe",{"title":1292,"description":1293},"Drata vs Secureframe: Pricing & Evidence Automation","Drata vs Secureframe on pricing, automated evidence collection, onboarding, and framework coverage. A side-by-side table and which team each one fits.","drata-vs-secureframe","drata","secureframe","7.compare\u002Fvs\u002Fdrata-vs-secureframe",{"chooseA":1299,"chooseB":1300,"chooseEpiski":1301},"Choose Drata if you value self-serve speed and visual compliance dashboards. Drata gets you operational faster and provides the clearest real-time view of your compliance posture — ideal for teams with in-house compliance knowledge.","Choose Secureframe if you want more hands-on guidance from dedicated compliance managers. Secureframe's human-led onboarding is better for teams running their first audit without experienced GRC staff.","Choose episki if you want GRC that runs itself — agents draft policies, answer questionnaires, and keep evidence evergreen while your team approves the work that matters. You get transparent flat pricing ($750\u002Fmo plus optional modules, unlimited seats) and a dedicated AI Governance module.","l-c3Qw1KfFCqWQlH82pSvFRHsRkvIaxScWlhnZbmUMI",{"id":1304,"title":1305,"advantages":1306,"body":1328,"comparison":1391,"competitor":1305,"cta":1439,"description":234,"extension":246,"faq":1442,"hero":1460,"lastUpdated":827,"meta":1468,"navigation":250,"path":1469,"seo":1470,"slug":1473,"stem":1474,"__hash__":1475},"compare\u002F7.compare\u002Farcher.md","Archer",[1307,1314,1321],{"title":1308,"description":1309,"bullets":1310},"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.",[1311,1312,1313],"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":1315,"description":1316,"bullets":1317},"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.",[1318,1319,1320],"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":1322,"description":1323,"bullets":1324},"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.",[1325,1326,1327],"Empty, undecodable, or partially collected evidence returns inconclusive and attests nothing","A failing check raises a finding with the offending records attached","An approved exception can satisfy a check for named records — but it needs an approver and it expires",{"type":14,"value":1329,"toc":1386},[1330,1334,1337,1340,1343,1363,1367,1370,1373,1376,1379,1383],[27,1331,1333],{"id":1332},"why-teams-evaluate-archer-alternatives","Why teams evaluate Archer alternatives",[17,1335,1336],{},"Archer is one of the originals in integrated risk management, and at the top of the market it earns its position: operational risk, IT risk, third-party risk, and regulatory compliance modeled together, configurable to almost any taxonomy, deployable on-premises where that is mandatory.",[17,1338,1339],{},"That power has a shape. Deployments are configuration projects measured in months, frequently with a partner. Pricing is modular and custom, commonly reported from $75,000 into the hundreds of thousands per year. And reviewers consistently describe the interface as dated with a steep learning curve — which matters when the people who need to file evidence are engineers, not risk analysts.",[17,1341,1342],{},"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.",[38,1344,1345,1351,1357],{},[41,1346,1347,1350],{},[44,1348,1349],{},"No implementation project"," — self-serve signup, sensible defaults, first policy drafted in minutes",[41,1352,1353,1356],{},[44,1354,1355],{},"A published price"," — $7,500\u002Fyr for the platform, unlimited users and frameworks",[41,1358,1359,1362],{},[44,1360,1361],{},"Agents that do the drafting"," — instead of workflows that route it to a person",[27,1364,1366],{"id":1365},"where-episki-is-different","Where episki is different",[17,1368,1369],{},"episki does not try to be Archer. It makes the opposite bet: rather than configurability for a risk department, opinionated defaults plus agents that do the work.",[17,1371,1372],{},"Those agents draft policies, answer security questionnaires, map controls across frameworks, and advance vendor reviews over email between audits. The AI authors deterministic recipes — plain, inspectable procedures — that then run without a model in the loop, so an auditor reads how an artifact was gathered rather than trusting a generation.",[17,1374,1375],{},"And every control check produces a verdict. Each integration operation decodes its response, evaluates its assertions, and writes pass, fail, or inconclusive. Empty evidence attests nothing. An incomplete sync cannot mark a control clean. A failing check raises a finding with the offending records attached. An approved exception, bound to an approver and an expiry, can satisfy a check for named records without pretending the condition changed.",[17,1377,1378],{},"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.",[27,1380,1382],{"id":1381},"when-archer-might-still-be-the-better-fit","When Archer might still be the better fit",[17,1384,1385],{},"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":234,"searchDepth":235,"depth":235,"links":1387},[1388,1389,1390],{"id":1332,"depth":235,"text":1333},{"id":1365,"depth":235,"text":1366},{"id":1381,"depth":235,"text":1382},[1392,1396,1400,1403,1407,1411,1415,1419,1423,1427,1431,1435],{"feature":1393,"episki":1394,"competitor":1395},"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":1397,"episki":1398,"competitor":1399},"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":1081,"episki":1401,"competitor":1402},"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":1404,"episki":1405,"competitor":1406},"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":1408,"episki":1409,"competitor":1410},"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":1412,"episki":1413,"competitor":1414},"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":1416,"episki":1417,"competitor":1418},"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":1420,"episki":1421,"competitor":1422},"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":1424,"episki":1425,"competitor":1426},"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":1428,"episki":1429,"competitor":1430},"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":1432,"episki":1433,"competitor":1434},"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":1436,"episki":1437,"competitor":1438},"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":1440,"description":1441},"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":1443,"items":1444},"episki vs Archer — frequently asked questions",[1445,1448,1451,1454,1457],{"label":1446,"content":1447},"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":1449,"content":1450},"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":1452,"content":1453},"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":1455,"content":1456},"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":1458,"content":1459},"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":1461,"title":1462,"description":1463,"links":1464},"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.",[1465,1466],{"label":1279,"icon":1280,"to":1281,"target":1282},{"label":1467,"icon":1285,"color":1286,"variant":1287,"to":1288},"Start free trial",{},"\u002Fcompare\u002Farcher",{"title":1471,"description":1472},"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":1477,"title":1478,"api":6,"authors":1479,"body":1482,"category":243,"date":1807,"description":1808,"extension":246,"faq":6,"features":6,"fixes":6,"highlight":6,"image":1809,"improvements":6,"meta":1811,"navigation":250,"path":1812,"seo":1813,"stem":1814,"summary":6,"updated":6,"__hash__":1815},"posts\u002F3.blog\u002Fmonitoring-csp.md","Monitoring for CSP (PCI DSS 11.6.1)",[1480],{"name":9,"to":10,"avatar":1481},{"src":12},{"type":14,"value":1483,"toc":1797},[1484,1487,1490,1493,1496,1500,1503,1514,1517,1520,1528,1531,1535,1538,1541,1564,1567,1570,1588,1591,1594,1598,1601,1607,1613,1619,1625,1631,1641,1645,1648,1651,1665,1668,1672,1675,1717,1720,1724,1727,1730,1734,1737,1757,1760,1762,1783,1786,1788],[17,1485,1486],{},"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.",[17,1488,1489],{},"That is not monitoring. That is hope with a header.",[17,1491,1492],{},"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?",[17,1494,1495],{},"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.",[27,1497,1499],{"id":1498},"what-1161-actually-requires","What 11.6.1 Actually Requires",[17,1501,1502],{},"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:",[38,1504,1505,1508],{},[41,1506,1507],{},"Security-impacting HTTP headers on payment pages",[41,1509,1510,1511],{},"Script contents of those payment pages ",[44,1512,1513],{},"as received by the consumer browser",[17,1515,1516],{},"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.",[17,1518,1519],{},"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.",[17,1521,1522,1523,1527],{},"Also note what it does ",[1524,1525,1526],"em",{},"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.",[17,1529,1530],{},"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.",[27,1532,1534],{"id":1533},"where-csp-fits-and-where-it-doesnt","Where CSP Fits, and Where It Doesn't",[17,1536,1537],{},"Content Security Policy is useful. It is not a complete 11.6.1 program by itself.",[17,1539,1540],{},"A solid CSP can:",[38,1542,1543,1551,1554],{},[41,1544,1545,1546,1550],{},"Limit which origins may load scripts (",[1547,1548,1549],"code",{},"script-src",")",[41,1552,1553],{},"Prefer hashes or nonces over wildcards",[41,1555,1556,1557,1560,1561],{},"Report violations via ",[1547,1558,1559],{},"report-to"," or ",[1547,1562,1563],{},"report-uri",[17,1565,1566],{},"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.",[17,1568,1569],{},"CSP still leaves gaps mid-market teams hit every week:",[38,1571,1572,1575,1578,1585],{},[41,1573,1574],{},"Dynamic payment scripts that resist clean Subresource Integrity (SRI) hashes",[41,1576,1577],{},"Tag managers that rewrite the allowlist faster than GRC can document it",[41,1579,1580,1581,1584],{},"Changes ",[1524,1582,1583],{},"to"," the CSP header itself, which can be an attack signal and must be monitored",[41,1586,1587],{},"\"Report-only\" policies that never graduate to enforcement because nobody owned the cleanup",[17,1589,1590],{},"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.",[17,1592,1593],{},"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.",[27,1595,1597],{"id":1596},"a-practical-stack-for-mid-sized-merchants","A Practical Stack for Mid-Sized Merchants",[17,1599,1600],{},"You do not need a Fortune-500 security engineering org. You need a stack you can run every week.",[17,1602,1603,1606],{},[44,1604,1605],{},"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.",[17,1608,1609,1612],{},[44,1610,1611],{},"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.",[17,1614,1615,1618],{},[44,1616,1617],{},"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.",[17,1620,1621,1624],{},[44,1622,1623],{},"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.",[17,1626,1627,1630],{},[44,1628,1629],{},"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.",[17,1632,1633,1636,1637,1640],{},[44,1634,1635],{},"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 ",[1524,1638,1639],{},"and"," the operating proof.",[27,1642,1644],{"id":1643},"operating-cadence-that-survives-an-audit","Operating Cadence That Survives an Audit",[17,1646,1647],{},"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.",[17,1649,1650],{},"Each cycle, ask:",[38,1652,1653,1656,1659,1662],{},[41,1654,1655],{},"Did any new script appear on an in-scope page?",[41,1657,1658],{},"Did any authorized script's content or source change without a change ticket?",[41,1660,1661],{},"Did security headers (CSP, HSTS, framing controls, and peers you treat as security-impacting) drift?",[41,1663,1664],{},"Were alerts acknowledged and closed with a disposition?",[17,1666,1667],{},"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.",[27,1669,1671],{"id":1670},"common-failure-modes","Common Failure Modes",[17,1673,1674],{},"Mid-sized programs usually stumble in the same places:",[38,1676,1677,1683,1689,1695,1705,1711],{},[41,1678,1679,1682],{},[44,1680,1681],{},"CSP with no report pipeline."," Blocks (or would block) but never alerts. A header without alerts, owners, and review evidence is configuration, not monitoring.",[41,1684,1685,1688],{},[44,1686,1687],{},"Inventory that is a one-time spreadsheet."," Drift starts the day after the assessment.",[41,1690,1691,1694],{},[44,1692,1693],{},"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.",[41,1696,1697,1700,1701,1704],{},[44,1698,1699],{},"Vendor \"we handle PCI\" assumptions."," Embedded forms help, but your SAQ or ROC still needs ",[1524,1702,1703],{},"your"," evidence for pages you control.",[41,1706,1707,1710],{},[44,1708,1709],{},"Alerts with no owner."," Detection without response is theater.",[41,1712,1713,1716],{},[44,1714,1715],{},"Weekly in theory, never in practice."," Teams document the cadence, then cannot show tickets or reports proving the check ran and someone reviewed results.",[17,1718,1719],{},"Fix those before you buy another dashboard.",[27,1721,1723],{"id":1722},"how-this-ties-to-day-to-day-grc","How This Ties to Day-to-Day GRC",[17,1725,1726],{},"11.6.1 is not a one-off project. It is an operating control: inventory, detect, alert, investigate, evidence.",[17,1728,1729],{},"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.",[27,1731,1733],{"id":1732},"what-good-enough-looks-like","What \"Good Enough\" Looks Like",[17,1735,1736],{},"For a mid-sized merchant, good enough usually looks like this:",[38,1738,1739,1742,1745,1748,1751,1754],{},[41,1740,1741],{},"Payment pages and parent pages are identified and owned",[41,1743,1744],{},"Scripts are inventoried and authorized under 6.4.3",[41,1746,1747],{},"CSP is implemented thoughtfully, with reporting turned on",[41,1749,1750],{},"A change and tamper detection mechanism compares browser-received scripts and security-impacting headers against baseline",[41,1752,1753],{},"Alerts reach a human on a defined schedule",[41,1755,1756],{},"Evidence of weekly (or TRA-defined) operation is retained for assessment",[17,1758,1759],{},"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.",[27,1761,196],{"id":195},[38,1763,1764,1771,1774,1777,1780],{},[41,1765,1766,1767,1770],{},"PCI DSS 11.6.1 requires change and tamper detection and alerting for payment-page scripts and security-impacting headers ",[44,1768,1769],{},"as the consumer browser receives them",", at least weekly or per TRA",[41,1772,1773],{},"CSP helps constrain unauthorized loads and can feed monitoring via violation reports, but CSP alone is not a complete 11.6.1 answer",[41,1775,1776],{},"Pair CSP with browser-perspective monitoring, a living 6.4.3 inventory, and named alert owners",[41,1778,1779],{},"Mid-sized merchants win with a simple weekly stack and evidence, not with an unread policy header",[41,1781,1782],{},"Common failures: no reporting, stale inventories, server-only checks, and orphaned alerts",[17,1784,1785],{},"Skimmers live in the gap between \"we set a header\" and \"we watch what customers actually load.\" Close that gap on purpose.",[218,1787],{},[17,1789,1790,1793,1794],{},[44,1791,1792],{},"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. ",[227,1795,232],{"href":229,"rel":1796},[231],{"title":234,"searchDepth":235,"depth":235,"links":1798},[1799,1800,1801,1802,1803,1804,1805,1806],{"id":1498,"depth":235,"text":1499},{"id":1533,"depth":235,"text":1534},{"id":1596,"depth":235,"text":1597},{"id":1643,"depth":235,"text":1644},{"id":1670,"depth":235,"text":1671},{"id":1722,"depth":235,"text":1723},{"id":1732,"depth":235,"text":1733},{"id":195,"depth":235,"text":196},"2026-10-19","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":1810},"\u002Fimages\u002Fblog\u002Fmonitoring-csp.webp",{},"\u002Fblog\u002Fmonitoring-csp",{"title":1478,"description":1808},"3.blog\u002Fmonitoring-csp","MQvwlNwCLwpjBPvroqYhLVy1PEASgzEdolxnjW6HpBQ",{"id":1817,"title":1818,"advantages":1819,"body":1841,"checklist":1848,"cta":1857,"description":1845,"extension":246,"faq":6,"hero":1860,"lastUpdated":827,"meta":1869,"name":1870,"navigation":250,"path":1871,"resources":1872,"seo":1885,"slug":1888,"stats":1889,"stem":1899,"__hash__":1900},"industries\u002F6.industry\u002F1.healthcare.md","Healthcare",[1820,1827,1834],{"title":1821,"description":1822,"bullets":1823},"PHI-aware control mapping","Map administrative, technical, and physical safeguards to your stack without rebuilding every audit.",[1824,1825,1826],"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":1828,"description":1829,"bullets":1830},"Clinician-friendly workflows","Keep nurses, clinicians, and ops aligned without burying them in tickets.",[1831,1832,1833],"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":1835,"description":1836,"bullets":1837},"Auditor and partner collaboration","Give regulators, payers, and partners scoped access instead of email threads.",[1838,1839,1840],"Auditor portal with threaded Q&A per safeguard","Secure uploads with expirations and access controls","Exports for SOC 2, PCI, or privacy questionnaires",{"type":14,"value":1842,"toc":1846},[1843],[17,1844,1845],{},"Healthcare buyers move fast when they trust your safeguards. episki keeps PHI protections documented, monitored, and shareable without slowing product or patient care.",{"title":234,"searchDepth":235,"depth":235,"links":1847},[],{"title":1849,"description":1850,"items":1851},"Healthtech compliance checklist","Use this inside your trial to assign owners, attach evidence, and track renewals.",[1852,1853,1854,1855,1856],"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":1858,"description":1859},"Launch a healthtech-ready workspace","Connect your stack, invite stakeholders, and show PHI protections the same day.",{"headline":1861,"title":1862,"description":1863,"links":1864},"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.",[1865,1867],{"label":1866,"icon":1285,"to":1288},"Start healthtech trial",{"label":1279,"icon":1868,"color":1286,"variant":1287,"to":1281,"target":1282},"i-lucide-message-circle",{},"healthcare and healthtech","\u002Findustry\u002Fhealthcare",{"headline":1873,"title":1873,"description":1874,"items":1875},"Healthcare enablement kit","Keep leadership, clinicians, and auditors aligned on the same story.",[1876,1879,1882],{"title":1877,"description":1878},"PHI data flow deck","Share sanitized diagrams plus segmentation notes for customers and partners.",{"title":1880,"description":1881},"Board + payer brief","Summarize control health, incidents, and remediation in plain language.",{"title":1883,"description":1884},"Auditor-ready workspace","Prebuilt template for requests, evidence, and walkthrough scheduling.",{"title":1886,"description":1887},"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",[1890,1893,1896],{"value":1891,"description":1892},"30-day rollout","Move from baseline controls to monitored safeguards in under a month.",{"value":1894,"description":1895},"PHI-safe sharing","Role-based portals keep BAAs, policies, and diagrams organized and protected.",{"value":1897,"description":1898},"Continuous watch","Drift detection across access, logging, vendors, and incidents.","6.industry\u002F1.healthcare","u08a7hidKILzMlQgEwXI8WBgv7i08HXpMKdsEpMA3Tw",1792689790561]