New features to highlight in this version

🛠️ JIRA Integration: Streamlined Issue Management

You can now send findings directly from Prowler into your JIRA projects. This integration helps security and engineering teams work in the same place where issues are tracked and resolved.

• Send findings straight into any configured JIRA project.
• Align security alerts with existing development workflows.
• Ensure findings are prioritized, tracked, and resolved without leaving JIRA.

https://github.com/user-attachments/assets/45cb0a29-59c1-4cae-88e9-c84016ebc0db

This feature bridges the gap between security and development, keeping everyone on the same page.

[!WARNING] The integration only works with the Task Jira work item and for projects where there are no custom required fields.

📊 Findings Overview API: Filter by Status

The GET /overviews/findings_severity endpoint now supports filtering by status. This enhancement allows you to refine aggregated results by specific outcomes like FAIL or PASS.

🔒 Token API Throttling

We've introduced throttling support for the token endpoint, giving you greater control over authentication traffic.

• Prevent overload and abuse of token requests.
• Adjust limits to match your organization’s needs.

Big thanks to @josemazo for joining the Prowler team and contributing to making cloud security even better! 🚀

⚡️ MongoDB Atlas Provider (Beta)

We're excited to announce that Prowler now includes MongoDB Atlas as a supported provider!

We added support in the CLI with 10 checks to scan Clusters, Projets and Organizations:

prowler mongodb-atlas --list-checks

• clusters_authentication_enabled - Ensure clusters have authentication enabled
• clusters_backup_enabled - Ensure clusters have backup enabled
• clusters_encryption_at_rest_enabled - Ensure clusters have encryption at rest enabled
• clusters_tls_enabled - Ensure clusters have TLS authentication required
• organizations_api_access_list_required - Ensure organization requires API access list
• organizations_mfa_required - Ensure organization requires MFA
• organizations_security_contact_defined - Ensure organization has security contact defined
• organizations_service_account_secrets_expiration - Ensure organization has maximum period expiration for service account secrets
• projects_auditing_enabled - Ensure database auditing is enabled
• projects_network_access_list_exposed_to_internet - Ensure project network access list is not exposed to internet

This addition strengthens Prowler's position as the go-to multi-cloud security tool, now covering AWS, Azure, GCP, Kubernetes, Microsoft 365, GitHub, and MongoDB Atlas.

---

UI

🚀 Added

• Jira integration(#8640),(#8649

🔄 Changed

• Overview chart "Findings by Severity" now shows only failing findings (defaults to status=FAIL) and chart links open the Findings page pre-filtered to fails per severity (#8186)
• Handle API responses and errors consistently across the app (#8621)
• No-permission message on the scan page (#8624)
• Markdown rendering in finding details page (#8604)

🐞 Fixed

• Scan page shows NoProvidersAdded when no providers (#8626)
• XML field in SAML configuration form validation (#8638)
• Social login buttons in sign-up page (#8673)

API

🚀 Added

• Integration with JIRA, enabling sending findings to a JIRA project (#8622), (#8637)
• GET /overviews/findings_severity now supports filter[status] and filter[status__in] to aggregate by specific statuses (FAIL, <[inline_block>4</inline_block>)(#8186(/issues/8186))
• Throttling options for /api/v1/tokens using the DJANGO_THROTTLE_TOKEN_OBTAIN environment variable (#8647)

SDK

🚀 Added

• Add more fields for the Jira ticket and handle custom fields errors (#8601)
• Support labels on Jira tickets (#8603)
• Add finding url and tenant info inside Jira tickets (#8607)
• Get Jira Project's metadata (#8630)
• Get Jira projects from test_connection (#8634)
• AdditionalUrls field in CheckMetadata (#8590)
• Support color for MANUAL finidngs in Jira tickets (#8642)
• --excluded-checks-file flag (#8301)
• Send finding in Jira integration with the needed values (#8648)
• Add language enforcement for Jira requests (#8674)
• MongoDB Atlas provider with 10 security checks (#8312)
• clusters_authentication_enabled - Ensure clusters have authentication enabled
• clusters_backup_enabled - Ensure clusters have backup enabled
• clusters_encryption_at_rest_enabled - Ensure clusters have encryption at rest enabled
• clusters_tls_enabled - Ensure clusters have TLS authentication required
• organizations_api_access_list_required - Ensure organization requires API access list
• organizations_mfa_required - Ensure organization requires MFA
• organizations_security_contact_defined - Ensure organization has security contact defined
• organizations_service_account_secrets_expiration - Ensure organization has maximum period expiration for service account secrets
• projects_auditing_enabled - Ensure database auditing is enabled
• projects_network_access_list_exposed_to_internet - Ensure project network access list is not exposed to internet

🔄 Changed

• Rename ftp and mongo checks to follow pattern ec2_securitygroup_allow_ingress_from_internet_to_tcp_port_* (#8293)

🐞 Fixed

• Renamed AdditionalUrls to AdditionalURLs field in CheckMetadata (#8639)
• TypeError from Python 3.9 in Security Hub module by updating type annotations (#8619)
• KeyError when SecurityGroups field is missing in MemoryDB check (#8666)
• NoneType error in Opensearch, Firehose and Cognito checks (#8670)