feat(compliance): add SOC2 Azure Processing Integrity requirements

[pedrooot]

Description

This pull request expands the SOC 2 compliance controls for Azure by adding new processing integrity requirements to the soc2_azure.json file. These additions introduce new controls and checks to ensure completeness, accuracy, timeliness, and protection of system inputs, processing, outputs, and stored data.

New Processing Integrity Controls:

• Added five new controls under "PI1.0 - Processing Integrity" (PI1.2 to PI1.5) with detailed descriptions and associated automated checks. These cover system input measurement, data processing accuracy, output distribution and retention, and stored data protection.

Associated Automated Checks:

• Each new control includes a set of relevant Azure checks such as logging, auditing, encryption, backup, and access controls to enforce the described requirements.

Steps to review

Please add a detailed description of how to review this PR.

Checklist

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

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

• 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]

✅ All necessary CHANGELOG.md files have been updated.

[github-actions]

✅ Conflict Markers Resolved

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.62%. Comparing base (eb24736) to head (59063d6).
⚠️ Report is 2 commits behind head on master.

❗ There is a different number of reports uploaded between BASE (eb24736) and HEAD (59063d6). Click for more details.

HEAD has 1 upload less than BASE

Flag	BASE (eb24736)	HEAD (59063d6)
api	1	0

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #9463      +/-   ##
==========================================
- Coverage   92.57%   86.62%   -5.95%     
==========================================
  Files         155      222      +67     
  Lines       22023     5632   -16391     
==========================================
- Hits        20387     4879   -15508     
+ Misses       1636      753     -883     

Flag	Coverage Δ
api	?
prowler-py3.10-azure	86.62% <ø> (?)
prowler-py3.11-azure	86.62% <ø> (?)
prowler-py3.12-azure	86.62% <ø> (?)
prowler-py3.9-azure	86.62% <ø> (?)

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

Components	Coverage Δ
prowler	86.62% <ø> (∅)
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.

[github-actions]

🔒 Container Security Scan

Image: prowler:ef6be68
Last scan: 2025-12-04 13:50:32 UTC

📊 Vulnerability Summary

Severity	Count
🔴 Critical	3
Total	3

3 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

[jfagoagas]

Great addition 🎖️