prowler-cloud/prowler

Issues getting remediation data into compliance CSV outputs

Open

#8,235 建立於 2025年7月9日

在 GitHub 查看
 (4 留言) (1 反應) (1 負責人)Python (8,957 star) (1,322 fork)batch import
feature-requesthelp wanted

描述

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.

貢獻者指南

技術棧
python
領域
backendcloudsecurity
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
needs maintainer response
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
unclear
前置要求
Basic knowledge of ProwlerFamiliarity with CSV reporting
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
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.