Web Security Service Announcement Chicago (GUSCH) Maintenance January 27, 2021

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The Chicago (GUSCH) WSS site will undergo maintenance beginning on January 27 , 2021 at 03:00 UTC lasting for a duration of up to 8 hours.

• IP address changes will occur so it is imperative to adjust access control lists appropriately. • Carefully review the information below to avoid disruption of service.

Ingress IP Addresses The IP addresses you forward traffic to for filtering. The IP address must match the connection method. For example, do not connect IPsec tunnels to the IP address for WSS Agent. IPsec / Proxy-forwarding / Explicit / SEP Agent (Explicit Mode):

NO CHANGE o 199.247.42.164

WSS Agent / Unified Agent / SEP Agent (Tunnel Mode):

NO CHANGE o 199.247.45.164 o 199.247.46.164 o 199.247.47.164 o 170.176.247.164 o 34.69.162.164

Egress IP Ranges The IP addresses WSS will use to access content on your behalf and to deliver filtered content to your users. If you use application or firewall access control lists, add new IP ranges prior to the maintenance:

NEW o 199.247.32.0/24 o 199.247.33.0/24

NO CHANGE o 199.247.42.0/24 o 199.247.43.0/24 o 199.247.44.0/24 o 199.247.45.0/24 o 199.247.46.0/24 o 199.247.47.0/24 o 170.176.247.0/24 o 34.69.162.0/24

Impact No impact to WSS traffic is expected during the maintenance window. However, it is important to make sure that your connection method aligns to the correct ingress IP address to avoid loss of connectivity. For example, following this maintenance IPsec connections will no longer be allowed to connect to IP addresses designated for WSS Agent (see ingress IP address detail above).

Required Action Failure to make these changes could prevent users from connecting to WSS, accessing third party web applications, or authenticating against the service using the Auth Connector (where applicable).

• Firewall rules regulating connectivity to/from your network to WSS should be adjusted to allow traffic to pass to the IP networks listed above. • Third party applications that regulate connections by source IP address should be updated to accept connections from the egress IP networks listed above to ensure traffic proxied through WSS can reach the application. • Auth Connector must be able to communicate with all egress ranges listed above on TCP 443, where applicable.

Guidance for specific connection methods: • IPsec: No action is needed unless your tunnel is connecting to the incorrect ingress IP address (see Impact section above). • WSS Agent, Unified Agent, SEP Agent (Tunnel Mode): User traffic will be automatically redirected by the service to the nearest alternate site during the maintenance window. • SEP Agent (Explicit Mode): No action is needed unless your traffic is directed to the incorrect ingress IP address (see Impact section above). • Explicit proxy and proxy forwarding: No action is needed unless your traffic is directed to the incorrect ingress IP address (see Impact section above).

WARNING: Any customer, regardless of connection method, with a configuration pointing to a specific site or IP address must manually failover to a secondary site during the migration window to avoid an outage. Explicit redirection should never point to an IP address. Only IPsec connections should be directed to IP addresses.

Support Questions? Contact technical support by visiting: https://support.broadcom.com/security. For service status and maintenance updates visit and subscribe to Broadcom Service Status: https://wss.status.broadcom.com.