Core Software Security - James Ransome and Anmol Misra


Below is an outline for the ebook "Core Software Security" by James Ransome and Anmol Misra. If you’re a member, then you can log into the Library and view it in your browser using the email address you signed up with. PS. Only members can successfully log in.

  • Click HERE to log into the library (Members only).
  • Folder: Books and Guides > Security eBooks

If you are having issues logging in, please check the following help guide, HERE.



1. Introduction

1.1.1. The Importance and Relevance of Software Security
1.1.2. Software Security and the Software Development Lifecycle
1.1.3. Quality Versus Secure Code
1.1.4. The Three Most Important SDL Security Goals
1.1.5. Threat Modeling and Attack Surface Validation
1.1.6. Chapter Summary - What to Expect from This Book
1.1.7. References


2. The Secure Development Lifecycle

2.1.1. Overcoming Challenges in Making Software Secure
2.1.2. Software Security Maturity Models
2.1.3. ISO/IEC - Information Technology - Security Techniques - Application Security
2.1.4. Other Resources for SDL Best Practices SAFECode U.S. Department of Homeland Security Software Assurance Program National Institute of Standards and Technology MITRE Corporation Common Computer Vulnerabilities and Exposures SANS Institute Top Cyber Security Risks U.S. Department of Defense Cyber Security and Information Systems Information Analysis Center (CSIAC) CERT, Bugtraq, and SecurityFocus
2.1.5. Critical Tools and Talent The Tools The Talent
2.1.6. Principles of Least Privilege
2.1.7. Privacy
2.1.8. The Importance of Metrics
2.1.9. Mapping the Security Development Lifecycle to the Software Development Lifecycle
2.1.10. Software Development Methodologies
2.1.11. Waterfall Development
2.1.12. Agile Development
2.1.13. Chapter Summary
2.1.14. References

3. Security Assessment (A1): SDL Activities and Best Practices

3.1.1. Software Security Team Is Looped in Early
3.1.2. Software Security Hosts a Discovery Meeting
3.1.3. Software Security Team Creates an SDL Project Plan
3.1.4. Privacy Impact Assessment (PIA) Plan Initiated
3.1.5. Security Assessment (A1) Key Success Factors and Metrics Key Success Factors Deliverables Metrics
3.1.6. Chapter Summary
3.1.7. References

4. Architecture (A2): SDL Activities and Best Practices

4.1.1. A2 Policy Compliance Analysis
4.1.2. SDL Policy Assessment and Scoping
4.1.3. Threat Modeling/Architecture Security Analysis Threat Modeling Data Flow Diagrams Architectural Threat Analysis and Ranking of Threats Risk Mitigation
4.1.4. Open-Source Selection
4.1.5. Privacy Information Gathering and Analysis
4.1.6. Key Success Factors and Metrics
4.1.7. Key Success Factors
4.1.8. Deliverables
4.1.9. Metrics
4.1.10. Chapter Summary
4.1.11. References

5. Design and Development (A3): SDL Activities and Best Practices

5.1.1. A3 Policy Compliance Analysis
5.1.2. Security Test Plan Composition
5.1.3. Threat Model Updating
5.1.4. Design Security Analysis and Review
5.1.5. Privacy Implementation Assessment
5.1.6. Key Success Factors and Metrics Key Success Factors Deliverables Metrics
5.1.7. Chapter Summary
5.1.8. References

6. Design and Development (A4): SDL Activities and Best Practices

6.1.1. A4 Policy Compliance Analysis
6.1.2. Security Test Case Execution
6.1.3. Code Review in the SDLC/SDL Process
6.1.4. Security Analysis Tools Static Analysis Dynamic Analysis Fuzz Testing Manual Code Review
6.1.5. Key Success Factors
6.1.6. Deliverables
6.1.7. Metrics
6.1.8. Chapter Summary
6.1.9. References

7. Ship (A5): SDL Activities and Best Practices

7.1.1. A5 Policy Compliance Analysis
7.1.2. Vulnerability Scan
7.1.3. Penetration Testing
7.1.4. Open-Source Licensing Review
7.1.5. Final Security Review
7.1.6. Final Privacy Review
7.1.7. Key Success Factors
7.1.8. Deliverables
7.1.9. Metrics
7.1.10. Chapter Summary
7.1.11. References

8. Post-Release Support (PRSA1-5)

8.1.1. Right-Sizing Your Software Security Group The Right Organizational Location The Right People The Right Process
8.1.2. PRSA1: External Vulnerability Disclosure Response Post-Release PSIRT Response Post-Release Privacy Response Optimizing Post-Release Third-Party Response
8.1.3. PRSA2: Third-Party Reviews
8.1.4. PRSA3: Post-Release Certifications
8.1.5. PRSA4: Internal Review for New Product Combinations or Cloud Deployments
8.1.6. PRSA5: Security Architectural Reviews and Tool-Based Assessments of Current, Legacy, and M&A Products and Solutions Legacy Code Mergers and Acquisitions (M&As)
8.1.7. Key Success Factors
8.1.8. Deliverables
8.1.9. Metrics
8.1.10. Chapter Summary
8.1.11. References

9. Applying the SDL Framework to the Real World

9.1.1. Introduction
9.1.2. Build Software Securely Produce Secure Code Manual Code Review Static Analysis
9.1.3. Determining the Right Activities for Each Project
9.1.4. The Seven Determining Questions
9.1.5. Architecture and Design
9.1.6. Testing Functional Testing Dynamic Testing Attack and Penetration Testing Independent Testing
9.1.7. Agile: Sprints
9.1.8. Key Success Factors and Metrics Secure Coding Training Program Secure Coding Frameworks (APIs) Manual Code Review Independent Code Review and Testing (by Experts or Third Parties) Static Analysis Risk Assessment Methodology Integration of SDL with SDLC Development of Architecture Talent
9.1.9. Metrics
9.1.10. Chapter Summary
9.1.11. References

10. Pulling It All Together: Using the SDL to Prevent Real-World Threats

10.1.1. Strategic, Tactical, and User-Specific Software Attacks Strategic Attacks Tactical Attacks User-Specific Attacks
10.1.2. Overcoming Organizational and Business Challenges with a Properly Designed, Managed, and Focused SDL
10.1.3. Software Security Organizational Realities and Leverage
10.1.4. Overcoming SDL Audit and Regulatory Challenges with Proper Governance Management
10.1.5. Future Predications for Software Security The Bad News The Good News
10.1.6. Conclusion
10.1.7. References

11. Appendix


Next steps:

This article was contributed by Jason Jacobs from Guyana. Jason is a member of the Caribbean CSPA. 


Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.