Skip to content

feat(compliance): add new Prowler Threat Score Compliance Framework #7603

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

pedrooot
Copy link
Member

@pedrooot pedrooot commented Apr 24, 2025

Description

This PR adds new Prowler ThreatScore Compliance, this compliance is divided in 4 main pillars and the regarding sub-pillars. In this compliance, each requirement has a LevelOfRisk from 1 to 5 depending on the quantity of damage could create the misconfiguration from the requirement.

Pillars:

  1. 1. Identity and Access Management
  2. 2. Attack Surface
  3. 3. Forensic Readiness
  4. 4. Encryption

Sub-Pillars:

  • 1.1 Authentication
  • 1.2 Authorization
  • 1.3 Privilege Escalation Prevention
  • 2.1 Network
  • 2.2 Storage
  • 2.3 Application
  • 3.1 Logging
  • 3.2 Retention
  • 3.3 Monitoring
  • 4.1 In-Transit
  • 4.2 At-Rest

Output Samples - CLI:
Screenshot 2025-04-25 at 11 38 23

Output Samples - Dashboard:
Screenshot 2025-04-24 at 14 34 36

Checklist

API

  • Verify if API specs need to be regenerated.
  • Check if version updates are required (e.g., specs, Poetry, etc.).
  • Ensure new entries are added to CHANGELOG.md, if applicable.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@pedrooot pedrooot requested review from a team as code owners April 24, 2025 12:34
@pedrooot pedrooot added the no-merge Please, DO NOT MERGE this PR. label Apr 24, 2025
@github-actions github-actions bot added compliance Issues/PRs related with the Compliance Frameworks and removed no-merge Please, DO NOT MERGE this PR. labels Apr 24, 2025
Copy link

codecov bot commented Apr 24, 2025

Codecov Report

Attention: Patch coverage is 68.44920% with 59 lines in your changes missing coverage. Please review.

Project coverage is 75.33%. Comparing base (90453fd) to head (2a67fd0).
Report is 7 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #7603      +/-   ##
==========================================
- Coverage   78.53%   75.33%   -3.20%     
==========================================
  Files         135       69      -66     
  Lines        6438     4412    -2026     
==========================================
- Hits         5056     3324    -1732     
+ Misses       1382     1088     -294     
Flag Coverage Δ
prowler 75.33% <68.44%> (-3.20%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
prowler 75.33% <68.44%> (-3.20%) ⬇️
api ∅ <ø> (∅)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@MrCloudSec MrCloudSec changed the title feat(aws): add new prowler threatscore compliance feat(compliance): add new Prowler Threat Score Compliance Framework Apr 24, 2025
Copy link
Member

@MrCloudSec MrCloudSec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please @pedrooot, add the changelog.
Also, change the colors of the summary table to use the same ones as the rest of compliance frameworks and remove the duplicate table:
image
It has to be like:
image

@pedrooot
Copy link
Member Author

Done @MrCloudSec thanks for the heads up!

@MrCloudSec MrCloudSec self-requested a review April 25, 2025 14:37
@pedrooot pedrooot merged commit 06f94f8 into master Apr 28, 2025
10 of 12 checks passed
@pedrooot pedrooot deleted the PRWLR-6185-create-json-file-for-threatscope-compliance-for-aws branch April 28, 2025 07:57
jfagoagas pushed a commit that referenced this pull request May 8, 2025
…7603)

Co-authored-by: MrCloudSec <hello@mistercloudsec.com>
andoniaf pushed a commit that referenced this pull request May 9, 2025
…7603)

Co-authored-by: MrCloudSec <hello@mistercloudsec.com>
andoniaf pushed a commit that referenced this pull request May 9, 2025
…7603)

Co-authored-by: MrCloudSec <hello@mistercloudsec.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compliance Issues/PRs related with the Compliance Frameworks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants