Issues getting remediation data into compliance CSV outputs · prowler-cloud/prowler#8235

(4 comments) (1 reaction) (1 assignee)Python (8,957 stars) (1,322 forks)batch import

feature-requesthelp wanted

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

Tech stack: python
Domain: backendcloudsecurity
Issue type: bug
Difficulty: 3
Estimated time: half day
Activity status: needs maintainer response
Clarity: unclear
Prerequisites: Basic knowledge of ProwlerFamiliarity with CSV reporting
Newbie friendliness: 30
Research direction: Review the documentation at https://github.com/prowler cloud/prowler/blob/55c226029efeb1b7f2dfefcc83fa13768c2ed3c3/docs/tutorials/reporting.md?plain=1#L83 L88 to understand expected CSV output. Examine the CSV generation code in the Prowler source, likely in prowler/output or similar directories. Look for recent commits that modified CSV output logic. In issue comments, maintainers may have provided guidance; check for any responses that clarify the missing remediation data.