ch8-Security Engineering(Ch14).pptVIP

Design guidelines 7-10 Validate all inputs Check that all inputs are within range so that unexpected inputs cannot cause problems. Compartmentalize your assets Organize the system so that assets are in separate areas and users only have access to the information that they need rather than all system information. Design for deployment Design the system to avoid deployment problems Design for recoverability Design the system to simplify recoverability after a successful attack. Chapter 14 Security Engineering * 14.2.3 Design for deployment Deployment involves configuring software to operate in its working environment, installing the system and configuring it for the operational platform. Vulnerabilities may be introduced at this stage as a result of configuration mistakes. Designing deployment support into the system can reduce the probability that vulnerabilities will be introduced. Chapter 14 Security Engineering * Software deployment Chapter 14 Security Engineering * Configuration vulnerabilities Vulnerable default settings Attackers can find out the default settings for software. If these are weak (often to increase usability) then they can be exploited by users when attacking a system. Development rather than deployment Some configuration settings in systems are designed to support development and debugging. If these are not turned off, they can be a vulnerability that can be exploited by attackers. Chapter 14 Security Engineering * Deployment support 1 Include support for viewing and analyzing configurations Make sure that the system administrator responsible for deployment can easily view the entire configuration. This makes it easier to spot omissions and errors that have been made. Minimize default privileges and thus limit the damage that might be caused Design the system so that the default privileges for an administrator are minimized. This means that if someone gains admin access, they do not have immediate access to the features of the system. Chapter