Exposure Validation Finder

Breach and attack simulation

Breach and attack simulation runs safe, scripted attack scenarios against your own controls and records which ones were blocked, which were detected and which got through unseen.

What it proves

A BAS run produces a control-by-control record. The email gateway let three of twenty malicious attachments through. The EDR blocked credential dumping on Windows hosts but only alerted on the macOS fleet. The SIEM received the events but no rule fired.

Because the scenarios are scripted and repeatable, the same test can run every week. That turns a one-time finding into a trend line, and it shows when a policy change or an agent update quietly breaks a control.

What it does not prove

BAS does not tell you whether an attacker can get from a phished laptop to your domain controllers. Each scenario tests a technique in isolation, usually from an agent you placed. It assumes the attacker is already where the agent sits.

It also says little about vulnerabilities you have not patched. A BAS tool tests behaviour against controls, not the exploitability of a specific CVE on a specific server.

How it differs from its neighbours

Adversarial exposure validation is the wider category Gartner introduced in 2025, and it absorbs BAS. Most BAS vendors now sell under the AEV label. The practical difference: an AEV platform adds attack-path testing or exploit validation next to the control tests.

Automated pentesting starts from the other end. It looks for a way in and through, and treats the controls as obstacles. BAS treats the controls as the subject.

Who buys it

SOC managers and detection engineers, usually after a tool consolidation or an EDR migration, when someone asks whether the new stack actually catches what the old one did. Compliance teams under DORA or NIS2 also buy it for repeatable evidence of control testing.

Expect to install agents. Most BAS products on this site need a test point, simulator, validator or actor on the hosts they test from. AttackIQ Flex is the documented exception: agentless test packages, Windows only, with a smaller content set.

Vendors that fit

Listed alphabetically: documented first, then partial claims. The note under each name is a summary of what the vendor's own pages claim, as read on 3 November 2026.

Documented (7)

Partial (1)

The pilot worksheet for breach and attack simulation