[Openvas-commits] r3441 - in trunk/openvas-compendium: . images

scm-commit@wald.intevation.org scm-commit at wald.intevation.org
Wed May 20 14:13:47 CEST 2009


Author: felix
Date: 2009-05-20 14:13:46 +0200 (Wed, 20 May 2009)
New Revision: 3441

Added:
   trunk/openvas-compendium/images/severity-overrides-in-action-en.png
Modified:
   trunk/openvas-compendium/ChangeLog
   trunk/openvas-compendium/MANIFEST
   trunk/openvas-compendium/Makefile
   trunk/openvas-compendium/openvas-compendium.tex
Log:
* openvas-compendium.tex: Added/expanded sections about severity
overriding mechanism and credentials "export" for lscs.

* images/severity-overrides-in-action.png: New. Screenshot showing
"severity override" functionality.

* Makefile, MANIFEST: Added path to new image file.


Modified: trunk/openvas-compendium/ChangeLog
===================================================================
--- trunk/openvas-compendium/ChangeLog	2009-05-20 10:44:08 UTC (rev 3440)
+++ trunk/openvas-compendium/ChangeLog	2009-05-20 12:13:46 UTC (rev 3441)
@@ -1,3 +1,13 @@
+2009-05-20  Felix Wolfsteller <felix.wolfsteller at intevation.de>
+
+	* openvas-compendium.tex: Added/expanded sections about severity
+	overriding mechanism and credentials "export" for lscs.
+
+	* images/severity-overrides-in-action.png: New. Screenshot showing
+	"severity override" functionality.
+
+	* Makefile, MANIFEST: Added path to new image file.
+
 2009-05-12 Geoff Galitz <geoff at galitz.org>
 
 	* openvas-compendium.tex: Edited "The Signature Verification Process"

Modified: trunk/openvas-compendium/MANIFEST
===================================================================
--- trunk/openvas-compendium/MANIFEST	2009-05-20 10:44:08 UTC (rev 3440)
+++ trunk/openvas-compendium/MANIFEST	2009-05-20 12:13:46 UTC (rev 3441)
@@ -34,6 +34,7 @@
 images/mainwindow-targetselection-de.png
 images/ovaldi-results-de.png
 images/preferences-dlg-de.png
+images/severity-overrides-in-action.png
 images/wlsc-client-de.png
 images/wlsc-client-result-de.png
 images/wlsc-windows-de.png

Modified: trunk/openvas-compendium/Makefile
===================================================================
--- trunk/openvas-compendium/Makefile	2009-05-20 10:44:08 UTC (rev 3440)
+++ trunk/openvas-compendium/Makefile	2009-05-20 12:13:46 UTC (rev 3441)
@@ -66,6 +66,7 @@
 	images/ovaldi-results-de.png \
 	images/per-host-ssh-key-selection-en.png \
 	images/preferences-dlg-de.png \
+	images/severity-overrides-in-action.png \
 	images/ssh-key-manager-en.png \
 	images/wlsc-client-de.png \
 	images/wlsc-client-result-de.png \

Added: trunk/openvas-compendium/images/severity-overrides-in-action-en.png
===================================================================
(Binary files differ)


Property changes on: trunk/openvas-compendium/images/severity-overrides-in-action-en.png
___________________________________________________________________
Name: svn:mime-type
   + application/octet-stream

Modified: trunk/openvas-compendium/openvas-compendium.tex
===================================================================
--- trunk/openvas-compendium/openvas-compendium.tex	2009-05-20 10:44:08 UTC (rev 3440)
+++ trunk/openvas-compendium/openvas-compendium.tex	2009-05-20 12:13:46 UTC (rev 3441)
@@ -2033,6 +2033,34 @@
 For further information see the section \ref{sec:Reports} about the menu command
 {}``Report->Export''.
 
+\xname{changing-severities-of-reported-issues}
+\subsection{Changing severities of reported issues}
+
+With an OpenVAS-Client version 2.0.3 or higher, the severity of reported issues
+(e.g. "Security Hole") is tunable. To do this "Severity Overrides" have to
+be defined.
+This feature can be used to mark "False Positives" (e.g. faulty NVTs or
+deliberately open ports), but it can also be used to increase the severity of
+reported issues (e.g. because running an apache on a classified machine is extra
+bad).
+
+Severity overrides are organized in a Severity filter.
+The filter is off by default. It can be switched on or
+off in the "Report" Menu (item "Override Severities"/ "Undo Severity Overrides")
+on a per-report basis. Reports for which the filter is active are
+highlighted by an icon as can be seen in the screenshot.
+
+\IncludeImageFigure[width=12cm]{images/severity-overrides-in-action-en}{Screenshot of OpenVAS-Client 2.0.3 showing the same report filtered and unfiltered and the dialog to add a severity override.}
+
+Severity overrides are created via the context menu that opens on a right mouse
+ button click in the tree view of the reported issues.
+Selecting the "Severities..." menu item will open a window where the issue
+can be selected and a new severity and reason for the change can be specified.
+Clicking the "Add override to filter" button will save this severity override
+and add it to the filter.
+In the tree, a different icon will indicate that an issue has an user-assigned
+severity and a notice is added to the text area.
+
 \xname{openvas-client-preferences}
 \section{OpenVAS-Client Preferences}
 
@@ -2283,6 +2311,33 @@
 \end{scriptsize}
 Of course you have to replace 'sshovas' with the username you specified.
 
+If you can install rpm packages on the target systems and use a recent 
+client (>= 2.0.4) you can also use the installer packages created by the
+OpenVAS LSC Credentials Manager.
+
+This requires the tools 'rpm', 'alien' or 'nsis' on the client machine,
+depending on the target machine where an account should be installed on.
+
+To do so, open the OpenVAS LSC Credentials Manager (menu item "LSC Credentials
+Manager" in the "Extras" menu), and select the appropriate account to find
+out where the rpm package is located.
+
+Next, copy the package to the target system, e.g. using scp
+\begin{scriptsize}
+\begin{verbatim}
+scp ~/.openvas/lsc-mngt/openvas_lsc_target_preparation_officeuseraccount.rpm user at target:~
+\end{verbatim}
+\end{scriptsize}
+
+On the target system you can install the package ('rpm -i'), which will create
+the user and copy the key file as in the example above.
+
+In principle, the same process should allows you to install users on deb- based
+systems (like Debian and Ubuntu) as well (with 'dpkg -i' instead of 'rpm -i').
+
+Note that when you remove the package, the user and the content of its home
+directory will be removed as well.
+
 \xname{configure-the-local-security-checks-in-openvas-client-seq-two-zero-one}
 \subsection{Configure the local security checks in OpenVAS-Client <= 2.0.1}
 Next, create a task and scope for your local checks.
@@ -2423,6 +2478,22 @@
 Make sure the Windows-(personal) Firewall is disabled for the OpenVAS Server
 host, or a correct rule for the Test-Network is entered.
 
+If the target machine runs a Windows Version that was released after Windows 98
+and you use a recent (>=2.0.4) version of the client, you can use the installer
+generated by the OpenVAS LSC Credentials Manager.
+Therefore you have to have the tool 'nsis' installed on the system that runs
+the client. The location of the installer can be found by opening the "OpenVAS 
+LSC Credentials Manager" from the menu item in the "Extras" menu and selecting
+the account that you want to install.
+
+The installer will create the user and provide it with administrator rights.
+
+Copy the resulting executable to the target machine and execute it with
+administrator privileges.
+To remove the user, execute the Uninstaller which should be located on the
+Desktop of the user that was used to install the user.
+Note that this will delete the test- users home directory as well.
+
 \paragraph{Additional Note for Windows XP}
 
 For Windows XP it is important that ``Easy Filesharing'' is switched off.



More information about the Openvas-commits mailing list