Red Hat NETWORK 3.6 - Guía de usuario descargar pdf (Pagina 13)

Starting PVS via the “RC” script will also lint the pvs.conf script for syntax errors

before starting. If errors are detected, PVS will direct you to address the errors

and will not start.

Post Installation

Once installed, the original RPM file or unpacked files are not needed and may be deleted if

desired.

If multiple Ethernet devices should be monitored, simply edit the pvs.conf file located in

/opt/pvs/etc and add multiple lines which contain “interface” keywords and the specified

Ethernet devices. For example, a pvs.conf file edited to support multiple Ethernet devices

on Linux may include a section like this:

# which interface are we listening on ?

interface "eth0";

interface "eth1";

interface "eth2";

File Locations

The PVS installs its files into the following locations:

Path

Purpose

/opt/pvs

Base directory

/opt/pvs/etc

Configuration files for PVS and the PVS Proxy

/opt/pvs/bin

Location of the PVS and PVS Proxy executables, plus several

helper tools for the PVS Proxy daemon

/opt/pvs/var

Plugins, discovered vulnerabilities, log files, keys, software

license agreement and other miscellaneous items

The software license agreement for PVS is located in PDF format in the directory

/opt/pvs/var/pvs. It is also available online at:

http://cgi.tenable.com/Tenable_Passive_Vulnerability_Scanner_3.x_Software_License_Agreement.pdf

OPERATIONS

Starting the Passive Vulnerability Scanner with the SecurityCenter

If PVS for Red Hat is to be managed by the SecurityCenter, use the service command to

launch the pvs and pvs-proxy binaries:

# service pvs start

Starting PVS Proxy[ OK ]

Starting PVS[ OK ]

1 2 ... 8 9 10 11 12 13 14 15 16 17 18 ... 60 61

Sin comentarios

Red Hat NETWORK 3.6 - Guía de usuario Pagina 13