Oracle OCI: User Added to a Group

Rule ID

PH_RULE_OracleOci_UserAddedToGroup

Default Status

Enabled

Description

Oracle OCI user was added to a group

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

T1098.001

Account Manipulation: Additional Cloud Credentials

Adversaries may add adversary-controlled credentials for Azure Service Principals in addition to existing legitimate credentials to maintain persistent access to victim Azure accounts. Azure Service Principals support both password and certificate credentials. With sufficient permissions, there are a variety of ways to add credentials including the Azure Portal, Azure command line interface, and Azure powershell.

https://attack.mitre.org/techniques/T1098/001

Impacts

Network

Data Source

Oracle OCI via OCI_Streaming_SDK

Detection

Correlation

Remediation Guidance

Confirm that the user is expected to be a member of the given group

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.

group_member_add

SubPattern Definitions

SubPattern Name: group_member_add

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 = "Oracle-OCI-identitycontrolplane-addusertogroup"

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

targetUserId,user,groupID

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=group_member_add.user,
targetUserId=group_member_add.targetUserId,
groupID=group_member_add.groupID

FortiSIEM Rules