MinIO
Connect MinIO to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect MinIO to collect cloud storage provider evidence with automated compliance tests, switched on per workspace.
| Category | Cloud Storage Provider |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| MinIO's guide | min.io |
Connect with an API token
-
In MinIO:
- Write a policy file that allows only the bucket-listing actions Safeguard needs (MinIO policies use AWS IAM syntax).
- Create the policy:
mc admin policy create ALIAS safeguard-read policy.json. - Create a dedicated user:
mc admin user add ALIAS USERNAME PASSWORD, and attach the policy:mc admin policy attach ALIAS safeguard-read --user USERNAME. - Generate an access key for that user:
mc admin accesskey create ALIAS USERNAME(add--policy policy.jsonto restrict the key further, and--expiry-durationif you want it to expire). - Copy the access key and secret key from the command output.
Where to find the other values:
- Server URL: The https endpoint of your MinIO deployment (the URL your
mcalias points to).
MinIO's public documentation does not cover every step.
MinIO's docs now redirect to the AIStor documentation; the mc commands are the same. The built-in readonly policy only reads a specific object without listing, so a custom policy is needed for bucket listing. MinIO Console steps were not sourced. The docs do not say whether the secret key is shown only once. Verification removed the action names s3:ListAllMyBuckets and s3:GetBucket* because the fetched pages do not list them.
Source: min.io, docs.min.io, docs.min.io, checked 2026-10-07.
The permissions Safeguard needs:
s3:ListAllMyBuckets,s3:GetBucket*. -
On Compliance › Connectors, open MinIO, click Connect, choose API token and fill in:
Field What to enter Server URL Required. Your own server: an https address reachable from the internet. Access key Required. Stored encrypted and never shown again. Secret key Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read MinIO 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 | A1.2, CC6.1, CC6.6 | 3 |
| ISO/IEC 27001 | Automated tests | A.8.13, A.8.20, A.8.24 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(7), 164.312(a)(1), 164.312(e)(1) | 3 |
| PCI DSS | Automated tests | 1.3.1, 3.5.1 | 2 |
| NIST CSF 2.0 | Automated tests | PR.DS-01, PR.DS-11, PR.IR-01 | 3 |
These tests are switched on per workspace by the Safeguard team.
Related
- Cloud Storage Provider 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