ldap.responses.attribute_type matches on LDAP attribute type/description
This keyword maps the eve field ldap.responses[].search_result_entry.attributes[].type
It is a sticky buffer
Supports multiple buffer matching
Supports prefiltering
Ticket: #7533
@ -498,3 +498,40 @@ add request operation and contains the LDAP attribute type
..container:: example-rule
alert ldap any any -> any any (msg:"Test attribute type and operation"; :example-rule-emphasis:`ldap.request.operation:add_request; ldap.request.attribute_type; content:"objectClass";` sid:1;)
ldap.responses.attribute_type
-----------------------------
Matches on LDAP attribute type from response operations.
Comparison is case-sensitive.
Syntax::
ldap.responses.attribute_type; content:"<content to match against>";
``ldap.responses.attribute_type`` is a 'sticky buffer' and can be used as a ``fast_pattern``.
``ldap.responses.attribute_type`` supports multiple buffer matching, see :doc:`multi-buffer-matching`.
This keyword maps to the EVE field ``ldap.responses[].search_result_entry.attributes[].type``
Example
^^^^^^^
Example of a signature that would alert if a packet has the LDAP attribute type ``dc``:
..container:: example-rule
alert ldap any any -> any any (msg:"Test responses attribute type"; :example-rule-emphasis:`ldap.responses.attribute_type; content:"dc";` sid:1;)
It is possible to use the keyword ``ldap.responses.operation`` in the same rule to
specify the operation to match.
Here is an example of a signature that would alert if a packet has an LDAP
search result entry operation at index 1 on the responses array,
and contains the LDAP attribute type ``dc``.
..container:: example-rule
alert ldap any any -> any any (msg:"Test attribute type and operation"; :example-rule-emphasis:`ldap.responses.operation:search_result_entry,1; ldap.responses.attribute_type; content:"dc";` sid:1;)