テクニカルガイド

Spotlighting and Datamarking Defenses

Spotlighting marks or transforms untrusted text so a model has a cue that it is data to process rather than an instruction to follow.

  • 3 分で読めます
  • 最終更新日
このページでは3 分で読めます
  1. 概要
  2. ディープダイブ
  3. 戦略的影響
  4. The Future of Spotlighting and Datamarking Defenses
  5. 現実世界の実装
  6. リスクとガードレール
  7. 実装ロードマップ
  8. 探検を続けましょう
  9. よくある質問

概要

Research describes delimiting, datamarking, and encoding variants, but results are tied to tested models and attacks; no formatting trick creates a guaranteed security boundary.

ディープダイブ

Spotlighting is a family of prompt transformations intended to make the provenance of untrusted content more visible in a model’s text context. A 2024 Microsoft-affiliated research paper describes three variants. Delimiting brackets a document with selected markers. Datamarking inserts a marker throughout the text, in the paper’s example replacing whitespace between words. Encoding transforms the document, for example using base64, and instructs the model to interpret the encoded block as data for the assigned task. Each variant also relies on a system instruction that explains how the marked text should be treated. The paper evaluated these methods on a synthetic indirect-injection corpus and older GPT-family model versions. It reported substantially lower attack success in its experiments, including a decrease from above 50% to below 2% for selected settings. Those numbers describe the paper’s particular tasks, attacks, and models; they are not expected production rates or guarantees for current systems. The paper also found encoding could impair underlying tasks for models less capable of decoding the text. This makes per-model utility evaluation important, not optional. Microsoft Foundry documents its Spotlighting preview as a document-attack control that uses base64 transformation and is supported only for models through the Chat Completions API. The docs say this increases document tokens and can cause long inputs to exceed limits, and note a possible user-visible encoding reference. That specific service behavior differs from a generic hand-built technique. In every case, marking helps signal provenance inside a shared text channel; it does not isolate data at a hardware or permission boundary. Test attacks that know the marker, preserve ordinary task quality, and restrict tool permissions so a successful injection has limited consequences.

戦略的影響

費用と予算

アーキテクチャの決定により、パフォーマンスと運用コストが何年にもわたって推進されます。

より明確な判決

技術教育は、チームが最新のスタックだけでなく、適切なスタックを選択するのに役立ちます。

品質管理

より良いエンジニアリングの選択により、本番環境での信頼性に関するインシデントが減少します。

The Future of Spotlighting and Datamarking Defenses

Provenance cues may become more native to model interfaces, but prompt-level markings still share the same context channel as the text they label. The research and product implementations will evolve, and their effects will vary with model versions and attack designs. Teams should retest task quality and adversarial cases after any change, while retaining independent permission checks and monitoring. Dynamic markers could make some simple spoofing attempts harder, but they do not create a separate trusted channel. Review new attack patterns as retrieval sources change.

現実世界の実装

A summarizer places a retrieved document between delimiters and states that instructions inside the passage are content to summarize, not commands.

A pipeline inserts a marker between words in a document, following a datamarking approach, then tests whether normal summarization still works.

A system transforms a passage using an encoding and tells a capable model how to interpret it as reference content, then measures task accuracy and attack success.

A security team pairs data marking with restricted tools and tests for attacks that copy, omit, or imitate the chosen marker.

リスクとガードレール

  • 1 つのベンチマークを最適化すると、より広範なシステムの弱点が隠れる可能性があります。

  • インフラストラクチャとメンテナンスのコストは過小評価されがちです。

  • システムが複雑になるにつれて、セキュリティと可観測性のギャップが拡大する可能性があります。

実装ロードマップ

  1. 実装前にレイテンシ、品質、コストの目標を定義します。

  2. 現実的な負荷とデータ条件でのベンチマーク。

  3. エラー、ドリフト、ユーザーへの影響を計測器で監視します。

  4. スケーリングの前に、ロールバックとインシデント対応のパスを準備します。

探検を続けましょう

Free newsletter

Get the daily AI briefing

Three verified AI stories every weekday morning, written in plain English. Free forever, no ads.

One email each weekday. Unsubscribe in one click. We never sell or share your address.

Test yourself

Take the Spotlighting and Datamarking Defenses quiz

Instant feedback on every answer, and a shareable certificate with a verifiable ID once you pass a course.

クイズを開始する

Support free AI education. AI Understanding is a 501(c)(3) nonprofit — no ads, no paywall, ever. Make a donation

よくある質問

What is Spotlighting and Datamarking Defenses?

Spotlighting marks or transforms untrusted text so a model has a cue that it is data to process rather than an instruction to follow. Research describes delimiting, datamarking, and encoding variants, but results are tied to tested models and attacks; no formatting trick creates a guaranteed security boundary.

What does spotlighting try to signal to a language model?

Spotlighting uses transformations and instructions to cue provenance of untrusted content.

How does datamarking work in the paper’s example?

The paper’s datamarking example interleaves a chosen character at word boundaries by replacing whitespace.

What should readers infer from the paper’s reported attack-success reductions?

The guide limits the reported numbers to the paper’s tested models, attacks, and tasks.

What limitation did the paper report for encoding on less capable tested models?

The paper reports that some tested models, including GPT-3.5-Turbo, struggled with encoded inputs and task quality.

What does Microsoft Foundry’s documented Spotlighting preview do?

Microsoft’s current docs describe base64-transformed document content for its Spotlighting preview.