Description
Connecting your own Avanan Email Protection licence to Guardz is a data-integration and remediation tool, not a managed detection and response service, as per Guardz documentation. Policy stays in the Check Point console, only two event types sync, and BYO detections never appear in Digest reports.
This article is for Manage Protect MSP partners. It explains what each Avanan option includes, why many "Guardz isn't working" reports are really BYO limitations, and what to check before raising a support case. For endpoint protection, see the companion article on SentinelOne BYO vs Guardz-Managed.
Comparison
MDR is a separately gated add-on, sold via Ultimate and Elite plans. It is not bundled with BYO Avanan, however the licence was sold.
Capability | BYO Avanan | Guardz-Managed Avanan |
|---|---|---|
Licence and billing | MSP owns the Check Point/Avanan licence and pays Check Point directly; Guardz does not bill for it | Guardz-provisioned licence, billed through Guardz |
Policy configuration | Only in the Check Point console; Guardz cannot view or change it | Configured directly in Guardz; nothing to touch in the Check Point portal |
What syncs to Guardz | Only two event types: Quarantine Emails and Alert Emails | Full detection set (alerts, spam, quarantine, user-reported) across all sources |
Digest reports and end-user visibility | Excluded from Digest reports and not visible to end users; only standard Guardz notifications fire | Included in Digest reporting per the MSP's plan |
Remediation actions | Quarantine/restore email and allow/block list updates only | Same actions, plus central spam management, phishing category review and DKIM/DMARC checks |
SOC/MDR coverage | None | MDR add-on available on Ultimate and Elite, with human-driven triage and response |
The Digest Report Gap
BYO Avanan detections are excluded from Digest reports by design. This is the limitation most likely to cause confusion.
An MSP reviewing a monthly Digest report for a BYO Avanan customer may see no email threats and assume nothing happened. In fact, the report structurally cannot show BYO email detections. To see what Avanan caught, check the Check Point console or the Quarantine and Alert events synced to Guardz.
Complaints that are expected behaviour on BYO
The below examples are not bugs - they are what BYO Avanan does by design.
Customer complaint | Why it happens on BYO |
|---|---|
"This didn't show up in our Digest report." | BYO detections are excluded from Digest reports and end-user visibility by design, not by mistake. |
"A phishing email got through that should have been caught." | Phishing category review, DKIM/DMARC checks and spam management stay entirely in the Check Point console on BYO. Guardz does not touch that policy layer. |
"Nobody at Guardz reviewed or responded to the threat." | BYO includes no SOC or MDR coverage. The MSP must act on synced alerts using the manual tools. |
"We thought we were paying for Guardz's SOC." | The account was sold or migrated to BYO without MDR named as a separate line item. Treat this one most seriously. |
Before you raise a ticket
If you do experience issues with Avanan in Guardz, please work through these checks first before raising a ticket. It might resolve your issue faster.
1. Open the customer in Guardz and confirm whether email protection is connected as BYO Avanan or Guardz-managed.
2. For a missed phishing email on BYO, review the policy in the Check Point console, not Guardz.
3. For missing Digest data on BYO, check the Check Point console and the Quarantine and Alert events in Guardz instead.
4. Check the customer's plan and whether the MDR add-on is active. MDR is only available on Ultimate and Elite.
If the account is BYO without MDR, the fix is usually a policy change in Check Point or a licencing conversation, not a support ticket.
If it does look like Guardz failed to sync or act on an event it should handle, please contact Manage Protect so we can escalate it to Guardz support.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article