This article discusses how to configure your Always-On policy to increase Internet security for users in your account.
The Always-on Policy enhances Internet security by defining rules for when users or User groups always connect to the Cato Cloud. This ensures all traffic goes through a PoP and Cato security engines inspect the traffic to ensure it complies with your security policies.
Company ABC's network is used by its own employees, who have access to corporate resources, and third-party contractors, who cannot access corporate resources. They create a rule to enable Always-On for their employees while the third-party contractors are able to directly access the Internet. This ensures all traffic from company employees, is passed through the Cato Cloud and is protected by security policies.
The Always-On Policy is an ordered rule-base. The rules in your policy are applied to a User or Group as follows:
-
When they meet a rule, the Client follows the configuration set in the rule
-
If they do not meet any rules, they are able to disconnect from the network
With the Always-On Policy enabled you can still provide users with direct access to the Internet by:
-
Using a temporary bypass method
-
Creating a rule with an On-Demand connected status
-
Allowing Internet access in Recovery mode
There can be some situations where users need to temporarily bypass the Cato Cloud and directly access the Internet. For example, to temporarily access a website that is blocked by an Internet Firewall rule. For each rule, you can configure how users temporary bypass the Cato Cloud.
On Windows v5.9 and higher, you can also configure how long users are able to bypass the Cato Cloud. During this period, Internet traffic does not flow through the Cato Cloud and is unsecured.
When the Client temporarily disconnects, events are generated that show the user details and the time duration that the Client was disconnected for. To view these events, on the Events page apply a filter for the sub-type VPN Never-Off Bypass. The Bypass Method in the event displays the method used to bypass the Client. For more about events in your account, see Analyzing Events in Your Network.
Users can temporarily bypass the Cato Cloud using either:
-
Admin controlled bypass with a bypass code
-
User controlled bypass
Note
Note: Supported on Windows, Android, iOS Clients, and macOS Client v5.4 and above
Use this option to generate a one-time password (OTP) in the Cato Management Application that you can give to any user and let them temporarily disconnect the Client. In Windows Client versions lower than 5.9 and other supported operating systems, the Client is bypassed for up to 15 minutes at a time. Each code can be valid for up to 15 minutes.
In addition, you can use an authentication app (such as Google Authenticator) to scan the QR code in this screen. Then you can always get an OTP for users from the authentication app. The authentication app refreshes the code every 30 seconds, so each code is only valid for 30 seconds.
You can use the same bypass code for multiple users, as long as the code is still valid.
Note
Note: Supported from:
-
Windows Client v5.9 and higher
-
macOS Client v5.5 and higher
This option lets users temporarily disconnect the Client on request. In the Client, the user must provide a reason for disconnecting the Client in a free text field. and then can immediately directly access the Internet. This reason is included in the event.
The Client is allowed to disconnect for the time duration that is configured in the Disconnect Duration.
A retail company's engineering team is responsible for ensuring their website has 100% availability to receive online orders. This means that they always need access to an online SaaS application required for troubleshooting issues. Access to the application is required out of hours and when working remotely. The company's security policy states that all Internet access must be secure.
To comply with the security policy, the IT enables Always-On. As a precaution, to avoid a situation where during a potential outage the Client cannot connect to the Cato Cloud, the IT team provides the engineers with a way to immediately access the Internet. The IT team created a rule in their Always-On policy for the engineer User group, where the Bypass Mode is configured to let users temporarily disconnect on request.
If an engineer needs to troubleshoot website issues in the middle of the night, the IT team can be sure that they can access the troubleshooting SaaS application even if there is an issue with the Client. The engineer does not need to wait for IT approval to bypass the Cato Cloud and begin troubleshooting the website issues.
If there are users who regularly need direct access to the Internet, you can add them to a rule with the connect status On-Demand. This configuration lets users connect or disconnect the Client as required.
Note
Note: Supported from:
-
Windows Client v5.9 and higher
-
macOS Client v5.5 and higher
You can also choose the Client behavior in a scenario where a connection to the Cato Cloud cannot be established. The Client can be configured to:
-
Allow Internet access (Default configuration): Users can access the Internet. Traffic does not flow through the Cato Cloud and is unsecured until a connection to the Cato Cloud is established.
-
Restrict Internet access: Users cannot access the Internet until a connection to the Cato Cloud, and secured Internet, is established.
Company ABC has Always-On enabled for all users. Their C-suite executives often travel and connect to the Internet from airports and hotels. Occasionally the Client doesn't detect the captive portal and is unable to establish an encrypted tunnel. To ensure the C-suite can continue to work when they are traveling, the IT team configures Recovery Mode in the Always-On rule for the C-suite User group to allow access to the Internet.
If the Client doesn't detect a captive portal, the C-suite users are able to continue to work, because the Client allows Internet access according to the Always-On policy. As soon as the Client reestablishes a tunnel, traffic flows through the Cato Cloud as expected.
Before you enable your Always-On Policy, consider how Always-On interacts with other features and Client versions in your environment. This section provides recommendations for how to use SSO, Client Connectivity, Device Authentication, and the Windows Client with your Always-On Policy.
For accounts that use Single Sign-On authentication for users, you can also configure the supported Clients to always remain connected to the Cato Cloud (Always-On). This configuration provides users with the simplicity of SSO and the security of Always-On. The Client is able to access the IdP provider and access to other resources is in accordance with your security policy.
Note
Note: To help users who can't authenticate to the Client, we recommend that you enable the a method of bypassing the Cato Cloud and review bypass events. Otherwise, the unauthenticated device can't connect to the Internet or the Cato Cloud).
This section contains best practices and recommendations for implementing Always-On with SSO in your account.
-
Start with enabling Always-On and SSO for a small number of users to minimize the impact on your account
-
Review bypass events, to monitor the usage of Bypass codes in your organization
-
Since unauthenticated users don't have Internet connectivity, make sure that users can log in to the device without relying on the Internet
-
Make sure that all the Clients are updated to the minimum supported version for the relevant OS. If a Client of an unsupported version is used, the Client cannot re-authenticate and traffic to the internet is blocked.
-
For deployments that use a third-party proxy, only In-Client Browser Authentication is supported for Always-On and SSO (for more about Browser Authentication, see Configuring the Authentication Policy for Cato Clients)
Your Client Connectivity Policy and Device Authentication settings apply Device Postures and Checks performed on devices for users. If the device fails to comply with the policy that was set for the profile, then the user can't connect to the Cato Cloud. Your Client Connectivity Policy and Device Authentication settings take precedence over your Always-On Policy.
For IT teams, delivering or shipping brand new devices to users around the world, we can provide Always-on Security out-of-the-box.
Starting with Windows Client v5.6, you can enhance Internet security even before a user authenticates to Cato. The Always-On policy is available out-of-the-box, and Internet access is only permitted after the user authenticates to your Cato account.
To enable this feature, simply add a registry key to the Windows device to enable Always-On. Once the user is added to the Client, the Always-On settings defined in the Cato Management Application are applied to that user.
For accounts that use the Pre login feature, the device is only allowed to access the Allowed Destinations before the user is added to the Client. All other Internet access is blocked.
We also recommend adding the registry key that launches the Client on start up. For more information, see Installing the Cato Client.
Note
Note: Before users are added to the Client, it's not possible to bypass the Cato Cloud.
This section explains how to create the Always-On Policy.
The Always-On Policy lets you define the users or User Groups for Clients that are required to always connect to the network.
To create the Always-On Policy:
-
From the navigation menu, click Access > Always-On Policy.
-
Click New.
The New Rule panel opens.
-
Enter a Name and set the Rule Order.
-
Define the Users & Groups, Platforms.
-
Define the Connected status, Bypass Mode, Disconnect Duration, and Recovery Mode.
-
Click Apply.
-
Repeat steps 2-5 for each rule in the Always-On Policy.
-
Enable the Always-On Policy and then click Save.
The slider
is green when the rule is enabled, and gray when the rule is disabled.
Note
Note: Supported from:
-
All Windows Clients
-
Linux Client v5.2 and above
You can provide users with an On-Demand connected status with additional security by configuring the Client to automatically connect during boot phase. Once connected, users can choose to disconnect and reconnect the Client whenever they need to. For users with an Always-On connected status, the Client automatically connects, without this configuration.
-
If the Connect on boot or the Start minimized options are selected in the Cato Management Application:
-
This is enforced on all Clients in your environment
-
Users cannot disable this setting from the Client
-
-
If the Connect on boot or the Start minimized options are unchecked, in the Cato Management Application:
-
Users can choose to enable these features on the Settings tab in the Client
-
Note: With Connect on boot enabled, if a user logs out of their Windows session, the Client connects to the Cato Cloud. This is to provide access to a Domain Controller to allow the user to log back in.
To configure default settings for Clients:
-
From the navigation menu, click Access > Always-On Policy.
-
Open the Settings tab.
-
In the Connect on Boot section, define the default settings for Windows Clients.
-
Click Save.
Note
Note: Supported from:
-
Windows Client v5.8 and above
-
Linux Client v5.2 and above
When a user connects behind a Cato Socket or IPsec site, the Client automatically connects to that site in Office Mode. For more information on Office Mode, see Configuring Office Mode.
You can configure if users with always-on enabled are required to authenticate to Cato when the Client is connected in Office Mode. This configuration has no impact on security policies.
A bypass code is a 6 digit code that is entered in the Client to let users temporarily disconnect from the Cato Cloud.
Depending on the Bypass Mode configured in the Cato Management Application, users can temporarily disconnect the Client using either a bypass code or by entering a reason to bypass.
The bypass code is generated by admins and sent to a user to be entered into the Client. After a valid code is entered, the Client temporarily bypasses the encrypted tunnel and the user can access the Internet. Windows Clients below v5.9, macOS, iOS, and Android Clients can be temporarily disconnected for a maximum of 15 minutes. Windows Client v5.9 and above can be disconnected for the length of time configured in the Disconnect Duration.
Users who authenticate with SSO or MFA need to re-authenticate to the Cato Client when re-connecting.
To enter a bypass code:
-
In the Windows Client, users can right-click the Client icon in the system tray and select Temporary Bypass
-
In the macOS Client, users can right-click the Client icon in the system tray and select Temporary Disconnect
-
In the iOS Client, on the Client home screen, select Bypass Always-on
-
In the Android Client, from the side menu, select Temporary Bypass
Note
Note: Supported from: Windows Client v5.9 and higher
-
Windows Client v5.9 and higher
-
macOS Client v5.5 and higher
Users are able to temporarily disconnect the Client after they provide a reason. After the user enters the reason, the Client temporarily bypasses the Cato Cloud and the user can access the Internet. The Client is disconnected for the length of time configured in the Cato Management Application.
Users who authenticate with SSO or MFA need to re-authenticate to the Cato Client when re-connecting.
You can customize the Always-On Policy for an individual user.
To configure the Always-On Policy for a specific user:
-
From the navigation menu, click Access > Always-On Policy.
-
Click New.
The New Rule panel opens.
-
Enter a Name and set the Rule Order.
-
In the User & Groups section, select SDP User.
-
Choose the specific user.
-
Define the Platforms and Connected status.
-
Click Apply.
-
Enable the Always-On Policy and then click Save.
The slider
23 comments
Updated article for Windows Client v5.6, Installing Windows Clients and Always-On
If I enable user-controlled bypass, where can I see the justification they provide for disconnecting?
My team is interested as well in where the justification by the user gets sent to for temporary bypass of the Cato cloud.
Hi Mark Knutson and Sean Newmann,
The justification provided by users is included in the event.
To view these events, filter for the event Sub-Type VPN Never-Off Bypass. The justification is is the Bypass Reason field.
For more about events in your account, see Analyzing Events in Your Network.
We have a particular use case where Manual PoP Selection is needed at times. After implementing Always-On it is no longer possible to edit the PoP used - even while in bypass. Is there a way to combine these two options at all?
Hello
How to disable “connect at startup” and “Start minimized” for external Users (Consultants) only?
Internal User should always connected
admin Huwyler Thanks for the question.
Currently, these options (Connect on boot and Start minimized) are account-level settings, and you can't define them for specific user groups.
hi,
i have the same problem as JM posted 4 months ago. is there planned solution to this ?
--
We have a particular use case where Manual PoP Selection is needed at times. After implementing Always-On it is no longer possible to edit the PoP used - even while in bypass. Is there a way to combine these two options at all?
Hi Lukasz Jaszczuk,
This is not currently supported, but it is planned as a future enhancement.
Michael Goldberg Version 5.11 still does not allow editing Manual PoP when Always-On is enabled, not sure what the rationale would be for preventing this. Is this still on the roadmap?
Hi JM,
Yes this functionality is on our roadmap and is planned as a future enhancement.
Is there a way in Cato Portal to setup or send a notification email when an Always On policy with User Bypass enabled triggers a bypass. I would like to start tracking and understanding why the users need to bypass and would like to get notified when this event occurs.
Search parameters are
event Sub-Type VPN Never-Off Bypass, Bypass Method is User Controlled
Email Notification Output should have the following output
Sub-Type VPN Never-Off Bypass
Bypass Method is User Controlled
Justification is the Bypass Reason
How can I get this setup?
We would also like to get notified about the bypass events that Mlamleli Mpofu mentions, but currently there appears to be no way to trigger alerts for such custom queries. Is this on the roadmap, or will this require use of the SIEM integration for the foreseeable future?
Hi Mlamleli Mpofu and JM,
Although all the information you requested is in an event, sending this data via email is not currently supported for the Always On policy.
This is on our roadmap and planned as a future enhancement.
Hello Cato Support,
Will Entering a Reason to Bypass support be added to macOS clients?
Thanks,
Fred
Fred Fermin Good news, this functionality is already supported for macOS Clients v5.5 and higher. For more information, see Summary of Cato macOS Client Releases
Hi Yaakov,
We are currently testing Always On, this may sound stupid, but would the option in the policy configuration to only apply Always On when a User is not behind a Socket be possible, so anyone WFH or out and about would be forced to connect to the VPN, whilst users sat behind a Socket are ignored?
Kr
Steve
Hi Steve Pettitt,
Enabling the Always-On policy means the Client always automatically connects to the Cato Cloud. This happens whether a user is working remotely or behind a site. When a user connects behind a site, they are connected to the Cato Cloud via the site and not the Client, and the Client enters Office Mode. Users behind a socket are automatically connected to the Cato Cloud (assuming they are connected to the corporate network and not a guest network) regardless of whether they are included in an Always-On policy rule or not.
Piggy-backing on what Michael G. is saying,
I highly recommend setting up your Trusted Networks setting (under the Access>Client Access Control section). Our org had some issues with Always-On not triggering the “Office Mode” until we got this setup correctly.
Hi Michael and Mark….
And therein lies the problem, we need our HelpDesk agents, and Infrastructure team to be able to connect to the VPN when on different Ethernet and WIFI subnets around our head office and remote offices that are all protected by Sockets.
We use reserved IP DHCP addresses when at our Desks at our Head Office, but when migrating around the network and on alternate IP Subnets, we use a reserved VPN address to allow access to restricted devices.
Office mode breaks this concept, we need to be able to, without using the bypass, connect to the VPN to access our reserved VPN IP address when on different IP subnets around our network locations.
I understand this may seem counterproductive, but we really need to not be forced into office mode when connecting behind a Socket location.
Kr
Steve
Hi Steve Pettitt,
We may have a solution for this use case. Please contact support for more information.
Hi Michael,
Please can you let us know what the solution may be. We have an existing ticket open #675588, Callum Bisley
on T3 Team has provided some useful information, however he has not has not solved our problem of
“Not being forced into Office Mode when behind a CATO Socket”. We can create an “Always-On” policy with
“On-Demand”, but this relies on the users connecting their CATO Client when out of the Office. Dave Cullen
has also provided some further information, where the only useable option appears to be reserving IP addresses
in DHCP at the necessary sites and subnets and then whitelisting those in CATO and on our Firewalls, this would work
but requires a lot of setup and ongoing maintenance.
Kind regards
Trevor
The Community is the best place to continue discussing this. I added these comments to a thread.
Please sign in to leave a comment.