Trend Micro Cloud One
Connect Trend Micro Cloud One to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Trend Micro Cloud One to collect cspm evidence with automated compliance tests, switched on per workspace.
| Category | CSPM |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Trend Micro Cloud One's guide | docs.trendmicro.com |
Connect with an API token
-
In Trend Micro Cloud One:
- In the upper right of the Trend Cloud One console, select the account, then click the account name and select Administration.
- Click the key icon on the left to display API Keys, then click New.
- Complete the New API Key dialog: enter an API Key Alias and Description, and under Role assign the role that determines the scope of the API key's access (pick a read-only role). Optionally set Language, Timezone and IP/CIDR ranges.
- Click Next, copy the displayed API key value and save it (if you lose the key, you must create a new one), then click Close. Paste it into Safeguard's API key field.
Where to find the other values:
- Region: Trend's docs list the region IDs us-1, in-1, gb-1, jp-1, de-1, au-1, ca-1 and sg-1; an account's region is set when it is created and cannot be changed. The docs do not say where the console shows it.
Trend Micro Cloud One shows the secret only once, so copy it before you leave the page.
Trend Micro Cloud One's public documentation does not cover every step.
The fetched page does not list role names, so the exact name of a read-only role is not confirmed. The UI location of the account region is not documented.
Source: docs.trendmicro.com, docs.trendmicro.com, checked 2026-10-07.
The permissions Safeguard needs:
Read Only. -
On Compliance › Connectors, open Trend Micro Cloud One, click Connect, choose API token and fill in:
Field What to enter API key Required. Stored encrypted and never shown again. Region Required. For example: us-1 -
Click Connect with token.
Frameworks
Safeguard's automated tests read Trend Micro Cloud One and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC7.1 | 3 |
| ISO/IEC 27001 | Automated tests | A.8.8, A.8.9 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(1) | 3 |
| PCI DSS | Automated tests | 2.2.1, 6.3.3 | 3 |
| NIST CSF 2.0 | Automated tests | ID.RA-01, PR.PS-01 | 3 |
These tests are switched on per workspace by the Safeguard team.
Related
- CSPM connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks