- Introduction
- Connect, Install, and Configure
- Connect the Appliance to a Cisco Cloud Web Security Proxy
- Intercepting Web Requests
- Acquire End-User Credentials
- Classify End-Users for Policy Application
- SaaS Access Control
- Integrate the Cisco Identity Services Engine (ISE) / ISE Passive Identity Controller (ISE-PIC)
- Classify URLs for Policy Application
- Create Policies to Control Internet Requests
- Create Decryption Policies to Control HTTPS Traffic
- Scan Outbound Traffic for Existing Infections
- Configuring Security Services
- File Reputation Filtering and File Analysis
- Managing Access to Web Applications
- Prevent Loss of Sensitive Data
- Notify End-Users of Proxy Actions
- Generate Reports to Monitor End-user Activity
- Secure Appliance Reports
- Secure Appliance Reports on the New Web Interface
- Detecting Rogue Traffic on Non-Standard Ports
- Monitor System Activity Through Logs
- Integrating with Cisco Threat Response
- Perform System Administration Tasks
- Troubleshooting
- Command Line Interface
- Additional Information
- End User License Agreement
Introduction
This topic contains the following sections:
What's New in AsyncOS 12.7
Feature |
Description |
---|---|
ISE-SXP integration |
You can integrate ISE-SXP deployment with Cisco Web Security Appliance for passive authentication. This allows you to get all defined mappings, including SGT-to-IP address mappings that are published through SXP. |
Related Topics
Using the Appliance Web Interface
Web Interface Browser Requirements
To access the web interface, your browser must support and be enabled to accept JavaScript and cookies. It must be able to render HTML pages containing Cascading Style Sheets (CSS).
The Cisco Web Security Appliance follows the Target Environments set by YUI: http://yuilibrary.com/yui/environments/
Your session automatically times out after 30 minutes of inactivity.
Some buttons and links in the web interface cause additional windows to open. Therefore, you may need to configure the browser’s pop-up blocking settings in order to use the web interface.
Note |
Only use one browser window or tab at a time to edit the appliance configuration. Also, do not edit the appliance using the web interface and the CLI at the same time. Editing the appliance from multiple places concurrently results in unexpected behavior and is not supported. |
To access the GUI, your browser must support and be enabled to accept JavaScript and cookies, and it must be able to render HTML pages containing Cascading Style Sheets (CSS).
Browser |
Windows 10 |
MacOS 10.6 |
---|---|---|
Safari |
— |
7.0 and later |
Google Chrome |
Latest Stable Version |
Latest Stable Version |
Microsoft Internet Explorer |
11.0 |
— |
Mozilla Firefox |
Latest Stable Version |
Latest Stable Version |
Microsoft Edge |
Latest Stable Version |
Latest Stable Version |
-
Internet Explorer 11.0 (Windows 10 only)
-
Safari (7 and later)
-
Firefox (Latest Stable Version)
-
Google Chrome (Latest Stable Version)
Browsers are supported only for operating systems officially supported by the browser.
You may need to configure your browser’s pop-up blocking settings in order to use the GUI, because some buttons or links in the interface will cause additional windows to open.
You can access the legacy web interface of the appliance on any of the supported browsers.
The supported resolution for the new web interface of the appliance (AsyncOS 11.8 and later) is between 1280x800 and 1680x1050. The best viewed resolution is 1440x900, for all the browsers.
Note |
Cisco does not recommend viewing the new web interface of the appliance on higher resolutions. |
Enabling Access to the Web Interface on Virtual Appliances
By default, the HTTP and HTTPS interfaces are not enabled on virtual appliances. To enable these protocols, you must use the command-line interface.
Procedure
Step 1 |
Access the command-line interface. See Accessing the Command Line Interface. |
Step 2 |
Run the
Pressing Enter at a prompt accepts the default value. Look for the prompts for HTTP and HTTPS and enable the protocol(s) that you will use. Look for the prompts for AsyncOS API (Monitoring) for HTTP and HTTPS and enable the protocol(s) that you will use. |
Accessing the Appliance Web Interface
If you are using a virtual appliance, see Enabling Access to the Web Interface on Virtual Appliances.
Procedure
Step 1 |
Open a browser and enter the IP address (or hostname) of the Web Security Appliance . If the appliance has not been previously configured, use the default settings:
-or-
where Otherwise, if the appliance is currently configured, use the IP address (or host name) of the M1 port.
|
||||
Step 2 |
[New Web Interface Only] Login to the legacy web interface and click Web Security Appliance
is getting a new look. Try it!! link to access the new web interface. When you click this link, it opens a new tab in your web browser and goes to
|
||||
Step 3 |
When the appliance login screen appears, enter your user name and passphrase to access the appliance. By default, the appliance ships with the following user name and passphrase:
If this is the first time you have logged in with the default admin user name, you will be prompted to immediately change the passphrase. |
||||
Step 4 |
To view a listing of recent appliance access attempts, both successes and failures, for your user name, click the recent-activity icon (i or ! for success or failure respectively) in front of the “Logged in as” entry in the upper right corner of the application window. |
Committing Changes in the Web Interface
Procedure
Step 1 |
Click the Commit Changes button. |
||
Step 2 |
Enter comments in the Comment field if you choose. |
||
Step 3 |
Click Commit Changes.
|
Clearing Changes in the Web Interface
Procedure
Step 1 |
Click the Commit Changes button. |
Step 2 |
Click Abandon Changes. |
Supported Languages
AsyncOS can display its GUI and CLI in any of the following languages:
-
German
-
English
-
Spanish
-
French
-
Italian
-
Japanese
-
Korean
-
Portuguese
-
Russian
-
Chinese
-
Taiwanese
The Cisco SensorBase Network
The Cisco SensorBase Network is a threat management database that tracks millions of domains around the world and maintains a global watch list for Internet traffic. SensorBase provides Cisco with an assessment of reliability for known Internet domains. The Cisco Web Security Appliance uses the SensorBase data feeds to improve the accuracy of Web Reputation Scores.
SensorBase Benefits and Privacy
Participating in the Cisco SensorBase Network means that Cisco collects data and shares that information with the SensorBase threat management database. This data includes information about request attributes and how the appliance handles requests.
Cisco recognizes the importance of maintaining your privacy, and does not collect or use personal or confidential information such as usernames and passphrases. Additionally, the file names and URL attributes that follow the hostname are obfuscated to ensure confidentiality. When it comes to decrypted HTTPS transactions, the SensorBase Network only receives the IP address, web reputation score, and URL category of the server name in the certificate.
If you agree to participate in the SensorBase Network, data sent from your appliance is transferred securely using HTTPS. Sharing data improves Cisco’s ability to react to web-based threats and protect your corporate environment from malicious activity.
Enabling Participation in The Cisco SensorBase Network
Note |
Standard SensorBase Network Participation is enabled by default during system setup. |
Procedure
Step 1 |
Choose Security Services > SensorBase. |
Step 2 |
Verify that SensorBase Network Participation is enabled. When it is disabled, none of the data that the appliance collects is sent back to the SensorBase Network servers. |
Step 3 |
In the Participation Level section, choose one of the following levels:
|
Step 4 |
In the AnyConnect Network Participation field, choose whether or not to include information collected from clients that connect to the Cisco Web Security Appliance using Cisco AnyConnect Client. AnyConnect Clients send their web traffic to the appliance using the Secure Mobility feature. |
Step 5 |
In the Excluded Domains and IP Addresses field, optionally enter any domains or IP addresses to exclude from traffic sent to the SensorBase servers. |
Step 6 |
Submit and commit your changes. |