FortiSIEM Rules

Cisco CallManager Malicious Call Trace

Rule ID

PH_Rule_CCM_31

Default Status

Enabled

Description

Malicious call exists in Cisco Unified Communications Manager - the malicious call identification (MCID) feature gets invoked

Severity

9

Category

Performance

MITRE ATT&CK® Tactics

Suspicious Activity

MITRE ATT&CK® Techniques

No Technique Specified

Impacts

Application

Data Source

Cisco Call Manager Via Syslog

Detection

Correlation

Remediation Guidance

Identify the root cause of the performance issue and allocate more resources if needed.

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.

CCM

SubPattern Definitions

SubPattern Name: CCM

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 = "Cisco_UC_RTMT_MaliciousCallTrace"

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

reptDevName

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 = CCM.reptDevName