- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
10-21-2022 01:58 AM
Hi community,
Does somebody is using Cortex XDR - Network Localtion (from agent settings profile).
My problem is that the network location is too long, specifically when users comme back to our office from their own internet connection, internal profile takes about 2 minutes to change from external to internal.
External = restricted firewall policy
Internal = light FW policy.
So logon scripts ... are timed out du to Cortex location too long to change.
Have you tried this, how do you deal with network location changing time?
Thank you !
Olivier.
10-21-2022 02:56 AM
Hi @Olivier-C ,
This is a known limitation due to checkin times. The agent performs a heartbeat to the cloud every 5 minutes and hence agents which are not able to checkin on network change do it in the next heartbeat cycle. This is a known behaviour and the lag is intermittent for the same reason. The agent upon the next checkin realises the location difference upon DC connectivity test and applies the rules accordingly. The workaround for this is that you set the required permissive rules which is a priority at the top and that should facilitate faster times for the same. Further you can request our TAC team to support further for the same.
Hope that answers your question!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!