Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  /

  / What Is a 3PAO? The Independent Assessor Behind FedRAMP

What Is a 3PAO? The Independent Assessor Behind FedRAMP

A 3PAO is the independent firm that decides whether a cloud service is secure enough to handle federal data. The acronym stands for Third-Party Assessment Organization, and these accredited auditors sit at the center of the FedRAMP process. A federal agency will not grant an Authority to Operate (ATO) at the Moderate or High impact level without a 3PAO assessment behind it.

That makes the 3PAO one of the most consequential vendors a cloud service provider (CSP) will hire on the road to the federal market. This guide explains what a 3PAO is, what it actually does, how a firm earns the accreditation, and when you should bring one in. It also covers how the role is changing under FedRAMP’s 2025 overhaul, because the job looks different now than it did even a year ago.

What Is a 3PAO

What Does 3PAO Stand For?

3PAO stands for Third-Party Assessment Organization. The “third party” part is the whole point. The assessor is independent of both the cloud provider being evaluated and the government agency relying on the results. That independence is what gives a 3PAO report its weight. An agency can trust the findings precisely because the assessor has no stake in the outcome.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

What Is a 3PAO?

A 3PAO is an independent firm accredited to evaluate the security of cloud services seeking authorization under FedRAMP, the Federal Risk and Authorization Management Program. The FedRAMP Program Management Office (PMO) recognizes these firms only after they pass a demanding accreditation process. Once recognized, a 3PAO is listed publicly on the FedRAMP Marketplace under the Assessors tab, where CSPs and agencies can find them.

3PAOs are not limited to federal work. The same firms are commonly authorized to perform GovRAMP assessments, the program formerly known as StateRAMP, for state and local government cloud procurement. The skill set transfers directly, since both programs lean on the same NIST control foundations.

What does a 3PAO do

What Does a 3PAO Do?

A 3PAO independently tests whether a cloud service offering (CSO) does what its documentation claims. The longer version breaks into four distinct areas:

1- Independent Security Assessments

The core deliverable is a security assessment. The 3PAO evaluates a CSP’s controls against the relevant FedRAMP baseline, which maps to NIST SP 800-53. It builds a Security Assessment Plan (SAP), executes the testing, and documents the findings in a Security Assessment Report (SAR). The SAR is the artifact an agency’s Authorizing Official reads when deciding whether to grant an ATO.

2- Documentation Review and Validation

Before any testing happens, the 3PAO reviews the System Security Plan (SSP), the primary document describing how each control is implemented. SSPs routinely run to hundreds of pages, and a vague or incomplete one will stall the schedule fast. The assessor checks that what the SSP claims matches what the system actually does, then tracks unresolved issues in a Plan of Action and Milestones (POA&M).

3- Penetration Testing

FedRAMP assessments include mandatory penetration testing, and the 3PAO performs it. The assessor probes the system the way an attacker would, looking for exploitable weaknesses that control documentation alone would never surface. A clean SSP means little if a tester can walk straight through the front door.

4- Ongoing Continuous Monitoring Support

Authorization is not a one-time event. CSPs must sustain compliance through continuous monitoring (ConMon), which includes regular scanning, vulnerability remediation, and periodic reassessment. 3PAOs often support annual assessments and significant-change reviews. One structural note worth tracking: as of March 2025, FedRAMP stopped running centralized continuous monitoring, and that responsibility now sits with each sponsoring agency.

Worth knowing: 3PAO Reports

FedRAMP states that 3PAO reports "serve as the basis from which the federal government makes informed, risk-based authorization decisions." The assessment is not a formality. It is the evidence the entire authorization rests on.

How Does an Organization Become an Accredited 3PAO?

Becoming a 3PAO is nearly as demanding as the assessments these firms perform. There is one accreditation body, and the bar is high.

A2LA Accreditation Requirements

The American Association for Laboratory Accreditation (A2LA) is the sole body that accredits FedRAMP 3PAOs. Its FedRAMP 3PAO accreditation program puts applicants through a rigorous evaluation of technical competence. A firm must spend at least a year in A2LA’s Cybersecurity Inspection Body Program before it can even be considered for FedRAMP recognition, and it must pass technical proficiency testing administered through A2LA’s testing partner.

ISO/IEC 17020 Compliance

Accreditation hinges on conformance with ISO/IEC 17020, the international standard for bodies that perform inspections. The standard sets requirements for impartiality, independence, technical competence, and a functioning quality management system. In practice, this is what stops a 3PAO from cutting corners or playing favorites. The accreditation certifies the firm’s process, not just the talent of its people.

FedRAMP-Specific Requirements

Beyond ISO/IEC 17020, FedRAMP layers on its own recognition requirements covering program-specific knowledge and assessment methodology. A firm has to demonstrate it understands FedRAMP’s baselines, templates, and reporting expectations — not just general inspection practice. Only after clearing both bars does the firm appear on the Marketplace as a recognized 3PAO.

Why are 3PAOs Important for FedRAMP

Why Are 3PAOs Important for FedRAMP?

FedRAMP runs on a “do once, use many” philosophy. One rigorous, independent assessment lets multiple federal agencies reuse the same authorization package instead of each running its own review. The 3PAO is what makes that trust transferable. Because the assessor is accredited and independent, an agency in one department can rely on a SAR produced for another.

The program exists because federal systems must meet security obligations set under FISMA, the Federal Information Security Modernization Act, and the General Services Administration (GSA) runs FedRAMP to standardize how cloud services meet them. Without accredited assessors, every agency would judge cloud security on its own terms — which is exactly the fragmentation FedRAMP was built to end.

Worth knowing: The FedRAMP Authorization

The FedRAMP authorization landscape changed significantly in 2024 and 2025. The Joint Authorization Board (JAB) and its provisional ATO path were dissolved under OMB Memorandum M-24-15, leaving a single "FedRAMP Authorized" designation. Authorizations now flow through agency authorization or the new 20x path, but the 3PAO's role as independent assessor carried straight through the transition.

Who Needs to Work with a 3PAO?

Any CSP that wants to sell a cloud service to the federal government at the Moderate or High impact level needs a 3PAO. At those levels, the assessment is mandatory, and an authorization package cannot be accepted without it. Providers handling federal data, contractors building CSOs for agency use, and vendors pursuing GovRAMP all fall into the same category.

At the Low impact level, the picture is more flexible, and the emerging 20x pathway is reshaping expectations there. Still, the safe assumption for most providers chasing meaningful federal business is that an independent assessment will be required at some point. The question is usually when, not whether.

One common point of confusion: a 3PAO is not a C3PAO. The names differ by a single letter, but they serve different programs. A 3PAO assesses cloud services for FedRAMP authorization and is accredited by A2LA. A Certified Third-Party Assessor Organization (C3PAO) assesses defense contractors for CMMC, the Cybersecurity Maturity Model Certification, and is authorized by the Cyber AB rather than A2LA. A handful of firms hold both, but the credentials are entirely separate.

Reach SOC 2 Compliance in 6 Weeks or Less

Schedule Your Free SOC 2 Assessment Today

How to Find an Accredited 3PAO

Start with the FedRAMP Marketplace. Its Assessors tab is the authoritative, public list of recognized 3PAOs, and any firm not on it is not a valid FedRAMP assessor — full stop. From there, the real work is vetting fit rather than legitimacy.

Pro tip: Do not choose on price or brand alone.

Do not choose on price or brand alone. Ask for verified experience at your target impact level, the names and credentials of the assessors who will actually do the work, and redacted samples that show SAR quality. A cheap assessment that an agency rejects is the most expensive option there is.

When Should You Engage a 3PAO?

Timing matters. Engage a 3PAO after your system and security program have matured, not before. Bringing in an assessor while controls are half-built guarantees findings, delays, and rework you will pay for twice. Most providers take a readiness step first, often producing a Readiness Assessment Report (RAR), which FedRAMP strongly recommends for the agency authorization process and which surfaces gaps before the formal assessment begins.

Insider note: FedRAMP 20x is changing when and how you work with assessors. As the program shifts toward automated, machine-readable validation built on Key Security Indicators and OSCAL, the 3PAO’s job is moving from reviewing screenshots to verifying that automated checks actually enforce the controls they claim to. Assessors now validate and verify rather than certify, and the CSP carries responsibility for the accuracy of what it submits. Expect to involve a 3PAO earlier in your process, and expect the engagement to be far more technical than the old document-review model.

There is also a hard rule worth flagging on independence. A 3PAO can offer advisory or consulting services, but it cannot assess a system it helped build. If you use one 3PAO as an advisor, you must hire a different one to perform the assessment, or the impartiality that A2LA accreditation depends on collapses entirely.

 

The Bottom Line

A 3PAO is the independent, accredited firm that turns a cloud provider’s security claims into evidence an agency can act on. The role is mandatory at higher impact levels, the accreditation behind it is hard-won, and the way 3PAOs work is shifting fast under FedRAMP 20x. Choose carefully, engage at the right moment, and treat the assessment as what it is: the foundation your entire authorization stands on.

Frequently Asked Questions

Is a 3PAO the same as an auditor?

Functionally, yes — with a caveat. A 3PAO performs an independent assessment much like a financial auditor, but under FedRAMP 20x the framing has shifted. Assessors now validate and verify a provider’s security claims rather than certify them or recommend an ATO. The agency, not the assessor, makes the final authorization decision.

There is no fixed price, and the assessment is only one line item in a larger FedRAMP budget. The fee scales with impact level, system complexity, and scope. Serious engagements run well into six figures — industry estimates commonly place a full initial FedRAMP authorization in the low-to-mid six figures once preparation, the assessment itself, and remediation are included. Get fixed-scope quotes from more than one recognized 3PAO before committing.

Yes, but not for the same system it assesses. FedRAMP allows 3PAOs to act as advisors, but impartiality rules mean a separate, independent 3PAO must perform the actual assessment of a service the first firm helped prepare. Mixing the two roles on one engagement is not permitted.

Accreditation is not permanent. A2LA recognition runs on a recurring cycle with ongoing surveillance and periodic reassessment, and a 3PAO must keep demonstrating independence, quality, and current FedRAMP knowledge to hold its standing. Firms that let competence or impartiality slip can lose recognition.

The FedRAMP PMO, operated under the GSA, recognizes 3PAOs and sets program requirements. A2LA is the sole accreditation body and verifies conformance with ISO/IEC 17020 plus FedRAMP-specific criteria. Recognized firms appear on the FedRAMP Marketplace.

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

Global AI regulation is not converging. Four distinct regulatory models have hardened over the past two years: the EU’s single horizontal law, China’s fast-moving sequence of targeted rules, the American patchwork of state laws and voluntary frameworks, and the Gulf’s procurement-driven approach, where the state shapes the market by being its biggest customer. Anyone waiting for these to merge into one global rulebook will be waiting well past 2030. That fragmentation, not any single law, is the defining trend in AI regulatory compliance. The practical question for 2026 through 2028 is no longer “which regulation applies to us” but “which regulatory model does each of our markets follow, and what carries over between them.” This article maps the four models, with extra time on the Gulf version because it gets far less coverage than it deserves. It also argues that ISO standards, led by ISO/IEC 42001, are becoming the only compliance credential that travels across all four. The Four Models of AI Regulation Most trend pieces treat AI regulation as one global movement running at different speeds. It’s more useful to treat it as four philosophies that answer the same question in incompatible ways.   European Union China United States Gulf (KSA, UAE) Instrument One horizontal law (EU AI Act) Sequence of targeted departmental rules State laws, voluntary frameworks, sector rules Data law plus procurement requirements Enforcer Commission, national authorities, notified bodies CAC and partner ministries States, regulators, courts, buyers SDAIA, NDMO, central banks, tender owners Core concern Fundamental rights, product safety Content security, data sovereignty Liability, consumer protection National strategy, data sovereignty, state procurement Speed Slow to write, long lead times Fast, iterative, hardening Uneven, litigation-led Fast: effective when a tender says so What travels Conformity assessment, technical files Filings and labeling rarely reusable Assurance reports, questionnaires ISO certification as procurement signal The European Union: One Law for Everything The EU chose a single horizontal statute, Regulation (EU) 2024/1689, better known as the EU AI Act. It classifies AI systems into risk tiers, bans a short list of practices outright, and attaches heavy obligations to high-risk systems: risk management, data governance, human oversight, technical documentation, and conformity assessment. It applies extraterritorially, so a Bahraini or American provider whose system reaches EU users is in scope. The model’s strength is predictability, and its weakness is pace. Prohibitions have applied since February 2025 and general-purpose AI obligations since August 2025, with Commission enforcement beginning in August 2026. The 2026 digital omnibus agreement then deferred the main high-risk deadlines to December 2027 and August 2028. The EU writes slowly, publishes a timetable, and expects the world to plan around it. China: Regulation One Risk at a Time China has no single AI statute and doesn’t appear to want one yet. Instead, the Cyberspace Administration of China and partner ministries have issued targeted rules in rapid sequence: algorithmic recommendation provisions in 2022, deep synthesis rules in 2023, interim measures for generative AI services the same year, AI content labeling requirements in September 2025, and rules for anthropomorphic AI interaction services that took effect in July 2026. Each rule attacks one risk scenario, takes effect quickly, and gets refined through practice. The direction of travel matters more than any single measure. China’s revised Cybersecurity Law, effective January 2026, wrote AI research, training data, computing infrastructure, and risk monitoring into a foundational statute for the first time. Soft guidance is hardening into binding law, and the organizing logic throughout is content security, data sovereignty, and platform accountability rather than individual rights. For foreign companies, the compliance burden is operational: filings, security assessments, and labeling obligations that arrive with short notice and almost no grace period. The United States: The Market as Regulator The US still has no federal AI statute, and the vacuum is being filled from two directions. States are legislating, with Colorado’s AI Act as the most complete example, and sector regulators are stretching existing consumer protection, employment, and financial rules to cover AI. The NIST AI Risk Management Framework sits underneath as the voluntary vocabulary everyone borrows. In practice, the binding force in America is commercial. Enterprise buyers, insurers, and litigators enforce AI governance through security questionnaires, vendor reviews, and lawsuits long before any statute does. For a company selling into the US, the real regulator is the procurement team of your largest prospect. The Gulf: The State as Customer The Gulf model is the least covered and, for anyone selling into the region, the most misunderstood. Saudi Arabia has no horizontal AI act. It regulates AI through data law and through the state’s position as the dominant buyer in the economy. The Saudi Data and Artificial Intelligence Authority (SDAIA), established in 2019 and reporting directly to the Prime Minister, runs the show: it sets national strategy, publishes the frameworks, and steers what government tenders ask for, a far more hands-on role than most regulators play. The load-bearing rules are the Personal Data Protection Law, enforced since September 2023, and its cross-border transfer regime. Around them sit SDAIA’s AI Ethics Principles, generative AI guidelines for government entities, and the AI Adoption Framework, published in November 2025 as a mandatory baseline for public sector bodies, with a four-tier risk classification and lifecycle auditing for high-impact systems. A draft Responsible AI Policy went through public consultation in May 2026, confirming that a formal, operational regime is coming. The Kingdom designated 2026 its Year of Artificial Intelligence, and the direction across the region matches: the UAE runs an AI Seal program and its central bank requires bias testing at financial institutions, Oman’s National AI Policy entered into force in April 2025, and Bahrain has a proposed AI law in progress. The defining feature is speed through procurement. A requirement in a Saudi government tender takes effect the day the tender document is published, with no transition period and no parliamentary debate. High-risk use cases increasingly require self-assessments before tenders or go-lives. Regulation by purchase order moves faster than regulation by statute, and in state-led

More than half of the average organization’s vendor footprint is now Shadow IT, and only two percent of it ever gets a security review, according to Vanta’s own research into vendor sprawl. That’s one symptom of a wider pattern: most risk registers drift from reality between review cycles — a spreadsheet nobody’s updated, a control nobody’s re-tested, a vendor relationship nobody’s re-assessed. This guide sets out what to check when evaluating risk management software, using four leading platforms as the test case. What Is Risk Management Software? Risk management software is the system of record for identifying, scoring, monitoring, and reporting on the risks an organization carries, spanning internal controls, regulatory obligations, and vendor relationships alike. The strongest platforms connect every risk source into one register instead of splitting them across separate tools, map each risk to the specific controls and assets it touches, and keep scoring current as those controls change. Third-party and vendor risk is one input into that system, not a separate category of software. Key Benefits of Risk Management Software A register that reflects reality. Continuous, signal-driven identification surfaces a lapsed control or a new exposure as your environment changes, instead of waiting for the next quarterly review to notice. Defensible answers, faster. Risks that are automatically mapped to the controls, assets, and vendors behind them mean an audit or board question gets a sourced answer instead of a manual reconstruction. One system instead of a spreadsheet plus a separate tool. Internal risk, vendor risk, and the controls that mitigate both live in one place, so scaling into a new business unit or region doesn’t mean standing up another platform. What to Look for in the Best Risk Management Software Most vendor comparisons focus on feature lists. The person who will configure the register and keep it current asks a narrower set of questions, and the answers aren’t always where a demo puts them. Continuous, Signal-Driven Risk Identification A risk register that only updates when someone remembers to run a review is already stale by the time it matters. Ask whether the platform surfaces new risks automatically as your environment changes (a new system, a failed control test, a new vendor relationship), or whether identification depends on someone scheduling a manual pass. Risk-to-Asset, Control, and Vendor Mapping A risk that isn’t tied to anything specific can’t be monitored and can’t be proven when an auditor asks how it’s covered. Ask whether risks map automatically to the assets, controls, and vendors involved, and whether a failed control raises the linked risk without anyone touching it. This is one of the more common places a platform’s marketing outpaces what it can actually demonstrate live, so ask for the mapping on screen rather than taking the claim at face value. Risk Scoring and Audit-Ready Reporting Boards and auditors expect both inherent risk (exposure before controls) and residual risk (exposure after), and a static score that only updates when someone re-scores it by hand loses credibility fast. Ask whether the platform scores both, whether residual risk updates automatically as controls change, and whether you can reproduce the register exactly as it stood on a specific past date rather than reconstructing it from an export. Platform Consolidation and Register Scale Nearly every vendor in this category positions itself as the one system that replaces a spreadsheet and every adjacent tool, which is a claim worth testing rather than taking at face value. Ask for a live demonstration showing risk findings, including vendor risk if that’s part of your program, and actually reach one register. Then ask specifically whether that register can split into multiple registers by business unit or entity with independently configured scoring, not just a single company-wide scale applied everywhere. AI Risk Governance AI is the fastest-growing, least-governed risk surface in most programs, and treating it as a side project instead of a line item in the main register is a common gap. Ask whether AI risk lives in the same register as everything else, mapped to named frameworks like the EU AI Act or ISO 42001, or whether it’s tracked separately, if at all. The Top Risk Management Platforms, Reviewed None of the platforms below have been tested hands-on for this guide. Each entry reflects what the vendor states on its own public pages, checked directly rather than taken from a review site or from a competitor’s comparison of it.   Vanta Vanta positions its risk product as a connected layer across compliance, internal risk, and third-party risk, built to sit inside the same automated-compliance workflow the platform is best known for. Strengths. Vanta maps risks to assets automatically, a shipped, generally available capability, and ships a named Risk Snapshots feature that captures the register at a specific point in time. It also provides a pre-built library of 100+ risk scenarios, and monitors internal and vendor risk continuously in one consolidated register, including, where third-party risk is part of the program, automating vendor questionnaire follow-up. Trade-offs. Risk-to-control mapping is in preview and risk-to-vendor mapping is on the roadmap, so don’t expect either live in a demo today. A more detailed, named-factor scoring model with automatic residual updates is also roadmap; what’s shipped today is a simpler inherent-and-residual score. Multiple risk registers by team or business unit are documented, but nothing public confirms independently configured scoring per register. Best for. Enterprise teams that want risk, compliance, and optionally vendor risk running on one continuously monitored foundation, and can wait on the control- and vendor-mapping roadmap.   OneTrust OneTrust positions itself broadly across privacy, data governance, and risk, with third-party risk as one module inside a wider platform. Strengths. OneTrust maps risks to related assets, processes, and vendors within its IT Risk Management product, and scores both inherent and residual risk with a stated ability to roll scores up through a risk hierarchy. It also has a dedicated AI Governance product mapping AI risk to the EU AI Act, NIST, and ISO 42001 by name, the most explicit AI-risk

OWASP published the 2026 edition of its Top 10 for LLM Applications on August 4, 2026, during Black Hat week, and eight of the ten entries changed position. One got renamed. The message behind the reshuffle is blunt: you won’t build a model that can’t be fooled, so build the application around it in a way that limits the damage when it is. That one idea explains almost every move in the new ranking, and it should change how your team thinks about shipping AI features. This guide walks through the 2026 list in plain English: what each risk means, a real-world example, and what your team can actually do about it, with or without a dedicated security function. What Is the OWASP GenAI LLM Top 10 2026? The OWASP Top 10 for LLM Applications is a community-built awareness document that ranks the ten most critical security risks in applications powered by large language models. The OWASP GenAI Security Project, a global open-source initiative under the OWASP Foundation, maintains it, and the 2026 edition is the third release since the list first appeared in 2023. OWASP, the Open Worldwide Application Security Project, has published risk lists for web applications since 2003, and those lists became the shared vocabulary security teams, auditors, and buyers use to talk about risk. The GenAI LLM Top 10 does the same job for AI. Whether you’re a two-person startup wiring an API into a chatbot or an enterprise running retrieval pipelines, it gives you a common map of what actually goes wrong. One scoping note matters before anything else. The 2026 edition covers the model as a component inside an application: something that accepts input, generates output, and maybe retrieves information. The moment the model becomes an actor, with tools it can call and consequences it sets in motion, the risk shifts to the companion OWASP Top 10 for Agentic Applications from December 2025. Most products now do both, so most teams need both lists. Why the 2026 Update Matters for AI Builders Two things separate this edition from everything OWASP has published on AI so far. First, the methodology changed. Every previous version rested purely on expert consensus, meaning hundreds of practitioners voting on which risks matter most. This time the vote carried 75% of the weight, and the remaining 25% came from analysis of 6,639 real-world AI security incidents pulled from public vulnerability databases and an AI-harm database. It’s the first edition grounded in evidence of what has actually gone wrong rather than expert prediction of what might. Second, the framing changed. The project leads open the 2026 release by telling teams to stop optimizing the model and start optimizing the containment. The industry has spent two years pouring effort into filters, guardrail models, and jailbreak resistance. The 2026 list says: assume those will eventually fail, and make sure that when they do, nothing important breaks. AI security becomes blast radius control rather than perfect prevention. And this isn’t just a security engineer’s document. Developers decide what tools and permissions a model gets. Product owners decide which workflows run without a human in the loop. Founders and ops leads are the ones answering the security questionnaires where these questions now show up. The 2026 edition also ships a mapping appendix that connects every risk to frameworks your customers and auditors already recognize: NIST’s AI Risk Management Framework, MITRE ATLAS, MITRE CWE, and the Agentic Top 10. Insider Note: Enterprise vendor assessments have started asking about the OWASP LLM Top 10 by name. In security questionnaires we complete for clients at Axipro, questions like “describe your controls against prompt injection and excessive agency” began appearing in early 2026, sometimes before the buyer’s own team could explain what they meant. Being able to answer with a mapped control set is becoming a deal-cycle advantage, not just a security exercise. How the 2026 List Differs From Previous Versions The top two entries held their positions. Everything below them moved. Key Shifts Since the 2025 Update Excessive Agency jumped from sixth to third, the biggest promotion on the list. In 2025, giving a model tools and autonomy was mostly a theoretical worry. By 2026, agentic deployments had produced real production incidents, and the community concluded that agency is what decides whether a successful prompt injection is an inconvenience or a breach. Unbounded Consumption rose four places, from tenth to sixth. Inference costs became a real budget line as reasoning models, long outputs, and agent loops multiplied the compute behind a single request. “Denial of Wallet,” where an attacker spends pennies to trigger spend you can’t afford, is now a mainstream finding. Improper Output Handling fell from fifth to tenth. The risk didn’t shrink. It fell because it’s well understood and directly fixable with encoding and validation practices web developers already have. The entries above it are neither. What’s New, Renamed, or Reprioritized System Prompt Leakage became Hidden Context Exposure, and the scope widened a lot. The 2025 entry worried about attackers extracting your system prompt. The 2026 entry covers everything assembled into the model’s context that users aren’t meant to see: system instructions, retrieved policy documents, tool schemas, workflow rules. The guidance is unusually honest for a security document: assume all of it is discoverable, and design so that disclosure costs you nothing. Data and Model Poisoning absorbed fine-tuning subversion. The attack surface for corrupting a model’s behavior runs from pretraining data through fine-tuning pipelines into the retrieval stores RAG systems depend on, and the entry now says so. Misinformation climbed on evidence, not opinion. Practitioners voted it low; the incident data ranked it high. As reported in Help Net Security’s coverage of the release, OWASP also describes a “defense effect” working in the opposite direction on prompt injection: teams block it so effectively that few successful attacks reach public databases, which makes the risk look smaller than the money spent containing it. Signals About Where AI Security Is Heading Read together, the moves point one