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

Examples of enterprise integration testing

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 popular music concert or theatre event. In Chapter 12, we looked at the integration testing of a web service called a MySQL stored procedure, called lock_seats. A significant challenge of developing large software systems is the complexity that comes from the dependency between subsystems. To allow us to test early, we create a stub in MySQL with a hardcode output response dependent on the input:

DELIMITER //
CREATE PROCEDURE lock_seats(IN inseat CHAR(6),OUT result VARCHAR(255))
BEGIN
  IF inseat = "AA101" THEN
    SET result = "Seat AA101 Locked";
  ELSE
    SET result = CONCAT('Seat ', inseat, ' Already Taken');  END IF;
END //

If we have the stored procedure...