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

Example of the enterprise secure object model

Throughout this book, we will build a secure design for an event ticketing system. Envision a software system that allows a box office or a website to sell tickets to a famous musical concert or theatre event.

The following figure shows a small sample of classes, relationships, and attributes for our ongoing event ticketing system example.

Figure 3.10 – Example UML class diagram

Figure 3.10 – Example UML class diagram

This example has four classes represented by the boxes with Cs. The guillemets (double chevrons, << >>) and the word confidential represent one stereotype. In this example, the stereotype is applied to the aggregation of payments by the Order class and directly to the Payments class. The lines show an association between customers and orders. The diamonds at the end of the lines between order, tickets, and payment classes show the aggregation. Aggregations are generally represented as one-to-many in the code. The...