Views:
Connecting your OCI compartment account allows various Trend Vision One apps and security features to access your cloud assets and gain greater visibility over assets and monitor for potential threats. Each feature and permission is described in the table below.
Feature
Description
Core Features and Cyber Risk Exposure Management
The core set of features and permissions required to connect your OCI compartment.
Core features enable you to connect your OCI compartment to Trend Vision One to discover your cloud assets and rapidly identify risks such as compliance and security best practices violations on your cloud infrastructure.
Note
Note
Core features are required to connect your OCI compartments and cannot be disabled. If you need to disconnect your account, see Oracle Cloud Infrastructure (OCI) compartments.
Note
Note
Your OCI assets appear in the Endpoint Inventory list. Assets without the Trend Vision One Endpoint Security agent installed appear as unmanaged endpoints.
Cyber Risk Exposure Management - Cloud account assessment
Discover and assess your cloud assets for attack exposure, risk factors, and security posture. When you enable Cyber Risk Exposure Management - Cloud account assessment, you can monitor and manage your OCI cloud assets in the following Trend Vision One apps:
Agentless Vulnerability & Threat Detection
Important
Important
This is a "Pre-release" feature and is not considered an official release. Please review the Pre-release disclaimer before using the feature.
This feature set allows Trend Vision One to deploy Agentless Vulnerability & Threat Protection in your OCI compartment to discover vulnerabilities and malware in your OCI block volumes, OCI boot volumes attached to computer instances, and OCI Container Registry images.
Important
Important
Enabling Agentless Vulnerability & Threat Detection requires LocalShell deployment. If you are enabling this feature on a compartment that was already connected using Oracle Resource Manager, you must change the deployment type to LocalShell. For more information on LocalShell deployment, see Connect an OCI compartment using LocalShell.