FortiSIEM Rules

NetBotz module door open

Rule ID

PH_Rule_Environ_10

Default Status

Disabled

Description

Detects that Netbotz door sensor values went from Close to Open

Severity

7

Category

Availability

MITRE ATT&CK® Tactics

Environmental

MITRE ATT&CK® Techniques

No Technique Specified

Impacts

Environmental

Data Source

APC NetBotz monitoring via SNMP

Detection

Correlation

Remediation Guidance

Identify the root cause and solve the issue

Time Window

If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.

300 seconds

Trigger Conditions

If the following defined pattern/s occur within a 300 second time window.

DoorClosed FOLLOWED_BY DoorOpen

Global Constraint

This defines how two or more distinct events are related in a time-series based action. e.g. An event occurs followed by another event if the source IP, user, and messageId are the same

DoorClosed.hostIpAddr = DoorOpen.hostIpAddr AND
                     DoorClosed.envSensorId = DoorOpen.envSensorId AND
		     DoorClosed.envSensorLabel = DoorOpen.envSensorLabel AND
		     DoorClosed.envSensorEnclosureId = DoorOpen.envSensorEnclosureId

SubPattern Definitions

SubPattern Name: DoorClosed

This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.

SubPattern Query

This is the query logic that matches incoming events

eventType = "PH_DEV_MON_HW_DOOR_SWITCH" AND hostIpAddr IN (Group@PH_SYS_DEVICE_ENV_GEN) AND doorSwitchSensorVal = "Closed"

Group by Attributes

This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID

hostIpAddr,hostName,envSensorId,envSensorLabel,envSensorEnclosureId

Aggregate Constraint

This is most typically a numerical constraint that defines when the rule should trigger an incident

COUNT (*) >= 1
Operator Rank: 0 Operator Type: FOLLOWED_BY

This operator defines the logic condition relating to the prior event subpattern clause and the following event subpattern clause

SubPattern Name: DoorOpen

This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.

SubPattern Query

This is the query logic that matches incoming events

eventType = "PH_DEV_MON_HW_DOOR_SWITCH" AND hostIpAddr IN (Group@PH_SYS_DEVICE_ENV_GEN) AND doorSwitchSensorVal = "Open"

Group by Attributes

This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID

hostIpAddr,hostName,envSensorId,envSensorLabel,envSensorEnclosureId

Aggregate Constraint

This is most typically a numerical constraint that defines when the rule should trigger an incident

COUNT (*) >= 1

Incident Attribute Mapping

This section defines which fields in matching raw events should be mapped to the incident attributes in the resulting incident.

The available raw event attributes to map are limited to the group by attributes and the aggregate event constraint fields for each subpattern

 hostIpAddr = DoorClosed.hostIpAddr,
 hostName = DoorClosed.hostName,
 envSensorId = DoorClosed.envSensorId,
 envSensorLabel = DoorClosed.envSensorLabel,
 envSensorEnclosureId = DoorClosed.envSensorEnclosureId