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

The principles of unit testing

Following certain principles helps create practical and maintainable unit tests. Here are some fundamental unit testing principles:

  • Isolation: Each unit test should be isolated from other tests to ensure that the outcome of one test does not affect another. Isolation helps identify the cause of failures and makes tests more predictable.
  • Independence: Unit tests should be independent of each other. The order in which tests are executed should not matter, and each test should produce consistent results regardless of the context in which it is run.
  • Fast fxecution: Unit tests should be fast to execute. Fast execution encourages developers to run tests frequently, providing quick feedback on the code changes. Rapid tests are essential for incorporating testing into the development workflow.
  • Repeatable: A unit test should produce the same results every time it is executed. A repeatable test ensures that failures can be consistently reproduced...