New Features - Strata Cloud Manager - June 2026

When you configure a webhook for incident notifications, you cannot verify that your endpoint URL, authentication method, and payload handling function correctly until a real incident triggers delivery. This lack of visibility means misconfigurations often go undetected and cause missed alerts during critical security events. To address this, Strata Cloud Manager now allows you to send an on-demand test payload directly from your webhook configuration, providing immediate confirmation that your integration works before an actual incident occurs.

When you test your webhook notification profile, Strata Cloud Manager provides an immediate success or failure result, including the HTTP status code or error category, so you can rapidly diagnose connectivity issues, authentication errors, or receiver misconfigurations.

You benefit from this capability when you onboard a new webhook endpoint, rotate authentication credentials, or migrate receivers to new infrastructure. Because Strata Cloud Manager tests your current configuration values before you save them, you can iterate rapidly and confirm correctness in a single workflow without generating unnecessary incident traffic.

When you configure email notification profiles, you cannot verify whether your email addresses and settings will successfully deliver messages until a real notification event occurs, which can result in missed alerts and production issues. The Test Email feature solves this problem by allowing you to send a test message to all configured recipients directly from the notification profile creation or editing workflow, giving you immediate confirmation that your email configuration is functional before you rely on it for critical alerts.

You can use this feature any time you create or modify an email notification profile to validate that each recipient address is reachable through your email provider. When you select the Test Email action, the system sends a test message to every configured address using the same delivery path as production notifications, then returns a per-recipient result indicating whether your email provider accepted or rejected the message. This ensures that common misconfigurations such as incorrect addresses, authentication failures, or connectivity issues are surfaced immediately rather than silently failing when a real security event triggers a notification.

When WildFire® detects suspicious activity across your environment, you need a way to surface findings as incidents without overwhelming your operations team with noise. The integration with the Unified Incidents Framework solves this by allowing WildFire to publish informational incidents through a centralized pipeline while giving you granular control over which objects generate incidents. By default, Strata Cloud Manager suppresses WildFire incident codes to ensure your queue remains relevant until you explicitly raise alerts for specific resources.

You can configure custom settings on a per-incident-code basis to select the exact objects for incident generation and optionally attach a notification profile to alert your team through preferred channels. Keep in mind that manual uploads do not support notifications. If you previously configured notifications in the legacy portal, you must recreate these settings in Strata Cloud Manager, as they do not migrate. To prevent duplicate alerts, Strata Cloud Manager sends only one email notification if you configure the same device in both the legacy and new portals.

Because these incidents are informational, the integration minimizes manual overhead. WildFire automatically clears the alerts after a controlled time period, and Strata Cloud Manager clears the associated incidents accordingly. Incidents also include a hold time, resulting in a five-to-six-minute delay for the first notification of every new incident.

To ensure alerting remains targeted when you configure WildFire incident settings, you must specify exact objects rather than using wildcards. The integration coordinates between WildFire and the correlation engine to match incoming alerts to your custom or default settings, ensuring accurate incident generation and proper notification routing across your deployment.