0%

Book Description

In the race to remain competitive, development teams in many companies are under tremendous pressure to create software on tight deadlines. And in most cases, that means dealing with security bugs only after software is released. But offensive testing and incident response are poor substitutes for good code, strong architecture, and threat-based design.

In this ebook, April C. Wright—security risk and compliance program advisor for a Fortune 15 company—teaches InfoSec professionals how to promote security as an integral part of an organization’s software development life cycle (SDLC). You’ll learn how to analyze existing development processes, gain insight into how developers and other stakeholders view software development, receive practical advice for including secure practices throughout the lifecycle, and learn how to track performance and success of your program.

  • Get guidelines for evaluating your SDLC and rebuilding your development program
  • Understand how developers, project managers, business execs, customers, and other key stakeholders each approach software development
  • Gain active stakeholder participation and management support for SDLC security improvements
  • Work directly with stakeholders to explain secure development, and push for change through policy and compliance
  • Increase software security awareness by integrating development teams with security teams
  • Get started through sample checklists and planning documents

Table of Contents

  1. Fixing an Insecure Software Life Cycle
    1. The Status Quo of Software Development Life Cycles
    2. Understanding Stakeholders and Existing Process Mechanics
      1. Stakeholders Have Differing Points of View
      2. Analyzing Existing Processes
      3. How Does Security Affect the Stakeholder?
      4. How Does Security Affect the Process?
    3. Preparing to Rebuild the Program
      1. Key Program Metrics
      2. Phased Goals
      3. Gaining Management Support
      4. Active Stakeholder Participation
    4. Working as a Unified Team
      1. The Importance of Collaborating as One Team
      2. Discussions, Not Just Bug Submissions
      3. Positive Interactions
      4. Rotating Work Assignments
      5. Embedded Security Liaisons
    5. Setting Expectations for Stakeholders
      1. Using Organizational Policy to Create a Need
      2. Compliance
      3. Knowledgeable Humans
      4. The Development Style Guide and Standard Libraries
      5. Checklists
    6. Sample Checklists and Planning Documents
      1. Handling Checklists
      2. Sample Planning Phase Checklist
      3. Sample Privacy Questionnaire
      4. Sample “Design/Architecture” Phase Checklist
      5. Sample “Development/Implementation” Phase Checklist
      6. Sample Policy Statement
    7. Conclusion
3.17.79.60