Skip to content

Commit

Permalink
chore: mention sysmon config as possible workaround
Browse files Browse the repository at this point in the history
  • Loading branch information
secDre4mer committed Feb 3, 2022
1 parent 97ee874 commit c516552
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion usage/detection-gaps.rst
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ There is no ETW provider that provides information about creation of or connecti
is the Kernel Object Handle provider which provides information about all handles that are opened and closed, but which is therefore very "noisy"
and only enabled in the intense configuration.

For this reason, Aurora in its standard configuration is unable to detect named pipe creations or connections.
To fill this detection gap, Sysmon can be used with e.g. `this configuration <https://github.com/NextronSystems/aurora-helpers/blob/master/sysmon-config/aurora-sysmon-config.xml>`_.

Registry Events
---------------
Expand Down Expand Up @@ -42,6 +42,8 @@ These captured events display the issues here: The first event (with Event ID 2)
The second event (with Event ID 7) is a `QueryValue` event. Again, the ``KeyName`` is empty; instead, the ``KeyObject`` field needs to be correlated with previous `OpenKey` events.
The data that was returned from the `QueryValue` is also missing. There is a field for it, (``CapturedData``) but it is apparently empty based on the ``CapturedDataSize`` and querying its value fails with the displayed error message.

To fill this detection gap, Sysmon can be used with e.g. `this configuration <https://github.com/NextronSystems/aurora-helpers/blob/master/sysmon-config/aurora-sysmon-config.xml>`_.

ETW disabling
-------------

Expand Down

0 comments on commit c516552

Please sign in to comment.