The 7 qualities of highly secure software / (Record no. 8274)

MARC details
000 -LEADER
fixed length control field 03556cam a22003137a 4500
001 - CONTROL NUMBER
control field vtls000012705
003 - CONTROL NUMBER IDENTIFIER
control field VRT
005 - DATE AND TIME OF LATEST TRANSACTION
control field 20250102223307.0
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION
fixed length control field 130529s2012 flua |b 001 0 eng
010 ## - LIBRARY OF CONGRESS CONTROL NUMBER
LC control number 2012-405842
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 9781439814468
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 1439814465
039 #9 - LEVEL OF BIBLIOGRAPHIC CONTROL AND CODING DETAIL [OBSOLETE]
Level of rules in bibliographic description 201402040234
Level of effort used to assign nonsubject heading access points VLOAD
Level of effort used to assign subject headings 201305290832
Level of effort used to assign classification laila
-- 201305290832
-- laila
050 00 - LIBRARY OF CONGRESS CALL NUMBER
Classification number QA76.76.D47
Item number P3774 2012
100 1# - MAIN ENTRY--PERSONAL NAME
Personal name Paul, Mano.
9 (RLIN) 20534
245 14 - TITLE STATEMENT
Title The 7 qualities of highly secure software /
Statement of responsibility, etc. Mano Paul.
246 3# - VARYING FORM OF TITLE
Title proper/short title Seven qualities of highly secure software
260 ## - PUBLICATION, DISTRIBUTION, ETC.
Place of publication, distribution, etc. Boca Raton, FL :
Name of publisher, distributor, etc. CRC Press,
Date of publication, distribution, etc. c2012.
300 ## - PHYSICAL DESCRIPTION
Extent xvi, 144 p. :
Other physical details ill. ;
Dimensions 25 cm.
500 ## - GENERAL NOTE
General note "An Auerbach book."
504 ## - BIBLIOGRAPHY, ETC. NOTE
Bibliography, etc. note Includes bibliographical references and index.
505 0# - FORMATTED CONTENTS NOTE
Formatted contents note 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 --
505 0# - FORMATTED CONTENTS NOTE
Formatted contents note 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 --
505 0# - FORMATTED CONTENTS NOTE
Formatted contents note 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.
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Computer software
General subdivision Development.
9 (RLIN) 5144
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Computer security.
9 (RLIN) 1265
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Software engineering.
9 (RLIN) 2677
942 ## - ADDED ENTRY ELEMENTS (KOHA)
Source of classification or shelving scheme Library of Congress Classification
Suppress in OPAC No
Koha item type Books
Holdings
Withdrawn status Lost status Source of classification or shelving scheme Damaged status Not for loan Home library Current library Shelving location Date acquired Cost, normal purchase price Total checkouts Barcode Date last seen Copy number Cost, replacement price Price effective from Koha item type
    Library of Congress Classification     Library Library First Floor 21/12/2024 27.00   18963 21/12/2024 1 54.00 21/12/2024 Books
New Arrivals

Loading...

Contact Us

Library: Location maps

Phone: 00968 2323 7091 Email: Ask us a question

Library Hours

Sunday - Thursday 7:30AM - 8:00 PM

Friday - Saturday Closed