feat(compliance): add SOC2 GCP Processing Integrity requirements

[pedrooot]

Description

This pull request adds new SOC 2 Processing Integrity controls for Google Cloud Platform (GCP) to the prowler/compliance/gcp/soc2_gcp.json compliance file. These additions expand coverage for automated checks related to system inputs, data processing, system outputs, and stored data, enhancing the overall compliance framework.

Processing Integrity Controls Added:

• System Inputs: Added control PI1.2 to ensure system inputs are measured, recorded, and monitored for completeness and accuracy, with checks for logging and audit capabilities.
• Data Processing: Added control PI1.3 to verify data is processed completely and accurately, with checks for configuration change monitoring and audit logs.

System Output and Data Storage Controls:

• System Outputs: Added control PI1.4 to ensure outputs are complete, accurate, securely distributed, and retained, including checks for encryption and access controls.
• Stored Data Protection: Added control PI1.5 to protect stored data from unauthorized modification, theft, or corruption, with checks for encryption, backups, and key management.

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]

✅ Conflict Markers Resolved

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

[github-actions]

✅ All necessary CHANGELOG.md files have been updated.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.96%. Comparing base (d264f3d) to head (0f77fcf).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #9464      +/-   ##
==========================================
+ Coverage   92.38%   92.96%   +0.58%     
==========================================
  Files         156      126      -30     
  Lines       22279     3013   -19266     
==========================================
- Hits        20582     2801   -17781     
+ Misses       1697      212    -1485     

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

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

Components	Coverage Δ
prowler	92.96% <ø> (∅)
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:1be7941
Last scan: 2025-12-10 07:51:55 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 🎖️