[Openvas-commits] r3418 - trunk/doc/website
scm-commit@wald.intevation.org
scm-commit at wald.intevation.org
Tue May 19 10:55:13 CEST 2009
Author: geoff
Date: 2009-05-19 10:55:13 +0200 (Tue, 19 May 2009)
New Revision: 3418
Modified:
trunk/doc/website/openvas-cr-32.htm4
Log:
added encryption suggestion to openvas-cr-32
Modified: trunk/doc/website/openvas-cr-32.htm4
===================================================================
--- trunk/doc/website/openvas-cr-32.htm4 2009-05-19 08:53:50 UTC (rev 3417)
+++ trunk/doc/website/openvas-cr-32.htm4 2009-05-19 08:55:13 UTC (rev 3418)
@@ -108,6 +108,16 @@
protocols (e.g. HTTP, FTP) as well.
</p>
+<p>
+An option to provide feed services with encryption can be offered. Encryption
+addresses the need to keep any potential future sensitive data private (e.g.
+secure logins to feed servers) and also as a "best practices" implementation.
+Encryption, even in the absence of sensitive data will raise the confidence level
+of potential deployment sites. Such practices are also a component of "defense
+in depth" which is designed to raise the level of effort needed by an intruder to
+such a level that network penetration becomes uneconomical.
+</p>
+
<h3>Effects</h3>
<p>
@@ -165,4 +175,6 @@
<ul>
<li> 2009-05-13 Michael Wiegand <michael.wiegand at intevation.de>:<br>
Initial text.</li>
+<li> 2009-05-19 Geoff Galitz <geoff at galitz.org>:<br>
+ Added paragraph suggesting encryption options to "Suggested Changes."</li>
</ul>
More information about the Openvas-commits
mailing list