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. Which of the following best describes integration testing?
    1. Testing the system as a whole to ensure it meets the specified requirements.
    2. Testing individual components or modules in isolation to ensure they function correctly.
    3. Testing the integration of different systems or subsystems to verify that they work together as intended.
    4. Testing the user interface and user interactions to ensure usability.
  2. What is the primary objective of system testing?
    1. To identify defects in the system’s design and architecture.
    2. To ensure that each individual component works correctly.
    3. To verify that the system meets its specified requirements and functions as expected.
    4. To evaluate the system’s performance under various conditions.
  3. Acceptance testing is typically performed by:
    1. Developers
    2. Quality Assurance (QA) team
    3. End users or stakeholders
    4. System architects
  4. Which of the following is NOT typically included in acceptance testing?
    1. Alpha testing
    2. Beta testing...