Prerequisite – Threat Modelling, DFD Based Threat modelling | Set 1
Visual representation using DFD:
DFD is iterative in nature. Thus modelling a system involves construction of different levels of DFD. This means to accurately reflect the system, DFD must be organized in a hierarchical way. Following the various shapes that are used in a DFD:
- Process –
Each process in a DFD is given a unique number where sub process will have a number prefixed with parent process number. Process means an entity that performs a specific task on a given data. Following is the shape for a process:
- Multiple process –
This means process has sub process and the sub process number is prefixed by the parent process number. For example parent process number is 1. Then sub process will have number 1.1 and sub sub process will have number 1.1.1 and so on. Shape for Multiple process is as follows:
- External entity –
It can only interact at Entry point or exit point and is located outside the system. It may only interact with process or multiple process. It can be either source of data or destination of data. Below is the shape for an external entity used in DFD:
- Data store –
It is the place where data is stored or from where data is retrieved. It can only interact with process or multiple process. Shape for Data Store is as follows:
- Data flow –
This is used to show the movement of data between the elements. Below is the shape for Data Flow:
- Trust boundary –
It is a boundary between trust levels or privileges. Following is the shape for trust boundary:
DFD starts with a overall context level diagram that represents the whole system as a single multiple process. Each node is then a more detailed DFD representing other processes.
Determining threats –
This is the last step in threat modelling a system. After creating a DFD, next step is to identify the goals adversary might have in the system. These goals are then used to determine the threat paths, locate entry/exit points and follow the data through the system to understand what data is supplied to which node.
Before going forward we will first understand what a threat path is. Threat path is a sequence of process nodes that perform some sort of security critical operation and are thus vulnerable to an attack. All the process nodes where there is a change or action on behalf of data are susceptible to threats.
Following are the series of steps conducted in this phase.
Threat profile –
This is the security design specification that describes following two things: first the possible goals of an adversary in system and second and the most important the vulnerabilities that exist due to these goals.
Each identified threat should either be prevented or mitigated. The threat profiles encompasses following key areas:
- Identify the threats –
Threat identification is the very important step towards building a secure system. Identifying threats is a 3 step process where first step involves analyzing each entry/exit point, second steps involves identifying the nature and type of critical processing occurring at entry/exit points and third and the last step involves thinking and describing how entry/exit point might be attacked. Identifying threats is not an easy process to do. It involves asking questions like:
Is it possible for an adversary to gain access to asset without being audited or by skipping access controls or by acting as another user?
How an adversary can use or manipulate data to retrieve information from the system or edit information in the system or modify/control the system or gain additional privileges or cause system to fail or become unusable.
These are just the basic questions. It requires a lot of brainstorming on the part of security team to identify as many possible threats.
The next step in identifying threats is threats classification. STRIDE is one of the method that we use in conjunction with DFD for threat classification. We have discussed STRIDE in previous article.
- Investigate and analyse the threats –
After identifying threats next step is to conduct a in depth analysis of identified threats to determine vulnerable areas and valid attack paths.
Threat trees are used for this purpose. There are two ways to express a threat tree: one is the graphical way, another is using the textual representation.
Basic structure of a threat tree consists of a root node and child nodes. Each child node represents a condition needed for the adversary to find and identify the threats. The procedure to identify the vulnerabilities involve beginning at a node with no child and then traversing is done in bottom up manner up to the root.
Another step in analyzing threats involves determining risk of threats and threat conditions. This is done by using DREAD Model. We have discussed this model in previous article.
- Mitigate the vulnerabilities caused by the threats –
Till this point all threats have been identified and resolved. If any threat remains still unresolved then it will result into a vulnerability. Upon completion of threat tree, attack paths are identified. If any attack path is not mitigated, it will result in a Vulnerability.A threat modelling document consisting of threats, threat tree, vulnerabilities and mitigation’s This threat document will be used in design phase as security specification document and in testing phase as a base to identify the vulnerable areas of the system.