Why is prompt injection different from ordinary bad input?

Instruction: Explain why prompt injection is a distinct safety problem in AI systems.

Context: Prompt injection as a data-to-authority failure.

Updated

Example Answer

Prompt injection tries to make the assistant follow instructions that were not authorized, often by putting them inside material it was meant to read. A typo or malformed input can cause a different kind of failure; the distinctive issue here is that data is being treated as authority. I’d explain it with a document that tells a summarizing assistant to send unrelated files elsewhere. Reading that sentence must not grant permission to send anything. I’d label external content, keep credentials outside model context, and validate any proposed action against the user’s request and permissions.

Concrete example

A source can supply an invoice amount for extraction, but it cannot authorize changing the payment recipient. The application must verify that proposed change independently.

Limit to explain

Ordinary bad input is not always harmless: parsers and databases have their own injection risks. Content labels and prompts alone cannot guarantee resistance to model-directed attacks.

Follow-up to practice

Which boundary would still protect the system if the model followed the injected instruction?

Your preparation path

Work through these questions in order. Read the answer aloud, then explain it in your own words.

Related Questions