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

Requirements gathering and specification

Software requirements can be broadly categorized into three main types: functional, non-functional, and constraints. These three categories help define what the software needs to do, how it should perform, and any limitations or restrictions that must be considered:

  • Functional requirements: Functional requirements specify what the software system should do regarding its features and capabilities. These requirements describe the system’s behavior and functionality, often in the form of use cases or user stories. Functional requirements answer questions such as “What does the software need to accomplish?” They can include features, user interactions, and data processing tasks. Examples of functional requirements include the following:
    • User authentication: Users must be able to create accounts, log in, and reset passwords. User authentication is an example that we will see on both sides of the functional and non-functional...