Architecting secure software systems / (Record no. 4129)

MARC details
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION
fixed length control field 100315s2009 flu a b 001 0 eng
010 ## - LIBRARY OF CONGRESS CONTROL NUMBER
LC control number 2008024408
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 9781420087840
035 ## - SYSTEM CONTROL NUMBER
System control number (Sirsi) u5125
040 ## - CATALOGING SOURCE
Original cataloging agency EG-CaNU
Transcribing agency EG-CaNU
Modifying agency EG-CaNU
042 ## - AUTHENTICATION CODE
Authentication code ncode
082 00 - DEWEY DECIMAL CLASSIFICATION NUMBER
Classification number 005.8
Edition number 22
100 1# - MAIN ENTRY--PERSONAL NAME
Personal name Talukder, Asoke K.
9 (RLIN) 10233
245 10 - TITLE STATEMENT
Title Architecting secure software systems /
Statement of responsibility, etc. Asoke K. Talukder, Manish Chaitanya.
260 ## - PUBLICATION, DISTRIBUTION, ETC.
Place of publication, distribution, etc. Boca Raton :
Name of publisher, distributor, etc. CRC Press,
Date of publication, distribution, etc. c2009.
300 ## - PHYSICAL DESCRIPTION
Extent xxxii, 446 p. :
Other physical details ill. ;
Dimensions 26 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 Security in Software Systems -- Architecting Secure Software Systems -- Constructing Secured and Safe C/UNIX Programs -- Constructing Secured Systems in NET -- Networking and Service-Oriented Architecture–Based Security -- Java Client-Side Security -- Security in Mobile Applications -- Security in Web-Facing Applications -- Server-Side Java Security -- Constructing Secured Web Services.
520 ## - SUMMARY, ETC.
Summary, etc. Traditionally, software engineers have defined security as a non-functional requirement. As such, all too often it is only considered as an afterthought, making software applications and services vulnerable to attacks. With the phenomenal growth in cybercrime, it has become imperative that security be an integral part of software engineering so that all software assets are protected and safe. Architecting Secure Software Systems defines how security should be incorporated into basic software engineering at the requirement analysis phase, continuing this sharp focus into security design, secured programming, security testing, and secured deployment.
596 ## -
-- 1
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Computer security.
9 (RLIN) 10234
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Computer architecture.
9 (RLIN) 10235
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Computer networks
General subdivision Security measures.
9 (RLIN) 10236
653 ## - INDEX TERM--UNCONTROLLED
Uncontrolled term Architecting Secure Software Systems
653 ## - INDEX TERM--UNCONTROLLED
Uncontrolled term Mobile Applications
700 1# - ADDED ENTRY--PERSONAL NAME
Personal name Chaitanya, Manish.
9 (RLIN) 10237
920 ## -
-- 1420087843
Holdings
Withdrawn status Lost status Source of classification or shelving scheme Damaged status Not for loan Home library Current library Shelving location Date acquired Source of acquisition Total Checkouts Full call number Barcode Date last seen Copy number Price effective from Koha item type
    Dewey Decimal Classification     Main library Main library General Stacks 01/26/2020 AHRA-P   005.8 / TA.A 2009 007079 11/24/2019 1 11/24/2019 Books