§ The CISO Learning Journey · Week 2 · Phase 1 · Awareness · June 2, 2026

The 80, 59, 89 numbers every CISO should know going into 2026.

By Lindsay Hiebert · Founder · CISSP

Three numbers framing the Shadow AI crisis: 80%+ unmanaged AI (Zluri 2025), 59% of employees hiding AI from IT (Cybernews 2025), 89% YoY increase in AI-enabled attacks (CrowdStrike 2026).
Three numbers · three primary sources · one story

Three numbers frame the Shadow AI crisis. 80%+ of enterprise AI usage is unmanaged today — Zluri’s State of AI in the Workplace 2025. Most of the AI your organization runs on did not come through procurement, was not vetted by security, and is not visible to IT. 59% of employees actively hide their AI usage from IT — Cybernews’s 2025 AI Workplace Survey, corroborated by KPMG at 57%. The phenomenon is defined by invisibility, not intent — employees are trying to be productive, not malicious, but the data still leaves the building. 89% year-over-year increase in attacks by AI-enabled adversaries, with 82% of 2025 detections occurring without malware — CrowdStrike’s 2026 Global Threat Report. Three numbers, three primary sources, one story: governance, behavior, and threat-actor velocity have all aligned against the mid-market security team.

Most AI governance content circulating in 2026 cites these numbers second-hand or rounds them up without sourcing. Big 4 advisory deliverables and consultant checklists rarely link to the primary report — and the round numbers (“90%”, “60%”, “100x”) read as marketing rather than evidence. An auditor or regulator will ask where each claim traces to. A claim that does not trace to a primary source is not defensible at deposition or in a renewal questionnaire. Same problem applies to the vendor-questionnaire ecosystem (SIG, Vanta, Drata, Secureframe) when its AI-governance content cites second-hand statistics rather than primary research.

What to do. Every claim in your governance program needs a citable primary source. SanctumShield’s multi-LLM agentic synthesis layer (Claude + Gemini) cross-validates every citation at artifact-generation time, and the Research Foundations section publishes the canonical citation chain for every claim that appears in customer-facing artifacts — primary research papers, framework texts, vendor disclosures, threat reports. Next step: review the Research Foundations to see what defensible AI governance evidence actually looks like.

Addendum, October 2026: the fourth number.

The three numbers above measure the surface. IBM’s 2026 Cost of a Data Breach study measures what happened to the organizations that were breached through it. one in five organizations reported a breach targeting their own AI models or applications (more than 20%). Of those, 92% of organizations that suffered an AI-related breach lacked proper AI access controls; only 40% of organizations report using access controls on AI models and data (IBM Cost of a Data Breach Report 2026, as summarized by IBM (Limor Kessem, IBM Think, July 29, 2026)). The same point as above applies: the 2025 edition’s figures still circulate, so the edition year travels with the number, or the number fails at deposition.

§ Why this is a legal question, not a tooling preference

Everything above is an argument about method. Underneath it sits an obligation that does not depend on which method you pick. Documented, dated, demonstrable governance is what the law asks for, and the dates have stopped being in the future.

EU AI Act Article 4 — AI literacy
In force since February 2, 2025. National enforcement began August 2, 2026.
EU AI Act Article 50 — transparency
Applies since August 2, 2026.
Colorado SB 26-189
Effective January 1, 2027.
EU AI Act Articles 12, 14 and 17 — record-keeping, human oversight, quality management
High-risk regime: December 2, 2027 (Annex III) and August 2, 2028 (Annex I).

Read those together and the shape is consistent. Each one asks an organization to produce something — a measure taken, a disclosure made, a record kept, a review performed — and to be able to show it after the fact. None of them names a product, a platform or a link, and nothing here should be read as saying a law requires one. What a law requires is the record. Making that record dated and third-party-verifiable is simply how you let an auditor, an underwriter or a board confirm it without being handed the contents, or being asked to take your word for it.

And literacy is not one obligation among several. It is the one the others rest on. You cannot exercise due diligence over a system you cannot recognise, and you cannot govern an authority you do not understand you have delegated.

That is why Article 4 sits in the opening chapter of the Act, ahead of the risk tiers, and why it applied eighteen months before the high-risk regime does. The duty is to take measures that support the development of AI literacy among the people operating AI on the organization’s behalf — and the useful version of that is matched to the seat. What a director needs to recognise is not what a developer needs to recognise, and neither is what the person pasting a contract into a browser tab needs to recognise. A single org-wide module satisfies the form and misses the point.

Free Shadow AI Risk Audit

See what your current stack is missing — in 12 questions.

The SanctumShield free Shadow AI Risk Calculator runs in your browser. No account, no email, no credit card. Twelve questions, instant risk score, three primary findings tailored to what you submit.

CISO Learning Journey: Week 2 of 27 · Phase 1 (Awareness) · see the full series →

The 80, 59, 89 Numbers Every CISO Should Know Going Into 2026 — SanctumShield