Community - please note your interest in this feature with a note if you like it.
ESE-485 - If you wish to request this as well from RSA support.
Due to the complexity of correlation rules we have setup for our customers and the significant duplication of effort that happens for each one, we would like a feature to simplify modifying a correlation rule to accommodate a new customer.
We have numerous customers within the same correlation rule, due to enVision application limitations.
So we’d like:
1) The ability to support more levels within a correlation rule. Currently limited to 3 levels (one of which is a limited filter), we’d like to see 5 levels.
2) The ability to include the names of each “level” to ALL output action types that enVision supports, including SNMP and SMTP. This currently means the Correlation rule name, the Circuit name and the Statement name .
3) The ability to perform complex logic within a Statement Filter. Such as nested SQL with AND/OR’s to group as the customer sees fit. The current logic prevents a Statement Filter like this:
Customer name: Customer1
Ignore these event matches (per line):
Var1 = "value3"
Destination IP = 184.108.40.206 and Var1 = "value1"
Destination IP = 220.127.116.11 and Var1 = "value2"
Destination IP = 18.104.22.168 and Source IP = 10.10.10.10 and Var1 = "value2"
SQL logic we appear to need to implement those changes (in general):
Where customer = "Customer1" AND
NOT (Var1 = "value3") OR
NOT (Destination IP = 22.214.171.124 and Var1 = "value1") OR
NOT (Destination IP = 126.96.36.199 and Source IP = 10.10.10.10 and Var1 = "value2") OR
NOT (Var1 = "value1")
We feel these features would enable other customers to improve ROI by providing additional capabilities that your customers can take advantage of. They are also logical additions to your product as customers’ usages grow. This design shown provides customer flexibility so that any customer may implement the feature as they require.