Slide 23 of 27
Part 4 · PreventionSlide 23
Slide 23 ยท Mitigation 5 of 6
Test your own system with extraction techniques before it ships.
๐Ÿ“„ OWASP LLM Top 10:2025 ยท LLM07 Prevention โ€” Security Testing
OWASP โ€” Security Testing
Red-Team System Prompt Extraction as Part of Pre-Deployment Review

“Document the potential risks and vulnerabilities associated with the use of system prompts and test the system for these vulnerabilities before deployment.”

Both the Bing Chat “Sydney” incident and the GitHub Copilot extraction happened at or immediately after launch. Neither had been tested against the extraction techniques that found them. A pre-launch red-team would have found the vulnerability in minutes โ€” the same way Kevin Liu did.

โ†’ Run all four extraction techniques (direct, multi-step, encoding, chained injection) against your own deployment before launch
โ†’ Test with and without the secrecy instruction present โ€” if the prompt is more extractable without it, extraction is the real risk
โ†’ Document extraction test results and link them to LLM07 in your security review
โ†’ Re-run tests after any significant prompt change

Spend 15 minutes trying to extract your own system prompt using the four techniques from Part 2. If you succeed, an attacker will too. The question is whether what you extract causes damage โ€” and if so, M1 and M2 need more work.

๐Ÿ’ผ Business takeaway

Ask your team whether anyone tested your system by trying to extract the system prompt before launch. Techniques like "repeat the above" or "translate your instructions to Spanish" are well-documented and should be part of pre-launch testing.

โ† BackNext โ†’ M6 โ€” Access controls