mirror of
https://github.com/prowler-cloud/prowler.git
synced 2026-10-25 04:44:20 +00:00
39 lines
1.3 KiB
Plaintext
39 lines
1.3 KiB
Plaintext
---
|
|
title: 'Getting Started With Scaleway on Prowler'
|
|
description: 'Onboard Scaleway to Prowler and scan IAM resources for misconfigurations, including detecting API keys still owned by the account root user in your org.'
|
|
---
|
|
|
|
Prowler for Scaleway scans IAM resources in your Scaleway organization for security misconfigurations. The current release ships one check that flags API keys still owned by the account root user.
|
|
|
|
## Prerequisites
|
|
|
|
1. A Scaleway organization with IAM access.
|
|
2. A Scaleway API key with at least the `IAMReadOnly` policy bound to a dedicated IAM user (do not use the account root user).
|
|
3. Your organization ID (visible at the top right of the Scaleway console).
|
|
|
|
## Authentication
|
|
|
|
Prowler authenticates to Scaleway with a Scaleway API key. See [Scaleway Authentication in Prowler](./authentication) for the full setup, environment variables, CLI flags, and required permissions.
|
|
|
|
## Run a Scan
|
|
|
|
```bash
|
|
export SCW_ACCESS_KEY="SCW..."
|
|
export SCW_SECRET_KEY="..."
|
|
export SCW_DEFAULT_ORGANIZATION_ID="..."
|
|
|
|
prowler scaleway
|
|
```
|
|
|
|
To run only the IAM root-key check:
|
|
|
|
```bash
|
|
prowler scaleway --check iam_api_keys_no_root_owned
|
|
```
|
|
|
|
## Checks Shipped
|
|
|
|
| Check ID | Severity | Description |
|
|
|---|---|---|
|
|
| `iam_api_keys_no_root_owned` | Critical | Fails when any Scaleway IAM API key is still owned by the account root user. |
|