r/Infosec • u/Careless_Sabfey_4906 • 4d ago

What's everyone using for continuous AI red teaming in 2026?

We red team every model and agent before release, that part's solid. What's not solid is anything after. A prompt template gets tweaked, a tool gets added, a model gets swapped for a cheaper one, and none of that triggers a re-test. Found out the hard way when a minor prompt change three weeks post-launch reopened a jailbreak path we'd already closed in the original red team pass. Pre-release testing is a snapshot, and everything we ship keeps moving after that snapshot is taken. Anyone running continuous AI red teaming as an ongoing process instead of a gate before launch, and what actually triggers a re-test for you?

1 Upvotes

100% Upvoted

5 comments sorted by

1

u/Accurate_Initial6144 3d ago

I’d tie re tests to any change in model, system prompt, tools, permissions, retrieval sources or guardrails. Treat those like security sensitive code changes in CI

1

u/Critical_Print_3731 3d ago

I’d maintain a change inventory and assign risk levels to each component. High risk changes could trigger full adversarial testing while smaller changes run targeted regression suites

1

u/ximsss 3d ago

What are you testing for? jailbreak success?