From http://www-128.ibm.com/developerworks/library/s-princ5.html
- Identify and reinforce the weakest link.
- Provide defense in depth, which means you should manage software risk by providing redundant security solutions. Usually, one level of redundancy is worthwhile; whether you need more depends on your particular project.
- Secure failure: Make sure that if the system could possibly fail, it will fail in a secure manner.
- Least privilege: Do not give out more privileges than necessary, and do not extend privileges longer than necessary.
- Compartmentalization: Try to keep failures in one part of a system from having an impact on the rest of the system.
- Keep it simple.
- Privacy: Don't give out any unnecessary information.
- It's hard to hide secrets.
- Don't extend trust easily.
- Trust the community.
No comments:
Post a Comment