Establish secure defaults

This is a principle or a set of principles. To view all principles, please see the Principle Category page.

This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.

Last revision (mm/dd/yy): 12/15/2014

Description

There are many ways to deliver an “out of the box” experience for users. However, by default, the experience should be secure, and it should be up to the user to reduce their security – if they are allowed. It is imperative for the software environment to have default secure settings which may be opted out of by the user or other options which may be opted into (commonly known as Opt-in and Opt-out).

For example, by default, password aging and complexity should be enabled. Users might be allowed to turn these two features off(Opt-out) to simplify their use of the application and increase their risk.

It is important to understand that by no means does “Secure Defaults” mean turning off all possible network applications or sockets and services. And neither do Secure Defaults mean a 100% secure environment. But, they should ensure the least number of possible loopholes and fewer drawbacks.

Examples

Short example name

A short example description, small picture, or sample code with links

Short example name

A short example description, small picture, or sample code with links

Related Vulnerabilities

• Vulnerability 1
• Vulnerabiltiy 2

Related Controls

• Controls 1
• Controls 2

References

• http://www.link1.com
• Title for the link2