Installation guide

Next, SecurityCenter’s /opt/sc4/support/conf/cosign.conf must be edited for the correct settings for your

environment. In the following example, 192.168.5.5 is used as the CoSign server’s IP address and 192.168.7.44 is the IP

address of the SecurityCenter server. Only the configured lines of the configuration file are displayed.

The configuration below is an example only. Please obtain the correct configuration parameters for your

environment from your CoSign administrator.

CosignProtected off

CosignHostname 192.168.5.5

CosignCrypto /opt/sc4/support/cosign/mod_cosign.key

/opt/sc4/support/cosign/mod_cosign.crt /opt/sc4/data/CA

CosignFilterDB /opt/sc4/support/cosign/filter

CosignCheckIP never

CosignService tenable

CosignRedirect https://192.168.5.5

CosignPostErrorRedirect https://192.168.5.5/post_error.html

CosignValidReference ^https?:\/\/192.168.7.44(\/.*)?

CosignValidationErrorRedirect https://192.168.5.5/invalid.html

CosignRequireFactor factor.sh

SetHandler cosign

CosignProtected Off

CosignValidReference ^https?:\/\/192.168.5.5(\/.*)?

CosignValidationErrorRedirect https://192.168.5.5/invalid.html

Allow from all

Satisfy Any

</Location>

Once the configuration file has been configured appropriately, the next step is to configure SecurityCenter to use CoSign

authentication. Log in as an admin user, navigate to the “Configuration” page and go to the “Authentication” tab. Under the

Server Authentication drop-down, select “CoSign” and submit.

After making the above changes, restart the SecurityCenter service with the “service SecurityCenter restart”

command to enable CoSign authentication for SecurityCenter. When navigating to the SecurityCenter server, you will

initially be redirected to the CoSign server for authentication. Once authenticated on the CoSign server, the log into

SecurityCenter will be completed.

Resource Management

The Resources tab provides the Admin user with the ability to configure supporting resources such as Log Correlation

Engines, Nessus scanners (and scan zones), and Passive Vulnerability Scanners. This section describes the various

resources and configuration options.

Nessus Scanners

In the SecurityCenter framework, the Nessus scanner behaves as a server, while SecurityCenter serves as a client that

schedules and initiates scans, retrieves results, reports results, and performs a wide variety of other important functions.

Click “Resources” and then “Nessus Scanners” to retrieve a list of the scanners and their current status, version, host,

number of assigned zones, and when they were last modified. If the status of a scanner has changed recently (since

visiting the page), click the “Update Status” button to see the latest scanner status.

There are three classifications of Nessus scanners that may be added to SecurityCenter: “Managed”, “Unmanaged”, and

“Perimeter Service”.