Security engineering: a guide to building dependable distributed systems. Library availability.
Security Engineering : A Guide to Building Dependable Distributed Systems (2nd) [Hardcover]
Have you read this? Please log in to set a read status Setting a reading intention helps you organise your reading. Read the guide. Your reading intentions are private to you and will not be shown to other users.
What are reading intentions? Here's an example of what they look like: Your reading intentions are also stored in your profile for future reference. How do I set a reading intention To set a reading intention, click through to any list item, and look for the panel on the left hand side:. System engineering skills, from business process analysis through software engineering to evaluation and testing, are also important; but they are not sufficient, as they deal only with error and mischance rather than malice.
Many security systems have critical assurance requirements.
Their failure may endanger human life and the environment as with nuclear safety and control systems , do serious damage to major economic infrastructure cash machines and other bank systems , endanger personal privacy medical record systems , undermine the viability of whole business sectors pay-TV , and facilitate crime burglar and car alarms. Even the perception that a system is more vulnerable than it really is paying with a credit card over the Internet can significantly hold up economic development.
The conventional view is that while software engineering is about ensuring that certain things happen 'John can read this file' , security is about ensuring that they don't 'The Chinese government can't read this file'. Reality is much more complex. Security requirements differ greatly from one system to another. One typically needs some combination of user authentication, transaction integrity and accountability, fault-tolerance, message secrecy, and covertness.
But many systems fail because their designers protect the wrong things, or protect the right things but in the wrong way. Good security engineering requires four things to come together. There's policy: what you're supposed to achieve.
There's mechanism: the ciphers, access controls, hardware tamper-resistance and other machinery that you assemble in order to implement the policy. There's assurance: the amount of reliance you can place on each particular mechanism. Finally, there's incentive: the motive that the people guarding and maintaining the system have to do their job properly, and also the motive that the attackers have to try to defeat your policy.
All of these things interact.
Author's Notes and Addenda to the Second Edition. Jump to: navigation , search.http://checkout.midtrans.com/la-vila-de-grcia-app-conocer-gente.php
Security Engineering - A Guide to Building Dependable Distributed Systems
Navigation menu Personal tools Log in. Namespaces Page Discussion. Views Read View source View history.
This page was last modified on 10 August , at This page has been accessed 9, times.
Related Security Engineering: A Guide to Building Dependable Distributed Systems (2nd Edition)
Copyright 2019 - All Right Reserved