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

Acceptance testing

Acceptance testing is the phase in the software testing process where the software is evaluated to determine whether it satisfies the specified requirements and is ready for deployment. End users or stakeholders typically conduct this type of testing to ensure the software meets their expectations and business needs. Acceptance testing is often the final phase before the software is released.

There are two main types of acceptance testing: User Acceptance Testing (UAT) and Operational Acceptance Testing (OAT). Each type comes from a different perspective and together they give a better understanding of software functionality and resiliency.

User Acceptance Testing (UAT):

  • Objective: To validate that the software meets the business requirements from the end user’s perspective
  • Participants: End users or end user representatives, business analysts, and other stakeholders
  • Execution: Users perform real-world scenarios and tasks to assess the...