Highlighted
Respected Contributor.
Respected Contributor.
620 views

How to view Based Event information in Correlated event?

Jump to solution

I am creating Correlated event basing on logon failure. the condition is: If there is 5 logon failure behaviour within 1 mins, the correlated rule will fire an Brute Force Attemp event.

However, the issue here is most of the Base event information related to that correlated event is not populated within Correlated event detail.

Is there anyway that we can pull the information from base event then insert it into respective correlated events?


Thank you for your advice in advance,

Regards,

Anh

0 Likes
1 Solution

Accepted Solutions
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Hello Anh

There are two aspects to this

If the correlation rule is set to trigger on 5 events where specific fields are the same (sourceUserName, sourceIpAddress etc)

Just set these fields in the aggregation tab (the lower part of the aggregation fields) in the rule editor, the fields which you choose to aggregate on will appear in the same fields in the correlation rule

If the correlation rule is set to trigger where specific fields are unique and you want all the unique field values to appear in the correlation event in one field this requires more sophistication (and one of the more annoying things in ArcSight)

In order to do this create an active list with the multimap option selected (by using multimap you will be able to record all events related to that login although they are using the same key fields)

Create a lightweight rule that uses the same conditions as your original rule

Set you standard rule to trigger only on the fifth time within X time

Create a variable within your standard rule that checks the multimap list and extracts all the unique values from the list

You can aggregate the variable and use set event field to map it to the correct field in the correlation event (in case it doesn't work you can create a pre-persistence rule which will work)

Best regards

David

View solution in original post

2 Replies
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Hello Anh

There are two aspects to this

If the correlation rule is set to trigger on 5 events where specific fields are the same (sourceUserName, sourceIpAddress etc)

Just set these fields in the aggregation tab (the lower part of the aggregation fields) in the rule editor, the fields which you choose to aggregate on will appear in the same fields in the correlation rule

If the correlation rule is set to trigger where specific fields are unique and you want all the unique field values to appear in the correlation event in one field this requires more sophistication (and one of the more annoying things in ArcSight)

In order to do this create an active list with the multimap option selected (by using multimap you will be able to record all events related to that login although they are using the same key fields)

Create a lightweight rule that uses the same conditions as your original rule

Set you standard rule to trigger only on the fifth time within X time

Create a variable within your standard rule that checks the multimap list and extracts all the unique values from the list

You can aggregate the variable and use set event field to map it to the correct field in the correlation event (in case it doesn't work you can create a pre-persistence rule which will work)

Best regards

David

View solution in original post

Highlighted
Respected Contributor.
Respected Contributor.

Thank you very much for your explanation 🙂

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.