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

Graphical use cases and misuse cases

Graphical use and misuse cases can be represented visually in diagrams, typically using the Unified Modeling Language (UML) notations. The Object Management Group (OMG) is an international, open-membership, not-for-profit technology standards consortium. UML is one of the standards developed and maintained by the OMG.

UML use cases describe legitimate interactions with the software, while misuse cases focus on potential misuse, abuse, or security threats. Next, I’ll provide examples of both graphical use cases and misuse cases.

Graphical use case diagram

In a use case diagram, you can represent use cases and actors visually. Here’s a simple example:

Figure 2.1 – Example graphical use case diagram

Figure 2.1 – Example graphical use case diagram

In this diagram, the User actor interacts with the Login use case, indicating that users log in to the system.

This diagram represents a legitimate user interaction scenario.

Graphical misuse...