Skip to main content

Threat Modeling Manifesto

Secure Your Code with Threat Modeling

As a software developer, security should be a top priority. By proactively identifying and addressing potential vulnerabilities, you can significantly reduce the risk of breaches and data loss.

What is Threat Modeling? 

Threat modeling is a systematic approach to identifying, assessing, and mitigating security threats. It involves looking at your system from a hacker's perspective to uncover weaknesses and devise strategies to protect against attacks. See the OWASP Cheat Sheet 

Why is Threat Modeling Important?

  • Proactive Security: By anticipating potential threats, you can take steps to prevent them.
  • Risk Mitigation: Identify and address vulnerabilities before they can be exploited.
  • Regulatory Compliance: Adhere to industry standards and regulations.
  • Enhanced Security Posture: Strengthen your overall security posture.

How to Get Started with Threat Modeling 

The Threat Modeling Manifesto provides a valuable framework for implementing threat modeling in your development process. It outlines key principles and best practices to guide your efforts. See the OWASP Cheat Sheet for a framework to organize your threat modeling process.

Learn from the Experts

Watch this video to hear from experienced practitioners who share their insights and experiences with threat modeling.

By incorporating threat modeling into your development workflow, you can build more secure and resilient software.

VIDEO: OWASP Threat Modeling discussion from the OWASP Projects Spotlight series

https://www.threatmodelingmanifesto.org/

OWASP Threat Modeling Cheat Sheet

Nist Glossary

NIST SP 800-53 Rev. 5


Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Unit Testing - What to Test

This I wrote to answer a question that came up when we were discussing our software process and I was training developers on how to unit test. It seems a simple enough question, but I kept pondering it and delving deeper until I realized I needed to write this monograph. What unit tests should we write? How do we know what to test? Ideally, unit tests should cover every path through the code. It should be your chance to see every path through your code works as expected and as needed. If you are practicing Test Driven Development then it's implied everything gets a test. In the real world, you might not be allowed to test everything - for instance, if the testing suite ends up taking a week to run, then the world will have changed by the time it finishes and the test results will be obsolete. Unit testing at it's basic is testing an object, a method - the smallest unit of your code that it can test independently. It should test the inputs "goes into" an...
Post a Comment
Read more

Risk Mitigations for Custom Applications

  In many healthcare applications, often due to the cloistered nature of the use cases – e.g. it will only be accessed by users authorized in a particular facility, such as an operating room suite – the needs for Authentication and Authorization are minimized when the system is designed and implemented. This presents a risk as soon as you allow for the possibility of users with ill-intent or that otherwise want to operate outside their given roles. Custom applications need to consider these possibilities and implement the following measure to ensure the integrity of the system. 1.   Authentication and Authorization Controls: Multi-Factor Authentication (MFA): Implement MFA for all user logins. This adds an extra layer of security beyond just a username and password. Role-Based Access Control (RBAC): Grant users access only to the data and functionalities they need for their specific role. This minimizes the potential for unauthorized access. Strong Password Policies: ...
Post a Comment
Read more

You don't really know who you're talking to online...

The following is a story that I think highlights the assumptions that get you into trouble online... https://www.proofpoint.com/us/blog/threat-insight/i-knew-you-were-trouble-ta456-targets-defense-contractor-alluring-social-media This is particularly scary since we found so much utility in online connections during the pandemic and out of necessity, started trusting more online. Please note the timeline for this breach - it was a long, slow process, a key factor in many 'cons'. "Build trust" is a key first step, once someone has identified you as a party. You think...you're convinced you know who your talking to, but if you don't triangulate the identity with some non-online, ideally in-person information, you shouldn't trust. And even if you do get what seems like real-life confirmations of identity, you must look at questioning motives, needs, and keeping danger at arms-length. Online includes email, texting (sms), application chatbots, voice communicati...
Post a Comment
Read more