Where it fits
- A product team changes the system prompt and wants to know if old jailbreaks now work.
- A platform team adds tools or function calls and needs to test authorization boundaries.
- A security team wants evidence for SOC 2, ISO 27001, vendor questionnaires, or customer review.
Operational steps
- Define the application policy, allowed tools, disallowed outputs, and sensitive data classes.
- Attach test packs for injection, jailbreak, leakage, tool misuse, and unsafe retrieval.
- Run the scan in CI and store reports beside the pull request or release artifact.
- Track recurring failures so prompt, retrieval, and guardrail changes can be measured over time.
Common risks
- Manual testing misses regressions after a model provider or prompt template changes.
- Tool permissions are tested in isolation but not through adversarial language.
- Security reports lack enough evidence for engineers to reproduce and fix the issue.
How PromptGuard Scan fits the workflow
PromptGuard Scan gives teams a command-line and API-first workflow with structured findings, CI status checks, and remediation guidance for prompt, RAG, and agent security issues.