Hi all, Is there any documented best practice on how to implement Security Heartbeat? I have activated heartbeat on our XG appliance and the Cloud Endpoint devices are reporting their status so the first part has already been implemented. I have two specific questions: To be able to quarantine infected devices I guess a separate “Heartbeat” zone/VLAN with heartbeat enabled policies are needed to avoid blocking not heartbeat enabled devices such as smartphones, scanners, printers etc.? During the Windows boot process, when does the client report its heartbeat status, and when is the device allowed internet access? We have a lot of Azure AD joined Windows 10 devices signing in to Azure AD that will need Internet access before the user has signed in. Will this be possible with heartbeat enabled policies? Anyone have any experience with this?

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Security Heartbeat implementation best practice?

Hi all,

Is there any documented best practice on how to implement Security Heartbeat?

I have activated heartbeat on our XG appliance and the Cloud Endpoint devices are reporting their status so the first part has already been implemented.

I have two specific questions:

To be able to quarantine infected devices I guess a separate “Heartbeat” zone/VLAN with heartbeat enabled policies are needed to avoid blocking not heartbeat enabled devices such as smartphones, scanners, printers etc.?
During the Windows boot process, when does the client report its heartbeat status, and when is the device allowed internet access? We have a lot of Azure AD joined Windows 10 devices signing in to Azure AD that will need Internet access before the user has signed in. Will this be possible with heartbeat enabled policies?

Anyone have any experience with this?

This thread was automatically locked due to age.