Cisco Cisco NAC Appliance 4.1.0
13-3
Cisco NAC Appliance - Clean Access Manager Installation and Administration Guide
OL-12214-01
Chapter 13 Configuring Network Scanning
Configure the Quarantine Role
Configure the Quarantine Role
See
for details.
Load Nessus Plugins into the Clean Access Manager Repository
When the Clean Access Manager is first installed, its Nessus scan plugin repository is empty
(
(
). Plugins in the repository are listed under Device Management > Clean Access >
Network Scanner > Scan Setup > Plugins. You can manually load plugins you have downloaded from
the Nessus website—as a combined plugins.tar.gz file or as individual .nasl files—to the Clean Access
Manager’s plugin repository. You can also load .nasl plugins that you have created yourself.
the Nessus website—as a combined plugins.tar.gz file or as individual .nasl files—to the Clean Access
Manager’s plugin repository. You can also load .nasl plugins that you have created yourself.
Figure 13-1
Network Scanner Plugins Page
Note
Due to a licensing requirement by Tenable, Cisco is not able to bundle pre-tested Nessus plugins or
automated plugin updates to Cisco NAC Appliance, effective Release 3.3.6/3.4.1. Customers can still
download Nessus plugins selectively and manually through
automated plugin updates to Cisco NAC Appliance, effective Release 3.3.6/3.4.1. Customers can still
download Nessus plugins selectively and manually through
For details on Nessus plugin feeds, see
.
To facilitate the debugging of manually uploaded plugins, see
Note
Most Nessus 2.2 plugins are supported and can be uploaded to the Clean Access Manager. You must
register for Nessus 2.2 plugins from
register for Nessus 2.2 plugins from
. Once you
register, you will be able to download the free plugins.
If a plugin you want to add has dependent plugins, you must load those dependencies or the plugin is not
applied. When customizing a plugin, it is recommended that you give the plugin a unique name, so that
it is not overwritten later by a plugin in a Nessus update set.
applied. When customizing a plugin, it is recommended that you give the plugin a unique name, so that
it is not overwritten later by a plugin in a Nessus update set.