prowler-cloud/prowler

Issues getting remediation data into compliance CSV outputs

Open

#8,235 opened on Jul 9, 2025

View on GitHub
 (4 comments) (1 reaction) (1 assignee)Python (1,322 forks)batch import
feature-requesthelp wanted

Repository metrics

Stars
 (8,957 stars)
PR merge metrics
 (Avg merge 9d 17h) (314 merged PRs in 30d)

Description

https://github.com/prowler-cloud/prowler/blob/55c226029efeb1b7f2dfefcc83fa13768c2ed3c3/docs/tutorials/reporting.md?plain=1#L83-L88

We're leveraging prowler to scan AWS accounts, but for some reason the compliance CSV outputs don't include recommend remediations that the CSV reporting tutorial shows as an avaialble output. How can we ensure we get remediation recommendations integrated into our CSVs? I know there's been a lot of changes recent months with some tech debt of docs. so wondering if i'm just missing info.

Contributor guide

Research direction
Check the compliance CSV output code in prowler to see how remediation data is included, and review the reporting tutorial to identify any missing steps or code changes.
Tech stack
python
Domain
security
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
PythonAWS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65