Oracle OCI: User Created

Rule ID

PH_RULE_OracleOci_UserCreated

Default Status

Enabled

Description

Oracle OCI user was created

Severity

MITRE ATT&CK® Tactics

Persistence

Persistence consists of techniques that adversaries use to keep access to systems across restarts, changed credentials, and other interruptions that could cut off their access. Techniques used for persistence include any access, action, or configuration changes that let them maintain their foothold on systems, such as replacing or hijacking legitimate code or adding startup code.

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

MITRE ATT&CK® Techniques

T1136.003

Create Account: Cloud Account

Adversaries may create a cloud account to maintain access to victim systems. With a sufficient level of access, such accounts may be used to establish secondary credentialed access that does not require persistent remote access tools to be deployed on the system. Adversaries may create accounts that only have access to specific cloud services, which can reduce the chance of detection.

https://attack.mitre.org/techniques/T1136/003

Impacts

Network

Data Source

Oracle OCI via OCI_Streaming_SDK

Detection

Correlation

Remediation Guidance

Confirm that the user creation event was expected. Check which groups the user is a member of.

Time Window

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

120 seconds

Trigger Conditions

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

user_created

SubPattern Definitions

SubPattern Name: user_created

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 IN ("Oracle-OCI-identitycontrolplane-createuser","Oracle-OCI-identitycontrolplane-createidpuser")

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

targetUser,user,srcIpAddr

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

 user=user_created.user,
targetUser=user_created.targetUser,
srcIpAddr=user_created.srcIpAddr

FortiSIEM Rules