Threat Modeling: Secure System In Five Simple Steps

Shakshi ShiviHead Of Content
Envision that you are chipping away at another e-business site with a team of pundit developers and designers. Everything seems, by all accounts, to be going easily.
Envision that you are chipping away at another e-business site with a team of pundit developers and designers. Everything seems, by all accounts, to be going easily. And as the release date is approaching closer, the marketing team prepared self to proclaim the new website to the world; everybody begins to celebrate a joy of a successful launch of a website.
At that point alerts sound! The designed system is currently unavailable due to a DDoS attack from an obscure source. In the wake of researching, Developers' distinguish the weakness, as Slow HTTP DoS attacks on some website's portion.

Presently the inquiry emerges, Despite building a superb site, why couldn't developers shield it from vulnerabilities?

Designing and developing a secure system is a complex task, thus, for this reason, developers neglected to take measures. Additionally, they fail to ensure security by shielding it from the vulnerabilities ahead of time.

In this way, the response to anticipating such a situation in future can be resolved by entering a Threat Modeling.

Now let's take a brief about what Threat modeling is: Threat modeling is a conducive arrangement & well-organized procedures through which application developers can create security systems.

Frequently systems are intended to take into account business necessities. In any case, Threat Modeling is a methodology that helps companies recognize security dangers and vulnerabilities in the application amid the design phase. It is imperative because fixing security issues identified amid the testing stage are tedious as well as expensive too.

So before companies institute Threat Modeling methodology, let's understand this approach better with an instance.

Presume that 'Threat Modeling' has not been implemented on the existing site, an analyzer discovers amid the entrance testing stage that an aggressor/programmer can control the request while setting a solicitation. He can change the order cost and shipping address.

A couple of reasons why the website was open to such dangers are:
  • Clients were permitted to perform basic operations without re-confirmation.
  • Before handling the Input data approval was not completed
  • Delicate data, for example, system details, session identifiers or record data were uncovered in blunder reactions.
How might companies impede threat modeling to relieve such dangers later on?
As draftsmen, every company has an alternate way to deal with the threat modeling contingent upon the requirement in a business enterprise.

Underneath are the 5 stages to secure company's system through risk displaying.

Step 1: Recognize security targets
Comprehend security prerequisites and recognize conceivable dangers in business streams to accomplish destinations. The companies must consider the compliance or security-related prerequisites that are a part of the business destinations. For instance, amid inspecting, delicate data (e.g. SSN number, age and so forth.) ought not to get logged and the log document ought to be available to a particular arrangement of clients as it were.
Step 2: Identify resources and outer conditions
Unapproved access to resources, for example, information, code, and system data are the reason behind the threats happenings. The security designer needs to recognize a rundown of resources for being shielded from potential assailants. They should likewise recognize outside conditions which are not part of code, but rather may pose a risk to the system. Additionally, consider how the application would be accessed in the web server or the production surroundings. And, consider how database correspondence will occur in a private or public network.
Step 3: Recognize the trust areas
Developers must recognize trust areas along with the corresponding entry-exit focuses. The data are used to develop the data flow diagrams thus must be documented. As it characterizes the way to deal with client verification and input data validation along with error handling. As discussed above, in the e-business site case the request handling (order processing) system can be distinguished as a trust zone that will require a value acceptance check against the requested thing ID.
Step 4: Recognize the potential vulnerabilities & threats
Other than driving a wide search for threats under a defined path like STRIDE, consider threats that would, for the most part, affect the company's system. A few cases could be - broken validation, session management vulnerabilities, and SQL injections. Distinguish hazard inclined zones like poor input acceptances, over privileged accounts, frail secret key approaches, custom encryption, inadequate evaluating or logging, showing blunder or special case messages to end client.
Step 5: Recognize Document Threat Model
Threat Modeling is a frequentative procedure and documentation is an essential feature of the organization's team duties. Developers and designers can utilize documentation to make secure design and relieve design-related security threats. On the more, developers can utilize the documentation as security rules to alleviate security risks and analyzers to drive test cases to discover vulnerabilities in the system. It too helps the analyzer in making security-related experiments in addition to validation test cases for trust areas. Threat modeling begins with the designing stage and runs parallel with a compositional design. In addition, it is vital to recollect that there is no single way to deal with threat modeling. Also, to accomplish ideal results companies are advised to take a predefined approach, for example, STRIDE & DREAD.

For more insights, please visit my blogWordPress website - blog
You can also connect me on LinkedIn  

Comments (1)

Jim HornSQL Server Data Dude
Most Valuable Expert 2013
Author of the Year 2015

Hi Shakshi

Thanks for your submission.  889 words, completely original content, and reads fairly well.  The technical aspects of this article seem pretty solid, but I'm going to send this back to Draft / Author Review for some general readability editing.  When you're done go ahead and resubmit and I'll review from there.

Please separate paragraphs with a blank line, as without that an article can resemble a 'word wall' where everything jumbles together and can be difficult to read.

>fruitful dispatch, inculcate, buttonhole, the prerequisite in a venture, Addedly, ingressed, environ
These words are rarely used and may confuse people.  Keep in mind that if these are local slang than it might not translate well to a global audience.  I can appreciate that you're trying to tell a story and be somewhat entertaining in the process, but just make sure you don't lose people in the translation.

>as it were, Addedly,
There are some phrases here that do not add value and can be deleted.

>Now let's take a brief about what Threat modeling is: Threat modeling does not include
Please define something by what it is, not what it is not.  The 'is not' stuff can always be added later.

If terms are going to be introduced but not defined please at minimum provide a link to a definition.

Please provide a conclusion.

Feel free to self-promote in the 'About the Author' section, especially if you have other publications that readers of this one may be interested in reading.

For a lot more recommendations on how to score maximum points on articles check out Top 10 Ways To Write Rock Star Technical Articles

Thanks in advance.  I look forward to seeing this as a finished product.

Have a question about something in this article? You can receive help directly from the article author. Sign up for a free trial to get started.