Author: jan
Date: 2008-09-25 10:46:29 +0200 (Thu, 25 Sep 2008)
New Revision: 1427
Modified:
trunk/openvas-compendium/ChangeLog
trunk/openvas-compendium/openvas-compendium.tex
Log:
* openvas-compendium.tex: Extended chapter on the planning
of OpenVAS use.
Modified: trunk/openvas-compendium/ChangeLog
===================================================================
--- trunk/openvas-compendium/ChangeLog 2008-09-25 08:31:51 UTC (rev 1426)
+++ trunk/openvas-compendium/ChangeLog 2008-09-25 08:46:29 UTC (rev 1427)
@@ -1,3 +1,8 @@
+2008-09-25 Jan-Oliver Wagner <[EMAIL PROTECTED]>
+
+ * openvas-compendium.tex: Extended chapter on the planning
+ of OpenVAS use.
+
2008-09-22 Michael Wiegand <[EMAIL PROTECTED]>
* openvas-compendium.tex: Incorporated changes from NTP to OTP in OTP
Modified: trunk/openvas-compendium/openvas-compendium.tex
===================================================================
--- trunk/openvas-compendium/openvas-compendium.tex 2008-09-25 08:31:51 UTC
(rev 1426)
+++ trunk/openvas-compendium/openvas-compendium.tex 2008-09-25 08:46:29 UTC
(rev 1427)
@@ -224,11 +224,11 @@
on OpenVAS, you should compare your targets with the coverage
of the currently available OpenVAS vulnerability tests.
-Please be aware that the OpenVAS server (actually its module
-``openvas-plugins'') delivers only a base set of tests.
+Please be aware that the OpenVAS server releases (actually the releases
+of its module ``openvas-plugins'') delivers a base set of tests.
The update cycle of this base set is quite long compared to
-the occurrence of new vulnerabilities and respective tests.
-New or changed tests are delivered via so-called ``feed services''.
+the occurrence of new vulnerabilities and respective NVTs.
+New or changed tests are promptly distributed via so-called ``feed services''.
If you want to test your network against the latest threats, a successful
outcome will depend on the quality of the feed service(s) you subscribed to.
@@ -251,6 +251,8 @@
families cover my audit target?
\item In case you are planning a permanent auditing solution and not just a
single shot: How sustainable is the feed service organized?
+\item Does the feed deliver signatures on the NVTs with a trust level
+ for quality you are comfortable with?
\end{itemize}
\xname{choose-location-of-scan-server}
@@ -277,17 +279,54 @@
the target system and might be acted upon legally and/or technically by
the administration of the system in question.
-%TODO: \item Targets are intranet desktops:
+\item Targets are intranet desktops and servers:
-%TODO: \item Targets are intranet servers:
+ In this case you should directly coordinate with
+ your system administration.
-%TODO: \item Targets are intranet active network components:
+ Depending on the complexity of the intranet, you
+ may need to find out how to reach specific subnets
+ from your OpenVAS Server installation. In some cases
+ it might be an option to install several OpenVAS Servers.
+ For local security checks you need to prepare the target systems
+ for remote access. For unixoid systems this is usually via ssh
connections,
+ for Windows it is about SMB shares.
\end{itemize}
-%TODO: \section{Choose Type of Scan-Server}
+\section{Choose Type of Scan-Server}
+\subsection{Hardware}
+OpenVAS usually does not need outstanding hardware performance nor
+consumes considerable disk space.
+A standard server configuration will be sufficient in most cases.
+
+Most users use OpenVAS with a IA32 architecture. 64bit and PowerPC
architectures
+are also supported, but not tested to the same extend.
+
+\subsection{Operating System}
+
+Only unixoid systems are supported by OpenVAS and out of this group,
+Linux distributions are tested most extensively. xBSD should work but
+has not been extensively tested.
+
+When selecting the operating system you should consider some aspects:
+
+\begin{itemize}
+
+\item OpenVAS can either be compiled out of source code or be
+ installed via prepared binary packages. In case you prefer the latter
+ method, you should check which operating systems are supported best
+ with installation packages.
+
+\item Several security tools are integrated into OpenVAS. If you plan to use
+ them, you should make sure you have them available with your selected
+ operating system. Again, some platforms are better supported with
+ binary installation packages than others.
+
+\end{itemize}
+
\clearpage
\xname{installing-and-configuring-openvas-server}
_______________________________________________
Openvas-commits mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-commits
