# security\_context via host tags - documentation wrong?

**URL:** <https://community.dynatrace.com/t/security-context-via-host-tags-documentation-wrong/56405>\
**Category:** Open Q&A\
**Tags:** data-privacy-and-product-security, documentation\
**Created:** [July 9, 2026, 10:59am UTC](https://community.dynatrace.com/t/security-context-via-host-tags-documentation-wrong/56405 "2026-07-09T10:59:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![r\_weber](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/r_weber/32/24884_2.png) [@r\_weber](https://community.dynatrace.com/u/r_weber)\
**Post date:** [July 9, 2026, 10:59am UTC](https://community.dynatrace.com/t/security-context-via-host-tags-documentation-wrong/56405/1 "2026-07-09T10:59:46Z")

</div>

As per the documentation it should be possible to set the security\_context of a host via automated tagging rules:

 ![r_weber_0-1783594552557.png](https://global.discourse-cdn.com/dynatrace/original/2X/4/4dfa86d3a8a86a16d609db0edbbc68edf879e54a.png)

And then, in combination with the topology configuration rules set the security context according to this tag value:

 ![r_weber_1-1783594639328.png](https://global.discourse-cdn.com/dynatrace/original/3X/1/1/11619d4df72b2909390bf9b883edf4170082b1d6.png)

However, this is not working. I guess tagging rules do not work for that, only custom host properties or when set via oneagentctl?

---

<div class="post-metadata">

**Author:** ![sujit\_k\_singh](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@sujit\_k\_singh](https://community.dynatrace.com/u/sujit_k_singh)\
**Post date:** [July 15, 2026, 4:22am UTC](https://community.dynatrace.com/t/security-context-via-host-tags-documentation-wrong/56405/2 "2026-07-15T04:22:08Z")

</div>

Hi&nbsp;[@r\_weber](https://community.dynatrace.com/user/35901)

automated tagging rules may not reliably propagate the dt.security\_context to all signal types (logs, spans, metrics, events). This is because dt.security\_context is a primary Grail field that needs to be enriched at the source (OneAgent level) before telemetry is sent to Dynatrace.&nbsp;[Enrich OneAgent telemetry with primary Grail fields and tags — Dynatrace Docs](https://docs.dynatrace.com/docs/manage/tags/tags-domain-oneagent)

Tagging Rules Don’t Work Here - Primary Grail fields/tags (like dt.security\_context) must be set at the source via OneAgent before data is sent to Dynatrace.  
Automated tagging rules are evaluated server-side after data arrives — too late for security context assignment.

Thanks,

Sujit
