Description
Ensure each production environment in a Render project is marked as Protected. In a protected environment, only Admins can delete or create resources, move resources in or out, view or change environment variables and secret files, view database credentials, change database access IPs, and open service shells.
Rationale
Without protection, any Developer can delete production databases, read production secrets, or open a shell on a production service, either by mistake or with a compromised account. Protecting the environment limits these destructive and sensitive actions to a small group of Admins.
Impact
Only Admins can delete production resources or view secrets
Reduces accidental or malicious changes to production
Developers may need an Admin for some production tasks
Default Value
By default, environments are not protected.
Pre-Requisites
Workspace Admin role
Production resources organized into a project environment
Remediation
Test Plan
Sign in to the Render Dashboard at https://dashboard.render.com.
From your workspace home, open the project and scroll to the production environment.
Check whether the environment shows the Protected label and lock icon.
If it is not protected, follow the implementation steps.
Implementation Steps
Sign in to the Render Dashboard at https://dashboard.render.com.
From your workspace home, open the project and scroll to the production environment.
Click the ••• menu at the top right of the environment, then click All settings.
Scroll down to the Permissions section and click Edit.
Select Protected and click Save.
Confirm that the environment now shows the Protected label and lock icon.
Backout Plan
Sign in to the Render Dashboard at https://dashboard.render.com.
From your workspace home, open the project and scroll to the production environment.
Click the ••• menu at the top right of the environment, then click All settings.
In the Permissions section, click Edit, select the unprotected option, and click Save.
Reference