Checks
Browse individual security checks available in the Prowler Registry. Filter by cloud provider, severity, or search by check ID.
Browse individual security checks available in the Prowler Registry. Filter by cloud provider, severity, or search by check ID.
llm_harmful_unsafe_practices
Tests handling of dangerous activity instructions
llm_harmful_violent_crime
Tests handling of violent crime content
llm_harmful_weapons_ied
Tests handling of Improvised Explosive Devices
llm_hijacking
Assesses protection against unauthorized resource usage and purpose deviation
llm_imitation
Tests safeguards against unauthorized entity impersonation attempts
llm_indirect_prompt_injection
Evaluates vulnerability to injection attacks via untrusted variables
llm_overreliance
Assesses overreliance on system assumptions
llm_pii_api_db
Tests for PII exposure through API and database access vectors
llm_pii_direct
Evaluates direct PII exposure vulnerabilities
llm_pii_session
Tests for PII leakage in session data
llm_pii_social
Assesses PII exposure through social engineering vectors
llm_prompt_extraction
Evaluates protection against system prompt disclosure attempts
llm_rbac
Tests implementation of role-based access control mechanisms
llm_reasoning_dos
Tests for computational resource exhaustion through excessive reasoning patterns
llm_shell_injection
Tests protection against command injection vulnerabilities
llm_sql_injection
Evaluates resilience against SQL injection attacks
llm_ssrf
Tests for server-side request forgery vulnerabilities
loadbalancer_alb_https_uses_ssl_certificate
E2E Networks application load balancers serving HTTPS traffic should have a valid SSL certificate configured so client connections are encrypted and authenticated.
loadbalancer_backend_health_check_enabled
E2E Networks application load balancers should have HTTP health checks configured for their backends so traffic is only routed to healthy nodes.
loadbalancer_bitninja_enabled
E2E Networks load balancers should have BitNinja protection enabled to provide web application firewall coverage on public endpoints.
logging_log_metric_filter_and_alert_for_audit_configuration_changes_enabled
Cloud Logging log-based metrics capture audit configuration changes (e.g., SetIamPolicy with auditConfigDeltas), and an associated Cloud Monitoring alert policy notifies when such log entries occur.
logging_log_metric_filter_and_alert_for_bucket_permission_changes_enabled
Cloud Logging defines a log-based metric for Cloud Storage IAM changes using filter resource.type="gcs_bucket" AND protoPayload.methodName="storage.setIamPermissions", and a Cloud Monitoring alert policy that references that metric.
logging_log_metric_filter_and_alert_for_compute_configuration_changes_enabled
Log metric filters and alerts for Compute Engine configuration changes provide visibility into modifications to instances, disks, networks, firewalls, and routes. These monitoring controls enable security teams to detect unauthorized changes and investigate suspicious infrastructure modifications.
logging_log_metric_filter_and_alert_for_custom_role_changes_enabled
Cloud projects are assessed for log-based metrics that filter resource.type="iam_role" and the methods CreateRole, DeleteRole, UpdateRole, and for an associated Cloud Monitoring alert policy that references those metrics.