How are the agents differentiated upon deployment and when you upgrade the agent?

When an agent is installed on a host, it generates a unique token and saves it in the Windows Registry on that host.

That unique token identifies that host to SecTeer VulnDetect.

When the agent is upgraded, it preserves the unique token and thus preserves its identity.

Related Articles
Does VulnDetect use remote or agent-based scans?
SecTeer VulnDetect utilizes agent-based scans with minimal resource usage.
I have deployed an Agent that is associated with the wrong Account or Site, can I just overwrite the Agent?
No, this requires that the old Agent is uninstalled first. When the agent is successfully installed, a unique auth-token is added to the registry. This auth-token is associated with the supplied email and used to identify the agent when it ...
Can I specify the group when deploying the agent MSI?
Yes. For this to work, the MSI needs to be run with the following options: msiexec.exe /quiet /i secteerSetup.msi WRAPPED_ARGUMENTS=”/options=group=groupname” groupname must be replaced with the group’s full name in VulnDetect. If the group name has ...
I would like to re-install the SecTeer VulnDetect Agent. Where can I find the Installer?
The SecTeer VulnDetect Agent can be downloaded from your Dashboard under “configuration”.
Is the communication between the SecTeer VulnDetect Agent/Graphical User Interface and SecTeer encrypted?
All the communication between the SecTeer VulnDetect Agent or the SecTeer VulnDetect Graphical User Interface and SecTeer is made through port 443, and by using SSL protocol with 256-bit encryption.

Related Articles