Some actions could result in DoS, through users spamming actions which require a lot of resources, or result in quota limits being reached on other APIs.Originally published by Alex Wauters on June 26th 2019 8,203 reads AlexWauters Alex Wauters Software Developer Cardiogram If you want to achieve security by design in your project and mitigate cyber threats before they hit your applications, you will need to discuss these risks with your team and plan ahead.
Microsoft Threat Modeling Tool 2019 Software Development MayEven business analysts who are not familiar with secure software development may identify threats that a developer or security expert did not foresee.
The best way to uncover as many threats as possible and make sure everyone knows them is to discuss them together. Invite at least the developers, someone who knows how the systems are deployed, someone from security team and your product owner. If more time is needed, you can always organize a follow-up session. For each asset passing through your data flow, go through a checklist and discuss potential security risks. Rate each risk (e.g. Discuss and decide what you will do about each risk Pick a use case You can discuss any number of use cases for your application in a threat modeling session, but for your first session its probably better to start with one or two use cases at most. I suggest you start with your authentication use case (how do people identify themselves and gain access) as well as one of the main flows of your application (for Medium it could be about a user posting a new story, for Lyft you might pick a user calling for a driver). You can do this step during the session, or prepare it beforehand. The data flows start with the rectangle at the left, the user actors performing the use case. It could be a web application, or a collection of applications. Collections of services can be hidden behind a double circle. You might want to encapsulate a service in this way in order to focus the exercise on other data flows without diving in too deep into the other services (yet). Microsoft Threat Modeling Tool 2019 Download The FrontStatic files have their own sets of risks (such as third-party injection) and may not be behind a trust boundary (not requiring authentication to download the front-end files.). Well get to trust boundaries in a minute. These could be anything ranging from a database, to files, to queues, to data contained in logs Attackers may be especially interested in this data, either because it is useful on its own or because it could be manipulated to become useful (e.g. A trust boundary means that data flows going through this line are not trusted. Typically a flow will need to present authentication credentials, and the sessions previously associated with that flow will no longer be valid across the boundary. Michael Henriksen has created a library which you can import in draw.io. In draw.io go to File - Open Library - Url, and refer to the raw file on github. OWASP Threat Dragon is a web app tool which saves your diagrams on github. Microsofts Threat Modeling tool is a Windows native application where you an draw data flows, annotate them and generate reports. Its not as simple as the approaches listed above, Windows-only and you need to save the diagrams on your local disk. Or a super-user could deny having accessed sensitive information such as employee salaries.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |