Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  /

  / Shadow AI Policy Template: Ready-to-Use IT Framework

Shadow AI Policy Template: Ready-to-Use IT Framework

One in five organizations has already suffered a breach traced back to shadow AI. Meanwhile, 63% of breached organizations either have no AI governance policy at all or are still drafting one. Below is a complete, copy-ready shadow AI policy template with twelve sections, plus guidance on adapting it for your company size, your industry, and the regulatory frameworks you answer to.

The template assumes one hard truth up front: your employees are already using unapproved AI tools. A policy that pretends adoption hasn’t started yet fails on day one, so this one starts from the assumption that it has.

What Is a Shadow AI Policy?

A shadow AI policy is a formal document that defines how your organization discovers, evaluates, approves, and governs AI tools that employees adopt outside official IT channels. The term borrows from shadow IT, the older problem of unsanctioned software and hardware, but the AI version carries sharper risks: data pasted into a public model may be retained, used for training, or exposed in ways the organization can’t reverse.

The policy does three jobs: it separates approved use from unapproved use, gives employees a fast and visible way to request new tools so the sanctioned route beats the workaround, and spells out what happens when someone crosses the line, including how the organization detects it and responds.

Shadow AI Policy vs. General AI Acceptable Use Policy

Many organizations already have an AI acceptable use policy (AUP) and assume it covers shadow AI. It usually doesn’t. An AUP tells employees how to behave inside approved tools. A shadow AI policy governs the tools themselves: which ones exist in your environment, which ones are allowed, and what happens with the rest.

You need both. The AUP handles conduct; the shadow AI policy handles inventory and control. If you only have room for one document, fold the AUP’s data-handling rules into Section 6 of the template below.

The Shadow AI Policy Template (Download Link and Copy-Ready Sections)

We’ve created a compliance safe template for Shadow AI Policy, use the link below to create a copy and customize for your company:

Copy the sections below into your policy management system and replace the bracketed placeholders. The language is plain on purpose. Legalese gets skimmed.

Shadow AI Policy Template Summary

Section 1: Purpose and Scope

This policy governs the acquisition, approval, and use of artificial intelligence tools, features, and services at [Company]. It applies to all employees, contractors, interns, and third parties with access to [Company] systems or data. It covers standalone AI applications, AI features embedded in existing software, browser extensions, AI agents, APIs, and personal AI accounts used for work purposes, on both corporate and personal devices. The purpose of this policy is to enable productive AI use while protecting [Company] data, customers, and legal obligations. This policy does not prohibit AI. It prohibits ungoverned AI.

That last sentence matters. Employees read the purpose statement first, and it decides whether they see the policy as an enabler or a blocker.

Section 2: Definitions and Terminology

Shadow AI: any AI tool, feature, agent, or service used for work purposes without formal approval under this policy. Approved AI Tool: an AI tool listed in the Approved AI Tools Registry (Section 4) and used under a [Company]-managed account. Personal AI Account: an account on any AI service registered to a personal email address or paid for personally. AI Feature: AI functionality embedded within otherwise approved software (e.g., an AI assistant added to a project management tool), which requires separate evaluation. Sensitive Data: data classified as [Confidential] or [Restricted] under [Company]‘s data classification policy, including the prohibited data classes in Section 6.

Define “AI feature” explicitly. Vendors now ship AI additions into already-approved SaaS products every month, and without this definition, those features inherit approval they never earned.

Section 3: Roles and Responsibilities

The CISO (or designated security lead) owns this policy, maintains the Approved AI Tools Registry, and runs the approval workflow. Department heads ensure their teams know the policy and surface tool requests rather than suppressing them. Legal and Compliance review tools that touch regulated data or fall under the EU AI Act, GDPR, HIPAA, or client contractual restrictions. IT operates detection and monitoring controls (Section 9). Every employee is responsible for using only approved tools for work, reporting unapproved AI use they discover, and requesting new tools through the workflow in Section 7 rather than adopting them directly.

Insider Note: In organizations under roughly 200 people, the “CISO” in this section is often the same overworked IT lead who manages laptops. Name a real person, not a title that doesn’t exist yet. A policy that assigns duties to a phantom role is unenforceable, and auditors notice.

Section 4: Approved AI Tools Registry

[Company] maintains a registry of approved AI tools at [location/URL]. For each tool, the registry records: tool name and vendor, approved use cases, prohibited use cases, permitted data classes, account type (enterprise/team/individual), data retention and training settings, risk tier (Section 5), approval date, and next review date. Only tools listed in the registry may be used for work. Tools not listed are unapproved by default. The registry is reviewed [quarterly].

Keep the registry somewhere employees actually look, such as your intranet homepage or IT help center, not buried in a GRC platform they can’t access. An invisible registry recreates the problem the policy exists to fix.

Section 5: Risk Tier Classification (Low, Medium, High)

Each tool in the registry is assigned a risk tier. Low: the tool processes only public or internal non-sensitive data, runs under an enterprise agreement with training opt-out, and produces output that a human reviews before use. Approval by IT Security alone. Medium: the tool processes internal business data or connects to [Company] systems via API or integration. Approval by IT Security plus the data owner. High: the tool processes sensitive data, customer personal data, or regulated data; makes or influences consequential decisions (hiring, credit, medical, legal); or operates autonomously as an agent. Approval by IT Security, Legal, and the executive sponsor, with a documented risk assessment.

Tiering is what keeps the approval workflow fast. Without it, a request for a grammar checker sits in the same queue as a request for an autonomous agent with database access, and both take six weeks.

Section 6: Prohibited Data Classes and Use Cases

The following data may never be entered into any AI tool that is not explicitly approved for it in the registry: customer or employee personal data; protected health information; payment card data; authentication credentials, API keys, and access tokens; source code designated proprietary; unreleased financial results; legal matters and privileged communications; client-confidential material governed by NDA; and any data classified [Restricted]. The following use cases are prohibited in all tiers without executive and Legal approval: automated employment decisions, biometric identification, emotion inference in the workplace, and any use case restricted or prohibited under the EU AI Act.

IBM’s 2025 report found that 65% of shadow AI breaches involved customer personal data, well above the 53% average across all breaches. This section is where you keep yours out of that statistic.

Section 7: Tool Request and Approval Workflow

Any employee may request a new AI tool by submitting [form/link] with: the tool name, intended use case, data classes involved, and account type. IT Security triages the request within [3 business days] and assigns a provisional risk tier. Low-tier requests receive a decision within [5 business days]; medium within [10]; high within [20]. If a decision misses its deadline, the request escalates automatically to [role]. Rejections must state the reason and, where possible, name an approved alternative. Approved tools are added to the registry before use begins.

The deadlines are the whole point. A workflow without service-level targets is a suggestion box, and employees will route around it within a week.

Pro Tip: Publish your approval statistics internally

Publish your approval statistics internally each quarter: requests received, approved, rejected, and average turnaround. When employees can see that 80% of requests get approved in under a week, the sanctioned path becomes the obvious one. Secrecy around approvals feeds the assumption that asking is pointless.

Section 8: Identity, Access, and Authentication Requirements

All approved AI tools must be accessed through [Company]-managed accounts provisioned via SSO where the vendor supports it. Multi-factor authentication is mandatory. Personal accounts may not be used for work data under any circumstances, including free tiers of tools whose enterprise version is approved. API keys for AI services are issued, stored, and rotated through [Secrets Manager] and may not be embedded in code, shared in chat, or pasted into other AI tools. Access to high-tier tools follows least privilege and is reviewed [quarterly]. Departing employees have AI tool access revoked as part of standard offboarding.

See our full breakdown of Identity, Access, and Authentication Requirements for the tooling behind this section. The personal-account clause deserves extra attention in training. Netskope’s 2026 research found that most generative AI users access tools through personal accounts, which sit entirely outside enterprise logging, retention controls, and legal hold.

Section 9: Monitoring, Detection, and Auditing

IT operates technical controls to detect unapproved AI use, which may include DNS and web proxy monitoring of known AI service domains, CASB or SSPM discovery of SaaS and OAuth grants, browser-level data loss prevention for paste and upload events into AI services, and review of network traffic to AI API endpoints. Detection exists to protect [Company] data, not to surveil individuals; findings are handled under Section 10 with a remediation-first approach. IT Security audits the environment for unsanctioned AI at least [quarterly] and reports findings to [governance committee]. Monitoring practices comply with applicable employment and privacy law in each jurisdiction where [Company] operates.

Only 34% of organizations with AI governance policies actually audit for unsanctioned AI, per IBM. Writing this section is easy. Resourcing it is the real commitment.

Section 10: Incident Response for Shadow AI Events

A shadow AI event includes sensitive data entered into an unapproved tool, an unapproved tool connected to [Company] systems, or an approved tool used outside its permitted data classes. Upon discovery, the responder must: (1) identify the tool, account, and data involved; (2) preserve evidence, including prompts and outputs where retrievable; (3) contain by revoking access, disabling integrations, and requesting vendor data deletion; (4) assess whether the event constitutes a reportable breach under GDPR, HIPAA, or contractual obligations, with Legal making the determination; (5) notify affected parties per legal requirements; and (6) complete a post-incident review that feeds back into the registry, training, and this policy. Self-reported events within [24 hours] of occurrence are treated as near-misses, not violations, provided no intentional misconduct occurred.

That final sentence is your early-warning system. IBM found shadow AI breaches take about a week longer than average to identify and contain, largely because nobody wants to admit what happened. A self-reporting safe harbor shortens that timeline more than any monitoring tool.

Section 11: Enforcement and Consequences

Violations are handled proportionally. First unintentional violations result in retraining and documentation. Repeated violations, or any violation involving sensitive data, escalate through [Company]‘s standard disciplinary process up to termination. Intentional concealment of AI use after a direct inquiry, falsification of approval records, or entering prohibited data classes knowingly are treated as serious misconduct. Contractors and third parties in violation may have access revoked and contracts reviewed. Enforcement decisions are documented by [HR/Legal] and reported in aggregate to the [governance committee].

Proportionality isn’t softness. Employees who think a single honest mistake ends their career will hide every mistake, and hidden mistakes turn into the breaches you read about.

Section 12: Policy Review Cadence

This policy is reviewed [every six months] and after any of the following triggers: a shadow AI incident classified medium or higher, a material change in AI regulation affecting [Company], adoption of a new AI category (e.g., autonomous agents), or a significant change in the approved tool registry. The policy owner presents review outcomes to [governance committee], and material changes are communicated to all staff with [30 days] notice.

Six months is the ceiling, not the target. The AI tool market moves faster than any software category your policies have covered before.

How to Customize the Template for Your Organization

The template above is generic by design. Its value depends on how you adapt it, and three variables matter most: size, industry, and regulatory exposure.

Adapting for Company Size (SMB, Mid-Market, Enterprise)

SMBs (under ~200 employees) should collapse the structure. Merge Sections 3, 7, and 9 into a single owner, usually the IT lead, with the CEO as escalation. Cut the three-tier approval to two: “IT approves” and “IT plus outside counsel approves.” Skip CASB tooling you can’t afford and rely on SSO enforcement, a short approved-tools list, and a standing rule that free-tier AI accounts are banned for work data. The whole policy should fit on two pages.

Mid-market companies (200 to 2,000) should implement the template roughly as written, with real detection tooling and a quarterly audit. This is the size band where shadow AI grows fastest: enough employees to generate hundreds of unsanctioned tools, not yet enough governance headcount to notice.

Enterprises should extend it. Add per-business-unit registries that roll up to a central one, integrate the approval workflow into existing ITSM tooling, assign a dedicated AI governance function, and align Section 12’s review triggers with the enterprise risk committee calendar. At this scale, also add a section on AI agents and non-human identities, because agent sprawl is the next form shadow AI takes.

Adapting for Regulated Industries (Healthcare, Finance, Legal)

Healthcare organizations must treat any tool that could touch protected health information as high-tier by default and require a Business Associate Agreement before approval. Wolters Kluwer research in 2026 found that one in ten healthcare professionals has already used an unauthorized AI tool in a direct patient care context, so Section 6 should name clinical use cases explicitly rather than relying on general data-class language.

Financial services firms should map Section 9’s monitoring to existing supervision and record-keeping obligations, since prompts and outputs may qualify as business communications regulators expect you to retain. Model risk management requirements also mean high-tier approvals need documented validation, not just a security review.

Legal organizations face privilege risk on top of confidentiality risk. A prompt containing client matter details entered into an unapproved tool can arguably waive privilege. Section 6 should prohibit matter-identifiable information in any tool without explicit client consent, and Section 10 should add a privilege assessment step to the incident workflow.

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

Strengthen Your Business Continuity Strategy​

Aligning with EU AI Act, GDPR, and NIST AI RMF

Three frameworks shape most shadow AI policies, and the template maps to each.

The EU AI Act matters even for shadow tools, because obligations attach to the use of AI, not just its procurement. Article 4’s AI literacy requirement, applicable since February 2025, means staff using AI need adequate training, which is impossible for tools you can’t see. Section 5’s high tier and Section 6’s prohibited use cases should mirror the Act’s prohibited and high-risk categories. Note that the Digital Omnibus proposals have shifted timelines for certain Annex III high-risk obligations toward late 2027, so keep Section 12’s regulatory trigger active rather than hardcoding dates.

Under the GDPR, an unapproved AI vendor processing personal data is a processor with no Article 28 contract, no lawful basis analysis, and no entry in your records of processing. Sections 6 and 10 carry the GDPR weight: prohibited data classes prevent the violation, and the incident workflow determines whether a 72-hour breach notification applies.

The NIST AI Risk Management Framework provides the vocabulary for the whole structure. The registry and detection controls implement the Map function, risk tiers implement Measure, the approval workflow and enforcement implement Manage, and the roles, review cadence, and governance reporting implement Govern. If you pursue ISO/IEC 42001 certification later, a shadow AI policy built this way gives you a running start on the management system’s inventory and risk assessment clauses.

Worth Knowing: IBM's 2025 Report

IBM's 2025 report found that 97% of organizations that suffered an AI-related security incident lacked basic AI access controls. Section 8 of this template, the least glamorous section, addresses the single most common failure condition in real-world AI breaches.

Why Bans Fail: The Permission Gap

Some leadership teams will read this template and ask the obvious question: why not just block everything? Because the data says blocking doesn’t work. PagerDuty’s 2026 survey of office professionals at large companies found that 66% had used AI tools at work despite believing it was against policy, and nearly half said they’d rather use AI without telling anyone than risk being told no. Microsoft and LinkedIn’s Work Trend Index put bring-your-own-AI at 78% of AI users back in 2024, before adoption accelerated further.

Call it the permission gap: the space between what employees are allowed to use and what their workload demands. When approved tools lag behind the job, employees close that distance themselves, on personal accounts and personal devices, outside of your control you own. A ban doesn’t shrink the gap. It pushes usage where you can’t see it, which is exactly where IBM measured that extra $670,000 in breach cost. The organizations with the least shadow AI aren’t the ones with the strictest bans. They’re the ones where the approved path is genuinely faster than the workaround.

 

Rolling It Out Without Killing Adoption

Sequence matters more than policy text. Start with discovery, not announcement: run your DNS, proxy, and SaaS discovery tools for two to four weeks before the policy goes live, so the initial registry reflects the tools people already depend on. Then grandfather aggressively. Take the ten most-used discovered tools, fast-track them through the approval workflow, and launch the policy with a populated registry rather than an empty one. A policy that opens by approving the tools people already rely on earns compliance. One that opens with prohibition doesn’t.

Announce with an amnesty window. Give employees 30 days to disclose the tools they use with no consequences, and route every disclosure into the request workflow. Pair the announcement with the training the EU AI Act already expects you to deliver, and keep it practical: show real examples of what may and may not go into a prompt, using your own data classes. Then measure adoption of the approved tools, not just violations. If usage of sanctioned tools is flat while detection findings climb, your approved offering is the problem, not your workforce.

Important: Don’t launch monitoring (Section 9) before the amnesty window closes. Employees who discover they were being watched during a supposed grace period will treat every future assurance from IT Security as hollow, and you’ll spend years rebuilding the trust that shadow AI governance depends on.

 

Conclusion

Shadow AI isn’t a discipline problem. It’s a governance vacuum, and vacuums get filled by whatever tool loads fastest. The twelve-section template above fills that vacuum with a registry, risk tiers, a fast approval path, real detection, and proportional enforcement, then adapts to your size, sector, and regulatory obligations. Copy it, name real owners, and populate the registry with the tools your people already use. Once asking beats hiding, the gap starts closing on its own.

Axipro Author

Picture of Pedro Dias

Pedro Dias

Pedro has been writing online for over 10 years. With experience in all things programming, cyber security, and compliance, he is our editor-in-chief at Axipro.

Blog Highlights

Explore More Articles

For the past two years, enterprise AI risk conversations have centered on a familiar set of concerns: model bias, hallucination, data privacy, and dependency on third-party models. These are real risks, and most organizations now run some version of a governance program to manage them. But something has shifted. Organizations are no longer just deploying AI that generates content for a human to review. They’re deploying AI that acts. Agents now plan multi-step tasks, call APIs, move data between systems, execute transactions, and coordinate with other agents, often with no human checkpoint in the loop. That shift deserves more than a footnote in the existing AI risk category. It deserves its own line in the risk register: Agentic Autonomy Risk. What Is Agentic AI Risk Management? Agentic AI risk management is the practice of identifying, assessing, and controlling the risks created when AI systems take autonomous action on an organization’s behalf. Where traditional AI governance evaluates outputs (accuracy, bias, privacy), agentic AI risk management governs what agents actually do: the tools they call, the permissions they inherit, and the downstream consequences of their actions. That distinction is the reason existing risk registers struggle with agents, and it’s worth unpacking properly. What Agentic AI Actually Changes Traditional AI systems, even generative ones, are advisory. They produce an output such as a summary, a prediction, a draft email, or a classification, and a human remains the last checkpoint before anything happens in the real world. Agentic AI removes that checkpoint. An agentic system doesn’t just produce an answer. It pursues a goal. It decides which tools to call and in what order, then executes those actions directly against live systems: submitting a purchase order, modifying a database record, sending an external communication, or orchestrating a set of sub-agents to complete a broader workflow. Agentic autonomy is the degree to which a system can plan and execute actions without a human explicitly authorizing each step. It’s a spectrum rather than a binary. At one end, the AI drafts and a human approves every action. At the other, the AI operates within broad guardrails and only escalates exceptions. The further an organization moves along that spectrum, the less its exposure looks like software risk and the more it looks like delegated authority risk, the kind normally reserved for employees, contractors, and automated financial systems. Why Existing Risk Registers Miss Agentic AI Risks Most enterprise risk registers were built on a reasonably safe assumption: a human initiates consequential actions, and the technology around that human behaves deterministically. Agentic AI breaks both halves of that assumption at once. A few specific gaps show up quickly when organizations try to map agentic deployments onto existing categories. Operational risk registers assume process failures come from human error or system outages, not from a system independently choosing an unanticipated path to a stated goal. Cybersecurity risk registers are built around unauthorized external access, while an agent problem usually involves an authorized system taking unauthorized internal actions with its own legitimate credentials. Model risk frameworks, borrowed largely from financial services, evaluate output accuracy rather than action consequences, which matters most when those actions can’t be reversed. And third-party risk assessments treat vendors as static entities, not as autonomous agents that might invoke other vendors’ agents on your behalf. See our guide to the NIST AI Risk Management Framework for how output-focused frameworks are structured. The result is a governance blind spot. An organization can be compliant against its AI policy, its cybersecurity policy, and its vendor risk policy, and still have nobody accountable for the specific risk of a system initiating a harmful sequence of actions before anyone notices. Defining Agentic Autonomy Risk Agentic Autonomy Risk is the risk that an AI system, operating with delegated decision-making and execution authority, takes actions that are harmful, non-compliant, or misaligned with organizational intent before adequate human oversight can intervene. Those actions might happen independently or in coordination with other agents. It deserves standing as a named category alongside cybersecurity, operational, legal, financial, and third-party risk because the loss event itself is different. The harm is a completed action in a live system, and it may be difficult or impossible to reverse. The accountability structure is different too: when an orchestrating agent delegates to sub-agents, responsibility for the outcome gets distributed in ways existing ownership models don’t cleanly capture. So is the detection window. Traditional controls assume a human is positioned to catch an error before it compounds, but an agent can execute dozens of dependent actions faster than any human review cycle. 7 Agentic AI Risk Scenarios to Put on Your Register 1. Unauthorized autonomous decision-making. An agent takes an action within its technical permissions but outside its intended business mandate. It adjusts pricing, approves a refund, or modifies a customer record, and no policy ever explicitly authorized that scenario. 2. Goal misalignment. The agent optimizes for a literal interpretation of its objective in a way that diverges from actual business intent, particularly under ambiguous or adversarial inputs. 3. Multi-agent interactions and cascading failures. One agent’s flawed output becomes another agent’s trusted input. A single error can propagate across a chain of agents faster than anyone can detect it, amplifying the original mistake instead of containing it. 4. Excessive tool or system permissions. Agents get provisioned with broad, standing access “to be safe” rather than scoped, least-privilege access tied to specific tasks. A productivity tool quietly becomes a privilege-escalation path. 5. Regulatory non-compliance. Autonomous actions trigger obligations under data protection, financial services, employment, or sector-specific regulation, and they execute without the compliance review a human-initiated process would normally receive. 6. Explainability and accountability gaps. An autonomous action causes harm and the organization can’t clearly reconstruct why the agent chose that path, or establish whether the business owner, the AI governance function, or the vendor is accountable for the outcome. 7. Autonomous third-party actions. A vendor’s agent, integrated into your environment, takes action on your behalf, or your agent acts against a

A SOC 2 penetration test costs between $1,000 and $30,000 for most companies. A typical SaaS scope, meaning one web application, its API layer, and the cloud infrastructure behind it, usually lands between $2,000 and $20,000. Early-stage startups with a narrow scope can get an auditor-accepted test for $1,000 to $8,000, while enterprises with multiple products and hybrid infrastructure regularly spend $20,000 to $50,000 or more. The spread is wide because “penetration test” covers everything from an automated scan with a cover page to weeks of manual testing by senior engineers. Auditors know the difference, and so do the enterprise customers who asked for your SOC 2 report in the first place. This guide breaks down what drives the price, where the hidden costs sit, and how to buy a test that holds up in fieldwork without overpaying for it. What Is SOC 2 Penetration Testing?​ A SOC 2 penetration test is a simulated attack on your systems, performed by a qualified security professional, scoped to the environment covered by your SOC 2 report. The tester tries to exploit real weaknesses the way an attacker would: broken access controls, injection flaws, misconfigured cloud services, exposed credentials. The output is a report your auditor reads as evidence that your security controls work in practice, not only on paper. That last part matters. A pentest bought for SOC 2 has a second audience beyond your security team. If the report doesn’t map findings to your audit scope, document its methodology, and show remediation, it fails the job you bought it for. We cover the full deliverable in our guide to what a SOC 2-ready VAPT report includes. How Penetration Testing Fits Into SOC 2 Compliance​ SOC 2 is built on the AICPA’s Trust Services Criteria, and the Security category (the Common Criteria) applies to every report. Penetration testing is the standard way to satisfy CC7.1, which expects you to detect and monitor for new vulnerabilities, and it supports CC4.1, which covers ongoing evaluations of whether controls actually function. The AICPA’s points of focus explicitly mention vulnerability scanning and penetration testing as examples of how companies meet these criteria. In practice, the test slots into your audit timeline as an evidence item. Your auditor will ask for the report, check the test date against the audit period, and review how you handled the findings. Remediation is often scrutinized harder than the test itself, because it shows whether your vulnerability management process runs or merely exists. Is Penetration Testing Required for SOC 2?​ Strictly speaking, no. The Trust Services Criteria never use the word “mandatory” about penetration testing. You could theoretically satisfy CC7.1 with vulnerability scanning and strong monitoring alone. In reality, almost every auditor expects one, and skipping it invites two problems. First, your auditor may push back during fieldwork or add exceptions to the report. Second, the enterprise buyers reviewing your SOC 2 report increasingly look for pentest evidence specifically, and a report without it raises questions during procurement. Treat the test as effectively required and budget for it from the start of your SOC 2 compliance checklist. How Much Does SOC 2 Penetration Testing Cost? Typical Price Range for SOC 2 Pen Testing Most companies pay $1,000 to $30,000, with the median engagement for a SaaS business sitting around $12,000 to $15,000. Compliance-focused tests at the lower end of the market start around $1,000 to $5,000. Deep manual testing from established firms runs $10,000 to $30,000. Anything quoted below roughly $3,000 is almost certainly automated scanning packaged as a pentest, which auditors are getting better at spotting. Cost by Company Size (Startup, SMB, Enterprise) Company size is a proxy, not the driver. A 15-person company with three products and a legacy on-prem component will pay more than a 200-person company with one tightly scoped SaaS platform. Testers price effort, and effort follows scope. Cost by Test Type (Network, Web App, API, Cloud, Internal/External) Most SOC 2 engagements bundle two or three of these. The common package for a cloud-native SaaS company is web app plus API plus cloud configuration, which is why the $1,000 to $20,000 band comes up so often. Companies with office networks and internal systems in their audit scope add internal network testing, and the price climbs accordingly. Factors That Influence SOC 2 Penetration Testing Cost Scope and Number of Assets Tested Scope is the single biggest cost driver. Every additional application, API endpoint group, cloud account, or network segment adds testing hours. A pentest priced without a scoping call is a pentest priced on guesswork, and the guess usually favors the vendor. Complexity of Application or Infrastructure​ A simple CRUD app with two user roles tests quickly. A multi-tenant platform with role hierarchies, workflow engines, file processing, and third-party integrations takes far longer, because each of those features creates attack surface a tester has to work through manually. Authentication tiers matter especially: every distinct role needs testing for privilege escalation and cross-tenant data access. Testing Methodology (Black Box, Grey Box, White Box) Black box testing gives the tester nothing but a URL, grey box adds credentials and documentation, and white box adds source code and architecture diagrams. Grey box is the default for SOC 2 and usually the best value, since the tester spends time exploiting rather than discovering. White box costs more upfront but finds deeper issues. Black box sounds rigorous but often wastes paid hours on reconnaissance an attacker would run for free. Depth of Testing and Manual vs. Automated Approaches Automated scanning finds known vulnerability patterns. Manual testing finds business logic flaws, chained exploits, and authorization gaps that no scanner catches, and it’s the part auditors and security-literate customers actually value. The ratio of manual work to automation is the honest explanation for most price differences between two quotes covering the same scope. Tester Credentials and Firm Reputation Senior testers holding OSCP, GPEN, or CREST credentials bill higher rates, and firms with recognized methodologies charge a premium for the credibility their letterhead carries

Two compromised versions of LiteLLM sat on PyPI for roughly 40 minutes on the morning of March 24, 2026. That window was enough to capture secrets from around 434,000 CI/CD pipeline runs across nearly 2,500 organizations, including AWS, Samsung, Cisco, Salesforce, Siemens, and Deloitte. In August, researchers at CloudSEK and Hudson Rock confirmed they had obtained the raw exfiltrated data: a 153GB archive containing 433,909 files of environment variables, cloud keys, Kubernetes secrets, and API tokens harvested live from running pipelines, as covered by Help Net Security’s reporting on the credential archive. If LiteLLM runs anywhere in your stack, or you touch any AI proxy infrastructure at all, you need answers to three things: whether you were exposed, what to rotate first, and whether the rotation you did back in March actually held. That last one matters more than it sounds, because “we rotated everything” has already burned at least one very large company. How the Breach Happened The attack didn’t start with LiteLLM. On March 19, 2026, a threat group called TeamPCP compromised the build pipeline of Trivy, a vulnerability scanner half the industry runs, and pushed a poisoned release. LiteLLM’s own CI pipeline ran Trivy, so the poisoned scanner had legitimate read access to the project’s runner environment. The attackers used that to steal LiteLLM’s PyPI publishing tokens and ship two malicious releases of their own: versions 1.82.7 and 1.82.8. KICS and the Telnyx Python SDK got hit in the same campaign. The payload design is the part worth studying. The malicious package dropped a .pth startup hook into site-packages, so the code ran the moment any Python interpreter started on the machine, whether or not anything imported LiteLLM. From there it harvested environment variables, read local credential files like .aws/credentials and .kube/config, tried to move laterally across Kubernetes clusters, and installed a systemd backdoor dressed up as a generic telemetry service. InfoQ’s coverage of the PyPI compromise put downloads of the compromised release above 40,000. For scale, LiteLLM normally gets downloaded around 3 million times a day. The exfiltration had a nasty fallback, too. According to CloudSEK, stolen data was encrypted and sent to a typosquatted domain, and when that failed, the malware created a public repository inside the victim’s own GitHub account and uploaded the loot as a release asset. Some companies were publishing their own secrets to the open internet and had no idea. Worth Knowing: The malicious code only existed in the PyPI artifacts. The GitHub source repository stayed clean the whole time, so a developer reviewing the code on GitHub saw nothing wrong. Source review isn’t artifact verification. If you don’t check that what the registry serves matches the upstream source, this class of attack is invisible to you. How to Check If You Were Exposed Three checks, from quickest to most involved. 1. Confirm whether the compromised versions ever ran The malicious versions went live on PyPI at 10:39 UTC on March 24, 2026 and got quarantined about 40 minutes later. The project’s advice: treat any install from that day before 16:00 UTC as suspect. Search your lockfiles, pip caches, SBOMs, and container image histories for 1.82.7 and 1.82.8. And check your internal artifact mirrors. An Artifactory or Nexus proxy that cached the bad release in March can keep serving it internally long after PyPI pulled it. Keep the .pth mechanism in mind when you scope this. The question isn’t “which applications import LiteLLM,” it’s “which machines had the package installed at all,” because every Python process on an infected machine triggered the payload. 2. Hunt for persistence Rotation is pointless if the attacker still has a foothold. Check developer machines, CI runners, and containers for unauthorized .pth files in site-packages and for suspicious systemd units, especially anything posing as a system telemetry service. And review activity from March 24 onward, not just the 40-minute window. Persistence is there so the access outlives the infection. Pro Tip: Don’t limit the persistence hunt to live machines. Base container images rebuilt in late March may have baked the payload into every image derived from them since. Scan your image registry for the affected LiteLLM versions and for unexpected .pth files, then trace which running workloads came from flagged images. 3. Check whether your secrets are in the dump Hudson Rock has published a domain lookup tool and is running ethical disclosures for affected organizations, and CloudSEK maintains a high-confidence victim list. Use them, but know their limits. Attribution in this dataset is genuinely hard. One dump with a siriusxm.com committer email actually traced, through its self-hosted GitLab endpoints, to AdsWizz, a SiriusXM subsidiary. And a large share of the dumps are generic pipeline configurations with no identifying domain, email, or server name at all. Absence from a victim list is not evidence of absence. If your pipelines ran the compromised versions, assume exposure no matter what a lookup tool tells you. What to Rotate, in What Order The guidance from both research teams is blunt: treat every secret the LiteLLM environment could reach as compromised. That covers secrets on disk, in memory, injected into CI jobs, and anything retrievable through instance metadata services. Work down by blast radius: Priority Credential type Why it comes first 1 Cloud IAM keys (AWS, GCP, Azure) Direct control of infrastructure, data stores, and billing. This is where attackers monetize fastest. 2 GitHub and GitLab PATs, package publishing tokens These let an attacker poison your releases and turn your company into the next link in the supply chain. 3 Kubernetes service account tokens and kubeconfigs Lateral movement across clusters was built into the payload, not a theoretical risk. 4 Database passwords and third-party API keys Dumped in plain text in the archive, often with no attribution, so nobody will warn you they leaked. 5 AI provider API keys Billing abuse, quota theft, and access to whatever data flows through your LLM routing layer. One word matters more than the rest of this article: revoke, don’t just rotate. That