CISSP Notes
CISSP Notes
Visual, Agile, and Simple Threat (VAST) is a threat modeling concept that integrates
threat and risk management into an Agile programming environment on a scalable
basis (see Chapter 20, “Software Development Security,” regarding Agile).
These are just a few in the vast array of threat modeling concepts and
methodologies available from community groups, commercial entities, government
agencies, and international associations.
Potential threats to your business are broad and varied. A company faces threats
from nature, technology, and people. Always consider the best and worst possible
outcomes of your organization's activities, decisions, and interactions. Identifying
Classification: Internal
threats is the first step toward designing defenses to help reduce or eliminate
downtime, compromise, and loss.
Process for Attack Simulation and Threat Analysis (PASTA) is a seven-stage threat modeling
methodology. PASTA is a risk-centric approach that aims at selecting or developing
countermeasures in relation to the value of the assets to be protected. The following
are the seven steps of PASTA:
Stage I: Definition of the Objectives (DO) for the Analysis of Risks
Stage II: Definition of the Technical Scope (DTS)
Stage III: Application Decomposition and Analysis (ADA)
Stage IV: Threat Analysis (TA)
Stage V: Weakness and Vulnerability Analysis (WVA)
Stage VI: Attack Modeling & Simulation (AMS)
Stage VII: Risk Analysis & Management (RAM)
Each stage of PASTA has a specific list of objectives to achieve and deliverables to
produce in order to complete the stage. For more information on PASTA, please
see Risk Centric Threat Modeling: Process for Attack Simulation and Threat Analysis (Wiley,
2015), by Tony UcedaVelez and Marco M. Morana.
Threat modeling isn't meant to be a single event. Instead, it's meant to be initiated
early in the design process of a system and continue throughout its lifecycle. For
example, Microsoft uses a Security Development Lifecycle (SDL)
(www.microsoft.com/en-us/securityengineering/sdl) with the motto of “Secure by
Design, Secure by Default, Secure in Deployment and Communication” (also known
as SD3+C). It has two goals in mind with this process:
To reduce the number of security-related design and coding defects
To reduce the severity of any remaining defects
Classification: Internal