CP Check Point Quantum Smart-1 Cloud AdminGuide
CP Check Point Quantum Smart-1 Cloud AdminGuide
QUANTUM SMART-1
CLOUD
Administration Guide
Check Point Copyright Notice
© 2019 - 2025 Check Point Software Technologies Ltd.
All rights reserved. This product and related documentation are protected by copyright and
distributed under licensing restricting their use, copying, distribution, and decompilation. No
part of this product or related documentation may be reproduced in any form or by any means
without prior written authorization of Check Point. While every precaution has been taken in
the preparation of this book, Check Point assumes no responsibility for errors or omissions.
This publication and features described herein are subject to change without notice.
TRADEMARKS:
Refer to the Copyright page for a list of our trademarks.
Refer to the Third Party copyright notices for a list of relevant copyrights and third-party
licenses.
Important Information
Important Information
Latest Software
We recommend that you install the most recent software release to stay up-to-
date with the latest functional improvements, stability fixes, security
enhancements and protection against new and evolving attacks.
Certifications
For third party independent certification of Check Point products, see the Check
Point Certifications page.
Feedback
Check Point is engaged in a continuous effort to improve its documentation.
Please help us by sending your comments.
Table of Contents
Smart-1 Cloud Overview 7
Key Benefits 7
Use Case 8
Supported Gateways and Versions 9
Getting Started with Smart-1 Cloud 12
Step 1: Create an Account in the Infinity Portal 12
Step 2: Access the Infinity Smart-1 Cloud Portal 13
Navigating the Smart-1 Cloud Portal 15
Creating and Deploying a New Smart-1 Cloud 17
A Smart-1 Cloud Home Page Overview 18
Connecting Gateways and Clusters in Smart-1 Cloud 19
Connecting on-premises Security Gateway or CloudGuard Network Security Gateway 20
Connecting a Cluster 25
Onboarding a new Quantum appliance using Zero Touch deployment 29
Connecting a Quantum Spark Appliance 30
Connecting an SMB Cluster 37
Connecting a Maestro Security Group 39
Using Clish Commands 41
Log in to SmartConsole from Smart-1 Cloud 43
Using the Settings in Smart-1 Cloud 46
General 46
Service Information: 46
API & SmartConsole 46
SmartConsole: 46
Migrate 48
CloudGuard Network Configuration 50
How to enable CloudGuard Network in Smart-1 Cloud 50
Add an account 50
Edit an account 52
Add a Security Gateway configuration template 52
Edit a Security Gateway configuration template 53
Advanced settings 54
Forwarding Events to SIEM 54
Forward to SIEM configuration 54
Adding a new destination 54
TLS/SSL over TCP Configuration 56
Edit the destination 56
Delete the destination 56
Start, stop, or restart the destination 56
Troubleshooting 57
Smart-1 Cloud Advanced Configuration 58
Smart-1 Cloud Gateway Commands 59
How to Connect a Security Gateway Behind a NAT/Proxy or Third-Party Security
Gateway 60
How to Connect a Quantum Spark Appliance with a Dynamic IP (DAIP) 61
How to Configure the Query Settings in SmartConsole 66
How to Connect a Local Active Directory to Smart-1 Cloud 67
How to Configure Access to Security Gateway Gaia Portal 70
How to Configure Access from the Security Gateway External IP Address to the
Internal Asset with Static NAT 71
How to Configure IP Address Selection by Remote VPN Peer 72
Smart-1 Cloud Configuration for Site-to-Site VPN 73
General Capabilities of Smart-1 Cloud 75
Management Capabilities 75
Logs & Events 77
Migration 78
Integrations with Other Services and Third-Party Tools 79
Smart-1 Cloud Limitations 80
Management Limitations 80
Logs & Events 82
Migration 82
Integrations with Other Services and Third-party Tools 82
Best Practices for Smart-1 Cloud 83
Management APIs 83
Smart-1 Cloud APIs 84
The Streamed SmartConsole 84
IPS Updates 85
Automatic Updates 85
Smart-1 Cloud Licensing 86
The Management License 86
Smart-1 Cloud License 86
Activating a license 86
Smart-1 Cloud Administrator Roles 87
Troubleshooting of Smart-1 Cloud 88
Frequently Asked Questions about Smart-1 Cloud 95
Key Benefits
n Always the Latest Security Management - The newest features are automatically
updated in your unified management platform.
n Zero Maintenance - No need to monitor or perform backup operations on your Security
Management Server.
n On-demand Expansion - Seamlessly increase capacity to support more Security
Gateways and additional storage needs.
Use Case
A typical use case is a company seeking to improve operational efficiency and reduce the
complexity of their Security Management platform. With Smart-1 Cloud, companies can focus
more on managing their core security rather than the underlying infrastructure.
Tasks like maintenance, software updates, security patches, backups, and system health
monitoring - all consume significant time and resources. Additionally, as companies grow, they
need to effectively scale their security solutions, often requiring new hardware purchases and
complex migration processes. By shifting these IT management responsibilities to Smart-1
Cloud, companies can significantly enhance their security management while concentrating
on their core business priorities.
Deploying a new Management Service in Smart-1 Cloud takes just one minute. Once
deployment completes, you get a new Security Management Server instance running the
latest version - immediately ready to connect with Security Gateways. Existing customers can
easily migrate from their on-premises environment to Smart-1 Cloud. After migration, you can
resume work precisely where you left off with your on-premises Security Management Server
(see "Migrate" on page 48 for more information).
Note - Smart-1 Cloud supports SecureXL in User Space mode (UPPAK - User Space
Performance Pack) starting from R81.20 Jumbo Hotfix Accumulator Take 53.
Important - The insights CLI tool, which provides monitoring for the entire Scalable
Platform cluster in Expert mode and Gaia gClish, can display an error indicating a
mismatch in the IP address for the MaaS tunnel interface under a specific context ID.
This is a cosmetic issue and does not affect the functionality.
2. Click the Menu icon in the top left corner of the Infinity Portal window.
3. From the Quantum group, select Security Management.
Note - Security Management provides a unified experience for all your Quantum
Management solutions.
You can connect multiple self-hosted (on-premises) Security Management Servers
and manage one Smart-1 Cloud environment in a single Infinity Portal tenant.
4. If you access the Smart-1 Cloud portal for the first time, select one of these options:
n Connect your User Center account if you already have a Check Point contract.
When you select this option, the Attach Account window opens. For more
information, see Associated Accounts in the Infinity Portal Administration Guide.
After selecting existing account, the main screen shows a dashboard (a Security
Policies dashboard by default) of your environment.
n Start a free trial if you do not want to associate Smart-1 Cloud with a user account.
When you select this option, you can use Smart-1 Cloud for a 30-day period.
l After you select Start free trial, the welcome page offers to Create a new
Smart-1 Cloud Management or Connect an existing Self-Hosted (on-
premises) Management.
Click
To do this:
this:
n Infinity Services.
The Preparing Account window opens. It takes 1-2 minutes to create a new service.
After the process completes, a confirmation email is sent to your account.
3. Fill in the required fields for the Check Point Security Gateway:
a. Enter name - The name for the Security Gateway.
b. IP Address:
n Automatic IPv4 address: Smart-1 Cloud assigns an internal IP address
used for cloud communication over an outbound tunnel.
n Custom IPv4 address: Assign a static IP address, except when
configuring an SD-WAN Gateway.
You can configure the Security Gateway object in Smart-1 Cloud with a static IP
address as the primary IP address. This configuration is similar to setting up a
Security Gateway from an on-premises Security Management Server.
When the Security Gateway is configured with a Tunnel IP address,
management traffic, control connections, and Smart-1 Cloud tenant
communications use this main static IP address through the maas_tunnel
interface.
6. Connect to the CLI on the Security Gateway. In Clish, run the provided command to
set the authentication token. The initial connection status is Pending connection.
After the Security Gateway connects to Smart-1 Cloud, the status changes to
Connected.
7. To establish Secure Internal Communication (SIC) between the Security Gateway
and Smart-1 Cloud, enter the one-time password you set on the Security Gateway.
8. Click Next and wait until the Security Gateway connection process finishes. Then
close the Connect Device window.
9. Click OK.
b. In Clish, run the command shown in the wizard to set the authentication token.
The gateway status initially shows Pending connection. When the gateway
connects successfully to Smart-1 Cloud, the status changes to Connected.
c. Click Next.
6. Publish the changes.
c. Click OK.
d. To test SIC communication, open the Security Gateway object again and click
Test Communication in the Options menu.
4. Click Yes.
Connecting a Cluster
Procedure
Notes:
n When you enter the Cluster Virtual IP address, do not use IP
l 100.70.x.x
l 100.71.x.x
l 100.100.x.x
l 100.101.x.x
n When you add cluster members to the cluster object, use the
This step is required after the cluster's migration to Smart-1 Cloud. For more information,
see "Migrate" on page 48.
Follow these steps to deploy a new appliance in Zero Touch mode and configure it as a
Security Gateway or Cluster Member.
1. Remove your new appliance from the shipping carton, connect the power cable, and
turn on the appliance.
2. Wait for the light on one of the network interface ports to start blinking, then:
n If you have a DHCP server:
Connect the network cable to the blinking interface port.
Make sure this connection leads to the environment with a working DHCP
server.
n If you do not have a DHCP server:
Configure an interface with the appropriate networking settings:
a. Connect to the command line on the appliance.
b. In Expert mode, disable Zero Touch DHCP:
/opt/CPzetc/bin/zetc_setlaunch 0
Note - If your appliance does not appear, check the Service and Contract page.
5. Click on your appliance's card, enter the required information, and click OK.
To replace an existing Security Gateway, click the arrow next to the Configure Device
button.
6. Follow the on-screen instructions in the portal.
7. After the card status changes to Registration completed, you can configure your new
Security Gateway in SmartConsole.
You can configure the Security Gateway object in Smart-1 Cloud with a static IP
address as the primary IP address. This configuration is similar to setting up a
Security Gateway from an on-premises Security Management Server.
When the Security Gateway is configured with a Tunnel IP address,
management traffic, control connections, and Smart-1 Cloud tenant
communications use this main static IP address through the maas_tunnel
interface.
4. Click Connect in the Device field.
The Connect Device window opens.
5. In the Security Gateway section, select Quantum Spark.
6. In the Connection preference section, select "Prepare the object now, connect the
Security Gateway later". Click Next.
7. To establish trust between the Security Gateway and Smart-1 Cloud, configure the
one-time password and enter it later on the Security Gateway. Click Next
8. Copy the authentication token to paste it later in the Security Management Server
setup. Then close the Connect Device window.
9. Click OK.
10. Connect to the Quantum Spark WebUI, navigate to the Security Management tab, and
click Setup.
11. Select the Use Security Management service checkbox and click Next.
12. Click Use the Infinity Portal to generate a new authentication token and paste the
token. Click Connect.
13. Wait for the status to change to Connected successfully to the Security
Management Server, then click Next.
15. Check Connect to the Security Management Server now and click Connect.
To connect a Quantum Spark Cluster appliance to Smart-1 Cloud, follow these steps:
1. In the Check Point Cluster Member window, enter the name and IP address of
Member ID 1.
n Automatic IPv4 address: Smart-1 Cloud assigns an internal IP address used
for cloud communication over an outbound tunnel.
n Custom IPv4 address: Assign a static IP address, except when configuring
an SD-WAN Gateway.
2. Click Connect in the Secure Internal Communication section.
b. Click GET to fetch all interfaces and topology for both members.
5. Define the first Sync interface, then click OK.
6. Publish the changes.
1. In Smart-1 Cloud, go to Gateways & Servers, select the cluster you want to connect,
and click Edit.
2. The Check Point Cluster window opens with the existing cluster configuration.
1. From the Options menu, select the member name and click Edit Member.
2. In the Check Point Cluster Member window, in the Secure Internal Communication
section, click Connect.
3. In the Connect Device wizard window that opens, under Security Gateway, select
Quantum Spark.
4. Copy the token and save it separately.
5. Follow the on-screen instructions to configure the Quantum Spark Gateway.
1. Get back to the Connect Device wizard in Smart-1 Cloud and wait until the
connection status changes to Connected.
2. Click Next
3. Read the message and click Close.
4. In the Check Point Cluster Member window, click OK.
The preliminary configuration of the Member 1 is completed.
1. Repeat steps 2, 3, and 4 for Member 2 - Edit Member, Configure Quantum Spark
Gateway, and Connect Member.
2. Make sure the preliminary configuration of the Member 2 is completed the same way
as for Member 1.
To verify the results, make sure the connection is established on your Quantum Spark
Appliance.
1. In your Quantum Spark Appliance WebUI, open Home > Security Management
page.
2. Under Security Policy, click Fetch Policy.
3. A confirmation message appears when the application fetches the policy.
Prerequisite
Install the required hotfixes on the Security Group Member before you add it to the Security
Group that connects to Smart-1 Cloud. Make sure the maas_tunnel is active.
Limitations
n Smart-1 Cloud does not support Maestro Security Groups in the VSX mode.
n The SMO Image Cloning is not supported if the Security Group R81.10 and higher
contains different appliance models.
n DAIP is not supported.
n Automatic IP not supported with Maestro Security Group.
Procedure
1. On the Maestro Orchestrator, configure the required Security Group - in Gaia Portal or
Gaia Clish.
See the Quantum Maestro Getting Started Guide and the Maestro Administration
Guide for your version.
Important - Write down the IP address of the Security Group. You must
configure it later in Smart-1 Cloud.
2. Install the required Hotfixes on the Security Group: For details, refer to sk181495.
3. Connect to the Smart-1 Cloud Portal.
2. Run:
n In Gaia gClish:
maas status
2. Run:
n In Gaia gClish:
maas off
n In Gaia gClish:
maas on
Note - Because of port tunneling limitations, you can only establish one connection to
a Smart-1 Cloud tenant from a desktop SmartConsole on the same computer.
As an alternative, consider using Web SmartConsole or Streamed SmartConsole.
On the Smart-1 Cloud page, select Settings > API & SmartConsole > Open Web
SmartConsole.
On the Smart-1 Cloud page, select Settings > API & SmartConsole > Open Streamed
SmartConsole.
Go to Settings > API & SmartConsole > Instructions for using Installed SmartConsole.
If you downloaded the EXE file, double-click it and follow the on-screen instructions.
If you downloaded the ZIP file, extract it. Refer to sk116158 for details.
4. Open SmartConsole.
See the R81.20 SmartConsole Online Help Guide for more information about how to
use SmartConsole.
5. From the server drop-down menu, select Cloud.
Notes
n Hover over the help icon to view the relevant links:
n Get the Management Connection Token from Settings view > API &
SmartConsole > Instructions for using Installed SmartConsole.
Use the Settings tab to learn how to use Management APIs, set the administrator's password,
or migrate an on-premises Security Management Server to Smart-1 Cloud.
General
Note - You can interact with the Security Management Server through APIs to
perform the same tasks available in SmartConsole, such as creating objects, defining
Security Policies, and deploying configurations.
Service Information:
n Status: The current service status.
n Service Identifier: The unique service identifier based on the prefix provided during the
service creation. When you contact Check Point, you must use this service identifier.
n Version: The current Security Management Server version.
n License: Shows "active" for the purchased Smart-1 Cloud license or "trial" for the
evaluation license.
n Expires: Shows the number of days before license expiration.
From the Smart-1 Cloud home page, select Settings > API & SmartConsole.
The Management API page shows the current web request structure.
To copy these details, click the clipboard button.
For additional information, see Check Point Management API Reference.
1. On the Smart-1 Cloud home page, go to Settings > Advanced > Restart Service.
2. Click Restart Environment.
Migrate
You can migrate your self-hosted Security Management Server to the Smart-1 Cloud
environment.
Note - The migration operation overwrites tenant information and does not merge
existing tenant data.
1. Open the Infinity Portal tenant connected to the Self-Hosted Security Management
environment.
2. Select the self-hosted Security Management Server you want to migrate.
3. Click the three-dot menu:
4. To make sure you can migrate this Security Management Server to Smart-1 Cloud,
select Run Pre-migrate verifier.
5. Click Migrate to Smart-1 Cloud.
Important - The migration process may take considerable time. The Smart-1
Cloud application will be unavailable during import. You will receive an email
notification when the process completes and the service becomes available.
Notes:
n After migrating a Standalone environment, it is divided into separate
7. Click the plus (+) icon below the existing Security Gateway. Then select the Security
Gateway you want to connect and follow the on-screen instructions.
8. For a Security Gateway running a version lower than R80.40 with Jumbo Hotfix
Accumulator Take 89, reset the Secure Internal Communication (SIC) before
initializing communication from SmartConsole to the Security Gateway. For more
information, see sk65764.
You can import configurations from an on-premises Management Server to Smart-1 Cloud.
Migration to Smart-1 Cloud is supported starting from Security Management Server version
R81.10.
To migrate an on-premises Security Management Server to Smart-1 Cloud:
1. On the Smart-1 Cloud home page in Infinity Portal, go to Settings > Migrate.
2. Below Export Data, click Download to download the migration tools.
3. On the on-premises Security Management, run the export tool.
4. Below Import and Start, click Choose file to upload the export file.
5. Click Upload & Start to start the migration process.
7. Click the plus (+) icon below the existing Security Gateway. Then select the Security
Gateway you want to connect and follow the on-screen instructions.
8. For a Security Gateway running a version lower than R80.40 with Jumbo Hotfix
Accumulator Take 89, reset the Secure Internal Communication (SIC) before
initializing communication from SmartConsole to the Security Gateway. For more
information, see sk65764.
Add an account
1. To add an account, on the corresponding cloud provider tile, click Add account.
Parameter Description
Parameter Description
Regions The AWS regions in which the Security Gateways are being
deployed.
STS Role The Amazon Resource Name (ARN) of an IAM role to assume.
STS External ID An optional STS External ID to use when assuming an IAM role in
the account.
Sub Accounts Add new sub accounts or configure properties of existing sub
accounts. The sub-account name must be unique.
Enter STS Role or STS External ID.
Parameter Description
Parameter Description
Edit an account
1. To edit an account, click the Edit button at the right, above the cloud provider tiles.
The CME Overview window opens.
2. In the Accounts table, select the account you want to edit and click the "pencil" icon in
the toolbar above the table.
The CME Account window opens.
3. Edit the parameters.
4. Click OK to save the changes.
8. In the CME Attributes section, select the policy to install on the Security Gateway.
Note - To add support for AWS Transit Gateways to the AWS account,
configure the below parameters in the CME Attributes section.
TGW Static Spoke CIDR is learned from the TGW over BGP and is re-
Spokes advertised by the Gateways of the TGW auto-scaling group
to the AWS TGW.
For more information on AWS Transit Gateway, refer to CloudGuard Network
for AWS Transit Gateway Deployment Guide.
Note - To add IPv6 support to the Azure account, select the IPv6 checkbox in
the CME Attributes section.
11. In the NAT section, select which settings to use for communication with the Security
Management Server or log servers when they are behind NAT or in the public cloud.
Note - This section is enabled only for the R82 version of Security Gateway.
Advanced settings
To open the Advanced Settings window, click the Advanced link at the right, above the cloud
provider tiles. In this section, you can:
n Change the Security Management Server name.
n Change the Delay Cycle value (the waiting time after each poll cycle).
n Download logs with information about CME operations and API calls.
In the configuration page you see a table with forward to SIEM destinations, and information
for the destination, such as status, encryption, name, target port, protocol and format.
LogRhythm, or RSA.
n Protocol: The destination protocol, can be either TLS over TCP, TCP, or UDP
Procedure:
n Click the Client Certificate box to download the Client certificate sign request (cp_
client.csr).
Note - Signing the request is done in your organization and is not part of Smart-
1 Cloud services.
n After you sign the request, click Browse below the Client Certificate box to upload the
signed certificate.
Important - If it takes time to obtain the signed certificate for upload, you can close the
Add Forwarding Destination window. Open it again later when you have the signed
certificate, fill in all the details, and just click Browse to upload the certificate.
You do not need to click the Client Certificate box again, because this will create a
new sign request.
n Upload the CA certificate.
Troubleshooting
If no logs arrive to your SIEM, follow these steps:
Important - For information and updates on Smart-1 Cloud external FQDNs and their
associated IP addresses, see sk182699.
n Make sure that your Security Gateway does not block traffic from the Smart-1 Cloud
public FQDN:
l Ireland: eu-west-1.allowed-ips.checkpoint.com
l London: eu-west-2.allowed-ips.checkpoint.com
l N. Virginia: us-east-1.allowed-ips.checkpoint.com
l Sydney: ap-southeast-2.allowed-ips.checkpoint.com
l Mumbai: ap-south-1.allowed-ips.checkpoint.com
n Check if all the details in the configuration are correct.
n If you use TLS, make sure you are using the correct certificates.
n Restart the destination.
If the issue persist, contact Check Point support and open a Service Request.
3. Fill in the required fields for the Check Point Security Gateway:
a. Enter name - The name for the Security Gateway.
b. IP Address - Select the Dynamic Address checkbox.
4. Click Yes in the Enable Dynamic Address? window.
3. In the Connection preference section, select Prepare the object now, connect the
Security Gateway later.
4. Click Next.
3. Click Next and securely save the generated token. This will be used on the Quantum
Spark device later.
4. Click Close and then OK.
2. Select the Use Security Management service checkbox and click Next.
3. Click Use the Infinity Portal to generate a new authentication token and paste the
token. Click Connect.
4. Wait for the status to change to Connected successfully to the Security Management
Server, then click Next.
5. Set the one-time password and click Next:
6. Check Connect to the Security Management Server now and click Connect.
7. Click Finish.
7. In the Proxy through field, select the Security Gateway / Security Cluster that has a route
to your AD server.
gateways.
n Available communication types:
l Clear - Communication between the Security Management Server
LDAP queries.
l For Security Gateway functionality - depends on the identity sources
Note - If a Security Gateway object is created with a static IP address, access to the
Security Gateway Gaia Portal is allowed without any change.
Change the Platform Portal IP address to the Security Gateway IP address used for the Gaia
login.
Note - When configuring NAT rules, standard settings are available if the Security
Gateway object is created with a static IP address.
Consequently, the destination IP address of this rule is actually a virtual tunnel IP address, and
not the Security Gateway's physical external interface.
This screenshot shows the IP address in the tooltip:
To configure access from the Security Gateway's External IP address to the Internal Asset
with NAT Policy, a static rule in Smart-1 Cloud, you must create a dummy object with the
physical IP address of the Security Gateway. You then use it in the NAT rule.
In this screenshot, the dummy Host object ("GW_Ext_int") that contains the Security
Gateway's physical IP address, replaces the Security Gateway object ("GW-183").
Note - If you create the Security Gateway object with a static IP address and not with
the tunnel IP, link selection is not required. You can use the standard settings for VPN
configuration on the Security Gateway.
We recommend configuring in Smart-1 Cloud a static IP address in the Security
Gateway object for VPN configuration.
Smart-1 Cloud uses the Security Gateway object's primary IP address for the tunnel
communication between the Security Gateway and our service in cloud. It is a virtual interface.
Consequently, you cannot use the Main address option.
As an alternative, use one of these options to select an address from topology table:
Option 1:
Option: 2
Note - You require this configuration only when you have Site-to-Site VPN between
two Security Gateways (not clusters).
8. Run steps 2-7 again for all Security Gateways in the Site-to-Site VPN.
9. Install the Access Control policy on all applicable Security Gateways.
Example:
Management Capabilities
n Multi-Domain Security Management
l With Smart-1 Cloud, a customer can have multiple environments on the same
Infinity Portal account registered with the same email address. This is the
equivalent of managing multiple domains.
l You can easily switch between different environments in the portal by selecting the
environment name from the drop-down list at the top of the window.
l Single Sign-On (SSO) to the environments - The login from the portal to the
Streamed SmartConsole uses the portal's credentials and enables SSO.
n Management Objects
l The management object in Smart-1 Cloud is read-only and is not visible in the
gateways and servers view. It can be seen in the object explorer in read-only
mode.
l Running actions on the management object is not required. As part of the service,
environment backups run automatically every 12 hours.
n Management Login - Supported Methods
l Log into SmartConsole using your Infinity Portal credentials. For available Infinity
Portal login methods, see the Infinity Portal Administration Guide.
n Two-Factor Authentication
l For Infinity Portal login, enable this option in Global Settings.
n Managing Endpoint
l Use the new Harmony Endpoint (also available in the Infinity Portal) to manage
Endpoint clients.
n Managing HA
l In Smart-1 Cloud, the target is availability is 99.9% uptime; no additional HA
solution is required.
n CloudGuard Network Auto Scaling Solutions
l If you use Smart-1 Cloud to manage Auto Scaling groups, you must manage the
Security Gateways with their public IPs.
l To configure Smart-1 Cloud to automatically provision CloudGuard Network
Security Gateways, contact Check Point Support for the required autoprov
commands to run on the Management Server.
l To use the "vsec_lic_cli" tool to apply CloudGuard Network licenses, contact
Check Point Support.
l Connection of a CloudGuard Network Auto Scaling Security Gateway as a new
gateway is supported.
Note - Logs usage does not count the external exporters, for example:
n Tufin: Hostname or LogID = Service Identifier (for logs from forward to SIEM
configuration (Syslog)).
You can find the Service Identifier in Settings > General.
n Tufin's SecureTrack is supported to manage policies on Smart-1 Cloud.
Migration
When migrating a Security Management Server to Smart-1 Cloud from on-premises, review
these requirements before starting.
In some cases, configuration changes are required before or after the migration.
Important to know before you start:
Gateway object with an See the list of "Supported Gateways and Versions" on page 9.
unsupported appliance or A Gateway that belongs to an unsupported appliance or has an
version unsupported version is migrated but cannot be connected to
the Service.
Management Object You cannot edit the Management object in Smart-1 Cloud.
Configuration During the import process:
n NAT configuration is removed.
n Proxy configuration is removed.
n Old network configuration is ignored.
Network objects with IP Smart-1 Cloud uses this subnet. Change IP addresses to a
addresses from the different subnet.
subnet
100.64.0.0/24. See
details here.
Migration
n Migrating on-premises Security Management Server in the Full High Availability Cluster
mode to Smart-1 Cloud is not supported.
n Migration from pre-R81 Multi-Domain Security Management Server to a Smart-1 Cloud
server fails (see sk180650 for details).
Open the Permission Profile, navigate to Management, make sure Management API Login
is enabled.
Example:
The CLI requests username and password.
To configure and show the Security Policy and objects in the Security Management use the
Management APIs.
For more information, see Check Point Management API Reference.
Note - The Streamed SmartConsole has a built-in timeout mechanism which expires
after 15 minutes of idle operation and, or after two hours. After the session expires,
you need to log in again.
n You can save the files locally in My files. When it is necessary to upload files, use this
toolbar:
n Upload the files to a temporary folder in my files. Downloaded files are saved here. Use
the folder icon, on the top toolbar, to download files to the local computer.
IPS Updates
To fetch IPS Updates in Smart-1 Cloud, it is recommended to configure Smart-1 Cloud to
download with Security Management Server and not with SmartConsole.
In Smart-1 Cloud, by default, your Management Environment has Internet connectivity.
This is the recommended configuration that results in better performance.
Automatic Updates
Refer to sk166056 to see the up-to-date list of Smart-1 Cloud Automatic Updates.
Note - Licenses in Smart-1 Cloud are additive. Make sure to allocate all licenses to
the Check Point User Center account linked with the Infinity Portal account.
Activating a license
1. In Smart-1 Cloud, go to Global Settings > Contracts.
2. From the top-right, click Associated Accounts.
The Managed Accounts window opens.
3. Click Attach Account.
The Attach Account window opens.
4. Enter the User Center credentials > click Next.
5. Select the license to apply > click Finish.
Your license is shown in the Contracts page.
Notes:
n If you already have a related account and want to add one more
license, go to Global Settings > Contracts > Associated Accounts and
use the sync option to update the license.
In Smart-1 Cloud, the license status shows at this time: Active.
n It can take up to 24 hours for the license status to update to Active in
Smart-1 Cloud.
In the 'Trial' status there are no limitations to start and use the service.
If the status continue to show Trial, contact [email protected].
Notes:
n Smart-1 Cloud specific service roles are in addition to the global roles and do not
override them.
n Smart-1 Cloud Portal permission is relevant for CONNECT GATEWAYS and
SETTINGS tabs.
n Custom permission profiles in SmartConsole are always overridden by system
profiles pushed by the Infinity Portal.
For more information about user management, refer to the Infinity Portal Administration Guide.
Cannot open a tunnel from the n Make sure the Security Gateway can contact:
Security Gateway to the service. updates.checkpoint.com
Error: maas: command not n Make sure the gateway can contact:
found. https://<Service-
Identifier>.maas.checkpoint.com
Security Gateway is unable to Enable the Download consent flag for this Security
connect to the service. Gateway.
For instructions:
n For R81.20 and higher, refer to: sk175504.
n For R81.10 and lower, refer to: sk111080.
No SIC with the Security Gateway. n Do these steps to connect the Security
Gateway:
Navigate to the Check Point Infinity Portal >
Smart-1 Cloud > select Connect Gateway.
n Make sure the MaaS tunnel is up and running:
l Run one of these commands:
o maas status
o show security-gateway
cloud-mgmt-service
l Run the ifconfig command and make
Tunnel works, but there is no n Make sure the MaaS tunnel is up and running:
communication between the l Run one of these commands:
cloud-mgmt-service
l Run the ifconfig command and make
After I installed policy, I lost n You must allow outbound HTTPS traffic to
management communication with FQDN listed below to allow the communication
the Security Gateway. between the Security Gateway and the
service:
l To your domain at Smart-1 Cloud:
<Service-
Identifier
>.maas.checkpoint.com
l For Smart-1 Cloud deployments in
Europe:
cloudinfra-
gw.portal.checkpoint.com
l For Smart-1 Cloud deployments in the
United States:
cloudinfra-gw-
us.portal.checkpoint.com
l For Smart-1 Cloud deployments in the
APAC:
https://cloudinfra-
gw.ap.portal.checkpoint.com
n If this is not possible, then reset the SIC, or
contact Check Point Support.
The " maas on or "set Make sure that the Security Gateway time is correct
security-gateway cloud- and synced with NTP.
mgmt-service on auth-token
XXXX" command shows this error:
error 132
The "maas status" or "show 1. Make sure your policy enables outgoing
security-gateway cloud- HTTPS (TCP 443) to your domain at MaaS:
mgmt-service" command <Tenant-ID>.maas.checkpoint.com
returned: If the Security Gateway connects to Smart-1
MaaS Status: Enabled Cloud through a Proxy Server, make sure the
MaaS Tunnel State: Down Security Gateway can connect to this Proxy
Unable to connect to MaaS Server.
at https://<Service- 2. If the Security Gateway connects to Smart-1
Identifier Cloud through a Proxy Server, make sure your
>.maas.checkpoint.com policy allows the HTTPS traffic to your Proxy
Server.
3. Make sure the Security Gateway can connect
to Smart-1 Cloud using FQDN, and there is no
HTTPS inspection:
a. Connect to the command line on the
Security Gateway and log in to the
Expert mode.
b. Get the Smart-1 Cloud FQDN and
CloudInfra URL:
CloudInfraURL=`jq -r
".data.cloudInfaUrl"
$FWDIR/conf/cloudinfra.conf`
FQDNURL=`jq -r ".data.fqdn"
$FWDIR/conf/cloudinfra.conf`
c. Try to connect to Smart-1 Cloud using
FQDN:
curl_cli $CloudInfraURL -k -
vvv
curl_cli https://$FQDNURL -k
-vvv
4. Compare the certificate the Security Gateway
gets in the curl_cli command output to the
certificate you see when you do not use the
proxy.
Gateway Gaia Portal not accessible. See "How to Configure Access to Security Gateway
Gaia Portal" on page 70.
Cannot change the SmartConsole Go to SmartConsole > Manage & Settings and
admin password from the Infinity make sure that the administrator password is not
Portal. configured as an OS password.
If it is, change it to Check Point password.
Error message in SmartConsole log Make sure that you have the latest SmartConsole
in, "Could not verify shared version.
secret". Download the SmartConsole from the Smart-1
Cloud portal (topic SmartConsole)
When you add a Cluster Member, Fetch cluster topology again, see sk171157.
the "failed to save object
validation error on maas_
tunnel network object"
messages appears.
Cannot see Security Gateway logs n Make sure the consent flag to upload data to
in SmartConsole, or the Security Check Point is enabled on the Security
Gateway does not send logs to Gateway (see sk111080).
Smart-1 Cloud. n Install Database:
1. Open SmartConsole.
2. Click the Menu > Install Database.
3. Select the Management Server object.
4. Click Install.
maas status
n In Gaia Clish:
1. New Quantum appliance is not 1. Make sure the Service and Contract page
discovered automatically on shows the correct contract.
the Connected Gateways 2. Make sure the appliance is powered on and
page. connected to the Internet with the blinking
2. Attempt to on board a new interface (this interface is configured to get an
Quantum appliance IP address from a DHCP server).
encounters an issue with 3. Make sure the appliance received the required
connectivity resulting in a "No IP address configuration from the DHCP
internet connection" server:
page. a. Connect to the command line on the
appliance.
b. Log in.
c. If you default shell is the Expert mode,
then go to Gaia Clish:
clish
d. Make sure the appliance received the
correct IP address:
show interface <Name of
Blinking Interface> all
e. Make sure the appliance received the
correct Default Gateway:
show route
4. Make sure your network allows the connection
from this appliance to the
zerotouch.checkpoint.com server.
Therefore, when required to use the Management IP address, such as Central License, use
this IP address: 100.64.0.52.
After Check Point releases a new software version, when is my Smart-1 Cloud environment
upgraded?
Several weeks after the release of a new GA version, Smart-1 Cloud is upgraded and runs
the new version for new environments.
Afterward, we gradually upgrade for existing customers.
The service runs pro-active monitoring on all production environments; in some cases,
maintenance actions are required to provide stable operation.
All maintenance operations are done after usual work hours for each deployed region and in
accordance with the regional maintenance windows.
For non-disrupted operations or operations with disruptions lasting up to 10 minutes, no
notification is shared with the customer.
(This is done only during regular off-hours.)
There are rare cases, such as major version upgrades, in which the maintenance operation
may take 1-2 hours. In such cases, an email notification is sent 10–14 days in advance,
providing a range of 2–3 days in which the operation will take place (again, always within
regional off-hours). The customer can reply to the email and request to reschedule to
another range.
Regional maintenance windows:
n APAC, India, EU and US - Every Sunday
n EU/UK - weekdays - from 20:00 to 06:00 am CET
n US - weekdays - from 20:00 to 06:00 am CST
n IN - weekdays - from 20:00 to 06:00 am IST
n APC - weekdays - from 20:00 to 06:00 am ACT (Australian Central Time)
You must allow outbound HTTPS traffic to FQDN listed below to allow the communication
between the Security Gateway and the service:
n To your domain at Smart-1 Cloud:
<Service-Identifier>.maas.checkpoint.com
n For Smart-1 Cloud deployments in Europe:
cloudinfra-gw.portal.checkpoint.com
n For Smart-1 Cloud deployments in the United States:
cloudinfra-gw-us.portal.checkpoint.com
n For Smart-1 Cloud deployments in the APAC:
https://cloudinfra-gw.ap.portal.checkpoint.com
From version R80.40, there is an implied rule that always allows this traffic when working in
the MaaS mode.
You can use the same SmartConsole to connect to your Smart-1 Cloud environments and
to your on-premises environments.
Yes, you can use the Management APIs with Smart-1 Cloud, go to Settings > API &
SmartConsole.
For more information, see the Check Point Management API Reference.
Backups of the environments are taken daily for the first ten days and, after that, less
frequently..
All tasks related to the maintenance of the environment are part of the service.
You can open a ticket with Check Point Support for assistance with SSH.
A customer that decides to cancel the service and needs the management DB (to move it to
the on-premises management), must open a Service Request with Check Point Support
and ask for the management database.
Note - It is not possible to download the logs.
Do these changes in configuration:
n Change the IP address in the management object (that primary IP address that holds
the Smart-1 Cloud management IP address).
n If "*.def" files were changed, then it is necessary to apply the changes. As an
alternative, request the files from Check Point Support.
n Other special configuration such as Security Gateway as a proxy to access the LDAP.
n On the Security Gateway, disconnect the Security Gateway from Smart-1 Cloud, run
the "maas off" command on the Security Gateway.
See "Smart-1 Cloud Gateway Commands" on page 59.
I purchased a Smart-1 Cloud license. How do I apply it, and what visibility do I have?
Congratulations, you have decided to join Smart-1 Cloud and purchased a license.
To help you ,our team will reach out to your sales representatives to get all the necessary
information.
For more information, see "Smart-1 Cloud License" on page 86.
If the issues continue, contact Account Services and ask to configure your account as
production.
Provide these details:
n Infinity Portal account name
n Smart-1 Cloud Service Identifier
n User Center Account
Which IP addresses the service uses to connect the Security Gateway to the Smart-1 Cloud?
When you register a new Gateway to the service, an IP address from one of these subnets
is used for the creation of a secure tunnel between the Security Gateway and the Smart-1
Cloud:
n 100.64.0.0/16
n 100.70.0.0/16
n 100.71.0.0/16
n 100.100.0.0/16
n 100.101.0.0/16
Note - The virtual interface that is created on the Security Gateway uses this IP
address as the primary IP address in the object that shows the Gateway in
SmartConsole..
Your Smart-1 Cloud license determines two key parameters for log management:
n Maximum daily log ingestion rate
n Log retention period (the number of days logs are stored)
These parameters vary based on your specific license SKU.
The standard offering includes 90 days of data retention. Extended retention periods (6
months or 1 year) are available for specific license SKUs (for more information on license
SKUs, see sk182394).
To monitor your log usage, check the Average Monthly Ingestion and Daily Log Ingestion
graphs on the Infinity Events > Log Ingestion page.
1. If you have a DAIP Security Gateway and you are concerned with the connectivity
between the Security Management Server and the Security Gateway, you can
configure the tunnel IP in the Security Gateway object.
2. When you configure a DAIP Security Gateway in Smart-1 Cloud, on the initialize SIC
sequence, you must enter the tunnel IP address as the Gateway IP address.
For support of the ICA Management Tool contact Check Point Support.
Yes, the Compliance blade is supported. You can see it from the Streamed SmartConsole.
Refer to "Log in to SmartConsole from Smart-1 Cloud" on page 43
To add or attach a VPN license to Smart-1 Cloud, contact Check Point Support and open a
service request.
Yes, ElasticXL is supported starting from R82. This is a new clustering technology that
simplifies operations by using a single management object, offering automatic configuration
and software synchronization across all cluster members.