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

An example of enterprise threat 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. We will demonstrate unit tests in three languages, PHP, Java, and Python, to test the Person class from our object model. This chapter will test a single method, but all methods with interesting behavior should have unit tests written. If you remember from our object, the create_login method takes in a password. We want to ensure the password has a length of eight characters or greater, uses both uppercase and lowercase characters, and has at least one symbol.

Note:

Naming conventions and consistency are important to improve software quality. We are using an example across many programming languages. In some languages, create_login should be written as createLogin to maintain language convention. You will see this later in the JUnit...