Skip to content

Fix USB monitoring example to use local ossec.conf #341

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
atomicturtle merged 1 commit into from
Jun 28, 2026
Merged

Fix USB monitoring example to use local ossec.conf #341

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 8 additions & 7 deletions docs/manual/monitoring/process-monitoring.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -135,21 +135,22 @@ Detecting USB Storage Usage
OSSEC. He used our policy auditing module for that, but I think USB monitoring
can be done in a much easier way with our new :xml:`check_diff` feature.

To get started, first configure your Windows agents to monitor the USBSTOR
registry entry using the reg command:
To get started, configure each Windows agent to monitor the USBSTOR registry entry
using the ``reg`` command. This must be in the agent's local ``ossec.conf`` — the
manager cannot push ``command`` or ``full_command`` localfile entries through
``agent.conf`` (see :ref:`full_command`).

.. code-block:: xml

<agent_config os="windows">
<ossec_config>
<localfile>
<log_format>full_command</log_format>
<command>reg QUERY HKLM\SYSTEM\CurrentControlSet\Enum\USBSTOR</command>
<frequency>3600</frequency>
</localfile>
</agent_config>
</ossec_config>



Next create a local rule for that command:
Next create a local rule for that command on the manager:

.. code-block:: xml

Expand Down
Loading