feat(api): ASD Essential Eight compliance framework support

[pedrooot]

Context

Backend API support for the new ASD Essential Eight compliance framework
for AWS. The SDK side (compliance JSON + EssentialEightAWS formatter)
landed in #10808 / PROWLER-1451. This PR plugs the framework into the API
export pipeline so scans emit a per-framework CSV with the Essential
Eight specific columns instead of the generic fallback.

Changes

• api/src/backend/tasks/jobs/export.py
  • Import EssentialEightAWS from prowler.lib.outputs.compliance.essential_eight.essential_eight_aws.
  • Register essential_eight_aws → EssentialEightAWS in COMPLIANCE_CLASS_MAP["aws"].

Checklist

Community Checklist

• This feature/issue is listed in here or roadmap.prowler.com
• Is it assigned to me, if not, request it via the issue/feature in here or Prowler Community Slack

• Review if the code is being covered by tests.
• Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
• Review if backport is needed.
• Review if is needed to change the Readme.md
• Ensure new entries are added to CHANGELOG.md, if applicable.

SDK/CLI

• Are there new checks included in this PR? Yes / No
  • If so, do we need to update permissions for the provider? Please review this carefully.

UI

• All issue/task requirements work as expected on the UI
• Screenshots/Video of the functionality flow (if applicable) - Mobile (X < 640px)
• Screenshots/Video of the functionality flow (if applicable) - Table (640px > X < 1024px)
• Screenshots/Video of the functionality flow (if applicable) - Desktop (X > 1024px)
• Ensure new entries are added to CHANGELOG.md, if applicable.

API

• All issue/task requirements work as expected on the API
• Endpoint response output (if applicable)
• EXPLAIN ANALYZE output for new/modified queries or indexes (if applicable)
• Performance test results (if applicable)
• Any other relevant evidence of the implementation (if applicable)
• 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.

[github-actions]

✅ Conflict Markers Resolved

All conflict markers have been successfully resolved in this pull request.

[github-actions]

✅ All necessary CHANGELOG.md files have been updated.

[github-actions]

🔒 Container Security Scan

Image: prowler-api:1fec1ae
Last scan: 2026-05-06 11:25:54 UTC

📊 Vulnerability Summary

Severity	Count
🔴 Critical	9
Total	9

8 package(s) affected

⚠️ Action Required

Critical severity vulnerabilities detected. These should be addressed before merging:

• Review the detailed scan results
• Update affected packages to patched versions
• Consider using a different base image if updates are unavailable

---

📋 Resources:

• Download full report (see artifacts)
• View in Security tab
• Scanned with Trivy

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.65%. Comparing base (19b602c) to head (e28dd07).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #10982       +/-   ##
===========================================
+ Coverage   61.36%   93.65%   +32.28%     
===========================================
  Files          87      230      +143     
  Lines        2876    33938    +31062     
===========================================
+ Hits         1765    31785    +30020     
- Misses       1111     2153     +1042     

Flag	Coverage Δ
api	93.65% <100.00%> (?)
prowler-py3.10-oraclecloud	?
prowler-py3.11-oraclecloud	?
prowler-py3.12-oraclecloud	?

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

Components	Coverage Δ
prowler	∅ <ø> (∅)
api	93.65% <100.00%> (∅)

🚀 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.