Prowler (Cloud Security)
What it is
Open-source cloud security audit tool (AWS, GCP, Azure). It checks hundreds of configuration controls against CIS, ISO 27001, NIS2 and GDPR benchmarks.
How to configure
No permanent configuration: it works by manual push. Identification is done through the x-integration-id header.
How data comes in
Run Prowler locally and send the JSON output to EterShield:
# 1. Correr auditoria AWS
prowler aws -M json -o prowler-output.json
# 2. Enviar para EterShield
curl -X POST https://etershield.etergrowth.com/api/v1/integrations/prowler/findings \
-H "Content-Type: application/json" \
-H "x-api-key: SEU_API_KEY" \
-H "x-integration-id: ID_DA_INTEGRACAO_PROWLER" \
--data-binary @prowler-output.json
Limit: 50MB per request. Rate limit: 10 ingestions/hour.
Only FAIL and WARNING results are imported; PASS results are ignored.
What it produces
For each imported finding:
- Integration finding with fields:
- Provider (aws/gcp/azure), account, region
- CheckID (e.g.
iam_root_mfa_enabled) - Service, resource type, resource ARN
- Severity (CRITICAL/HIGH/MEDIUM/LOW)
- Suggested remediation
- Unique fingerprint for deduplication between runs
Control mapping (AI-generated after ingestion):
- Maps each finding to the relevant ISO 27001, NIS2 and DORA control(s)
- Includes confidence (0-1) and justification (Claude API)
Evidence (auditable chain):
- Links the technical finding to the compliance control
- Lets you close assessment answers based on technical evidence
Where it appears in EterShield
Findings → list with filters by severity, status and framework. Each finding shows the mapped controls and the evidence chain.
Finding lifecycle
When Prowler runs again and the finding disappears, it is automatically marked as RESOLVED.