|
| 1 | +--- |
| 2 | +title: OCI Configuration Guide for Cloud SIEM |
| 3 | +further_reading: |
| 4 | +- link: "/security/default_rules/#cat-cloud-siem-log-detection" |
| 5 | + tag: "Documentation" |
| 6 | + text: "Explore Cloud SIEM default detection rules" |
| 7 | +- link: "/security/cloud_siem/triage_and_investigate/investigate_security_signals" |
| 8 | + tag: "Documentation" |
| 9 | + text: "Learn about the Security Signals Explorer" |
| 10 | +- link: "/security/cloud_siem/detect_and_monitor/custom_detection_rules/" |
| 11 | + tag: "Documentation" |
| 12 | + text: "Create new detection rules" |
| 13 | +--- |
| 14 | + |
| 15 | +## Overview |
| 16 | + |
| 17 | +Cloud SIEM applies detection rules to all processed logs in Datadog to detect threats such as targeted attacks, communication with threat intel-listed IPs, or insecure resource modifications. Detected threats are surfaced as Security Signals in the Security Signals Explorer for triage. |
| 18 | + |
| 19 | +This guide walks you through the following steps to start detecting threats with your OCI Audit logs: |
| 20 | + |
| 21 | +1. [Set up Datadog’s OCI integration](#set-up-datadogs-oci-integration) |
| 22 | +2. [Enable log collection](#enable-log-collection) |
| 23 | +3. [Use Cloud SIEM to triage Security Signals](#use-cloud-siem-to-triage-security-signals) |
| 24 | + |
| 25 | +## Set up Datadog’s OCI integration |
| 26 | + |
| 27 | +Set up Datadog’s [OCI integration][5] using either the QuickStart (recommended) or the Terraform method. |
| 28 | + |
| 29 | +## Enable log collection |
| 30 | + |
| 31 | +Ensure that log collection is enabled in the Datadog OCI integration tile: |
| 32 | + |
| 33 | +{{< img src="security/cloud_siem/guide/oci_config_guide/oci_logs_enabled.png" alt="The OCI integration tile in Datadog with log collection enabled" style="width:90%;" >}} |
| 34 | + |
| 35 | +## Use Cloud SIEM to triage Security Signals |
| 36 | + |
| 37 | +Cloud SIEM applies out-of-the-box detection rules to all processed logs, including your OCI Audit logs. When a threat is detected with a detection rule, a Security Signal is generated and can be viewed in the Security Signals Explorer. |
| 38 | + |
| 39 | +- Go to the [Cloud SIEM Signals Explorer][1] to view and triage threats. See [Investigate Security Signals][2] for further details. |
| 40 | +- See [out-of-the-box detection rules][3] that are applied to your logs. |
| 41 | +- [Create rules][4] to detect threats that match your specific use case. |
| 42 | + |
| 43 | +## Further reading |
| 44 | + |
| 45 | +{{< partial name="whats-next/whats-next.html" >}} |
| 46 | + |
| 47 | +[1]: https://app.datadoghq.com/security/siem/signals |
| 48 | +[2]: /security/cloud_siem/triage_and_investigate/investigate_security_signals/ |
| 49 | +[3]: /security/default_rules/#cat-cloud-siem |
| 50 | +[4]: /security/detection_rules/#create-detection-rules |
| 51 | +[5]: /integrations/oracle-cloud-infrastructure/?tab=createvcnrecommended |
0 commit comments