

It is fundamental to identify who would want to exploit the assets of a company, how they might use them against the company, and if they would be capable of doing so. You should be familiar with the following terms that will be used throughout this cheat sheet.Ī threat agent is an individual or group that is capable of carrying out a particular threat. The principles in the document apply equally to designing and building systems such as network infrastructures or server clusters as they do to designing or developing desktop, mobile, or web applications. Note that throughout the document, the terms "systems" and "applications" are used interchangeably.
Papers please cheat sheet software#
All developers, software and system designers, and architects should strive to include threat modeling in their software development life cycle. You do not need to be a security expert in order to implement the techniques covered in this cheat sheet.
Papers please cheat sheet how to#
This cheat sheet aims to provide guidance on how to create threat models for both existing systems or applications as well as new systems. Threat modeling is a structured approach of identifying and prioritizing potential threats to a system, and determining the value that potential mitigations would have in reducing or neutralizing those threats. Threat Modeling Cheat Sheet ¶ Introduction ¶ Reduce risk in risk log for verified treated risk Test risk treatment to verify remediation Select appropriate controls to mitigate the risk Map Threat agents to application Entry pointsĭefine the Impact and Probability for each threatĪgree on risk mitigation with risk owners and stakeholders Highlight Authorization per user role over the DFD

Manage to present your DFD in the context of MVCĭefine applications user roles and trust levels Insecure Direct Object Reference PreventionĬonsider Data in transit and Data at rest
