Oracle OCI: Policy Created

Rule ID

PH_RULE_OracleOci_PolicyCreated

Default Status

Enabled

Description

Oracle OCI Policy Created. Policies define access to resources in OCI.

Severity

MITRE ATT&CK® Tactics

Defense Evasion

Defense Evasion consists of techniques that adversaries use to avoid detection throughout their compromise. Techniques used for defense evasion include uninstalling/disabling security software or obfuscating/encrypting data and scripts. Adversaries also leverage and abuse trusted processes to hide and masquerade their malware. Other tactics’ techniques are cross-listed here when those techniques include the added benefit of subverting defenses.

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

MITRE ATT&CK® Techniques

T1562.007

Impair Defenses: Disable or Modify Cloud Firewall

Adversaries may disable or modify a firewall within a cloud environment to bypass controls that limit access to cloud resources. Cloud firewalls are separate from system firewalls. Modifying or disabling a cloud firewall may enable adversary C2 communications, lateral movement, and/or data exfiltration that would otherwise not be allowed.

https://attack.mitre.org/techniques/T1562/007

Impacts

Network

Data Source

Oracle OCI via OCI_Streaming_SDK

Detection

Correlation

Remediation Guidance

Investigate the policy details, and if the admin was allowed to create the policy, following change management procedures.

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.

policy_created

SubPattern Definitions

SubPattern Name: policy_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 = "Oracle-OCI-identitycontrolplane-createpolicy"

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

compartmentName,policyName,srcIpAddr,user

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=policy_created.user,
srcIpAddr=policy_created.srcIpAddr,
policyName=policy_created.policyName,
compartmentName=policy_created.compartmentName

FortiSIEM Rules