Asset Visibility in the Posture Tab
An asset appears in the Posture tab only after it is activated for Policy Audit, added to a policy, and its compliance data is collected. Activating an asset, including activating it from the CSAM module, does not by itself display the asset in the Posture tab.
Posture is evaluated per policy. If an asset is not included in any policy, no posture is generated for it, even if the asset is activated and scanned.
Use the following sections to understand how and when posture data becomes available for each tracking method, and what to check if an asset does not appear in the Posture tab.
How and When Posture Data Is Available
The following table describes the steps required before posture data is available for an asset in the Posture tab, based on how the asset is tracked.
| Step | IP / DNS / NetBIOS | Cloud Agent | Amazon EC2 | Oracle Cloud Agent (OCA) |
|---|---|---|---|---|
| 1. Add the asset | Add the IP address, DNS hostname, or NetBIOS name in Assets > Host Assets. The asset must be on a network the scanner can reach. | Install the Cloud Agent on the host. The asset registers automatically and is tracked by agent UUID. | Connect the AWS account by using a connector. The EC2 instance is displayed as a cloud asset with EC2 tracking. | Deploy the Oracle Cloud Agent on the OCI instance. The asset registers with OCA tracking. |
| 2. Activate the asset for Policy Audit | Activate the asset for the Policy Audit module so that it is covered by your scanner license. | Activate the Policy Audit (PC/SCA) module in the agent's configuration profile. | Activate the cloud asset for Policy Audit, either through the agent on the instance or through the connector that covers it. | Activate the agent for Policy Audit on the OCI instance. |
| 3. Add the asset to a policy | Create or edit a policy and include the asset, directly or through an asset group or asset tag assigned to the policy. | |||
| 4. Collect compliance data | Launch an authenticated compliance scan that targets the IP address, DNS hostname, or NetBIOS name. | Wait for the agent's scheduled compliance scan to run and upload results, or select Scan Now. | Launch a scan on the EC2 instance's public DNS name or IP address, or rely on the scan run by the agent on the instance. | The agent uploads Policy Audit results according to its scan schedule. |
| 5. View posture | In the Posture tab, search for the asset by IP address, DNS hostname, or NetBIOS name to view posture by control or policy. | In the Posture tab, the asset is displayed with agent tracking. | In the Posture tab, the asset is displayed as an EC2 instance. | In the Posture tab, the asset is displayed with OCA tracking. |
Why an Asset Does Not Appear in the Posture Tab
If you completed the steps above and the asset still does not appear in the Posture tab, check the following.
| Check | IP / DNS / NetBIOS | Cloud Agent | Amazon EC2 | Oracle Cloud Agent (OCA) |
|---|---|---|---|---|
| Is the asset included in a policy? | Verify that the asset, or an asset group or asset tag that includes it, is assigned to at least one policy. Activation alone does not display the asset in the Posture tab. | |||
| Did the scan or upload complete? | Verify that the scan status is Finished, not just launched. | Verify that the agent's last check-in and last compliance scan time are recent. | Verify that the connector is synced and the scan is finished. | Verify that the agent checked in recently. |
| Is the asset matched correctly? | Verify that there is one host record per IP address, DNS hostname, or NetBIOS name. Duplicate records indicate a tracking method mismatch. | Verify the asset merging rules. Merging or splitting assets can associate the results with a different host record. | Verify that the public DNS name or IP address matches the activated asset. Cloud assets that are not activated are skipped. | Verify that the host is in the OCA tracking group. |
| Is the operating system supported? | Verify that the host's operating system or technology is included in the policy's technologies. For agent-based assets, also verify that the agent supports compliance data collection for that operating system. | |||