An ESA rule is disabled after being deployed to the ESA service and reports the error below.
ESA was unable to deploy one or more rules, and these rules were disabled. Common issues include: missing metadata, invalid rule syntax, and unavailable external connections at the time of deployment.
The ESA log level WARN contains the following message:
Implicit conversion from datatype 'String' to 'String' is not allowed
Within the ESA service the hunting and investigation meta keys were changed from a string type to a multi-valued type.
The following meta keys are affected:
Version 10.6.2.1 and Above
To deploy custom ESA rules using these meta keys the rules must be updated to use array syntax and redeployed. For example:
ioc = 'homograph detected'
'homograph detected' = ANY(ioc)
Version 10.6.2 and Below
To deploy RSA Live ESA rules using these keys the meta keys must be added to the ESA service using the multi-valued type. In addition, any custom ESA rules using these meta keys must be updated to use array syntax.
The steps below explain how to add the meta keys to the ESA service with the multi-valued type.
In the RSA Security Analytics UI, navigate to Administration > Services > ESA > Explore > Workflow > Source > nextgenAggregationSource > ArrayFieldNames.
In the ArrayFieldNames property, enter the meta keys separated by commas. Be sure to use underscores for multi-word meta keys.
Restart the ESA service.
Update custom ESA rules using these meta keys to change them from string syntax to array syntax. For example: