000			02243cam a2200337 a 4500
008			100315s2009 flu a b 001 0 eng
010			_a2008024408
020			_a9781420087840
035			_a(Sirsi) u5125
040			_aEG-CaNU _c EG-CaNU _d EG-CaNU
042			_ancode
082	0	0	_a005.8 _2 22
100	1		_aTalukder, Asoke K. _910233
245	1	0	_aArchitecting secure software systems / _c Asoke K. Talukder, Manish Chaitanya.
260			_aBoca Raton : _b CRC Press, _c c2009.
300			_axxxii, 446 p. : _b ill. ; _c 26 cm.
500			_a"An Auerbach book".
504			_aIncludes bibliographical references and index.
505	0		_aSecurity 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			_aTraditionally, 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.
650		0	_aComputer security. _910234
650		0	_aComputer architecture. _910235
650		0	_aComputer networks _x Security measures. _910236
653			_a Architecting Secure Software Systems
653			_aMobile Applications
700	1		_aChaitanya, Manish. _910237
920			_a1420087843
596			_a1
999			_c4129 _d4129