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 dynamic 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.

Figure 4.15 shows an example sequence diagram for a simple ticket purchase:

Figure 4.15 – Sequence diagram for ticket purchase

Figure 4.15 – Sequence diagram for ticket purchase

In the diagram, the patron requests to add tickets to the order. The Order class passes the request on to the ticket class for each ticket to lock the ticket so others cannot purchase. After the tickets are locked, the patron requests to create a login. The login is passed onto the Person class. Next, the patron pays with a credit card. The message is passed from the Order class to the Payment class, and we see the stereotype and OCL pre-condition marked in the note. At the end, a confirmation page is passed back to the patron.

Figure 4.16 shows an activity diagram...