Skip to content

FEAT: Adversarial Models Blog Post - #2519

Open
Victor Valbuena (ValbuenaVC) wants to merge 10 commits into
microsoft:mainfrom
ValbuenaVC:adversarial-blog
Open

FEAT: Adversarial Models Blog Post#2519
Victor Valbuena (ValbuenaVC) wants to merge 10 commits into
microsoft:mainfrom
ValbuenaVC:adversarial-blog

Conversation

@ValbuenaVC

@ValbuenaVC Victor Valbuena (ValbuenaVC) commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Description

Blog post for the adversarial model benchmark (AdversarialBenchmark) in PyRIT. The blog post explains what adversarial models are, why they matter in PyRIT, and what happened when we created and ran a benchmarking scenario on them. Small datasets and graphs are attached in this PR.

Tests and Documentation

N/A. All changes are under /doc/blog.

@ValbuenaVC Victor Valbuena (ValbuenaVC) changed the title FEAT: Blog post contents [DRAFT] FEAT: Blog post contents Aug 31, 2026
Comment thread doc/blog/2026_09_02_adversarial_model_selection.md Outdated
Comment thread doc/blog/2026_09_02_adversarial_model_selection.md Outdated
Comment thread doc/blog/2026_09_02_adversarial_model_selection.md Outdated
PyRIT helped us discover that we could improve the attack success rate of our adversarial chat target by more than 19 percentage points.

We use PyRIT during red teaming operations, where many automated techniques use an adversarial model for attack orchestration. We wanted better adversarial models for PyRIT, so we built a tool to automate that comparison process. This became PyRIT's `AdversarialBenchmark` scenario and turned model selection from an intuition-driven choice into a repeatable evaluation. We are scaling this evaluation through CI/CD to continuously discover effective models for automating red teaming. When we ran it against in-house models, we discovered surprising patterns in attack performance across techniques, which this post explores.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another thing I might add to the first paragraph is a recommendation; "Grok is a decent adversarial model to start with".

One of the biggest hurdles to getting started is selecting an adversarial model, so writing this down I think can be helpful

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I may disagree on making a recommendation to use a specific model. The blog post ends with noting that the "best" model depends on technique, objectives, scoring, etc. So, I feel like pointing to a provider even as a good place to start with is misleading. Thoughts?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still think it's nice to say it's decent, even if we caveat it. I know it will change, but I want to make things as easy as we can for folks to get started is a good thing

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Approved with smallish things

@ValbuenaVC Victor Valbuena (ValbuenaVC) changed the title [DRAFT] FEAT: Blog post contents [DRAFT] FEAT: Adversarial Models Blog Post Sep 1, 2026
Comment thread doc/blog/2026_09_02_adversarial_model_selection.md Outdated
Comment thread doc/blog/2026_09_02_adversarial_model_selection.md Outdated
Comment thread doc/blog/2026_09_02_adversarial_model_selection.md Outdated
Comment thread doc/blog/2026_09_02_adversarial_model_selection.md Outdated
@ValbuenaVC Victor Valbuena (ValbuenaVC) changed the title [DRAFT] FEAT: Adversarial Models Blog Post FEAT: Adversarial Models Blog Post Sep 1, 2026
@ValbuenaVC
Victor Valbuena (ValbuenaVC) marked this pull request as ready for review September 1, 2026 23:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants