Scaleway API keys are checked to ensure none is bound to the account root user. The account root user is the original Scaleway account owner; its credentials bypass IAM policies and grant unrestricted access to the entire organization.
Risk
API keys owned by the account root user cannot be scoped down with IAM policies. Leaking one of these keys yields immediate full control over every project, resource and billing setting in the organization, and rotating them disrupts every automation depending on root credentials.
prowler scaleway --checks iam_api_keys_no_root_owned
Recommendation
Never use API keys owned by the account root user for automation. Create scoped IAM users or applications, attach least-privilege policies, and rotate any existing root API keys to that new bearer.
Remediation
scw iam api-key delete <ACCESS_KEY>
- Sign in to the Scaleway console as a user with IAM admin permissions.
- Create a dedicated IAM user or application scoped with the minimum required policy.
- Generate a new API key for that bearer and roll it out to the workloads currently using the root key.
- Delete the API key owned by the account root user from the IAM > API keys page.
Source Code
Resource Type
NotDefined