Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Crafting Secure Software
  • Toc
  • feedback
Crafting Secure Software

Crafting Secure Software

By : Greg Bulmash, Thomas Segura
5 (1)
close
Crafting Secure Software

Crafting Secure Software

5 (1)
By: Greg Bulmash, Thomas Segura

Overview of this book

Drawing from GitGuardian's extensive experience in securing millions of lines of code for organizations worldwide, Crafting Secure Software takes you on an exhaustive journey through the complex world of software security and prepares you to face current and emerging security challenges confidently. Authored by security experts, this book provides unique insights into the software development lifecycle (SDLC) and delivers actionable advice to help you mitigate and prevent risks. From securing code-writing tools and secrets to ensuring the integrity of the source code and delivery pipelines, you’ll get a good grasp on the threat landscape, uncover best practices for protecting your software, and craft recommendations for future-proofing against upcoming security regulations and legislation. By the end of this book, you’ll have gained a clear vision of the improvements needed in your security posture, along with concrete steps to implement them, empowering you to make informed decisions and take decisive action in safeguarding your software assets.
Table of Contents (11 chapters)
close
Appendix: Glossary of Acronyms and Abbreviations: Index

Threat modeling

There are multiple approaches and tools in threat modeling, but at its core, there are three main areas: mapping data flows, analyzing attack surfaces, and assessing the impacts of failure.

The Open Web Application Security Project (OWASP) has a three-step threat-modeling process:3

  1. Decompose the application.
  2. Determine and rank threats.
  3. Determine countermeasures and mitigation.

Decompose the application

This starts with understanding the use cases for the application. For example, with a game, one use case might be to play the game, while another might be to top up tokens from the in-app store.

Then, identify the entry points where an attacker could interact with the application, resources, and assets that would be of interest to an attacker, and the trust levels and access rights the application grants to external entities such as users, tech support, moderators...

bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete