liveBook · Manning

Shadow AI

As explained in Vibe Engineering

Shadow AI is the unapproved use of AI tools or services outside an organization's governed and auditable processes.

Shadow AI is the unapproved use of AI tools or services outside governed, auditable processes. Its most dangerous form is invisible production usage: code serves traffic while nobody knows which parts were generated or how. section 10.5

Banning desirable tools creates a prohibition trap. Developers may continue using them through endpoints and services that evade security review, auditing, and operational visibility. Provision beats prohibition: make the sanctioned path faster, safer, and easier to use. section 10.5

A practical response combines:

  • Sanctioned AI tools with proper audit trails. section 10.5
  • Visible engineering checks, including lint-as-architecture and triage. section 10.5
  • A deliberate effort to improve the governed path rather than merely punish the shadow path. section 10.5

How Vibe Engineering covers it

How deep it goes
Explains the prohibition failure mode and names sanctioned tools, audit trails, linting, and triage without detailing implementation.
Examples
Uses unknown production code, blocked endpoints, Prohibition, speakeasies, and a sanctioned engineering pipeline.
What it assumes
Assumes organizational AI demand and developer access to tools, while treating shadow usage as unmet demand rather than misconduct.
What you can do after
Operate/configure AI governance by provisioning auditable tools and strengthening the visible engineering path.
How it connects
Connects shadow AI to audit trails, sanctioned tools, security, and code review visibility.

Also explained in

Compare how 2 books explain shadow AI →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.