Pass the Checkpoint CCES 156-536 Questions and answers with CertsForce

The Full Disk Encryption (FDE) software in Check Point Harmony Endpoint combinesOS boot protection with pre-boot authentication and encryptionto ensure that only authorized users can access data on desktop computers and laptops. This is detailed in theCP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdfonpage 217, under "Check Point Full Disk Encryption," where it states:

"Combines Pre-boot protection, boot authentication, and strong encryption to make sure that only authorized users are given access to information stored on desktops and laptops."

This extract highlights three key elements:

Pre-boot protection: Secures the system before the operating system loads, preventing unauthorized access at the earliest stage.

Boot authentication: Requires users to authenticate (e.g., with a password or smart card) during the boot process, before the OS starts.

Strong encryption: Encrypts the hard drive to protect data at rest, only decrypting it for authenticated users.

Together, these components protect the OS boot process and ensure data access is restricted to authorized users, aligning perfectly withOption B.

Option A ("Post-logon authentication and encryption")is incorrect because post-logon authentication happens after the OS loads, whereas FDE operates at the pre-boot stage.

Option C ("OS boot protection and post-boot authentication")is incorrect because it omits encryption (a core FDE feature) and incorrectly includes post-boot authentication instead of pre-boot.

Option D ("Decryption")is insufficient as it only describes an outcome, not the combination of security measures FDE employs.

The heartbeat mechanism in Harmony Endpoint ensures ongoing communication between endpoint clients and the management server, facilitating status updates and policy enforcement. TheCheck Point Harmony Endpoint Server Administration Guide R81.20clarifies the timing of this process.

Onpage 27, under "Client to Server Communication," the guide notes:

"The client is always the initiator of the connections. Most communication is over HTTPS (TCP/443), including Policy downloads and Heartbeat."

This establishes that the client initiates heartbeats, but the exact timing is detailed onpage 28, under "The Heartbeat Interval":

"Endpoint clients send 'heartbeat' messages to the Endpoint Security Management Server to check the connectivity status and report updates."

Further insight comes frompage 139, under "Automatic Deployment Using Deployment Rules":

"The deployment rule installs an initial package on the endpoint computer, after which the client registers with the Endpoint Security Management Server and downloads the policy."

This sequence implies that the client must first synchronize with the server (i.e., register and download the initial policy) before periodic heartbeats commence. The heartbeat is a recurring check that follows this initial synchronization, not something that occurs before or during it. Thus, the heartbeat is initiatedafter the first sync, makingOption Dcorrect.

Evaluating the alternatives:

Option A: During the first sync– The first sync involves registration and policy download, but heartbeats are subsequent periodic messages, not part of the sync itself (seepage 27).

Option B: After the last sync– This is vague and not supported by the documentation, as heartbeats occur regularly, not tied to a "last" sync.

Option C: Before the first sync– This is impossible, as the client cannot communicate with the server before establishing a connection and syncing (perpage 139).

Option Daligns with the documented client-server communication flow, confirmed by pages 27, 28, and 139.

An administrator can confirm a successful macOS Harmony Endpoint client installation whenthe Endpoint icon appears in the computer's menu bar. This is stated on page 151 under "Deploying Mac Clients," noting that "After installation, the Endpoint Security icon appears in the menu bar." Options like automatic reboot (A) or pop-up messages (B, D) are not documented as standard indicators of successful installation in the guide.

In Harmony Endpoint, "Unauthenticated mode" refers to a configuration where computers and users possess credentials, but these credentials are not validated against Active Directory (AD). This mode is used when AD authentication is not implemented or required, yet some form of credential-based access control is still in place.

TheCP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdfdoes not provide a single, explicit definition of "Unauthenticated mode" in a dedicated section. However, the concept is inferred from the authentication mechanisms described, particularly in relation to Active Directory integration. Onpage 208, under "Active Directory Authentication," the documentation states:

"Endpoint Security supports Active Directory authentication for users and computers. This allows for centralized management of user credentials and policies."

This indicates that AD authentication is a supported method for verifying credentials centrally. Onpage 209, in "Configuring Active Directory Authentication," the guide details the process for enabling AD-based authentication, implying that without this configuration, credentials are not verified through AD. In such cases, the system may rely on local credentials or alternative methods, which aligns with the concept of "Unauthenticated mode" (i.e., not authenticated via AD).

Option C("Computers and users have credentials, but they are not verified through AD") directly matches this scenario:

"Have credentials": Users and computers still use credentials (e.g., usernames and passwords) to access the system.

"Not verified through AD": These credentials are not checked against an AD server, distinguishing this mode from AD-authenticated setups.

Let’s analyze the other options:

Option A ("Computers and users might present a security risk, but still have access"): This could be a potential outcome of unauthenticated mode, as lack of AD verification might increase risk. However, it describes a consequence rather than defining the mode itself, making it less precise.

Option B ("Computers and users are trusted based on their IP address and username"): The documentation does not mention trust based on IP address and username without AD verification, so this is unsupported.

Option D ("Computers and users are trusted based on the passwords and usernames only"): This is partially correct, as unauthenticated mode may involve local credential checks. However, it lacks the critical distinction of "not verified through AD," which is central to the concept in Harmony Endpoint.

Thus,Option Cis the most accurate and specific definition based on the documentation’s discussion of authentication methods.

On-premises servers have only two user roles: "Admin" & "Read-only".

These are the roles:

Admin - Full Read & Write access to all system aspects.

Read-Only User - Has access to all system aspects, but cannot make any changes.

https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_EndpointWebManagement_AdminGuide/Topics-HEPWM-R81/Managing_Users_in_Harmony_Endpoint.htm

Endpoint Policy Servers (EPS) are integral to the Harmony Endpoint architecture, designed to optimize communication between Endpoint clients and the Endpoint Security Management Server (EMS). TheCP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdfexplicitly defines their placement.

Onpage 25, under "Optional Endpoint Security Elements," the documentation states:

"Endpoint Policy Servers improve performance in large environments by managing most communication with the Endpoint Security clients. Managing the Endpoint Security client communication decreases the load on the Endpoint Security Management Server, and reduces the bandwidth required between sites."

This confirms that EPS are positionedbetween the Endpoint clients and the EMS, handling tasks like policy downloads, heartbeats, and updates to offload the EMS.Option Baccurately reflects this architecture.

Evaluating the other options:

Option A: "Between the Endpoint clients and the EPS" is nonsensical, as EPS (Endpoint Policy Servers) cannot be between themselves and clients—it’s a self-referential error.

Option C: "Between the Endpoint clients and the NMS" introduces "NMS," likely a typo for Network Management System, which isn’t part of Harmony Endpoint’s architecture per the document.

Option D: "Between the Endpoint clients and the SMS" refers to the Security Management Server (SMS), which manages gateways in Check Point’s broader ecosystem, not the EMS specific to Harmony Endpoint (seepage 23for EMS definition).

Thus,Option Bis directly supported by the documentation as the correct placement of EPS.

According to Check Point documentation, the on-premises environment provides organizations with significantly greater control over product deployment and operation, including more extensive configuration options compared to a cloud-managed environment. Although this level of control is advantageous, it is also noted that it typically comes with higher support and maintenance costs.

Exact Extract from Official Document:

"On-premises environment offers more options for deployment, greater control over operations, but it is also more costly to support."

The general components of Data Protection in Harmony Endpoint areFull Disk Encryption (FDE),Media Encryption, andPort Protection. This is explicitly detailed in theCP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdfon page 20 under "Introduction to Endpoint Security," within the table listing "Endpoint Security components that are available on Windows." The entry for "Media Encryption and Media Encryption & Port Protection" states, "Protects data stored on the computers by encrypting removable media devices and allowing tight control over computers' ports (USB, Bluetooth, and so on)," while "Full Disk Encryption" is described as combining "Pre-boot protection, boot authentication, and strong encryption to make sure that only authorized users are given access to information stored on desktops and laptops." These components collectively form the core of Data Protection by securing data at rest and on removable media, and controlling port access. Option B accurately lists these three components. Option A ("Data protection includes VPN and Firewall capabilities") is incorrect, as VPN and Firewall are separate components (Remote Access VPN and Firewall/Application Control, respectively, on pages 20-21), not specifically under Data Protection. Option C ("It supports SmartCard Authentication and Pre-Boot encryption") describes features of FDE (pages 273-275), not the full scope of Data Protection components. Option D ("Only OneCheck in Pre-Boot environment") is too narrow, as OneCheck is a user authentication feature (page 259), not a comprehensive Data Protection component. Thus, option B is the verified answer.

The Check Point Harmony Endpoint documentation clearly specifies that the pre-boot environment supports multi-factor authentication methods. These methods combine different authentication mechanisms to enhance security significantly beyond traditional password-based authentication alone.

Exact Extract from Official Document:

"You can also use TPM in addition to Pre-boot authentication for two-factor authentication."