An edition of The 7 qualities of highly secure software
(2012)
The 7 qualities of highly secure software
by Mano Paul
- 1 Have read
Share
×Close
This edition doesn't have a description yet. Can you add one?
Check nearby libraries
Buy this book
| Edition | Availability |
|---|---|
1
7 Qualities of Highly Secure Software
2012, Auerbach Publishers, Incorporated
in English
0429131534 9780429131530
|
zzzz
|
|
2
7 Qualities of Highly Secure Software
2012, Taylor & Francis Group
in English
1306499682 9781306499682
|
zzzz
|
|
3
7 Qualities of Highly Secure Software
2012, Auerbach Publishers, Incorporated
in English
146656654X 9781466566545
|
zzzz
|
|
4
7 Qualities of Highly Secure Software
2012, Auerbach Publishers, Incorporated
in English
1439814473 9781439814475
|
zzzz
|
5
|
aaaa
|
|
6
7 Qualities of Highly Secure Software
2012, Auerbach Publishers, Incorporated
in English
1466533188 9781466533189
|
zzzz
|
Book Details
Table of Contents
Machine generated contents note: 1.Quality #1: Security Is Built In, Not Bolted On
Prelude: The Ant and the Grasshopper
Introduction
Security Myths That Need Busting
Myth #1 We Have a Firewall
Myth #2 We Use SSL
Myth #3 We Have Intrusion Detection Systems and Intrusion Prevention Systems (IDSs/IPSs)
Myth #4 Our Software Will Not Be Accessible from the Internet
Myth #5 We Have Never Been Compromised
Myth #6 Security Is "Not My Job" but the Responsibility of the Service Provider
Myth #7 Security Adds Little to No Value to the Business
Build Security In: The Need
Build Security In: What It Takes
Build Security In: The Value-Add
Conclusion
References
2.Quality #2: Functionality Maps to a Security Plan
Prelude: Breaking the Tape
Introduction
What Is a Security Plan?
Security Plan Development
Step 1 Identify Security Objectives
Step 2 Identify Applicable Requirements
Step 3 Identify Threats
Contents note continued: Step 4 Identify Applicable Controls
Benefits of a Security Plan
Mapped Software
Conclusion
References
3.Quality #3: Includes Foundational Assurance Elements
Prelude: What Lies Beneath?
Introduction
Data: The New Frontier
Data under Siege
Foundational Assurance Elements
Confidentiality
Integrity
Availability
Authentication
Authorization
Auditing
Conclusion
References
4.Quality #4: Is Balanced
Prelude: The Clown Fish and the Anemone
Introduction
Balancing Scale: Risk and Reward
Balancing Scale: Functionality and Assurance
Balancing Scale: Threats and Controls
Conclusion
References
5.Quality #5: Incorporates Security Requirements
Prelude: Lost in Translation
Introduction
Types of Software Security Requirements
Techniques to Elicit Software Security Requirements
Traceability of Software Security Requirements
Requirements to Retirement
Conclusion
Contents note continued: References
6.Quality #6: Is Developed Collaboratively
Prelude: There Is No "I" in Team!
Introduction
Stakeholders in the Game: Whose Perspective?
Business
Security
Management
Development
Legal
Privacy
Auditors
Vendors
Conclusion
References
7.Quality #7: Is Adaptable
Prelude: The Shark is a Polyphyodont
Introduction
Law of Resiliency Degradation
Software Adaptability: Technology, Threats, and Talent
Technology
Threats
Talent
Begin with the Future in Mind
Secure Software Requires Security-Savvy People
Conclusion
References
8.Epilogue.
Edition Notes
"An Auerbach book."
Includes bibliographical references and index.
Classifications
The Physical Object
ID Numbers
Community Reviews (0)
Feedback?
History
- Created September 22, 2020
- 5 revisions
Wikipedia citation
×CloseCopy and paste this code into your Wikipedia page. Need help?
| December 20, 2023 | Edited by ImportBot | import existing book |
| February 3, 2023 | Edited by ImportBot | import existing book |
| December 9, 2022 | Edited by MARC Bot | import existing book |
| September 17, 2021 | Edited by ImportBot | import existing book |
| September 22, 2020 | Created by MARC Bot | Imported from Library of Congress MARC record |