You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/developer-guide/check-metadata-guidelines.mdx
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -215,3 +215,6 @@ Also is important to keep all code examples as short as possible, including the
215
215
| e5 | M365 and Azure Entra checks enabled by or dependent on an E5 license (e.g., advanced threat protection, audit, DLP, and eDiscovery) |
216
216
| privilege-escalation | Detects IAM policies or permissions that allow identities to elevate their privileges beyond their intended scope, potentially gaining administrator or higher-level access through specific action combinations |
217
217
| ec2-imdsv1 | Identifies EC2 instances using Instance Metadata Service version 1 (IMDSv1), which is vulnerable to SSRF attacks and should be replaced with IMDSv2 for enhanced security |
218
+
| vercel-hobby-plan | Vercel checks whose audited feature is available on the Hobby plan (and therefore also on Pro and Enterprise plans) |
219
+
| vercel-pro-plan | Vercel checks whose audited feature requires a Pro plan or higher, including features also available on Enterprise or via supported paid add-ons for Pro plans |
220
+
| vercel-enterprise-plan | Vercel checks whose audited feature requires the Enterprise plan |
Copy file name to clipboardExpand all lines: docs/developer-guide/checks.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -387,7 +387,7 @@ Provides both code examples and best practice recommendations for addressing the
387
387
388
388
#### Categories
389
389
390
-
One or more functional groupings used for execution filtering (e.g., `internet-exposed`). You can define new categories just by adding to this field.
390
+
One or more functional groupings used for execution filtering (e.g., `internet-exposed`). Categories must match the predefined values enforced by `CheckMetadata`; adding a new category requires updating the validator and the metadata documentation.
391
391
392
392
For the complete list of available categories, see [Categories Guidelines](/developer-guide/check-metadata-guidelines#categories-guidelines).
|**Security**| Web Application Firewall (WAF), rate limiting, IP blocking, and managed rulesets |
162
162
|**Team**| SSO enforcement, directory sync, member access, and invitation hygiene |
163
+
164
+
## Checks With Explicit Plan-Based Behavior
165
+
166
+
Prowler currently includes 26 Vercel checks. The 11 checks below have explicit billing-plan handling in the provider metadata or check logic. When the scanned scope reports a billing plan, Prowler adds plan-aware context to findings for these checks. If the API does not expose the required configuration, Prowler may return `MANUAL` and require verification in the Vercel dashboard.
167
+
168
+
| Check ID | Hobby | Pro | Enterprise | Notes |
169
+
|----------|-------|-----|------------|-------|
170
+
|`project_password_protection_enabled`| Not available | Available as a paid add-on | Available | Checks password protection for deployments |
171
+
|`project_production_deployment_protection_enabled`| Not available | Available with supported paid deployment protection options | Available | Checks protection for production deployments |
172
+
|`project_skew_protection_enabled`| Not available | Available | Available | Checks skew protection during rollouts |
173
+
|`security_custom_rules_configured`| Not available | Available | Available | Returns `MANUAL` when the firewall configuration cannot be assessed from the API |
174
+
|`security_ip_blocking_rules_configured`| Not available | Available | Available | Returns `MANUAL` when the firewall configuration cannot be assessed from the API |
175
+
|`team_saml_sso_enabled`| Not available | Available | Available | Checks team SAML SSO configuration |
176
+
|`team_saml_sso_enforced`| Not available | Available | Available | Checks SAML SSO enforcement for all team members |
177
+
|`team_directory_sync_enabled`| Not available | Not available | Available | Checks SCIM directory sync |
178
+
|`security_managed_rulesets_enabled`| Bot Protection and AI Bots managed rulesets | Bot Protection and AI Bots managed rulesets | All managed rulesets, including OWASP Core Ruleset | Returns `MANUAL` when the firewall configuration cannot be assessed from the API |
179
+
|`security_rate_limiting_configured`| Not available | Available | Available | Returns `MANUAL` when the firewall configuration cannot be assessed from the API |
180
+
|`security_waf_enabled`| Not available | Available | Available | Returns `MANUAL` when the firewall configuration cannot be assessed from the API |
181
+
182
+
<Note>
183
+
The five firewall-related checks (`security_waf_enabled`, `security_custom_rules_configured`, `security_ip_blocking_rules_configured`, `security_rate_limiting_configured`, and `security_managed_rulesets_enabled`) return `MANUAL` when the firewall configuration endpoint is not accessible from the API. The other 15 current Vercel checks do not currently include plan-specific handling in provider logic, but every Vercel check includes exactly one billing-plan metadata category (`vercel-hobby-plan`, `vercel-pro-plan`, or `vercel-enterprise-plan`) alongside its functional security category.
Copy file name to clipboardExpand all lines: prowler/CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ All notable changes to the **Prowler SDK** are documented in this file.
9
9
-`bedrock_guardrails_configured` check for AWS provider [(#10844)](https://github.com/prowler-cloud/prowler/pull/10844)
10
10
- Universal compliance pipeline integrated into the CLI: `--list-compliance` and `--list-compliance-requirements` show universal frameworks, and CSV plus OCSF outputs are generated for any framework declaring a `TableConfig`[(#10301)](https://github.com/prowler-cloud/prowler/pull/10301)
11
11
- ASD Essential Eight Maturity Model compliance framework for AWS (Maturity Level One, Nov 2023) [(#10808)](https://github.com/prowler-cloud/prowler/pull/10808)
12
+
- Update Vercel checks to return personalized finding status extended depending on billing plan and classify them with billing-plan categories [(#10663)](https://github.com/prowler-cloud/prowler/pull/10663)
Copy file name to clipboardExpand all lines: prowler/providers/vercel/services/authentication/authentication_no_stale_tokens/authentication_no_stale_tokens.metadata.json
Copy file name to clipboardExpand all lines: prowler/providers/vercel/services/authentication/authentication_token_not_expired/authentication_token_not_expired.metadata.json
0 commit comments