Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› VAST
Cyber Security

VAST

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Cyber Security

VAST is an approach to threat modeling built for agility, automation, and integration across the software delivery lifecycle. It focuses on making threat analysis scalable for development teams by embedding it into workflows, rather than relying on slow, manual reviews that quickly fall out of date as systems change.

What VAST Changes in Threat Modeling

VAST is less a single worksheet and more a delivery-oriented method for embedding threat modeling into fast-moving engineering workflows. Its core value is scale: instead of treating threat analysis as a one-time review, it aims to make threat thinking repeatable, lightweight, and usable by product and development teams as systems evolve.

That matters because traditional threat modeling often breaks down when teams ship frequently, architecture changes quickly, or the backlog outpaces manual review. VAST shifts the emphasis from rare, heavyweight workshops to a process that can travel with the product and stay relevant as the design changes.

How VAST Fits the Software Delivery Lifecycle

VAST is designed for environments where security work has to keep pace with CI/CD, platform change, and distributed ownership. Rather than sitting outside delivery, it is meant to be integrated into planning, design, build, and release activities so threat analysis happens closer to the point where decisions are made.

That integration is important because threat models lose value when they lag behind implementation. In practice, VAST is most useful where security teams need a model that can be refreshed often, shared across roles, and applied consistently across many services without turning every review into a bespoke exercise.

What VAST Is Good At

VAST is strongest when organisations want broad coverage with low friction. It is well suited to portfolio-level programs, platform teams, and software organisations that need a common approach for many applications, services, or microservices rather than a deep manual analysis for only a few high-risk systems.

Its practical strength is repeatability. By standardising how teams think about threats, VAST helps reduce dependence on specialist bottlenecks and makes it easier to keep pace with design changes, new dependencies, and evolving attack surfaces.

That said, the method still depends on the quality of the inputs. A scaled process does not eliminate the need for good architecture context, clear ownership, and timely updates when the system or its dependencies change.

Where VAST Can Fall Short

VAST can be weakened if teams treat it as a checkbox rather than an operating model. If the workflow is too lightweight, it may miss deeper design flaws; if it is too heavy, teams may stop using it. The balance between speed and rigor is the central trade-off.

It can also struggle where engineering groups lack shared architecture language or where threat findings are not connected to backlog work. In those cases, the model may generate documentation without changing design decisions, which defeats the point of embedding it into delivery.

Risk and Threat Considerations

Threat modeling approaches create risk when they are too slow to match the rate of change, or when they are adopted inconsistently across teams. The result is blind spots in design, missed trust-boundary changes, and delayed recognition of new attack paths as systems and dependencies evolve.

Failure mechanism: Manual or infrequent reviews can lag behind architecture change, leaving teams with stale assumptions about data flow, trust boundaries, and exposed components. Attackers benefit when security analysis does not keep pace with delivery because exploitable design issues remain unchallenged for longer.

Impact: Weak or outdated threat analysis can translate into preventable control gaps, insecure integration decisions, and slower remediation of design-level flaws that are harder to fix after release.

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 SAMM, CIS Controls v8 and OWASP ASVS set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0GV.RM-01 — Risk Management StrategyVAST operationalises repeatable threat-model risk management across delivery.
Recommendation — Embed threat modeling into the software delivery risk strategy so design risks are identified before release.
OWASP SAMMD-SD — Secure ArchitectureVAST supports building threat analysis into secure design and development practices.
Recommendation — Integrate threat modeling into secure design activities and keep findings connected to engineering work.
MITRE ATT&CKAdversary Tactics and TechniquesThreat modeling maps attack paths and abuse cases to adversary techniques.
Recommendation — Map likely abuse paths to attacker techniques and use them to prioritise defensive coverage.
CIS Controls v8CIS-17 — Incident Response ManagementVAST helps teams prepare for likely abuse paths that should feed response planning.
Recommendation — Feed modeled attack paths into response planning so likely failures are rehearsed before incidents.
OWASP ASVSV15 — Secure Coding and ArchitectureVAST reinforces architecture-level security decisions during design and implementation.
Recommendation — Use architecture threat analysis to drive secure design choices and validate them during implementation.

Practitioner Guidance

Why practitioners should care: VAST is most useful when security must be built into delivery without becoming a release blocker. The practical question is not whether teams perform threat modeling, but whether they can do it often enough that the analysis still reflects the current system.

Practitioner note: The method works best when it is tied to real workflow points such as design review, major change, and release gating, with clear ownership for turning findings into backlog items. If the output is not actionable in the delivery process, the model will degrade into paperwork.

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.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org