FortiSIEM Rules

Oracle OCI: User API Key Created and Uploaded

Rule ID


Default Status



Oracle OCI API key was created. Admin users can create keys, tokens, and credentials for other users, and some users are allowed to create these themselves. So the user and target user id may not always refer to the same account. API keys can be manually uploaded by users, or dynamically generated, but the event is the same.







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.

MITRE ATT&CK® Techniques


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.



Data Source

Oracle OCI via OCI_Streaming_SDK



Remediation Guidance

Confirm that the user intentionally created an api key for the given user account. In some cases users are allowed to create their own api key, so confirm that behavior should be allowed with the Oracle cloud admin.

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.


SubPattern Definitions

SubPattern Name: api_key_create_upload

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-uploadapikey"

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


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