A bank is preparing to launch a multi-agent customer assistant. Security wants shift-left adversarial testing of prompt injection, tool abuse, and jailbreak attempts before production. Which Foundry-aligned practice should they adopt?
Select an answer to reveal the explanation.
Short Explanation
Correct answer: B. Shift-left security for multi-agent systems means adversarial testing before go-live. The AI Red Teaming Agent in Foundry—and related adversarial evals—probe prompt injection, tool abuse, and jailbreaks so you can fix issues pre-release. Waiting for public traffic (A) is late and risky. Port scans alone (C) miss LLM-specific attacks. Turning off safety filters in production (D) is the opposite of defense. Feed red-team findings into guardrails, tool permissions, and evaluation suites.
Full Explanation
Implementing shift-left security principles, including the AI Red Teaming Agent in Foundry, is a stated skill for securing multi-agent solutions. Option B correctly places adversarial testing in development/pre-production with remediation before release. Option A delays discovery until customer impact. Option C covers only traditional infrastructure attack surface. Option D weakens controls. Integrate red-team scenarios into CI, track residual risk, and re-run after major prompt or tool changes.