Check Point¶
This guide covers the Check Point-specific steps (R8x, SmartConsole) needed to
allow the RTA's outbound OpenVPN connection to
connect.remotetesting.secureworks.com on TCP/443.
Note
For the full background (what the RTA connects to, why an ordinary "allow outbound 443" rule is not enough, and the two failure modes: TLS/SSL decryption and application control), see the firewall troubleshooting overview.
Activation-mode platforms also need get.remotetesting.secureworks.com
Appliances deployed from a generic image (AWS, GCP, Azure, Hyper-V on
Windows 11) register and activate over a second outbound connection:
standard HTTPS on TCP/443 to get.remotetesting.secureworks.com. When
you add the decryption exception and application rule for
connect.remotetesting.secureworks.com, also allow this destination and
exempt it from TLS/SSL decryption (the appliance does not trust an
intercepting proxy's re-signed certificate). Its IP addresses are not
guaranteed to stay constant, so allowlist it by FQDN, not by IP.
Pre-registered appliances (vSphere, VMware Workstation, VirtualBox, Nutanix,
Hyper-V Server) do not use this endpoint.
Choose how to apply the fix¶
-
Create the destination object, the HTTPS Inspection bypass, and the Application Control and IPS exceptions in SmartConsole, then install the policy.
-
Script the same objects and rules through the Management API with
mgmt_cli, then publish and install the policy from the command line. -
A copy-paste prompt that walks your AI assistant through the SmartConsole changes, pausing for your confirmation before the policy install.