Skip to main content

Staff are pasting company data into public AI tools without approval. How would you handle shadow AI?

AI security · Pro 2

Short answer

Banning everything usually drives it underground. I would find out what people use and why, offer an approved tool with proper data terms, write a short policy on what data may go where, add technical controls for the riskiest data, and train people with real examples. Then keep an AI inventory and review new tools through a quick, clear process.

Deeper answer

Start with discovery: proxy and DNS logs, browser extension lists, expense claims and a no-blame survey. Classify the risk: customer personal data, source code, unreleased financials and credentials are the main concerns, along with DPDP Act duties for personal data.

Then offer a safe path: an enterprise AI tool with data not used for training, sign-on, logging and retention settings. Write a one-page policy with clear examples of allowed and not allowed. Back it with controls: data loss prevention rules for identifiers and secrets, blocking unapproved tools that handle sensitive data, and an intake form so teams can request a new tool and get an answer in days, not months. Measure adoption of the approved tool and repeat discovery every quarter.

What a strong answer covers

Answer it out loud in the mock interview about 1.5 min

Follow-ups to expect

Common mistakes

Learn it

Run an AI security programme

Practice AI security questions

More on this topic

Today's AI turns are used

Lessons, roadmaps, videos, practice cards and the code playground stay free with your account, with no limit.