Cisco Cisco Web Security Appliance S670 ユーザーガイド

Use the commands below to perform the required tasks:

Commit your changes.

.

By default, the Web Security appliance has one log subscription created for Web Proxy logging 
messages, called the “Default Proxy Logs.” This captures basic information on all Web Proxy modules. 
The appliance also includes log file types for each Web Proxy module so you can read more specific 
debug information for each module without cluttering up the Default Proxy Logs.

Follow the steps below to troubleshoot Web Proxy issues using the various logs available.

Read the Default Proxy Logs.

If you see an entry that might related to the issue but does not have enough information to resolve it, 
create a log subscription for the relevant specific Web Proxy module. The following Web Proxy module 
logs types are available:

New

Add a new key.

Host

Display system host keys. This is the value to place in the remote system’s 
‘known_hosts’ file.

Fingerprint

Display system host key fingerprints.

User

Displays the public key of the system account that pushes the logs to the remote 
machine. This is the same key that is displayed when setting up an SCP push 
subscription. This is the value to place in the remote system’s ‘authorized_keys’ file. 

Access Control Engine Logs

AVC Engine Framework Logs

Configuration Logs

Connection Management Logs

Data Security Module Logs

DCA Engine Framework Logs

Disk Manager Logs

FireAMP

FTP Proxy Logs

HTTPS Logs

License Module Logs

Logging Framework Logs

McAfee Integration Framework Logs

Memory Manager Logs

Miscellaneous Proxy Modules Logs

Request Debug Logs

SNMP Module Logs

Sophos Integration Framework Logs

WBRS Framework Logs

WCCP Module Logs

Webcat Integration Framework Logs

Webroot Integration Framework Logs