Oracle Database Listener Down

Rule ID

PH_Rule_Avail_53

Default Status

Enabled

Description

Detects that an Oracle database server listener is down

Severity

MITRE ATT&CK® Tactics

Impact

Impact consists of techniques that adversaries use to disrupt availability or compromise integrity by manipulating business and operational processes. Techniques used for impact can include destroying or tampering with data. In some cases, business processes can look fine, but may have been altered to benefit the adversaries’ goals. These techniques might be used by adversaries to follow through on their end goal or to provide cover for a confidentiality breach.

https://attack.mitre.org/tactics/TA0040

MITRE ATT&CK® Techniques

T1489

Service Stop

Adversaries may stop or disable services on a system to render those services unavailable to legitimate users. Stopping critical services can inhibit or stop response to an incident or aid in the adversary's overall objectives to cause damage to the environment. Adversaries may accomplish this by disabling individual services of high importance to an organization, such as MSExchangeIS, which will make Exchange content inaccessible.

https://attack.mitre.org/techniques/T1489

Impacts

Application

Data Source

Oracle DB Server via JDBC

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.

180 seconds

Trigger Conditions

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

DBDown

SubPattern Definitions

SubPattern Name: DBDown

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_PERF_ORADB" AND listenerStatus != "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, instanceName, instanceStatus, listenerStatus

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=DBDown.hostIpAddr,
hostName=DBDown.hostName,
 instanceName=DBDown.instanceName,
instanceStatus=DBDown.instanceStatus,
 listenerStatus = DBDown.listenerStatus

FortiSIEM Rules