1) Requirement for real-time endpoint behavioral detection
- The product is backup- and snapshot-centric and does not replace endpoint telemetry and containment solutions.
2) Requirement for transparent, list-priced procurement
- Organizations that require public list pricing and minimal sales negotiation may find the vendor’s typical sales-led, quote-based approach a poor fit.
3) Requirement for guaranteed detection of very small-scale changes
- If the threat model requires guaranteed alerting for small-scale or very short-lived encryption events, validate detection thresholds in a representative proof of concept.
4) Core workloads outside documented support
- If the environment includes workloads or cloud disk types that are excluded from anomaly detection per the vendor’s compatibility guidance, consider alternatives with broader native coverage.
5) Need for explicit allowlisting as a primary control
- If operations require deterministic whitelisting rather than feedback-based false-positive handling, confirm current product capabilities before purchase.