Overview
Twigs supports agent less, cloud-native discovery for Oracle Cloud Infrastructure Compute workloads / instances using native inventory provided by Oracle OS Management Hub.
Pre-requisites
Please refer to Oracle documentation for setting up OS Management Hub.
Please setup OCI SDK and CLI as described here on the Twigs box. Twigs uses default configuration file from following location “~/.oci/config” and it refers to the DEFAULT profile in the configuration file. You can specify your custom configuration file location and profile name on the twigs command-line.
Steps involved
- Open a new shell / terminal.
- You can run the command:
twigs oci [--enable_tracking_tags] [--config_file CONFIG_FILE] [--config_profile CONFIG_PROFILE]
- It is suggested that you specify “–enable_tracking_tags” on Twigs command-line, which allows you to easily identify OCI compute instances in ThreatWorx.
- You can specify your custom configuration file location (CONFIG_FILE) and profile name (CONFIG_PROFILE) on the twigs command-line.
- OCI cloud discovery may require some time depending on the number of compute instances in your cloud setup.
- After discovery is complete, you can login into ThreatWorx Console to view the newly discovered assets.
Example
$ twigs oci --enable_tracking_tags
Discover your OCI compute workloads as assets in ThreatWorx. Note you need to setup OCI SDK and CLI first.