Principles are important because they help us make security decisions in new situations. By considering each of these principles, we can derive security requirements, make architecture and implementation decisions, and identify possible weaknesses in systems.
The important thing to remember is that in order to be useful, principles must be evaluated, interpreted, and applied. You can't simply tell a software developer that their software must "fail safely" or that they should do "defense in depth". It won't mean anything.
How to add a new Principle article
You can follow the instructions to make a new Principle article. Please use the appropriate structure and follow the Tutorial. Be sure to paste the following at the end of your article to make it show up in the Principle category:
Some proven application security principles
- Apply defense in depth (complete mediation)
- Use a positive security model (fail safe defaults)(minimize attack surface)
- Fail safely
- Run with least privilege
- Avoid security by obscurity (open design)
- Keep security simple (verifiable)(economy of mechanism)
- Detect intrusions (compromise recording)
- Don’t trust infrastructure
- Don’t trust services
- Establish secure defaults (psychological acceptability)
Applying security principles
Consider the exercise of designing a simple web application that allows people to send email to a friend. By evaluating and interpreting each principle, we can arrive at many of the threats to this application and ultimately derive a set of protection requirements. We want to end up with a complete list of what is required to offer this service securely.
TBD: walk through this exercise
A. http://web.mit.edu/Saltzer/www/publications/protection/Basic.html (Saltzer and Schroeder)(see Section 3)
Pages in category "Principle"
The following 18 pages are in this category, out of 18 total.