Client will also not go into the assumed compliance state. Then, on the server side there will be no compliance reporting (inform, warn, restrict). cloned or edited, this rule will not be applied to the macOS Compliance blade. If the default name of the compliance rule for checking if assigned blades are running is changed, i.e. The following compliance checks are not supported:
Remediation actions are not triggered on macOS.Įnvironment variables in path of checked files are not supportedĬompliance blade on macOS currently supports checks for the following Anti-Virus vendors: The Forensics report does not show Network events. If nodeJS is installed on the Mac, build directories should be excluded in SBA policy (AR/EFR and TE) to improve performance.ĮPS-40903: Time machine restore of a backup containing an Endpoint Security installation is not supported.
The Big Sur macOS version does not display correctly in SmartEndpoint reports. To avoid this, Check Point recommends MDM management tools to predefine the desired configurations. The Big Sur macOS, (and later) may ask users to grant access to security modules after some special activities. Only English is supported as the interface's language. To use SideCar and Airdrop features, starting E83.20 for macOS client, you need to allow IPv6 traffic in the Endpoint Firewall policy.
Emulation on local Threat Emulation (TE) appliances is supported
0 kommentar(er)
