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

Types of tests

There are various types of penetration testing in software, each focusing on different security aspects. Here are some common types:

  • Black box testing:
    • Testers have no prior knowledge of the target system
    • Simulates an external hacker with no insider information
    • Helps identify vulnerabilities that can be exploited without internal knowledge
  • White box testing:
    • Testers have complete knowledge of the target system’s internal workings
    • Simulates an attack by someone with insider information
    • Helps identify vulnerabilities that might be exploited with insider knowledge
  • Gray box testing:
    • Testers have partial knowledge of the target system in terms of some information on the environment, such as the OS or compiler, but no access to source code
    • Simulates an attack by someone with limited insider information
    • Aims to find vulnerabilities that could be exploited with partial knowledge
  • Web application testing:
    • Focuses on identifying vulnerabilities in web...