Establish secure defaults - Revision history

Simran bakshi: /* Description */

2014-12-19T08:37:58Z

‎Description

2014-12-15T19:16:53Z

‎Description

2014-12-15T19:13:16Z

‎Description

2009-04-07T12:29:30Z

2009-03-04T19:15:05Z

‎Overview

2009-03-04T19:14:20Z

2008-09-07T12:36:39Z

2008-09-05T18:53:20Z

2006-06-14T14:49:22Z

2006-06-14T14:42:23Z

← Older revision		Revision as of 08:37, 19 December 2014
Line 17:		Line 17:

	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.		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.
		+
		+	==Operating Systems==
		+
		+	Although OpenBSD claims to be the only fully secure by default operating system, it isn't necessarily the most secure operating system because the definition of an operating system is varied. An operating system which cant interact with other systems may not be connected across a network thereby being more secure than one which is prone to network vulnerabilities.
		+	Windows provides User Account Controls whereas Ubuntu which is a Linux OS hides the administrative account by default and gives administrative privileges to the first user for tasks like managing the disk drives. MAC OS X doesn’t hide this account but gives limited privileges.

	==Examples==		==Examples==

← Older revision		Revision as of 19:16, 15 December 2014
Line 15:		Line 15:

	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.		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==		==Examples==

@@ Line 12: / Line 12: @@
 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.
-For example, by default, password aging and complexity should be enabled. Users might be allowed to turn these two features off to simplify their use of the application and increase their risk.
+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.
 ==Examples==

← Older revision		Revision as of 19:14, 4 March 2009
Line 2:		Line 2:

	{{Template:Stub}}		{{Template:Stub}}
−
−	~~{{Template:Principle}}~~

	Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''		Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''

@@ Line 2: / Line 2: @@
 {{Template:Stub}}
 <br>
@@ Line 8: / Line 12: @@
-==Overview==
+==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.
 For example, by default, password aging and complexity should be enabled. Users might be allowed to turn these two features off to simplify their use of the application and increase their risk.
 [[Category:Principle]]