UEBA detections delivered by the UEBA content add-on render an editable annotations section in Enterprise Security | Content Management. Editing the annotation values and selecting Save completes without an error, but the values are not written to the detection. Reopening the detection shows the original values.
The behavior is the same for users holding premium administrator roles such as ess_admin and sc_admin, so it is not caused by missing capabilities or write permissions.
Follow these steps to confirm the annotations were not committed.
| rest splunk_server=local /servicesNS/nobody/DA-ESS-UEBA/saved/searches
| search title="<UEBA detection title>"
| table title eai:acl.perms.write action.correlationsearch.annotations
action.correlationsearch.annotations field confirms the annotation was never written to the detection.eai:acl.perms.write field confirms the role is not the limiting factor.No further role, capability, or app permission troubleshooting is required.
UEBA detections are not editable in Splunk Enterprise Security 8.5.x, including their annotations. The editable fields in Content Management are a display-only artifact of the shared detection editor.
To annotate UEBA-driven content, clone the detection and apply annotations to the cloned copy:
SA-ThreatIntelligence or a custom app, rather than to DA-ESS-UEBA.| rest splunk_server=local /servicesNS/-/-/saved/searches
| search title="<cloned detection title>"
| table title action.correlationsearch.annotations
Add annotations to detections in Splunk Enterprise Security
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
01-Oct-2026
|
Initial Release |