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

Self-assessment questions

  1. What is high coherence?
    1. A change in one subsystem will not affect any other subsystem
    2. Changes to one subsystem will have a high impact on the other subsystem
    3. Lots of miscellaneous and auxiliary classes, and almost no associations
    4. The classes in the subsystem perform similar tasks and are related to each other via many associations
  2. What is low coherence?
    1. The classes in the subsystem perform similar tasks and are related to each other via many associations
    2. Lots of miscellaneous and auxiliary classes, and almost no associations
    3. Changes to one subsystem will greatly impact the other subsystem
    4. A change in one subsystem will not affect any other subsystem
  3. What is low coupling?
    1. The classes in the subsystem perform similar tasks and are related to each other via many associations
    2. Lots of miscellaneous and auxiliary classes, and almost no associations
    3. Changes to one subsystem will have a high impact on the other subsystem
    4. A change in one subsystem will...