I just downloaded a copy of the threat modeling guide for IT infrastructure, released by Microsoft on June 2009. Not sure if you’ve heard of this, but it is kind of a guideline which helps enterprises assess their security/compliance needs with a 5 step process –vision, model, validate, identify threats and mitigate risks. This apparently helps to prioritize investments in IT security and will need a proactive approach to assist you in your efforts to protect your organization’s assets and sensitive information. This guide provides an easy-to-understand method that enables you to develop threat models for your IT environment and prioritize your investments in IT infrastructure security.
Why should any kind of modeling be necessary?
- For viability and reputation
- To be able to conduct day to day business operations smoothly
- If an attack exposed confidential information, it could be perceived as a one that failed to do what was necessary to protect itself
- Failure to protect customer information could lead to legal obligations
Apparently, the threat modeling guide can be used to do just that. It allows you to determine what threats exist that could affect your organization’s IT infrastructure, helps you identify threat mitigations to protect resources and sensitive information, and helps you prioritize the identified threats so that you can manage your security efforts in a proactive manner.
IT infrastructure threat modeling should be incorporated into an organization’s IT mindset as a matter of policy, much like any other part of the validation, implementation, and installation process. Threat modeling in the name of secure infrastructure should be performed throughout the technology implementation process, much like any other component that is measured for performance, usability, and availability.
Start the IT infrastructure threat modeling process from the onset of any new technology project, because doing so might reveal weaknesses in your architecture or implementation and design planning that could require significant changes to the project. Design changes early in the implementation process are significantly less expensive than a complete reimplementation after a failed attempt that wasn’t well planned, or if an insufficiently secured system achieves production status.
In my next post, I will talk about how NetEnrich can help.