liveBook · Manning

Redaction

As explained in Context Engineering

The removal or masking of sensitive information from data before it is shared, stored, exposed, or processed.

Redaction detects and masks sensitive information before it enters an LLM context or is exported in an observability trace. It reduces exposure of personal data in prompts, memory, and telemetry. section 8.3.4 section 9.1.1

Redaction operates at two points in an LLM system:

  • During context assembly, mask sensitive entities before they enter the context window or are sent to an external LLM. section 9.1.1
  • Before exporting traces, apply field-level masking to prompt payloads; limit trace retention as an additional privacy control. section 8.3.4 section 9.1.1

Customer support context

Before constructing a prompt, filter account identifiers, email addresses, payment details, past tickets, and free-text messages according to purpose and authorization. Tools such as Microsoft Presidio or OpenDP can detect, redact, anonymize, or transform PII before dispatch to an external LLM or persistence in long-term memory. section 9.1.1

How Context Engineering covers it

How deep it goes
Places masking before context entry and trace export, but does not detail detection or masking algorithms.
Examples
Uses credit card numbers, phone numbers, and customer-support identifiers, messages, tickets, and payment details as sensitive data examples.
What you can do after
Apply it via Microsoft Presidio or OpenDP to detect, redact, anonymize, or transform PII before dispatch or persistence.
How it connects
Pairs with data minimization, scoped authorization, retention limits, and observability trace masking.

Also explained in

Compare how 2 books explain redaction →

Related concepts

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