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

Phases

Software penetration testing typically involves several phases to ensure a comprehensive evaluation of the security posture of a system or application. The exact phases may vary depending on the methodology or framework followed, but the following are commonly recognized phases in penetration testing:

  1. Pre-engagement:
    • Scope Definition: Clearly define the scope of the penetration test, specifying what systems, networks, and applications are within the testing boundaries.
    • Rules of engagement: Establish rules and guidelines for the testing team, including what actions are permitted, the testing timeframe, and any constraints.
  2. Information gathering (reconnaissance):
    • Passive reconnaissance: Collect information without directly interacting with the target, such as through public sources or social media. Passive reconnaissance uses open-source intelligence (OSINT) techniques to gather publicly available information that can assist in later phases.
    • Active reconnaissance: Gather...