Microsoft Security Exposure Management
Vulnerabilities and exposure

Codename Mdash Faq

In brief

The FAQ no longer includes the bullet explaining that Codename MDASH dynamically executes triggering inputs to validate vulnerability preconditions. Its model-agnostic architecture paragraph remains documented.

What Defender admins need to know

Administrators consulting the FAQ will see less detail about the vulnerability-validation workflow. No action is required.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

  • Scan: Runs specialized auditor agents over candidate code paths, emitting candidate findings with hypotheses and evidence.
  • Validate: A second cohort of agents (debaters) argue for and against each finding's reachability and exploitability.
  • Dedupe: Collapses semantically equivalent findings (for example, patch-based grouping).
  • Prove: Constructs and executes triggering inputs where the bug class allows, validating the pre-condition dynamically to prove the vulnerability exists.

What kinds of vulnerabilities is Codename MDASH designed to find?

If Codename MDASH uses multiple models, do results just depend on which model is best at any moment?

This is exactly why the architecture is model-agnostic by design. When a better model becomes available, Codename MDASH can integrate it without rebuilding the pipeline. Targeting logic, validation stages, agent configuration, and prove infrastructure all carry over. The value is not any one model, it's the orchestration; how Codename MDASH structures model outputs, debates and validates findings, and turns hypotheses into confirmed, provenconfirmed vulnerabilities.

Which AI models does Codename MDASH use?