Book Image

Security-Driven Software Development

By : Aspen Olmsted
Book Image

Security-Driven Software Development

By: Aspen Olmsted

Overview of this book

Extend your software development skills to integrate security into every aspect of your projects. Perfect for any programmer or developer working on mission-critical applications, this hands-on guide helps you adopt secure software development practices. Explore core concepts like security specifi cation, modeling, and threat mitigation with the iterative approach of this book that allows you to trace security requirements through each phase of software development. You won’t stop at the basics; you’ll delve into multiple-layer att acks and develop the mindset to prevent them. Through an example application project involving an entertainment ticketing software system, you’ll look at high-profi le security incidents that have aff ected popular music stars and performers. Drawing from the author’s decades of experience building secure applications in this domain, this book off ers comprehensive techniques where problem-solving meets practicality for secure development. By the end of this book, you’ll have gained the expertise to systematically secure software projects, from crafting robust security specifi cations to adeptly mitigating multifaceted threats, ensuring your applications stand resilient in the face of evolving cybersecurity challenges.
Table of Contents (20 chapters)
Free Chapter
1
Part 1: Modeling a Secure Application
8
Part 2: Mitigating Risks in Implementation
13
Part 3: Security Validation

Capturing scenarios

Software use and misuse scenarios are valuable tools in software development and security. They help identify how the software is intended to be used, abused, or misused. Use scenarios focus on legitimate and expected interactions with the software, while misuse scenarios concentrate on potential security threats and vulnerabilities. Scenarios capture specifics about the users and the systems they are interacting with. Scenarios can capture how the current systems work, or they can be visionary of how they want the system to work. Here are examples of use scenarios:

  • User registration: Kate, a new user, creates an account by providing a username, email, and password, and she receives a confirmation email after the process is complete
  • Login: A registered user, Fred, enters his account by entering his credentials into the web page
  • Product purchase: A customer, Sally, adds items to their shopping cart, proceeds to checkout, and completes a purchase
  • ...