Pre-boot authentication in Harmony Endpoint disablesworkarounds to computer security. This is explicitly stated in theCP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdfonpage 223, under "Authentication before the Operating System Loads (Pre-boot)," which explains: "only authorized users are given access to information stored on desktops and laptops" by requiring authentication before the OS loads. This prevents unauthorized access attempts that might bypass OS-level security measures, such as booting from alternative media or exploiting OS vulnerabilities-effectively disabling "workarounds to computer security."
* Option B ("Identity theft")is a broader security concern not specifically addressed by pre-boot authentication; it's a potential outcome, not a direct mechanism disabled.
* Option C ("Incorrect usernames")is a user error, not something pre-boot authentication disables; it simply rejects invalid credentials.
* Option D ("Weak passwords")relates to password policy enforcement (covered on page 264), not the function of pre-boot authentication itself.
* Option A ("Workarounds to computer security")is directly supported by the documentation, as pre- boot authentication ensures security at the earliest stage, blocking bypass attempts.
References:
CP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdf, Page 223: "Authentication before the Operating System Loads (Pre-boot)" (describes the purpose of pre-boot authentication).
CP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdf, Page 264: "Password Complexity and Security" (covers password policies, not pre-boot authentication's role).

In the Harmony Endpoint portal, the POLICY Tab is used to manage security policies for various software capabilities such as Threat Prevention, Data Protection, and others. These policies are enforced through rules that dictate how each capability behaves on endpoint machines. TheCP_R81.
20_Harmony_Endpoint_Server_AdminGuide.pdfprovides clear evidence on how these rules are structured by default.
Onpage 166, under the section "Defining Endpoint Security Policies," the documentation states:
"You create and assign policies to the root node of the organizational tree as a property of each Endpoint Security component." This indicates that a default policy (or rule) is established at the root level of the organizational hierarchy, inherently applying to all entities-users and computers-within the organization unless overridden by more specific rules. Further supporting this, onpage 19, in the "Organization-Centric model" section, it explains:
"You then define software deployment and security policies centrally for all nodes and entities, making the assignments as global or as granular as you need." This global assignment at the root node confirms that the default rule encompasses all users and computers in the organization, aligning withOption D. The documentation does not suggest that the default rule is limited to computers only (Option A), nor does it state that no rules exist initially (Option B), or that rules are exclusive to the Firewall capability (Option C). Instead, each capability has its own default policy that applies globally until customized.
* Option Ais incorrect because the default rule is not limited to computers. Page 19 notes: "The Security Policies for some Endpoint Security components are enforced for each user, and some are enforced on computers," showing that policies can apply to both based on the component, not just computers.
* Option Bis false as the guide confirms default policies exist at the root node, not requiring administrators to create them from scratch (see page 166).
* Option Cis inaccurate since rules exist for all capabilities (e.g., Anti-Malware on page 313, Media Encryption on page 280), not just Firewall, and all capabilities involve rules, not just actions.
References:
CP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdf, Page 19: "Organization-Centric model" (global policy assignment).
CP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdf, Page 166: "Defining Endpoint Security Policies" (policy assignment to the root node).

Full Disk Encryption (FDE) primarily protects data when the computer is turned off or locked. If the laptop is booted and left unattended without being locked or shut down, the encryption does not actively protect data at the moment. Anyone who gains physical access to the device during this time can view and access all open data and applications until the computer auto-locks or is manually locked.
Exact Extract from Official Document:
"Pre-boot Protection requires users to authenticate to their computers before the computer boots. This prevents unauthorized access to the operating system using authentication bypass tools at the operating system level or alternative boot media to bypass boot protection." This implies that once booted and logged in, the data is accessible if the laptop is left unattended and unlocked.
Reference:Check Point Harmony Endpoint Specialist R81.20 Administration Guide, Section: "Pre-boot Protection".