Web Security Service Announcement Washington DC (GUSAS) Maintenance March 19, 2021

The scheduled maintenance has been completed.

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

The Washington DC (GUSAS) WSS site will undergo maintenance beginning on March 19, 2021 starting at 03:00 UTC, lasting for a duration of up to 12 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 addresses for WSS Agent.

IPsec / Proxy-forwarding / Explicit / SEP Agent (Explicit Mode):

• 170.176.240.164 - NO CHANGE

WSS Agent / Unified Agent:

• 168.149.146.164 - NO CHANGE • 168.149.151.164 - CAN BE RETIRED AFTER THE MAINTENANCE • 34.86.67.164 - CAN BE RETIRED AFTER THE MAINTENANCE

Egress IP Addresses 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, you need to update those lists prior to the maintenance.

• 170.176.240.0/24 - NO CHANGE • 168.149.146.0/24 - NO CHANGE • 168.149.151.0/24 - NO CHANGE • 168.149.152.0/24 - NO CHANGE • 168.149.153.0/24 - NO CHANGE • 34.86.67.0/24 - CAN BE RETIRED AFTER THE MAINTENANCE

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: Switch to your secondary tunnel prior to the maintenance window. • WSS Agent and Unified Agent: User traffic will be automatically redirected by the service to the nearest alternate site during the maintenance window. • SEP Agent: User traffic will be automatically redirected by the service to the nearest alternate site during the maintenance window. • Explicit proxy and proxy forwarding: Customers directing traffic to proxy.threatpulse.net will be automatically redirected by the service to the nearest alternate site during the maintenance window.

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.