Network Protocol Design With Machiavellian Robustness
Download Network Protocol Design With Machiavellian Robustness PDF/ePub or read online books in Mobi eBooks. Click Download or Read Online button to get Network Protocol Design With Machiavellian Robustness book now. This website allows unlimited access to, at the time of writing, more than 1.5 million titles, including hundreds of thousands of titles in various foreign languages.
Network Protocol Design with Machiavellian Robustness
Author: Brett Keith Watson
language: en
Publisher: The Famous Brett Watson
Release Date: 2010-11-14
This thesis is on the subject of network protocol design. It takes a collection of known, practical problems that we face on the Internet—namely, abuses of the network—and considers these problems in light of both existing practical countermeasures and abstract analysis. Protocol design features and techniques with Machiavellian robustness are then proposed to address these problems, to the extent that such a remedy is possible. A protocol called ‘Invite’ is then designed from scratch using these new techniques. The Invite protocol thus serves as a practical example of design for Machiavellian robustness, but its duty as a protocol is to convey that robustness to some other protocol, so it is then applied to email (and its well-known abuses such as spamming and mailbombing). In that context, its effectiveness is analysed and compared with other approaches, both proposed and currently practised. Lastly, the broader implications of Machiavellian robustness are considered, suggesting possible avenues of future research.
Economics of Information Security
Author: L. Jean Camp
language: en
Publisher: Springer Science & Business Media
Release Date: 2004-09
Designed for managers struggling to understand the risks in organizations dependent on secure networks, this book applies economics not to generate breakthroughs in theoretical economics, but rather breakthroughs in understanding the problems of security.
Security Engineering
Now that there's software in everything, how can you make anything secure? Understand how to engineer dependable systems with this newly updated classic 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, including: How the basic elements of cryptography, protocols, and access control translate to the new world of phones, cloud services, social media and the Internet of Things Who the attackers are – from nation states and business competitors through criminal gangs to stalkers and playground bullies What they do – from phishing and carding through SIM swapping and software exploits to DDoS and fake news Security psychology, from privacy through ease-of-use to deception The economics of security and dependability – why companies build vulnerable systems and governments look the other way How dozens of industries went online – well or badly How to manage security and safety engineering in a world of agile development – from reliability engineering to DevSecOps 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?