Support articles
Find clear, step-by-step solutions to common WithSecure issues across installation, configuration, updates, and product performance.
Error: "New rule creation unavailable" appears in Accepted behavior feature due to Broad Context Detection does not contain any identified key detections
Last updated
Issue:
When closing a Broad Context Detection event as Accepted Behavior, we are getting this error:
New rule creation unavailable.
Broad Context Detection is now closed as Accepted behavior.
This Broad Context Detection does not contain any identified key detections, making it unsuitable for generating a suppression rule.
Resolution:
Here's a community article you might find helpful about the 'Accepted behavior' for WithSecure Elements Endpoint Detection and Response:
- Elements EDR - New Feature - Accepted Behavior - WithSecure™
- Elements Endpoint Detection and Response (EDR) detects a safe application. How to whitelist the detection? - WithSecure™
When creating a suppression rule, Broad Context Detection (BCD) should at least has one or more key detections. This will prevent and auto suppress future BCD events with the same key detection from triggering alerts.
A suppression rule cannot be created unless a key detection is present in the BCD event. Instruction for creating suppression rules can be found in the EDR user guide: Suppress detections individually | Elements Endpoint Detection and Response | Latest | WithSecure User Guides