Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  /

  / Personal Data Protection Law in Bahrain, UAE, and Saudi Arabia

Personal Data Protection Law in Bahrain, UAE, and Saudi Arabia

Three Gulf states now run three different data protection regimes.

Saudi Arabia’s regulator has already issued dozens of enforcement decisions. Bahrain has had a working statute since 2019, and the UAE has a federal law on the books but is still waiting on the executive regulations that will give it teeth. For any company operating across the region, the practical question is no longer whether these laws apply but how far apart they sit, and where compliance built for one falls short of another.

This is a structured comparison of the personal data protection laws in Bahrain, UAE, and Saudi Arabia: what each one demands, where they converge on familiar GDPR principles, and the specific points where treating them as interchangeable will get you fined.

Personal Data Protection Law in Bahrain, UAE, and Saudi Arabia

The Three Laws at a Glance

Bahrain moved first. Law No. 30 of 2018, the Personal Data Protection Law (PDPL), came into force on August 1, 2019, making it the first comprehensive standalone data protection statute in the Gulf Cooperation Council. It is supplemented by ten ministerial resolutions issued in 2022 that cover transfers, security measures, and notification procedures.

The UAE followed with Federal Decree-Law No. 45 of 2021, effective January 2, 2022 — the country’s first federally applicable, GDPR-style law, issued alongside Federal Decree-Law No. 44 of 2021, which created the UAE Data Office as the federal regulator. The catch is that the executive regulations meant to flesh out timelines and penalties have still not been published, which leaves parts of the regime in a holding pattern.

Saudi Arabia’s Personal Data Protection Law, issued by Royal Decree M/19 in September 2021 and amended in March 2023, is the strictest and the most actively enforced of the three. It came into force on September 14, 2023, and a one-year grace period ended on September 14, 2024. Since then, every organization processing the personal data of people in the Kingdom has been fully on the hook.

Worth knowing: Saudi Arabia's PDPL

Saudi Arabia's PDPL protects a person's data not only during their lifetime but after death. That post-mortem protection is unusual among global privacy laws and means retention and disclosure decisions cannot assume an individual's rights simply lapse when they die.

Who the Laws Actually Reach

All three statutes reach beyond their own borders. Bahrain’s PDPL applies to anyone residing or doing business in Bahrain, and to entities outside the country that process personal data using equipment located inside it. The UAE law applies to the processing of data belonging to people in the UAE, regardless of where the controller or processor is based. Saudi Arabia goes furthest, applying to any entity inside or outside the Kingdom that processes the personal data of Saudi residents — a scope that pulls in international businesses that may never have considered themselves subject to Gulf regulation.

The big structural difference is the UAE’s free zones. The federal PDPL does not apply inside zones that maintain their own data protection regimes, most notably the Dubai International Finance Centre (DIFC) and the Abu Dhabi Global Market (ADGM), each of which runs its own established framework. A company in the DIFC answers to DIFC rules, not the federal law. That carve-out has no equivalent in Bahrain or Saudi Arabia, and it matters enormously for regional structuring decisions.

Ready for GCC data privacy compliance?

Talk to our experts and simplify Bahrain, UAE, and Saudi data privacy compliance.

The Regulators

Each country has its own supervisory authority, and they are at very different stages of maturity. Bahrain’s Personal Data Protection Authority (PDPA) operates under the Ministry of Justice, Islamic Affairs and Waqf and has full investigation, audit, and penalty powers. SDAIA — the Saudi Data and Artificial Intelligence Authority — is the current regulator in Saudi Arabia, with long-term supervision potentially moving to the National Data Management Office under the Kingdom’s wider data governance framework. SDAIA is visibly active: its enforcement committees issued 48 decisions confirming PDPL violations across the 2025 and 2026 review cycles, a level of regulatory output that should get the attention of any compliance team operating in the region.

The UAE is the outlier. The UAE Data Office exists in law but is not yet fully operational, and the Telecommunications and Digital Government Regulatory Authority was tasked with providing administrative support during the office’s early years. In practice this means data subjects in the UAE currently lack a clear federal route to lodge a complaint, and enforcement guidance is still maturing. That ambiguity cuts both ways: it reduces immediate enforcement risk, but it also makes it harder to know exactly what compliance looks like.

PDPL Bahrain UAE Saudi Arabia

Lawful Basis, Consent, and Core Principles

Consent sits at the center of all three regimes, but Bahrain leans on it hardest. Bahrain’s PDPL sets a default rule that personal data may not be processed without the data subject’s written and explicit consent, with a narrow set of alternative bases such as contract performance, legal obligation, and vital interests. Saudi Arabia and the UAE both recognize consent alongside other grounds, and Saudi Arabia’s amended law added legitimate interest as a basis — though it cannot be used for sensitive data and controllers are warned against treating consent as a convenient fallback when a more specific ground applies.

Beneath the lawful-basis question, the three laws share the principles that anyone familiar with the same GDPR-shaped foundation will recognize: lawfulness, fairness and transparency, purpose limitation, data minimization, accuracy, storage limitation, and security. The vocabulary and structure track the European model closely, and deliberately so. That means a mature GDPR program is a strong starting point, not a finished one — the architecture transfers, but the local rules introduce enough variation to demand dedicated attention.

 

Data Subject Rights

The rights packages are broadly similar across the three jurisdictions, but the enforcement emphasis differs. Individuals in all three countries can access their data, request correction, and object to certain processing. Saudi Arabia’s PDPL spells out the most comprehensive set — including access, correction, deletion, objection, and portability — and SDAIA has flagged failure to honor these requests as one of its most common enforcement findings, which means it is not a theoretical obligation. Bahrain grants access, correction, and a specific right to object to direct marketing such as behavioral targeting and SMS or email advertising. The UAE law likewise provides for access, correction, erasure, restriction, portability, and objection, though the procedural mechanics depend in part on the awaited executive regulations.

For organizations receiving high volumes of data subject requests across all three markets, the practical challenge is building workflows that satisfy each regime’s specific framing — not just a single generic process dressed up in three languages.

 

Registration, DPO, and Record-Keeping

This is where the day-to-day compliance burden diverges most visibly. Bahrain requires controllers to submit prior notifications or authorization requests to the PDPA for certain processing activities, and it maintains a register of accredited data protection officers — referred to in the law as Data Protection Guardians. Saudi Arabia requires controllers to register on the National Data Governance Platform, maintain records of processing activities, and appoint a DPO where they carry out large-scale or sensitive processing, per SDAIA’s dedicated rules on the role. The UAE requires the appointment of a DPO in defined circumstances and the keeping of processing records, with detail again deferred to the pending regulations.

Insider note: Bahrain quietly solved a problem the other two have not. Its adequacy list under Resolution 42/2022 includes all other GCC states, so transfers from Bahrain to Saudi Arabia, the UAE, Qatar, Kuwait, and Oman proceed without prior PDPA authorization. For a regional operation, routing certain intra-Gulf data flows through a Bahrain entity can remove an approval step that Saudi Arabia’s regime would otherwise require.

 

Cross-Border Transfers

Transfer rules are where the three laws feel least alike in practice. Bahrain prohibits transfers outside the Kingdom without the data subject’s specific consent unless the destination appears on a ministerial whitelist or a special authorization is issued — and as noted above, the whitelist already covers the rest of the GCC. Saudi Arabia restricts transfers under Article 29, permitting them only to countries SDAIA deems adequate or under explicit authorization; SDAIA issued standard contractual clauses and dedicated transfer regulations in September 2024 to provide compliant mechanisms for transfers that cannot rely on adequacy. The UAE law also restricts transfers to jurisdictions with adequate protection or under prescribed safeguards, with the specifics once more tied to the pending regulations.

The practical implication is that a single transfer mechanism — whether that is an SCC, a whitelist reliance, or a consent capture — will not work uniformly across all three. Each transfer route needs to be mapped and validated against the rules of the specific originating jurisdiction.

 

Breach Notification

This is the single clearest divergence across the three regimes, and the one most likely to trip up a unified incident response policy. Saudi Arabia imposes a hard deadline: controllers must notify SDAIA within 72 hours of becoming aware of a breach that poses a risk to data or data subjects, and must inform affected individuals without undue delay where the risk is serious. The UAE PDPL requires notification to the Data Office once a controller becomes aware of a breach, but a precise statutory timeline awaits the executive regulations, leaving the practical standard somewhat open. Bahrain does not set a single fixed general deadline equivalent to Saudi Arabia’s 72-hour rule, handling notification instead through its ministerial procedures — though failure to notify where required carries its own penalty.

Pro tip: Build your Incident Response

Build your incident response plan to the Saudi standard and apply it everywhere. A documented 72-hour clock with predefined breach-classification criteria and clear internal ownership satisfies the strictest regime in the region, and it gives you a defensible process in the UAE and Bahrain even while their procedural detail keeps shifting.

Penalties

The financial exposure differs by an order of magnitude across the three. Bahrain’s penalties top out at BHD 20,000 for serious violations such as processing without a lawful basis or unauthorized cross-border transfers, with failure to notify a breach drawing fines up to BHD 10,000, and imprisonment available for certain offenses. Saudi Arabia carries the heaviest sanctions: general violations attract fines up to SAR 5 million, doubled for repeat offenses, while disclosing or publishing sensitive personal data with intent to harm can bring imprisonment of up to two years and a fine of up to SAR 3 million. The UAE’s penalty structure is set to be defined in the executive regulations, and commentary widely anticipates administrative fines in the range of AED 50,000 to AED 5 million.

The gap between Bahrain’s ceiling and Saudi Arabia’s is not marginal — it reflects a deliberate regulatory choice to make non-compliance genuinely expensive. For large organizations, the reputational and operational consequences of an enforcement action in any of the three markets are likely to exceed the fines themselves, but the Saudi penalty structure removes any temptation to treat compliance as a low-stakes calculation.

Comparison of Major Provisions

Provision

Bahrain

UAE

Saudi Arabia

Legislation

PDPL, Law No. 30 of 2018

Federal Decree-Law No. 45 of 2021

PDPL, Royal Decree M/19 (2021, amended 2023)

In force

August 1, 2019

January 2, 2022

September 14, 2023

Regulator

Personal Data Protection Authority (PDPA)

UAE Data Office (not yet fully operational)

SDAIA

Default lawful basis

Explicit written consent

Consent plus alternatives

Consent plus alternatives including legitimate interest (non-sensitive)

Breach notification deadline

No single fixed deadline; ministerial procedures apply

Prompt notification; precise timeline pending regulations

72 hours to SDAIA; individuals notified without undue delay

Cross-border transfers

Whitelist (covers GCC) or consent or authorization

Adequacy or safeguards; detail pending regulations

SDAIA adequacy or SCCs or authorization

DPO requirement

Accredited Data Protection Guardian; mandatory for licensed financial institutions

Required in defined circumstances; detail pending regulations

Required for large-scale or sensitive processing

Maximum fine

BHD 20,000

Anticipated AED 50,000–5 million (pending regulations)

SAR 5 million (doubled for repeat offenses)

Free-zone carve-out

None

Yes — DIFC and ADGM operate separate regimes

None

Post-mortem data protection

No equivalent provision

No equivalent provision

Yes — rights extend beyond the data subject’s death

Building One Program Across Three Jurisdictions

The temptation is to pick the strictest law, comply with it, and assume the rest follow. That instinct is broadly right but incomplete. Saudi Arabia is the high-water mark on enforcement, breach timing, and penalties, so building to its 72-hour notification rule, registration requirements, and DPO expectations covers a great deal of ground. What it does not cover is the structural quirks: Bahrain’s consent-first default and whitelist transfer mechanism, and the UAE’s free-zone carve-out that may put part of your operation under DIFC or ADGM rules entirely.

A workable approach starts with a multi-jurisdictional gap assessment that maps where personal data actually flows between the three countries and out of the region. From there, a unified framework should adopt the strictest common requirement as the baseline, then layer country-specific controls on top: a Bahrain whitelist check before intra-GCC routing, a DIFC or ADGM determination for any UAE entity, and SDAIA registration and SCC mechanics for Saudi transfers. Vendor contracts need processor clauses that satisfy all three, and staff handling data in any of the markets need training that reflects local rules rather than a single generic module. The frameworks rhyme, but the details bite.

Underpinning all of this is a documentation and accountability structure that can demonstrate compliance to three different regulators with three different priorities. ISO 27001 certification provides a strong technical and organizational security baseline that is recognized across the region and maps naturally onto the security obligations in all three laws — it will not substitute for legal compliance, but it gives regulators and counterparties something concrete to point to, and it structures the internal controls that make compliance sustainable rather than reactive.

Ready for GCC data privacy compliance?

Talk to our experts and simplify Bahrain, UAE, and Saudi data privacy compliance.

The Bottom Line

Bahrain, the UAE, and Saudi Arabia have each built data protection laws on the same GDPR-shaped foundation, which makes a single coherent program achievable. The risk lies in the gaps between them: Saudi Arabia enforcing hard today, the UAE still waiting on the regulations that will define its edges, and Bahrain running its own consent and transfer logic. Treat the strictest regime as your floor, then account for the structural differences each country adds, and you have a defensible position across all three. Treat them as one law, and you will be compliant with none of them.

Frequently Asked Questions

Which is stricter: Bahrain, UAE, or Saudi Arabia's data protection law?

Saudi Arabia’s PDPL is the strictest in practice. It is fully enforced, carries the highest penalties, imposes a firm 72-hour breach notification deadline, and is backed by an active regulator that has already issued dozens of enforcement decisions. Bahrain has a mature and functioning regime, while the UAE is still developing the executive regulations that will complete its framework.

Yes. All three have extraterritorial reach. A company anywhere in the world that processes the personal data of people in Saudi Arabia, the UAE, or Bahrain can fall within scope, particularly if it offers goods or services to, or monitors the behavior of, individuals in those countries. The extraterritorial logic mirrors the GDPR’s Article 3 approach and should be taken seriously by any organization with Gulf-based customers or users.

No, but it is central, and Bahrain in particular treats explicit written consent as the default. All three laws recognize alternative bases such as contract performance, legal obligation, and vital interests, and Saudi Arabia’s amended law also allows legitimate interest for non-sensitive data. Controllers should identify the most appropriate lawful basis for each processing activity rather than defaulting to consent across the board.

They share the GDPR’s core architecture: lawful bases, data subject rights, breach notification, accountability, and transfer restrictions. The main differences are substantially lower maximum fines in Bahrain, the use of regulator-issued adequacy decisions and authorization mechanisms for transfers rather than the EU’s adequacy framework, and varying degrees of enforcement maturity across the three regulators.

Not universally. Saudi Arabia and the UAE require a DPO in defined circumstances, typically large-scale or sensitive processing. Bahrain maintains a register of accredited Data Protection Guardians, and recent financial-sector directives have made appointment mandatory for licensed institutions. Organizations operating across all three markets should assess the DPO requirement independently in each jurisdiction rather than applying a single determination.

Not automatically, but Bahrain makes it easier than the others. Bahrain’s adequacy list covers the other GCC states, so transfers from Bahrain into the region avoid prior authorization. Transfers out of Saudi Arabia still require SDAIA adequacy determination, SCCs, or specific authorization. UAE transfers depend on safeguards detailed in its pending regulations. For now, Bahrain’s whitelist mechanism is the most streamlined intra-GCC transfer route available.

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