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

Stereotypes

UML allows you to extend and customize its standard notations and semantics through stereotypes. Stereotypes are a way to add domain-specific or application-specific information to your UML models. When representing security requirements in UML, you can use stereotypes to indicate specific security-related elements or aspects within your diagrams. Developers use common stereotypes, but it is essential to realize you can build your own and are not limited to the common ones. Here are some common UML stereotypes and how they can be used to represent security requirements:

  • <<security>>: This stereotype can be applied to various UML elements to indicate that they have security implications. Here are some examples:
    • A class with <<security>> stereotype might imply that it contains sensitive data or requires access control
    • A use case with <<security>> stereotype may indicate that it involves authentication or authorization
  • <&lt...