Breach Secure Now Status

Investigating: An issue is preventing the deletion or archiving of inactive clients in the portal. When attempting this action as either a Partner Admin or Support Admin, a “Status 400” error is displayed.

Our team is actively investigating the issue and will provide updates as more information becomes available. Thank you for your patience.

Monitoring: Microsoft will shut off their legacy Exchange Online Token in October. This change affects older Catch Phish deployments.

Partners currently using the workaround (re-enabling Exchange Online Tokens) must upgrade to the latest version of Catch Phish from the Microsoft Add-on Store.

Partners who have not yet acted and are just learning about this deadline also need to upgrade.

Upgrades can be completed by following the instructions in the Help Center. Alternatively, partners can open a support ticket, and our team will assist with the deployment.

Monitoring: Our team has identified and resolved the issue that prevented partners from saving the Metadata URL during SSO configuration in the portal. The error message, “Failed to save Federated Login: Failed to save Metadata URL,” has been addressed, and the fix has been successfully deployed. We will continue monitoring the situation to ensure the feature remains fully operational. Thank you for your patience while we worked to resolve this.

Investigating: An issue with SSO setup has been identified. When trying to save the SSO configuration, an error is displayed saying, “Failed to save Federated Login: Failed to save Metadata URL.” This issue only impacts new SSO setups. Existing SSO setups are still working correctly.

Our team is investigating the issue and will provide updates as we learn more. Thank you for your patience and understanding.

Identified: We have implemented a workaround for phishing campaigns stuck in the queue and are working towards a permanent solution. For any partners who have not already opened a support ticket reporting their stuck phishing campaigns, please open a ticket and we will apply the workaround. Thank you for your patience as we address this matter.

Identified: We have identified an issue with our simulated phishing system that is causing delays in processing emails in the queue. As a result, simulated phishing emails are taking longer than expected to be sent out.

Our team is actively working on a fix and will provide updates as soon as more information is available. We appreciate your patience and understanding as we resolve this matter.

Resolved: We have implemented a permanent fix that addresses the phishing campaign scheduling issue. Our Support team is following up with partners who have open tickets related to this matter and will continue monitoring phishing campaign performance to ensure stability.

Identified: We are currently experiencing issues with simulated phishing emails not being delivered to Google Workspace and Gmail accounts. This may be due to an increased volume of simulated phishing emails being sent to Google-hosted accounts.

Google is currently blocking delivery. Our team is actively working with Google to resolve this matter. We will provide updates as soon as more information becomes available. Thank you for your patience.