FortiSIEM Rules

Performance monitoring jobs deleted by discovery

Rule ID

PH_Rule_Avail_PH_32

Default Status

Disabled

Description

FortiSIEM discovery procedure removed performance monitoring jobs because credentials became invalid or job execution failed during discovery. Discovery tests whether the jobs can still run using the credentials provided. PING jobs are never removed but all other jobs are removed. Incorrect credentials lead to protocol timeouts which in turn lead to bad performance affecting all other devices.

Severity

5

Category

Availability

MITRE ATT&CK® Tactics

FortiSIEM

MITRE ATT&CK® Techniques

No Technique Specified

Impacts

Internal

Data Source

FortiSIEM Self Monitoring

Detection

Correlation

Remediation Guidance

This means that discovery determined that FortiSIEM cannot monitor a performance metric and therefore it removed that metric from its monitored list. Monitoring may have failed because server does not return values for the performance metric. Run the command manually to identify why the server does not return the metric.

Time Window

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

600 seconds

Trigger Conditions

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

PerfJobRemove

SubPattern Definitions

SubPattern Name: PerfJobRemove

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_AUDIT_DEV_MON_JOB_STATUS_CHANGE" AND jobStatusType IN ("DiscoveryRemoved", "DiscoveryNotScheduled")

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

customer,hostName,hostIpAddr,jobName,appTransportProto

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

 hostName = PerfJobRemove.hostName,
 hostIpAddr = PerfJobRemove.hostIpAddr