
Copyright © 2002-2012 Tenable Network Security, Inc.
destined for one or more addresses on the Internet.
Inbound Interactive
Sessions
The PVS has detected one or more interactive network
sessions originating from one or more addresses on the
Internet to this address within your focus network.
Internal Encrypted
Session
The PVS has detected one or more encrypted network
sessions between two hosts within your focus network.
Outbound Encrypted
Session
The PVS has detected one or more encrypted network
sessions originating from within your focus network and
destined for one or more addresses on the Internet.
Inbound Encrypted
Session
The PVS has detected one or more encrypted network
sessions originating from one or more addresses on the
Internet to this address within your focus network.
The PVS logs the number of hops away each host is
located.
WORKING WITH PASSIVE VULNERABILITY SCANNER
PLUGINS
VULNERABILITY AND PASSIVE FINGERPRINT OVERVIEW
The PVS has two sources of “plugin” information: the .prmx and .prm plugin libraries in the
plugins directory and the operating system fingerprints in the osfingerprints.txt file.
Tenable distributes its passive vulnerability plugin database in an encrypted format. This file
is known as tenable_plugins.prmx and can be updated on a daily basis, if necessary. PVS
plugins that are written by the customer or third parties have the extension of .prm.
Tenable has also implemented passive fingerprinting technology based on the open-source
SinFP tool. With permission from the author, Tenable has also included the database of
passive operating system fingerprints for the fingerprinting technology in this distribution of
the PVS. New passive operating system fingerprints can be added by PVS users through by
manually editing the os_fingerprint_sinfp.pasl file and restarting the PVS.
Downloading New Vulnerability Plugins
Tenable ships the PVS with a utility that downloads the most recent plugins. To manually
update the PVS plugins on Unix systems, run /opt/pvs/bin/pvs-update-plugins.sh. This
will update the plugins, located in /opt/pvs/var/pvs/plugins. If the SecurityCenter is
being used to manage a PVS, new plugins for the PVS will automatically be sent and the
PVS Proxy will restart the PVS.
Writing Custom Plugin Libraries
PVS customers can write their own passive plugin libraries. These plugins are added into the
plugins directory in the PVS’s installation directory. The plugin library must end with a .prm
extension for the PVS to see it. The next section details exactly how to write PVS plugins.
Comentarios a estos manuales