Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  / ISO 9001:2026: Key Changes, Timeline & Transition Guide

ISO 9001:2026: Key Changes, Timeline & Transition Guide

A new version of the world’s most widely adopted quality management standard is on the way. The Draft International Standard (ISO/DIS 9001) was released on 27 August 2025, and ISO member bodies voted to approve it in December 2025. Final publication is targeted for September 2026, with a three-year transition window expected to follow. Over 1.3 million organizations worldwide currently hold ISO 9001 certification. For every one of them, understanding what is changing, and what is not, matters.

This guide covers the confirmed changes in the DIS, the full revision timeline, what the update means for currently certified organizations, and how to plan your transition. Whether you are managing an existing Quality Management System (QMS) or considering certification for the first time, this is what you need to know.

What Is ISO 9001:2026?

ISO 9001 is the international standard that defines requirements for a Quality Management System. Published by the International Organization for Standardization (ISO), it provides a framework organizations can use to consistently deliver products and services that meet customer and regulatory requirements, and to drive continual improvement. Certification to ISO 9001 is recognized in virtually every industry and country worldwide.

ISO 9001:2026 is the sixth edition of the standard. It succeeds ISO 9001:2015 and is being developed by ISO/TC 176/SC 2, the technical subcommittee responsible for quality management system standards. The revision is being drafted by Working Group 29 (WG 29), a body of international experts convened specifically for this purpose.

Why Is ISO 9001:2015 Being Revised?

ISO standards undergo a formal review cycle every five years. Member bodies assess whether a standard remains relevant, needs updating, or should be discontinued. After a 2020 user survey led the committee to confirm ISO 9001:2015 without revision, a 2023 re-evaluation by a new task force reversed that decision. The conclusion: the world had changed enough since 2015 to warrant an update.

Three broad forces are driving the revision. The first is sustainability and climate change. ISO formally amended ISO 9001:2015 in February 2024, requiring organizations to consider climate change as part of their context analysis. That amendment is now being embedded directly into the body of the 2026 standard. The second is digital transformation. Since 2015, AI, IoT, cloud computing, and remote auditing have moved from emerging technologies to standard business practice. The standard needs to reflect that reality. The third is stakeholder expectations. Customers, employees, suppliers, and communities now expect organizations to operate transparently and ethically, not just efficiently.

The revision also reflects feedback from quality practitioners globally, who found certain parts of the 2015 standard, particularly the treatment of risks and opportunities, unclear in practice.

Pro Tip: EU and UK Customers

If your EU or UK customers ask for “an ISAE 3000 report” without specifying the assurance level, clarify upfront. A limited assurance engagement involves materially less testing and a lower fee, but some enterprise buyers will only accept reasonable assurance. Getting alignment early saves weeks of rework.

Current Status of the ISO 9001:2026 Revision

Draft International Standard (DIS)

The DIS was published on 27 August 2025, marking the first time the revised text was available to ISO member bodies for formal review and ballot. The voting period closed on 4 December 2025, with member countries approving the proposal. That approval is a significant milestone: it confirms the standard will be published and locks in the broad direction of the changes, though minor editorial refinements are still possible before final publication.

The DIS itself is not freely available, but its content has been widely discussed by national body experts, certification bodies such as DNV and Intertek, and quality management organizations globally. The picture of what is changing is now clear.

Final Draft International Standard (FDIS)

Following DIS approval, the working group addresses submitted comments before preparing the Final Draft International Standard (FDIS), expected in early 2026. This is typically a near-final text, with only minor adjustments possible at this stage. Once the FDIS is approved, the standard moves directly to publication.

ISO 9001:2026 Publication and Transition Timeline

Publication is targeted for September 2026. Following publication, the International Accreditation Forum (IAF) will establish the official transition timeline and accreditation requirements for certification bodies.

Important: The IAF has not yet formally confirmed the transition period. Based on precedent with previous major revisions, a three-year window is expected. Do not finalize your planning around any specific deadline until the IAF publishes its official transition rules after the standard is published.

Key Changes in ISO 9001:2026

The DIS confirms that ISO 9001:2026 is an evolutionary update, not a rebuild. The core requirements in Clauses 4 through 10 have changed modestly. The most significant additions appear in the non-mandatory Annex A, which has been substantially expanded to provide clearer implementation guidance. For organizations currently certified to ISO 9001:2015, the transition burden is expected to be manageable.

Ethics and Integrity Within Leadership

Clause 5.1.1 now explicitly requires top management to promote and demonstrate a culture of quality and ethical behavior. Previous editions required leadership commitment to the QMS, but the 2026 version makes quality culture and ethical conduct formal leadership responsibilities,  not just implied expectations.

Clause 7.3 adds a corresponding requirement at the workforce level: employees must be aware of what quality culture and ethical behavior mean in their context. This pairs leadership obligation with organizational awareness, creating accountability at both ends of the organization.

Enhanced and Restructured Risk Management

Risk-based thinking has been part of ISO 9001 since 2015, but practitioners consistently reported that the standard did not give enough guidance on how to handle risks and opportunities differently. The 2026 revision addresses this directly.

Clause 6.1 is restructured into sub-sections: 6.1.2 for actions to address risks, and 6.1.3 for actions to address opportunities. This is not just editorial. The separation forces organizations to treat opportunity management as a distinct planning activity, not simply the positive counterpart to risk. Many organizations with mature QMS processes had already made this distinction informally,  the standard now makes it explicit.

Greater Emphasis on Stakeholder Engagement

The revision places stronger emphasis on understanding and responding to the perspectives of interested parties: customers, employees, suppliers, regulatory bodies, and the broader community. This reflects a decade of change in how organizations are expected to operate, particularly around transparency and social accountability. The requirements stop well short of making ISO 9001 an ESG standard, but the direction is clear.

Digital Transformation and Industry 4.0

The standard does not mandate specific technologies or tools. However, the 2026 revision acknowledges that quality management now routinely involves digital workflows, automated monitoring, AI-assisted analysis, and remote audit capabilities. Organizations using these tools are expected to ensure their QMS reflects and governs them appropriately. The documented information requirements in Clause 7.5 are expected to be clarified to better accommodate modern digital record-keeping,  a welcome update for organizations that have moved well beyond paper-based systems.

Sustainability, Climate Change, and Social Responsibility

ISO 9001:2026 does not attempt to replicate ISO 14001 or become an ESG framework. But sustainability concerns are more visible than in previous editions. The Climate Change Amendment of 2024, already binding on certified organizations, is formally embedded in Clause 4.1. Organizations are required to consider whether climate change is relevant to their context and to reflect that assessment in their QMS if it is.

The 2024 amendment added two short but consequential notes to Clauses 4.1 and 4.2 of ISO 9001:2015. Clause 4.1 now includes a note that relevant interested parties can have requirements related to climate change. Clause 4.2 notes that climate change can be a relevant external issue to consider. These are not requirements to act on climate change,  they are requirements to consider it. The integration of these notes into the body of ISO 9001:2026 formalizes what has already been expected since February 2024.

Pro tip: If your organization has not yet updated its context analysis (Clause 4.1) and interested party register (Clause 4.2) to reflect the 2024 Climate Change Amendment, do it now. Certification bodies are already checking for this during regularly scheduled audits,  and it is also the most straightforward part of your ISO 9001:2026 preparation.

Greater Flexibility and Simplification

One persistent criticism of ISO 9001 has been that it creates unnecessary documentation burden, particularly for smaller organizations. The 2026 revision continues the trend toward flexibility. Several clauses have been editorially revised to make requirements clearer and easier to audit, without adding new obligations. Quality objectives must be measurable, but only where practical,  a nuance that gives organizations more room to set meaningful targets in complex environments.

Improved Alignment with Other Management Systems

The Harmonized Structure introduced in 2015 aligned ISO 9001 with other management system standards. ISO 9001:2026 deepens this alignment by updating terminology and clause structure to reflect changes across the ISO management system family since 2015. Organizations running integrated management systems covering quality, environment, and occupational health and safety will find the 2026 version easier to integrate with updated editions of ISO 14001 and ISO 45001. For organizations that also manage information security, it is worth reviewing how ISO 9001 compares with and integrates with data protection frameworks.

What Isn’t Changing in ISO 9001:2026

The seven quality management principles that underpin ISO 9001 remain unchanged: customer focus, leadership, engagement of people, process approach, improvement, evidence-based decision making, and relationship management. These principles, codified in ISO 9000:2015, are the philosophical foundation of the standard and are not being revised.

The Plan-Do-Check-Act (PDCA) cycle remains the operational model. The process approach is unchanged. The High-Level Structure (HLS) is maintained, preserving compatibility with ISO 14001, ISO 27001, ISO 45001, and other management system standards. Organizations certified to ISO 9001:2015 will not need to redesign their QMS from scratch. For most, the transition will be a focused update, not a reinvention.

What ISO 9001:2026 Means for Your Organization

Impact on Currently Certified Organizations

The transition burden for currently certified organizations is expected to be low. The core requirements you implemented for ISO 9001:2015 remain valid. The changes that require active attention are the ethics and quality culture requirements in Clauses 5.1.1 and 7.3, the restructured approach to risks and opportunities in Clause 6.1, and the formal integration of the climate change considerations you should already have addressed following the 2024 amendment.

Documentation updates will be required to reflect the revised clause structure. Internal audit programs will need to be updated to check against the new requirements. Leadership briefings are worth prioritizing early, since the quality culture and ethical behavior expectations now sit explicitly at the top management level.

Impact on Organizations Not Yet Certified

For organizations that have not yet pursued ISO 9001 certification, there is no reason to wait for the 2026 edition. ISO 9001:2015, supplemented by the 2024 Climate Change Amendment, remains the current standard and is fully certifiable today. A QMS built to that standard will provide a solid foundation for the 2026 transition. Beginning the certification journey now means you gain the operational and commercial benefits of certification sooner, and your system will already be mature by the time the 2026 transition window opens.

Your Certification Is Secure Until 2029

Existing ISO 9001:2015 certificates will remain valid during the transition period. Based on precedent with the 2015 revision, organizations will have approximately three years from the date of publication to transition to the new standard. If ISO 9001:2026 is published in September 2026, the 2015 version would likely remain valid until September 2029, subject to formal IAF confirmation.

How to Prepare for the ISO 9001:2026 Transition

Conducting a Gap Analysis

A gap analysis compares your current QMS against the requirements of ISO 9001:2026. With the DIS now approved, the picture of what is changing is sufficiently clear to begin this exercise. For a detailed walkthrough of the process, the gap analysis guide provides a practical framework that translates well across management system standards. Focus particularly on how your organization currently documents quality culture, how leadership commitment to ethical behavior is demonstrated, and how your risk and opportunity planning distinguishes between the two,  these are the areas most likely to reveal gaps.

Training and Awareness

The explicit awareness requirement in the revised Clause 7.3 means that employee training programs will need updating. Quality culture and ethical behavior need to be defined in your organizational context, communicated clearly, and evidenced in training records. Leadership briefings should start early, since top management is now formally responsible for demonstrating these behaviors.

Updating Documentation

Documentation updates for the 2026 transition are primarily structural: updating clause references, revising the QMS manual or policy documents to reflect the new requirements, and ensuring records support the separated risk and opportunity planning approach. No organization should find itself rebuilding its entire documented system. The task is refinement and alignment, not reconstruction.

Internal Audits

Your internal audit programs should be updated to include the new and revised requirements once the final standard is published. Auditors will need training on the specific changes, particularly the quality culture and ethics requirements and the restructured Clause 6.1. Scheduling a focused internal audit against the 2026 requirements before your first external transition audit is strongly recommended.

Engaging Stakeholders

The stronger emphasis on interested parties in the 2026 revision means that your stakeholder register,  and the processes you use to identify and respond to their needs,  should be reviewed. This is particularly relevant for organizations operating in sectors where customer, regulatory, or community expectations around sustainability and transparency have shifted significantly since 2015.

Investing in Technology

The standard does not require any specific technology. However, organizations that still rely heavily on paper-based or legacy document control systems may find that the 2026 revision is a practical prompt to modernize. Digital QMS platforms can simplify compliance evidence, automate KPI tracking, and make the audit process significantly more efficient. Investing in these capabilities before the transition also gives you time to validate them properly.

Pro tip: Map a rough three-year transition plan from September 2026 now. Gap analysis in months 1–6, documentation and training updates in months 6–18, internal audits in months 18–24, and your transition certification audit scheduled before the September 2029 deadline. When the IAF publishes official transition rules, adjust accordingly. Starting with a plan is far better than waiting for certainty.

Action Plans for the ISO 9001:2026 Transition

For Companies Not Yet Certified

Start your ISO 9001:2015 implementation now, including the 2024 Climate Change Amendment. Do not wait for the 2026 edition,  you gain no advantage from waiting and lose time in which your QMS could be delivering operational benefit. ISO 9001 certification is available today, and a well-implemented 2015 system will make your eventual 2026 transition straightforward. Explore our certification services to understand how to get started efficiently.

For Companies Already Certified

Conduct a gap analysis against the DIS changes now. Prioritize the climate change amendment compliance check, the quality culture and ethics awareness updates, and the risk-opportunity separation review. Begin updating training materials and leadership briefings. Schedule your transition audit well in advance of the 2029 deadline to avoid the bottleneck that typically develops in the final year of any ISO transition window.

For Individuals Considering Professional Certification

ISO 9001:2015 auditor and implementer certifications remain fully valid and highly valued. Obtaining them now gives you immediate credibility in the job market while positioning you to update your knowledge when the 2026 edition is published. The changes are not extensive enough to make current qualifications obsolete.

For Individuals with Existing Professional Certification

Monitor updates from the ISO/TC 176/SC 2 committee and from your certification body or professional association. Once the final standard is published, seek formal transition training. Focus your continuing professional development on the areas of change: quality culture, ethical behavior, risk-opportunity separation, and the sustainability and digital dimensions of the 2026 update.

When Is ISO 9001:2026 Coming Out?

Publication is targeted for September 2026. The DIS was approved by ISO member bodies in December 2025, and the Final Draft International Standard (FDIS) is expected in early 2026. Barring unexpected delays, the September 2026 timeline is considered reliable.

The confirmed changes in the DIS include: formal integration of the 2024 Climate Change Amendment into Clause 4.1; a new leadership requirement for promoting quality culture and ethical behavior in Clause 5.1.1; a new employee awareness requirement on quality culture and ethics in Clause 7.3; separation of risks and opportunities into distinct sub-clauses (6.1.2 and 6.1.3); and a substantially expanded Annex A providing clearer implementation guidance. The core requirements of Clauses 4–10 remain largely unchanged.

Not immediately. Certification bodies must complete accreditation training before they can issue certificates to the new standard. This process is expected to take approximately 12 months following publication, meaning very few ISO 9001:2026 certificates will be issued before late 2027.

Your ISO 9001:2015 certificate remains valid during the transition period, expected to run until approximately September 2029. You are not required to transition before that date, though transitioning earlier avoids a last-minute rush and gives your organization more time to embed the new requirements properly.

No. ISO 9001:2015, with the 2024 Climate Change Amendment, is the current standard and remains fully certifiable. Waiting delays both certification and the operational benefits it delivers. A well-implemented 2015 QMS will require only targeted updates to transition to 2026.

For most certified organizations, the transition is expected to be manageable. The core requirements are not changing. The work involves a gap analysis, documentation updates to reflect the new clause structure, training updates for quality culture and ethics awareness, and revisions to risk and opportunity planning. It is not comparable in scope to the 2008-to-2015 transition, which required organizations to adopt an entirely new structure and philosophy.

ISO reviews all management system standards every five years. The 2023 re-evaluation concluded that changes in sustainability expectations, digital technology, and stakeholder transparency since 2015 justified a revision. The goal is to keep ISO 9001 relevant and effective as a quality management tool without disrupting the enormous installed base of certified organizations worldwide. If you want expert support navigating the transition, whether you are starting from scratch or updating an existing system, contact us to discuss how we can help.

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