- Views: 16
- Report Article
- Articles
- Computers
- Programming
Threat Modelling: What Is It and How It Is Done?
Posted: Dec 07, 2019
Here is a hypothetical situation for you:
You are an architect and have been assigned a new project. You have to design a bridge that connects two remote mountainous areas. So you come up with a very beautiful design and get the best construction workers to work with high-quality materials and finish the project as soon as they can. Three days after its completion, a mild earthquake hits the region. It brings down the land around the bridge, and the bridge goes down with it.
After the disaster, you regret not taking into account the potential risks of any natural disasters happening in the area where you built the bridge. But is there anything you can do now, or is it too late?
No matter what task it is that you are working on, there is always a chance of something going wrong. You need to keep these risk factors in mind and plan accordingly. The process of software development also follows the same rule.
What is threat modeling?Threat modeling refers to the process of assessing any risks associated with a software development project and taking measures to prevent them from happening or minimize their effects. A large number of threats that software applications face are related to data and network vulnerabilities. Thus, they are the focus of most threat modeling activities.
Who is responsible for the threat modeling process?Many developers argue that taking care of such threats should be the network security team’s job. However, networking personnel are often unaware of the intricacies of the project. Only developers know every project inside out. Therefore, it is important that developers design projects while keeping all kinds of security risk factors in mind.
When is threat modeling performed?Suppose you have two options.
Think of all possible risks beforehand and put in place certain mechanisms to protect the system from those risks in the future after the project goes live.
Try to fix and save the system after an attack has been launched on it.
Which option would you choose?
Experts recommend developers to carry out the threat modeling process during the design phase because prevention is better than cure.
That being said, this is not a rule of threat modeling.
You are allowed to perform this task at any stage of the development process. However, if you do it at a later stage and then find a major security issue, you might have to come back to your initial development stage and start from scratch. This will cause the developers’ time, effort, and energy to go to waste.
The processThere are many different kinds of threat modeling techniques that are used by developers. However, in general, this is how the process goes:
As a developer, you need to lay down the scope of the model, that is, what areas the analysis is going to cover or how deep it will go.
Map out in detail how your software will be working and how the data will flow within the system as well as into/out of the system. A data flow diagram (DFD) could be a good way to represent this information.
Identify all the "actors", i.e. all the people or other programs that will be interacting with your system, and through what channels they will be doing so.
Next, you need to think of all the ways in which the system could be compromised, i.e. the risks.
Once you have identified the risks, you need to prioritize them. Assign a criticality level to each risk. That way, you can start off with the areas of the system that are at the highest risk, and work your way down from there.
After prioritizing the risks, you must get to work and brainstorm ideas to counter those risks. These could be in the form of changes to the software architecture, engineering process, or business or functional requirements, or other preventive and prescriptive measures.
It would be even better to carry out these steps in an iterative manner so that the system can evolve continuously and achieve maximum security levels.
Wrapping Up…I would like to lay stress on the importance of threat modeling with one closing comment:
No matter what stage or method you pick for conducting threat modeling for your project, you need to make sure that you or your fellow developers don’t skip out on this process entirely. Up until the project goes live, you can keep modeling potential threats and risks iteratively so that you can come up with software that is safe and secure from a maximum number of threats.
About the Author
Emily Williamson is a Technical Writer at Goodcore Software. It is a bespoke software development company in the UK. We focused on helping entrepreneurs, small, and medium businesses create competitive and winning software.
Rate this Article
Leave a Comment