Use BAS when you need repeatable control validation against known behaviours. Use CART when you need to know whether an adversary can reach a target objective through adaptive chaining. They answer different questions, so the right decision is usually to run both as layered assurance rather than choose one.
What BAS is good for, and where it stops
BAS is strongest when the question is whether a known control or defensive behaviour works as intended under repeatable conditions. That makes it useful for validating detection rules, prevention logic, segmentation outcomes, and response playbooks against a controlled scenario. The value is consistency: the same test can be rerun, compared over time, and used to spot drift in defensive effectiveness.
BAS is less useful when the real concern is whether an attacker can combine multiple steps into an outcome you did not model in advance. A single control may look healthy in isolation while the overall path to impact still exists. That is why BAS is best treated as a control-validation layer, not as a full path-to-objective exercise. The Breach and Attack Simulation (BAS) Guide is useful when teams want to understand how repeatable simulation supports control assurance and detection coverage.
What CART adds that BAS does not
CART is designed for a different decision: can an adversary, using adaptive chaining, reach a target objective through your actual environment and dependencies? That shifts the focus from isolated control checks to end-to-end attack logic, including sequencing, branching, and the ability to adapt when one step is blocked. It is closer to asking, “Does the route to the goal still exist?” than “Did this control fire?”
Because of that, CART is often more useful for exposure management, segmentation review, privilege path analysis, and testing whether layered controls really interrupt an attack path. It is also more realistic when defenders need to understand how partial compromise can be extended into material impact. The Continuous Automated Red Teaming (CART) Guide helps frame CART as continuous adversary path validation rather than simple simulation.
How to choose, or why most mature teams layer both
The decision usually comes down to the assurance question you need answered. Choose BAS when the priority is broad, repeatable coverage and you want to measure whether specific controls behave consistently over time. Choose CART when the priority is adversary realism and you need to know whether a reachable chain to impact still exists despite those controls. If you only use one, you risk optimising for the wrong signal.
In practice, the two approaches work best as complements. BAS can show where control performance is weak or unstable, while CART can show whether those weaknesses matter in a realistic path to objective. Used together, they reduce the common mistake of treating a passing simulation as proof that no viable attack path exists. External guidance such as the FIRST standards can also help teams anchor these activities in disciplined incident and response practice, especially when test findings need to be operationalised.
Risk and Threat Considerations
The main risk is false assurance. BAS can confirm that a known behaviour was blocked or detected without proving that an attacker cannot achieve the same objective through a different sequence. CART can surface that path, but it may miss some of the repeatability and coverage discipline that BAS gives you. Teams that treat one as a substitute for the other often overestimate their defensive confidence.
Failure mechanism: A control passes a scripted simulation, while the environment still contains an alternate route, dependency gap, or privilege chain that an adaptive adversary can use to reach the target objective.
Impact: Exposure persists even though the control appears effective, which can leave detection blind spots, delayed remediation, and a misleading security posture.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while NIST CSF 2.0, OWASP ASVS and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | DE.CM-01 — Monitoring for Anomalies and Events | BAS and CART both validate whether monitoring and response behave under test. |
| PR.AA-05 — Identity Management, Authentication, and Access Control | CART often tests whether access paths and privilege chains still enable objective reachability. | |
| Recommendation — Validate detection coverage with repeatable tests and track drift in alerting performance. Test whether access controls actually block path-to-objective movement. | ||
| MITRE ATT&CK | T1588 — Acquire Capabilities | CART and BAS map adversary behaviours and chaining against known technique patterns. |
| Recommendation — Map simulated steps to ATT&CK techniques and hunt for missing coverage. | ||
| OWASP ASVS | V16 — Security Logging and Error Handling | BAS commonly validates whether security logging and alerting trigger as expected. |
| Recommendation — Verify that logging and alerting produce actionable evidence during simulation. | ||
| CIS Controls v8 | CIS-8 — Audit Log Management | Simulation programs depend on logging to confirm whether controls observed the test. |
| Recommendation — Ensure audit logs capture the events needed to judge simulation outcomes. | ||
Practitioner Guidance
What to prioritise: Decide first whether the business question is control validation or attack-path validation. If the team is measuring control quality over time, BAS is the better primary signal; if the team is testing whether a target can still be reached, CART should take priority.
What to verify: Make sure the test design matches the assurance claim. A passing BAS run should not be reported as proof that no adversary can succeed, and a CART result should not be treated as a substitute for ongoing control coverage metrics. Use each to answer the question it is actually built to answer.
Practitioner takeaway: The strongest programmes do not ask BAS to do CART’s job, or CART to do BAS’s job; they use both to separate control reliability from real-world compromise potential.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org