liveBook · Manning

System-level response

As explained in Prompt Engineering in Practice

A security measure implemented in the surrounding system rather than in the prompt or model generation process.

A system-level response addresses security failures outside the prompt and model generation process. Use one when prompt hardening delays but cannot prevent persistent behavioral drift or gradual scope expansion. section 10.5.1

Possible responses include:

  • Evaluate outputs turn by turn, enforce conversation scope, or filter content. section 10.5.1
  • Audit conversations, route between models, or limit request rates. section 10.5.1

Persistent scope expansion

A conversation gradually shifts beyond its intended scope and elicits restricted content over several reasonable turns. Prompt hardening may delay this failure; consider conversation scope enforcement, turn-by-turn evaluation, or content filtering. section 10.5.1

How Prompt Engineering in Practice covers it

How deep it goes
Names response types and the prompt-security boundary, but does not detail their implementation.
Examples
Uses gradual scope expansion and restricted-content disclosure across multiple conversational turns.
What it assumes
Assumes familiarity with prompt hardening and untrusted-input risks; teaches how to recognize where prompt-level defenses end.
What you can do after
Evaluate when prompt-level security is insufficient and identify an appropriate kind of system-level response.
How it connects
Connects prompt hardening with output filtering, conversation auditing, model routing, and rate limiting.

Related concepts

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