Security engineering : a guide to building dependable distributed systems /
Ross Anderson.
- Third edition
- 1 online resource (1232 pages) : illustrations
Includes index.
Includes bibliographical references and index.
What is security engineering? -- Who is the opponent? -- Psychology and usability -- Protocols -- Cryptography -- Access control -- Distributed systems -- Economics -- Multilevel security -- Boundaries -- Inference control -- Banking and bookkeeping -- Locks and alarms -- Monitoring and metering -- Nuclear command and control -- Security printing and seals -- Biometrics -- Tamper resistance -- Side channels -- Advanced cyptographic engineering -- Network attack and defence -- Phones -- Electronic and information warfare -- Copyright and DRM -- New directions? -- Surveillance or Privacy? -- Secure systems development -- Assurance and sustainability -- Beyond "computer says no"
In Security Engineering: A Guide to Building Dependable Distributed Systems, Third Edition Cambridge University professor Ross Anderson updates his classic textbook and teaches readers how to design, implement, and test systems to withstand both error and attack. This book became a best-seller in 2001 and helped establish the discipline of security engineering. By the second edition in 2008, underground dark markets had let the bad guys specialize and scale up; attacks were increasingly on users rather than on technology. The book repeated its success by showing how security engineers can focus on usability. Now the third edition brings it up to date for 2020. As people now go online from phones more than laptops, most servers are in the cloud, online advertising drives the Internet and social networks have taken over much human interaction, many patterns of crime and abuse are the same, but the methods have evolved. Ross Anderson explores what security engineering means in 2020. The third edition of Security Engineering ends with a grand challenge: sustainable security. As we build ever more software and connectivity into safety-critical durable goods like cars and medical devices, how do we design systems we can maintain and defend for decades? Or will everything in the world need monthly software upgrades, and become unsafe once they stop?