Threat ManagementTagging Rules and False Positives

Tagging Rules and False Positives

A freshly installed SIEM (security information and event management system) raises alerts for some activity that is normal in your organization. Tagging rules let UTMStack label new alerts automatically, and the system tag False positive closes known, harmless alerts as soon as they arrive. Handling false positives well keeps your team focused on real threats and reduces alert fatigue.

How tagging rules work

A tagging rule has one or more conditions and one or more tags. When a new alert matches all the conditions, UTMStack adds the rule's tags to it.

  • Rules apply only to alerts raised after the rule is saved. Existing alerts are not tagged again.

  • UTMStack reloads the rules every 60 seconds, so a new or changed rule can take about a minute to take effect.

  • An alert gets the tags of every rule it matches.

  • Echoes (repeats grouped under a first alert) are checked the same way as other new alerts.

  • Each rule belongs to one tenant.

The False positive tag

False positive is a system tag. It cannot be renamed or deleted.

When a tagging rule adds False positive to a new alert, UTMStack saves the alert with the status Completed and the status note Status changed to completed because alert was tagged as False positive. The alert is still stored:

  • You can find it on the Completed tab.

  • It is not counted in the number of open alerts.

  • It is not counted by the Rule flood guard.

  • It is still emailed to the Alert recipients, like any other new top-level alert.

Every other new alert is saved as Open, with the status note This alert has been evaluated by the tag rules engine.

Who can manage tagging rules

What you want to doPermissionBuilt-in roles
See tagging rulesalerts.readAdministrator, Analyst, Viewer
Create, edit and delete tagging rulesalerts.writeAdministrator, Analyst

Create a tagging rule

You can start a rule in three ways:

  • On Threat Management > Tagging Rules, click New rule.

  • On Threat Management > Alerts, click the tag icon Create a tag from this alert on an alert row. The new rule is filled in with one is condition for each field of the alert that has a value. Remove the conditions you do not need.

  • In any tag menu on the Alerts page, click Create tagging rule with this tag. The new rule is filled in with that tag.

The New tagging rule panel looks like this:

The New tagging rule panel with the Basics section (Rule name and Description), Tags to apply with the Add tag button, Conditions (ALL must match) with a field, operator and value row and the Add condition button, and the Create button
  1. 1

    Name the rule

    Under Basics, enter a Rule name (unique in your tenant) and a Description that says why the rule exists. Both are required.

  2. 2

    Choose the tags

    Under Tags to apply, click Add tag and pick one or more tags. To close matching alerts as false positives, pick False positive. You can also click Create tag to make a new tag here.

  3. 3

    Add conditions

    Under Conditions (ALL must match), click Add condition. For each condition, choose a field, an operator and a value. Make the conditions as narrow as you can, so that the rule does not hide real attacks.

  4. 4

    Save

    Click Create. The rule applies to alerts raised from about a minute later.

Fields

Alert name, Category, Technique, Datasource, Data type, and for both sides of the alert:

AdversaryTarget
Adversary IPTarget IP
Adversary hostTarget host
Adversary userTarget user
Adversary domainTarget domain
Adversary URLTarget URL
Adversary countryTarget country
Adversary ASNTarget ASN
Adversary ASOTarget ASO

ASN is the number of the network that owns the address, and ASO is that network's owner (organization name).

Operators

OperatorValueHow it matches
is, is notOne valueExact match. Letter case must match.
contains, does not containOne valuePart of the text. Letter case is ignored.
starts with, does not start withOne valueStart of the text. Letter case is ignored.
ends with, does not end withOne valueEnd of the text. Letter case is ignored.
is one of, is not one ofComma-separated valuesExact match against any value in the list. Letter case must match.
contains one of, does not contain one ofComma-separated valuesPart of the text, for any value in the list. Letter case is ignored.
is between, is not betweenTwo numbers, comma-separatedA number range. Of the fields above, only the ASN fields hold numbers.
exists, does not existNoneWhether the field has a value.

Example: stop alerts from a known scanner

Your vulnerability scanner at 10.0.5.20 sets off port-scan alerts every night.

  1. On Threat Management > Alerts, find one of these alerts and click its tag icon Create a tag from this alert.

  2. Enter a Rule name, for example Nightly vulnerability scanner, and a Description.

  3. Under Tags to apply, add False positive.

  4. Keep the condition Adversary IP is 10.0.5.20 and the Alert name condition. Remove the others.

  5. Click Create.

From about a minute later, new alerts from that address with that name are saved as Completed with the False positive tag.

Close a single alert as a false positive

To close one alert by hand without creating a rule:

  1. Open the alert on Threat Management > Alerts.

  2. Click Set status and choose Complete + false positive.

  3. Write an Observation (required) and click Continue.

The alert is set to Completed and gets the False positive tag. If you later set it back to Open, the False positive tag is removed.

Manage tagging rules

The Tagging Rules page with the New rule button, the Search by rule name box, the All tags menu and the list of rules with their tags and number of conditions

Go to Threat Management > Tagging Rules. The list shows Rule, Tags and Conditions (the number of conditions). More rules load as you scroll. Use Search by rule name… and the All tags menu to find a rule. Click a rule to see it, then Edit or Delete.

A tagging rule cannot be switched off. To stop a rule, delete it. UTMStack asks you to confirm: Delete the rule "<name>"? Future alerts matching its conditions will stop being tagged. Alerts that the rule already tagged keep their tags.

Check that a tagging rule works

  1. Wait at least a minute after you save the rule.

  2. Wait for, or cause, a new alert that should match.

  3. On Threat Management > Alerts, filter on the alert name and open the new alert. Its tags should include the rule's tags. If the rule adds False positive, look on the Completed tab: the alert's Status note reads Status changed to completed because alert was tagged as False positive.

Existing alerts are never tagged again, so testing with an old alert shows nothing.

Troubleshooting

SymptomWhyWhat to do
New alerts are not taggedThe rule was saved less than about a minute before the alert, or one of its conditions does not match. All conditions must match.Open the alert and compare each condition with the alert's values. Remove conditions you do not need.
An is condition does not match although the value looks the sameis and is one of compare letter case exactly.Copy the value from the alert, or use contains.
The rule tags far more alerts than intendedA negative condition (is not, does not contain and the others) also matches alerts that do not have the field at all.Add an exists condition on the same field.
An is between condition never matchesIt needs numbers, and only the ASN fields hold numbers.Use it only on Adversary ASN or Target ASN.
Alerts closed as False positive still arrive by emailEvery new top-level alert is emailed, whatever its status.Expected in UTMStack v12.0.2. See Alert and Incident Notifications.
A real attack was closed automaticallyThe rule's conditions are too broad.Narrow or delete the rule. Search the Completed tab for alerts with the False positive tag and reopen the ones that matter: setting them back to Open removes the tag.