This document describes how to bypass authentication in Secure Web Appliance (SWA).
Cisco recommends that you have knowledge of these topics:
Cisco recommends that you have these tools installed:
This document is not restricted to specific software and hardware versions.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Exempting authentication for certain users or systems in the Cisco SWA can be crucial for maintaining operational efficiency and meeting specific requirements. Firstly, some users or systems require uninterrupted access to critical resources or services that could be hindered by authentication processes. For example, automated systems or service accounts performing regular updates or backups need seamless access without the delays or potential failures introduced by authentication mechanisms.
Additionally, there are scenarios where the web service provider recommends not using a proxy to access their service. In such cases, exempting authentication ensures compliance with the provider guidelines and maintains service reliability. Furthermore, to effectively block traffic for certain users, it is often necessary to first exempt them from authentication and then apply the appropriate blocking policies. This approach allows for precise control over access permissions.
In some instances, the web service being accessed is trusted and universally acceptable, such as Microsoft updates. Exempting authentication for such services simplifies access for all users. Moreover, there are situations where the user operating system or application does not support the configured authentication mechanism in the SWA, necessitating a bypass to ensure connectivity.
Lastly, servers with fixed IP addresses that do not have user logins and have limited, trusted Internet access do not require authentication, as their access patterns are predictable and secure.
By strategically exempting authentication for these cases, organizations can balance security needs with operational efficiency.
Exempting authentication in SWA can be achieved through various methods, each tailored to specific scenarios and requirements. Here are some common ways to configure authentication exemptions:
Here are the steps to create an Identification Profile to exempt from Authentication:
Step 1. In the GUI, Choose Web Security Manager and then click Identification Profiles.
Step 2. Click Add Profile to add a profile.
Step 3. Use the Enable Identification Profile check box to enable this profile, or to quickly disable it without deleting it.
Step 4. Assign a unique profile Name.
Step 5. (Optional) Add Description.
Step 6. From the Insert Above drop-down list, choose where this profile is to appear in the table.
Note: Position Identification Profiles that do not require authentication on top of the list. This approach reduces the load on the SWA, minimizes the authentication queue, and results in faster authentication for other users.
Step 7. In the User Identification Method section, choose Exempt from authentication/ identification.
Step 8. In the Define Members by Subnet, Enter the IP addresses or subnets to which this Identification Profile applies. You can use IP addresses, Classless Inter-Domain Routing (CIDR) blocks, and subnets.
Step 9. (Optional) Click Advanced to define additional membership criteria, such as, Proxy Ports, URL Categories or User Agents.
Caution: In transparent proxy deployment, SWA cannot read user agents or the full URL for HTTPS traffic unless the traffic is decrypted. As a result, if you configure the Identification Profile using User Agents or a Custom URL Category with regular expressions, This traffic fails to match the Identification Profile.
For more information about how to configure Custom URL Category, visit: Configure Custom URL Categories in Secure Web Appliance - Cisco
Tip: The policy uses an AND logic, meaning that all conditions must be met for the ID profile to match. When Advanced options are set, every single requirement must be satisfied for the policy to apply.
Image - Steps to Create ID profile to Bypass Authentication
Step 10. Submit and Commit changes.
| Revision | Publish Date | Comments |
|---|---|---|
2.0 |
21-Oct-2026
|
Recertification - Updated Formatting |
1.0 |
07-Oct-2024
|
Initial Release |