The 7 qualities of highly secure software
By: Mano Paul
Publisher: CRC Press
Published: 2012
Place of publication: Boca Raton, FL
Language: eng
Number of pages: 144
ISBN-13: 9781439814468
Subjects: Development; Computer security; Software engineering; Computer software
Other titles: Seven qualities of highly secure software
Notes: "An Auerbach book."

Includes bibliographical references and index.
Table of contents: title: Machine generated contents note: 1.Quality #1: Security Is Built In, Not Bolted On; title: Prelude: The Ant and the Grasshopper; title: Introduction; title: Security Myths That Need Busting; title: Myth #1 We Have a Firewall; title: Myth #2 We Use SSL; title: Myth #3 We Have Intrusion Detection Systems and Intrusion Prevention Systems (IDSs/IPSs); title: Myth #4 Our Software Will Not Be Accessible from the Internet; title: Myth #5 We Have Never Been Compromised; title: Myth #6 Security Is "Not My Job" but the Responsibility of the Service Provider; title: Myth #7 Security Adds Little to No Value to the Business; title: Build Security In: The Need; title: Build Security In: What It Takes; title: Build Security In: The Value-Add; title: Conclusion; title: References; title: 2.Quality #2: Functionality Maps to a Security Plan; title: Prelude: Breaking the Tape; title: Introduction; title: What Is a Security Plan?; title: Security Plan Development; title: Step 1 Identify Security Objectives; title: Step 2 Identify Applicable Requirements; title: Step 3 Identify Threats; title: Contents note continued: Step 4 Identify Applicable Controls; title: Benefits of a Security Plan; title: Mapped Software; title: Conclusion; title: References; title: 3.Quality #3: Includes Foundational Assurance Elements; title: Prelude: What Lies Beneath?; title: Introduction; title: Data: The New Frontier; title: Data under Siege; title: Foundational Assurance Elements; title: Confidentiality; title: Integrity; title: Availability; title: Authentication; title: Authorization; title: Auditing; title: Conclusion; title: References; title: 4.Quality #4: Is Balanced; title: Prelude: The Clown Fish and the Anemone; title: Introduction; title: Balancing Scale: Risk and Reward; title: Balancing Scale: Functionality and Assurance; title: Balancing Scale: Threats and Controls; title: Conclusion; title: References; title: 5.Quality #5: Incorporates Security Requirements; title: Prelude: Lost in Translation; title: Introduction; title: Types of Software Security Requirements; title: Techniques to Elicit Software Security Requirements; title: Traceability of Software Security Requirements; title: Requirements to Retirement; title: Conclusion; title: Contents note continued: References; title: 6.Quality #6: Is Developed Collaboratively; title: Prelude: There Is No "I" in Team!; title: Introduction; title: Stakeholders in the Game: Whose Perspective?; title: Business; title: Security; title: Management; title: Development; title: Legal; title: Privacy; title: Auditors; title: Vendors; title: Conclusion; title: References; title: 7.Quality #7: Is Adaptable; title: Prelude: The Shark is a Polyphyodont; title: Introduction; title: Law of Resiliency Degradation; title: Software Adaptability: Technology, Threats, and Talent; title: Technology; title: Threats; title: Talent; title: Begin with the Future in Mind; title: Secure Software Requires Security-Savvy People; title: Conclusion; title: References; title: 8.Epilogue.