Knowledge Base

Yes

Environment

Carbon Black Cloud Console: October 2020 Release and later
- Endpoint Standard (was CB Defense)

Comma separated policy rule no longer functional in console
When editing path based policy rule, following message will be observed
```
Separate paths with new lines
```
If a policy is saved with comma separated application paths, then the rule will not take effect e.g. A Blocking and Isolation Rule set to terminate action will not terminate Application(s) At Path

Policy rules no longer use commas to separate the application paths. New application paths are now to be separated by a new line.

Manually separate all policy rules by line break and remove all commas used to separate each rule

Existing comma separated policy rules will continue to function as expected
Existing comma separated policy rules should have automatically been converted from comma separated to line separated
This change from comma separated to line separated policy rules applies to both permission rules and blocking and isolation rules
The Carbon Black Console will continue to allow comma separated application paths in policy rules although this will invalidate the rule and the rule will not take effect. CB investigating the possibility of not allowing the policy to be saved if the rule is in an incorrect format.
Under the "Fixed Issues" section of the Release Notes, the change relating to commas in path name is referenced under DSER-26162