Difference between Running and Startup Config

Rule ID

PH_Rule_Change_1

Default Status

Enabled

Description

Detects that the startup and running configurations of a network device (router or firewall) are different. This is achieved via logging in.

Severity

MITRE ATT&CK® Tactics

Policy Violation

MITRE ATT&CK® Techniques

No Technique Specified

Impacts

Network

Data Source

Any Device Config Monitoring via SSH

Detection

Correlation

Remediation Guidance

Make sure it is an authorized change

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.

StartupRunDelta

SubPattern Definitions

SubPattern Name: StartupRunDelta

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

hostIpAddr IN (Group@PH_SYS_DEVICE_ROUTER_SWITCH,Group@PH_SYS_DEVICE_FIREWALL) AND eventType = "PH_DEV_MON_DELTA_CONFIG"

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, addedItem, deletedItem

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 = StartupRunDelta.hostIpAddr,
 hostName = StartupRunDelta.hostName,
 addedItem = StartupRunDelta.addedItem,
 deletedItem = StartupRunDelta.deletedItem

FortiSIEM Rules