Nimbostratus
Cumulonimbususually the windows's system level startup is controlled via Task Scheduler (taskschd.msc).
you might try to arrange the task order so that F5 VPN agent is started after Palo alto antivirus.
you can also try to change service startup of Palo Alto AV to "Automatic (delayed start)" in services.msc
NimbostratusThanks for your answer.
F5 VPN client is not automatically launched on Windows startup, it's a user action. So the issue appears when the user opens the VPN client very quickly after computer startup.
Do you know how the compliance check is done ? I could give the info to Palo Alto so they can figure out the issue.
Cumulonimbususually the vpn client has dictionary of the process names.
it also checks the signature, version, etc. of of the av executables.
vpn client usually has background components that runs as background services.
correction to my previous comment, you can try to set f5 vpn backgound service as "Automatic delayed start" while set Paloalto AV as "Automatic"
Nimbostratus
zamroni777 wrote:usually the vpn client has dictionary of the process names.
it also checks the signature, version, etc. of of the av executables.
That's what I thought. We've noticed that the cyserver.exe process (one of the main Cortex processes) also takes around 1 minute 30 to start up. Is it possible that this is the process being checked? Where can I find information on which process is verified by the client (and therefore OPSWAT) for Palo Alto Cortex XDR?