OSSEC Authd

New in version v1.1.

ossec-authd is an automatic agents registration tool, it will automatically add an agent to the manager and provide a new key to the agent.

Now, ossec-authd tool is password protected, increasing security in the agent registration process. OSSEC Manager looks for a defined password at file /var/ossec/etc/authd.pass. If a password isn’t found, a random one is generated and shown on the console.

Duplicated IPs are no longer allowed. So if there’s an attempt to add two agents with the same IP, ossec-authd will fail and report it through an alert.

Configuration

On server-side

New options:

-i Register agent with client’s IP instead of any.
-f <seconds> Remove old agents with the same IP if they were not connected since <seconds>. It has only sense along with option -i.
-P Enable shared password authentication.

Option -f forces the insertion on IP collision, this means that if OSSEC finds another agent with the same IP, but it has not connected since a specified time, that agent will be deleted automatically and the new agent will be added. To force insertion always (regardless of the time of the last agent connection), use -f 0.

See also

For a complete description of every option, please read OSSEC documentation: ossec-authd.

On client-side

New options:

-P <password> Use the specified password instead of searching for it at authd.pass.

If a password is not provided in the file nor on the console, the client will connect with the server without a password (insecure mode).

See also

For a complete description of every option, please read OSSEC documentation: agent-auth.

Data backup

Before OSSEC removes an agent by forcing, it will backup the data of the old agent in /var/ossec/backup/agents/<id> <name> <ip> <delete timestamp>, in a new folder with the agent’s name and IP, and the current timestamp. The saved data is the following:

  • Agent’s operating system.
  • Version of the agent.
  • Timestamp when it was added.
  • Syscheck database.
  • Rootcheck database.

See also

There is a compile option that allows a new agent to inherit the ID of the agent that was removed by forcing insertion. To learn more about this, please read Agent ID reusage.