About
When you connect DigitalOcean to DSALTA, the platform evaluates this control on every sync using read-only API access. If the requirement is not met, DSALTA activates this check.Why This Matters
Addressing this check ensures your environment meets the security baseline expected by SOC 2, ISO 27001, and other compliance frameworks, and reduces the risk of misconfiguration, unauthorized access, or data loss.How to Fix
Before you begin- Ensure you have administrator access to DigitalOcean.
- Review the failing configuration in your DigitalOcean console.
- Apply the recommended setting to bring the resource into compliance.
- Verify the change is active in the resource configuration.
Frequently Asked Questions
How often does this check run?
How often does this check run?
This check runs automatically every 24 hours while the DigitalOcean integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
What happens if it keeps failing?
What happens if it keeps failing?
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
Can I exclude this check?
Can I exclude this check?
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
Does DSALTA change my DigitalOcean configuration?
Does DSALTA change my DigitalOcean configuration?
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in DigitalOcean.
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)