000 | 03501cam a2200505 i 4500 | ||
---|---|---|---|
999 |
_c200436343 _d54555 |
||
001 | 200436343 | ||
003 | TR-AnTOB | ||
005 | 20200217102759.0 | ||
007 | ta | ||
008 | 010628t20022002maua b 001 0 eng | ||
015 |
_aGBA1W7338 _2bnb |
||
020 |
_a020172152X _q(hardcover) |
||
020 |
_a9780201721522 _q(hardcover) |
||
020 | _a0321774957 | ||
020 | _a9780321774958 | ||
035 |
_a(OCoLC)47238955 _z(OCoLC)49874358 |
||
035 | _a(TR-AnTOB)200436343 | ||
040 |
_aDLC _beng _erda _cDLC _dUKM _dC#P _dOCLCQ _dNLGGC _dUBA _dBTCTA _dYDXCP _dOCLCG _dIG# _dDEBBG _dEXW _dORX _dOCLCF _dBEDGE _dOCLCQ _dUtOrBLW _dTR-AnTOB |
||
041 | 0 | _aeng | |
042 | _apcc | ||
050 | 0 | 0 |
_aQA76.76.D47 _bV857 2002 |
090 |
_aQA76.76.D47 _bV857 2002 |
||
100 | 1 |
_aViega, John _eauthor _921484 |
|
245 | 1 | 0 |
_aBuilding secure software : _bhow to avoid security problems the right way / _cJohn Viega, Gary McGraw ; foreword by Bruce Schneier. |
264 | 1 |
_aBoston : _bAddison-Wesley, _c[2002] |
|
264 | 4 | _c©2002 | |
300 |
_axxx, 493 pages : _billustrations ; _c24 cm |
||
336 |
_atext _btxt _2rdacontent |
||
337 |
_aunmediated _bn _2rdamedia |
||
338 |
_avolume _bnc _2rdacarrier |
||
490 | 0 | _aAddison-Wesley professional computing series | |
504 | _aIncludes bibliographical references and index | ||
505 | 0 | 0 |
_tIt's All about the Software -- _tDealing with Widespread Security Failures -- _tBugtraq -- _tCERT Advisories -- _tRISKS Digest -- _tTechnical Trends Affecting Software Security -- _tThe 'ilities -- _tWhat Is Security? -- _tIsn't That Just Reliability? -- _tPenetrate and Patch Is Bad -- _tOn Art and Engineering -- _tSecurity Goals -- _tPrevention -- _tTraceability and Auditing -- _tMonitoring -- _tPrivacy and Confidentiality -- _tMultilevel Security -- _tAnonymity -- _tAuthentication -- _tIntegrity -- _tKnow Your Enemy: Common Software Security Pitfalls -- _tSoftware Project Goals -- _tManaging Software Security Risk -- _tAn Overview of Software Risk Management for Security -- _tThe Role of Security Personnel -- _tSoftware Security Personnel in the Life Cycle -- _tDeriving Requirements -- _tRisk Assessment -- _tDesign for Security -- _tImplementation -- _tSecurity Testing -- _tA Dose of Reality -- _tGetting People to Think about Security -- _tSoftware Risk Management in Practice -- _tWhen Development Goes Astray -- _tWhen Security Analysis Goes Astray -- _tThe Common Criteria -- _tSelecting Technologies -- _tChoosing a Language -- _tChoosing a Distributed Object Platform -- _tCORBA -- _tDCOM -- _tEJB and RMI -- _tChoosing an Operating System -- _tAuthentication Technologies -- _tHost-Based Authentication -- _tPhysical Tokens -- _tBiometric Authentication -- _tCryptographic Authentication -- _tDefense in Depth and Authentication -- _tOn Open Source and Closed Source -- _tSecurity by Obscurity -- _tReverse Engineering -- _tCode Obfuscation -- _tSecurity for Shrink-Wrapped Software -- _tSecurity by Obscurity Is No Panacea |
590 | _aDonated by Kemal Bıçakcı | ||
650 | 0 |
_aComputer software _xDevelopment _9367 |
|
650 | 0 |
_aSystem design _9530 |
|
650 | 7 |
_aComputer security _9912 |
|
700 | 1 |
_aMcGraw, Gary, _d1966- _eauthor _929585 |
|
700 | 1 |
_aSchneier, Bruce, _d1963- _ewriter of preface _92794 |
|
776 | 0 | 8 |
_iOnline version: _aViega, John. _tBuilding secure software. _dBoston : Addison-Wesley, ©2002 _w(OCoLC)606571780 |
776 | 0 | 8 |
_iOnline version: _aViega, John. _tBuilding secure software. _dBoston : Addison-Wesley, ©2002 _w(OCoLC)607840440 |
942 |
_2lcc _cBK |