172 Best Practices for Converting Requirements to Secure Software Designs
Be very aware of access control issues. Always run code with the
fewest possible permissions. When code fails, find out why it failed
and fix the problem instead of increasing permissions. The more
permissions any code has, the greater its exposure to abuse.
Default installations should be secure
. Carefully review for vulnera-
bilities all functionality and exposed features that are enabled by
default and that constitute the attack surface.
Consider a defense-in-depth approach. The most exposed entry
points should have multiple protection mechanisms to reduce the
likelihood of exploitation of any security vulnerabilities that might
exist. If possible, review public sources ...