Deployment - Revision history

KirstenS at 12:30, 4 May 2009

2009-05-04T12:30:13Z

2009-05-04T12:25:53Z

‎Malicious software

2009-03-04T16:01:33Z

‎Easter eggs

2008-08-28T12:14:28Z

‎Links

2008-08-28T12:10:19Z

‎How to identify if you are vulnerable

2008-08-28T12:08:23Z

2007-08-16T15:28:50Z

‎How to protect yourself

2007-08-16T15:28:29Z

‎How to identify if you are vulnerable

2007-08-16T15:27:49Z

‎How to identify if you are vulnerable

2007-02-20T21:14:54Z

‎Best Practices

@@ Line 1: / Line 1: @@
 {{Template:Stub}}
+<br>
 [[Guide Table of Contents| Development Guide Table of Contents]]__TOC__

@@ Line 181: / Line 181: @@
 * Microsoft partner and premium support web sites were distributing Hotfixes with the FunLove virus in 2001
-* Hewlett-Packard had the FunLove virus on their web site, in 2000 and also 2006. Though in 2006 it was a printer that was no longer made and the Korean version
+* Hewlett-Packard had the FunLove virus on their web site, in 2000 and also 2006. Though in 2006 it was a printer that was no longer made and the Korean version of Windows 95 drivers for it, so not as big a deal as in 2000
 * Linux kernel with a backdoor was submitted to CVS tree in November 2003. It was spotted (by Larry McVoy) because it had been placed directly into CVS, not via  BitKeeper

@@ Line 153: / Line 153: @@
 ==Easter eggs ==
-Easter eggs are mostly small (but sometimes not) hidden features. Often they will contain the developer’s names or activate hidden advanced or developer features, but occasionally, they are more like mini-applications. For the most part, they have no business function.
+Easter eggs are mostly small (but sometimes not) hidden features. Often they will contain the developers' names or activate hidden advanced or developer features, but occasionally, they are more like mini-applications. For the most part, they have no business function.
@@ Line 168: / Line 168: @@
 ===How to protect yourself ===
 ==Malicious software ==

@@ Line 288: / Line 288: @@
 ==Links==
-[[Guide Table of Contents]]
+[[Guide Table of Contents| Development Guide Table of Contents]]
 [[Category:OWASP_Guide_Project]]
 [[Category:Activity]]
 [[Category:Deployment]]

@@ Line 66: / Line 66: @@
 * Does the media contain any viruses or harmful code?
-* Was it obtained from a third party download site? If so, does it contain an accurate link back to your
+* Was it obtained from a third party download site? If so, does it contain an accurate link back to your site?
 ===How to protect yourself ===

← Older revision		Revision as of 15:28, 16 August 2007
Line 149:		Line 149:

	===How to protect yourself ===		===How to protect yourself ===
		+	* Never generate common or default credentials.
		+	* Always remove any default user accounts from the server and applications prior to deployment.

	==Easter eggs ==		==Easter eggs ==

@@ Line 145: / Line 145: @@
 ===How to identify if you are vulnerable ===
 * Identify the default user accounts that are standard with the product you are using.
 * Run periodic tests to ensure none of the accounts you identify are enabled or exist.
 ===How to protect yourself ===

← Older revision		Revision as of 15:27, 16 August 2007
Line 145:		Line 145:

	===How to identify if you are vulnerable ===		===How to identify if you are vulnerable ===
		+	* Always remove any default user accounts from the server and applications prior to deployment.
		+	* Identify the default user accounts that are standard with the product you are using.
		+	* Run periodic tests to ensure none of the accounts you identify are enabled or exist.
		+	* Never generate common or default credentials.

	===How to protect yourself ===		===How to protect yourself ===

← Older revision		Revision as of 21:14, 20 February 2007
Line 26:		Line 26:

	* Documentation should not contain any default accounts, nor should the installer contain any pre-chosen or default accounts		* Documentation should not contain any default accounts, nor should the installer contain any pre-chosen or default accounts
		+
		+	* Every configuration parameter must to be findable

	==Release Management ==		==Release Management ==