Configuring Oracle Cloud Infrastructure (OCI) Connectors

This connector allows Stellar Cyber to ingest logs from the Oracle Cloud Infrastructure (OCI) and add the records to the data lake.

Oracle Cloud Infrastructure integration with Stellar Cyber provides advanced threat detection and response capabilities, combining Oracle's security solutions with real-time threat intelligence and automated response workflows to improve incident response and threat mitigation.

This connector queries the Oracle Streaming Service to collect log data found within a provided stream name. The stream can be configured for different log types.

Connector Overview: Oracle Cloud Infrastructure

Capabilities

  • Collect: Yes

  • Respond: No

  • Native Alerts Mapped: Yes

  • Runs on: DP

  • Interval: Configurable

Collected Data

Content Type

Index

Locating Records

Log data in provided Stream Name

 Syslog

msg_class:

oracle_cloud_audit (if oracle.oracle.loggroupid is _Audit)

oracle_cloud_guard (if oracle.source starts with CloudGuard (case insensitive))

oracle_cloud_log (everything else)

msg_origin.source:

oracle_cloud_infrastructure

msg_origin.vendor:

oracle

msg_origin.category:

paas

Domain

N/A

Response Actions

N/A

Third Party Native Alert Integration Details

This connector ingests logs from OCI to get the raw alerts that are stored in the Syslog index.

Stellar Cyber maps OCI CloudGuard alerts. The alerts are read from the Syslog index, enriched with Stellar Cyber fields, and mapped (with de-duplication) to the Alerts index.

Deduplication is by tenantid, oracle.data.additionalDetails.tenantId, event.threat.name, and cloud.resource.id.

The resource types include instances, buckets, and others.

For details, see Integration of Third Party Native Alerts.

Required Credentials

  • Bootstrap Server, Username, Auth Token (Password), and Stream Name

Locating Records

To search the alerts in the Alerts index, use the query: msg_class: oracle_cloud_guard AND exists:event.threat.name

To search the Original Records in the Syslog index, use the query: msg_class: oracle_cloud_guard AND exists:event.threat.name

               Let us know if you find the above overview useful.

Adding an Oracle Cloud Infrastructure Connector

To add an Oracle Cloud Infrastructure (OCI) connector:

  1. Obtain your Oracle Cloud Infrastructure credentials
  2. Add the connector in Stellar Cyber
  3. Test the connector
  4. Verify ingestion

Obtaining your OCI Credentials

Follow the guidance in the Oracle Cloud Infrastructure documentation for Creating Streams to create the credentials for Stellar Cyber API calls. You can also refer to Kafka Python Client and Streaming Quickstart.

  1. Log in as an administrative user to the Oracle Cloud Console with your Oracle Cloud Infrastructure account.

  2. Navigate to Analytics & AI and choose Streaming under Messaging.

  3. Navigate to Analytics and choose Stream Pools. Choose the Compartment in which the stream was configured. For Create Stream Pool, choose DefaultPool.

  4. Navigate to Kafka Connection Settings.
    • In Bootstrap Servers, note the Bootstrap Server. It has the format: cell-1.streaming.<region>.oci.oraclecloud.com:9092.
    • In SASL Connection Strings, note the Username. It has the format: <OCI_tenancy_name>/<your_OCI_username>/<stream_pool_OCID>.
    • In SASL Connection Strings, note the Password. It has the format: <your_OCI_user_auth_token>.

  5. Navigate to Analytics and choose Streams. Note the stream name.

Fetching Audit Logs

Once the stream is configured, you need to send audit logs to the configured stream.

Follow the guidance in the Oracle Cloud Infrastructure documentation for Creating a Connector with a Logging Source to transfer log data from the logging service to a target service.

Adding the Connector in Stellar Cyber

With the access information handy, you can add an OCI connector in Stellar Cyber:

  1. Log in to Stellar Cyber.

  2. Click System | Integration | Connectors. The Connector Overview appears.

  3. Click Create. The General tab of the Add Connector screen appears. The information on this tab cannot be changed after you add the connector.

  4. Choose PaaS from the Category drop-down.

  5. Choose Oracle Cloud Infrastructure from the Type drop-down.

  6. For this connector, the supported Function is Collect, which is enabled already.

  7. Enter a Name.

    This field does not accept multibyte characters.

  8. Choose a Tenant Name. This identifies which tenant is allowed to use the connector.

  9. Choose the device on which to run the connector.

    • Certain connectors can be run on either a Sensor or a Data Processor. The available devices are displayed in the Run On menu. If you want to associate your collector with a sensor, you must have configured that sensor prior to configuring the connector or you will not be able to select it during initial configuration. If you select Data Processor, you will need to associate the connector with a Data Analyzer profile as a separate step. That step is not required for a sensor, which is configured with only one possible profile.

    • If the device you're connecting to is on premises, we recommend you run on the local sensor. If you're connecting to a cloud service, we recommend you run on the DP.

  10. (Optional) When the Function is Collect, you can create Log Filters. For information, see Managing Log Filters.

  11. Click Next. The Configuration tab appears.

  12. Enter the Bootstrap Server you noted above.

  13. Enter the Username you noted above.

  14. Enter the Auth Token (the Password) you noted above.

  15. Enter the Stream Name you noted above.

  16. Choose the Interval (min). This is how often the logs are collected.

  17. Click Next. The final confirmation tab appears.

  18. Click Submit.

    To pull data, a connector must be added to a Data Analyzer profile if it is running on the Data Processor.

  19. If you are adding rather than editing a connector with the Collect function enabled and you specified for it to run on a Data Processor, a dialog box now prompts you to add the connector to the default Data Analyzer profile. Click Cancel to leave it out of the default profile or click OK to add it to the default profile.

    • This prompt only occurs during the initial create connector process when Collect is enabled.

    • Certain connectors can be run on either a Sensor or a Data Processor, and some are best run on one versus the other. In any case, when the connector is run on a Data Processor, that connector must be included in a Data Analyzer profile. If you leave it out of the default profile, you must add it to another profile. You need the Administrator Root scope to add the connector to the Data Analyzer profile. If you do not have privileges to configure Data Analyzer profiles, a dialog displays recommending you ask your administrator to add it for you.

    • The first time you add a Collect connector to a profile, it pulls data immediately and then not again until the scheduled interval has elapsed. If the connector configuration dialog did not offer an option to set a specific interval, it is run every five minutes. Exceptions to this default interval are the Proofpoint on Demand (pulls data every 1 hour) and Azure Event Hub (continuously pulls data) connectors. The intervals for each connector are listed in the Connector Types & Functions topic.

    The Connector Overview appears.

The new connector is immediately active.

Testing the Connector

When you add (or edit) a connector, we recommend that you run a test to validate the connectivity parameters you entered. (The test validates only the authentication / connectivity; it does not validate data flow).

  1. Click System | Integrations | Connectors. The Connector Overview appears.

  2. Locate the connector that you added, or modified, or that you want to test.

  3. Click Test at the right side of that row. The test runs immediately.

    Note that you may run only one test at a time.

Stellar Cyber conducts a basic connectivity test for the connector and reports a success or failure result. A successful test indicates that you entered all of the connector information correctly.

To aid troubleshooting your connector, the dialog remains open until you explicitly close it by using the X button. If the test fails, you can select the  button from the same row to review and correct issues.

The connector status is updated every five (5) minutes. A successful test clears the connector status, but if issues persist, the status reverts to failed after a minute.

Repeat the test as needed.

ClosedDisplay sample messages...

Success !

Failure with summary of issue:

Show More example detail:

 

Verifying Ingestion

To verify ingestion:

  1. Click Investigate | Threat Hunting. The Interflow Search tab appears.
  2. Change the Indices to Syslog. The table immediately updates to show ingested Interflow records.