Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  / ,

  / ISO 27001 & GDPR: Why Certification Isn’t Compliance

ISO 27001 & GDPR: Why Certification Isn’t Compliance

Plenty of companies treat an ISO 27001 certificate as proof of GDPR compliance. It is not. The two frameworks overlap heavily, but they answer different questions, and the gap between them is exactly where regulators tend to look.

ISO 27001 tells you how to build a defensible security program.

GDPR tells you what the law expects when that program touches personal data.

Run one without understanding the other, and you will either over-engineer security you do not strictly need, or miss privacy obligations that carry real financial exposure.

This article maps where ISO 27001 and GDPR meet, where they part ways, and how to run them as a single coordinated effort rather than two competing projects.

ISO 27001 and GDPR

What Is ISO 27001?

ISO/IEC 27001 is the international standard for an Information Security Management System, or ISMS. The current edition is ISO 27001:2022. It is not a checklist of technical fixes. It is a management framework: a structured, repeatable way to identify information security risks, decide how to treat them, document those decisions, and improve over time.

Clauses 4 to 10 of the standard define the mandatory ISMS requirements, covering leadership, risk assessment, internal audit, and management review. Annex A then lists 93 controls grouped into four themes: organisational, people, physical, and technological.

You do not implement all 93 by default. You select the controls that address your assessed risks and justify your choices in a document called the Statement of Applicability. Certification against ISO 27001 is voluntary and is granted by an accredited third-party body after an audit.

What Is GDPR?

The General Data Protection Regulation is European Union law. It has been applied since 25 May 2018, and it applies to any organisation that processes the personal data of people in the EU, wherever that organisation is based.

GDPR is fundamentally about the rights of individuals, not just the security of data. It grants people rights over their personal data, including access, correction, erasure and portability. It places obligations on the organisations that decide how data is used (controllers) and those that process it on their behalf (processors).

It requires a lawful basis for every processing activity, mandates breach notification, and demands transparency about what happens to people’s information. You do not implement GDPR and receive a certificate. You obey it, and a regulator decides whether you have.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

Key Differences Between ISO 27001 and GDPR

Scope and Purpose

ISO 27001 protects all information assets an organisation holds: intellectual property, financial records, operational data, source code and, yes, personal data. Its purpose is the confidentiality, integrity and availability of information in general. GDPR is narrower in one sense and broader in another. It covers only personal data of individuals in the EU, but it protects the person behind the data, not merely the data itself. A system can be flawlessly secure and still violate GDPR.

Legal Obligation vs. Voluntary Certification

This is the difference that catches people out. GDPR is binding law. If you process EU personal data, compliance is not optional, and there is no opting out. ISO 27001 is a voluntary standard. Organisations pursue it for assurance, for competitive advantage, and because customers increasingly demand it. Crucially, there is no such thing as a GDPR certificate. Regulators assess compliance through investigation and enforcement, not through a badge you can display.

Penalties for Non-Compliance

GDPR fines run on two tiers under Article 83. Less severe infringements — such as failures around records of processing or breach notification — can reach €10 million or 2% of global annual turnover, whichever is higher. The more serious tier, covering breaches of the core processing principles and data subject rights, can reach €20 million or 4% of global annual turnover. Failing an ISO 27001 audit carries no legal fine at all. The consequence is commercial: you do not get the certificate, or you lose it, and that can cost you contracts.

How ISO 27001 and GDPR Align

Despite their different purposes, the two frameworks were built on compatible logic, which is why running them together works.

Both treat information security as central.

GDPR Article 32 requires “appropriate technical and organisational measures” to secure personal data. That phrasing is almost a direct description of what an ISO 27001 ISMS produces. The controls an organisation selects for confidentiality and access already serve the regulation’s security expectations.

Both are risk-based.

ISO 27001 starts every control decision from a risk assessment. GDPR expects the same proportionality: the measures you apply should match the sensitivity of the data and the likelihood and severity of harm. One risk methodology can serve both, provided you assess personal data processing risks alongside broader security risks.

Both demand incident response.

ISO 27001’s incident management controls require organisations to detect, assess and respond to security events. GDPR Article 33 requires notifying the supervisory authority of a personal data breach within 72 hours of becoming aware of it. The ISO process is the engine that makes the GDPR deadline achievable.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

How ISO 27001 Can Help You Comply With GDPR

Four areas of an ISMS do direct, practical work toward GDPR compliance.

Asset management.

ISO 27001 requires an inventory of information and associated assets, with owners assigned. You cannot protect personal data, respond to access requests, or maintain records of processing if you do not know where that data lives. The asset inventory is the foundation for both frameworks.

Access control.

Identity management, privileged access controls and the principle of least privilege limit who can see personal data. That directly supports the GDPR requirement to ensure confidentiality and to prevent unauthorised access.

Operational security.

Logging, malware protection, backup and secure configuration keep personal data accurate, available and resistant to compromise. These map cleanly onto the integrity and availability expectations in Article 32. Techniques such as data masking for GDPR and ISO 27001 also sit within this space, reducing exposure without sacrificing operational utility.

Incident management.

A defined process for detecting and handling security events gives you the evidence trail and the response capability you need to meet breach notification obligations and to demonstrate you took the breach seriously.

 

Does ISO 27001 Certification Mean You Are GDPR Compliant?

No. This is the single most expensive misconception in this area. ISO 27001 builds strong security, and security is one part of GDPR.

It does not address lawful basis for processing, consent management, transparency notices, the handling of data subject rights such as access and erasure, data protection impact assessments, the appointment of a Data Protection Officer where required, or the legal mechanisms for transferring data outside the EU.

A certified ISMS can sit on top of processing that is entirely unlawful. It is also one of the most common pitfalls organisations encounter with ISO 27001 — assuming the certificate does more than it actually does.

 

GDPR Principles and How ISO 27001 Supports Them

Article 5 of GDPR sets out seven principles for processing personal data. Looking at each one shows precisely where ISO 27001 carries weight and where it leaves you exposed.

Lawfulness, fairness and transparency requires a valid legal basis for processing and clear communication with individuals about it. ISO 27001 barely touches this. It is almost entirely privacy work.

Purpose limitation means data collected for one purpose should not be repurposed incompatibly. ISO 27001 does not govern why you collect data, so it offers little here.

Data minimisation calls for collecting only what you need. ISO 27001 will secure whatever you hold, but it does not tell you to hold less. The principle is a privacy and design decision.

Accuracy requires personal data to be correct and current. ISO 27001’s integrity controls help protect data from unauthorised alteration — partial support — though data quality processes themselves sit outside the standard.

Storage limitation means not keeping data longer than necessary. ISO 27001 provides retention and secure deletion controls that operationalise a retention schedule, but deciding the actual retention period is a legal call.

Integrity and confidentiality — the security principle — is where ISO 27001 is at its strongest. The overlap with Article 32 is near-total. An ISMS is, in effect, a delivery mechanism for this principle.

Accountability requires you to demonstrate compliance, not just achieve it. Here, ISO 27001 is genuinely powerful: its documented policies, risk registers, internal audits and management reviews produce exactly the kind of evidence the accountability principle demands.

The pattern is clear. ISO 27001 supports the last two principles strongly and the rest partially or barely. Everything that is distinctly about privacy still needs dedicated work.

Control Mapping: ISO 27001 Annex A vs. GDPR

GDPR states what you must achieve. ISO 27001 Annex A offers a practical set of controls for how to achieve the security-related parts of it. The table below maps common GDPR requirements to the ISO 27001 controls that support them.

GDPR Requirement

Relevant ISO 27001 Annex A Controls

Coverage

Article 32 — Security of processingA.8.1 User endpoint devices, A.8.3 Information access restriction, A.8.5 Secure authentication, A.8.24 Use of cryptographyStrong
Article 33 — Breach notification (72-hour rule)A.5.24 Information security incident management planning, A.5.25 Assessment of information security events, A.5.26 Response to information security incidentsStrong
Article 30 — Records of processing activitiesA.5.9 Inventory of information and other associated assets, A.5.10 Acceptable use of informationPartial
Article 25 — Data protection by design and by defaultA.8.25 Secure development life cycle, A.8.27 Secure system architecture and engineering principlesPartial
Article 28 — Processor obligationsA.5.19 Information security in supplier relationships, A.5.20 Addressing information security within supplier agreementsPartial
Article 17 — Right to erasureA.8.10 Information deletionPartial
Article 6 — Lawful basis for processingNone directly applicableNot covered
Articles 13–14 — Transparency and privacy noticesNone directly applicableNot covered
Article 35 — Data protection impact assessmentNone directly applicable (risk assessment methodology can inform a DPIA)Not covered

A mapping like this is worth building for your own environment. It shows teams which work serves both objectives and prevents the duplication that comes from treating the two programmes as unrelated. An ISO 27001 gap analysis is the natural starting point: it tells you where your ISMS controls already satisfy GDPR expectations and where the gaps are large enough to require separate privacy work.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

Why Technical Measures Alone Are Not Enough for GDPR Compliance

Article 32 deliberately requires technical “and organisational” measures. The wording is not decorative. Encryption, firewalls and access controls reduce the risk of a breach, but they say nothing about whether you had the right to process the data in the first place.

Consider a system protected to the highest technical standard that processes personal data with no lawful basis, sends no transparency notice, and ignores erasure requests. Every security control could pass an audit, while the processing remains unlawful from the first record.

GDPR compliance is a governance, legal and operational discipline as much as a technical one. ISO 27001 strengthens one pillar of it. It does not replace the others.

 

Why You Need Both ISO 27001 and GDPR Compliance

Time and Cost Savings by Pursuing Both Together

Organisations that treat ISO 27001 and GDPR as separate, unconnected projects end up paying twice. They run two risk assessments, write two overlapping sets of policies, deliver two training programmes and maintain two toolsets. Treated together, the shared elements are done once. A single risk assessment can cover personal data processing risks and broader security risks.

Encryption, access management and logging serve certification and compliance simultaneously. The marginal cost of addressing both at once is far lower than tackling them in isolation. If you are still scoping out where to start, gap analysis services can give you a clear picture of what already maps across and what still needs attention.

Building Trust With Customers and Partners

ISO 27001 certification is recognised globally and shortens vendor due diligence: a procurement team that sees the certificate can move faster. GDPR compliance, meanwhile, is effectively table stakes for doing business involving EU data, and customers increasingly ask for evidence of it directly.

Holding both signals a mature, deliberate approach to managing information and privacy. It tells partners you treat data protection as a discipline rather than a box to tick. According to Gartner research, only a minority of customers believe organisations will handle their personal data responsibly without being asked — demonstrable compliance changes that calculation.

 

How to Integrate ISO 27001 and GDPR Compliance

There are three workable approaches to organising the documentation when you run both programmes.

A fully unified system merges all policies, risk registers and evidence into a single management system. This works well for smaller organisations where the security and privacy functions are not sharply separated, but it can become unwieldy as the business grows, since GDPR-specific items such as DPIAs and records of processing activities sit awkwardly inside an ISMS structure designed around information assets.

Completely separate systems keep the ISMS and the privacy management framework entirely independent, with their own documentation, risk registers and review cycles. This avoids confusion about ownership but creates real risk of duplication and drift — the two programmes can develop inconsistencies that neither team notices until an audit or investigation surfaces them.

An integrated but distinguishable structure treats the ISMS as the foundation and builds GDPR-specific documentation alongside it, with explicit cross-references where controls serve both. The same risk assessment methodology drives both; the same incident process feeds both breach response obligations. Privacy-specific obligations live in dedicated documents owned by the privacy function, but they are linked to the security controls that support them. For most organisations this is the pragmatic middle ground. You can also use compliance tools to manage the cross-framework evidence in a single platform, which reduces the administrative overhead considerably.

 

ISO 27701: The Privacy Extension That Bridges ISO 27001 and GDPR

If ISO 27001 covers security and GDPR covers privacy, ISO/IEC 27701 is the standard built to close the distance. It defines a Privacy Information Management System, or PIMS, and adds privacy-specific controls for organisations acting as data controllers and processors. Its annexes include a direct mapping to GDPR requirements, which makes it the closest thing to a certifiable demonstration of privacy governance.

One important development is worth knowing. ISO 27701 was first published in 2019 as an extension to ISO 27001, meaning you had to hold an ISMS before you could implement or certify it.

In October 2025, ISO published a revised edition, ISO/IEC 27701:2025, which turns it into a stand-alone standard.

Organisations can now implement and certify a privacy management system independently, without ISO 27001 as a prerequisite, with a transition deadline of October 2028 for those already certified to the 2019 version.

In practice, ISO 27701 still works best alongside ISO 27001, since privacy depends on security. It gives a structured, auditable way to address the privacy obligations that ISO 27001 leaves untouched. One caveat carries over from GDPR itself: certification to ISO 27701 supports and evidences compliance, but no certificate is a substitute for the legal assessment a regulator would make.

Frequently Asked Questions

Is ISO 27001 compliant with GDPR?

ISO 27001 is compatible with GDPR and supports many of its requirements, particularly around security of processing, access control and incident management. It is not, by itself, a complete route to GDPR compliance, because it does not address privacy-specific obligations such as lawful basis and data subject rights.

No. Certification proves you have a working information security management system. GDPR compliance additionally requires lawful basis, transparency, consent where relevant, handling of data subject rights, data protection impact assessments and lawful international transfers. A certified ISMS covers the security pillar of GDPR, not the whole regulation.

No. GDPR is European Union law, enforced by national supervisory authorities. ISO standards are voluntary frameworks published by the International Organization for Standardization. They can support legal compliance, but they are not laws and cannot replace one.

If you process personal data of individuals in the EU, GDPR compliance is legally required. ISO 27001 remains optional, but it provides the security backbone that GDPR expects and is often demanded by customers and partners. Most organisations handling EU personal data benefit from running both.

GDPR is the legal obligation, so its requirements cannot wait. In practice, building the ISMS first is efficient, because it produces much of the risk assessment and many of the “appropriate technical and organisational measures” GDPR requires. The pragmatic answer is to plan them together rather than strictly sequencing one before the other.

GDPR carries administrative fines of up to €10 million or 2% of global turnover for less severe breaches, and up to €20 million or 4% for serious ones, whichever is higher. ISO 27001 has no legal penalty. Failing an audit means losing or not obtaining the certificate, which is a commercial consequence rather than a fine.

Organisations that handle significant volumes of EU personal data and that sell to security-conscious customers gain the most. Technology and SaaS providers, healthcare and financial services firms, and any processor handling data on behalf of EU clients benefit from pairing a recognised security certification with demonstrable privacy compliance.

ISO 27701 defines a Privacy Information Management System and adds privacy controls that ISO 27001 does not cover, with a built-in mapping to GDPR requirements. It began as an extension to ISO 27001 and, since the 2025 revision, can be implemented and certified as a stand-alone standard. It is the most direct bridge between an ISO security programme and GDPR’s privacy obligations, though it still does not amount to legal certification of compliance.

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