Whole document tree
Chapter 6. Structure Program Internals and Approach
Like a city whose walls are broken down is a man who lacks self-control. | |
| Proverbs 25:28 (NIV) |
- Table of Contents
- 6.1. Follow Good Software Engineering Principles for Secure Programs
- 6.2. Secure the Interface
- 6.3. Separate Data and Control
- 6.4. Minimize Privileges
- 6.4.1. Minimize the Privileges Granted
- 6.4.2. Minimize the Time the Privilege Can Be Used
- 6.4.3. Minimize the Time the Privilege is Active
- 6.4.4. Minimize the Modules Granted the Privilege
- 6.4.5. Consider Using FSUID To Limit Privileges
- 6.4.6. Consider Using Chroot to Minimize Available Files
- 6.4.7. Consider Minimizing the Accessible Data
- 6.4.8. Consider Minimizing the Resources Available
- 6.5. Minimize the Functionality of a Component
- 6.6. Avoid Creating Setuid/Setgid Scripts
- 6.7. Configure Safely and Use Safe Defaults
- 6.8. Load Initialization Values Safely
- 6.9. Fail Safe
- 6.10. Avoid Race Conditions
- 6.10.1. Sequencing (Non-Atomic) Problems
- 6.10.2. Locking
- 6.11. Trust Only Trustworthy Channels
- 6.12. Set up a Trusted Path
- 6.13. Use Internal Consistency-Checking Code
- 6.14. Self-limit Resources
- 6.15. Prevent Cross-Site Malicious Content
- 6.16. Foil Semantic Attacks
- 6.17. Be Careful with Data Types