# How to effectively tie organizational owner to systems, applications, and services to enforce security mandates **URL:** \ **Category:** Elasticsearch\ **Created:** [April 20, 2017, 11:54am UTC](https://discuss.elastic.co/t/how-to-effectively-tie-organizational-owner-to-systems-applications-and-services-to-enforce-security-mandates/83045 "2017-04-20T11:54:21Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Andrew\_Feller](https://avatars.discourse-cdn.com/v4/letter/a/7ea924/32.png) [@Andrew\_Feller](https://discuss.elastic.co/u/Andrew_Feller)\ **Post date:** [April 20, 2017, 11:54am UTC](https://discuss.elastic.co/t/how-to-effectively-tie-organizational-owner-to-systems-applications-and-services-to-enforce-security-mandates/83045/1 "2017-04-20T11:54:21Z")
We are working to lockdown elastic stack access to organizational units that own and operate services. To this end, I was hoping others in the community that must support ISO 27K can elaborate on how they capture organizational information relative to systems, applications, and services for the purposes of security. I don't know if people try to use the doc\_type attribute of log events to reflect this information or use completely custom attributes. Documentation[[1](https://www.elastic.co/guide/en/watcher/2.4/actions.html#_configuring_index_actions)] simply describe doc\_type as _The type of the document the data will be indexed as._ I'd appreciate whatever insights and recommendations anyone has to offer! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 18, 2017, 12:06pm UTC](https://discuss.elastic.co/t/how-to-effectively-tie-organizational-owner-to-systems-applications-and-services-to-enforce-security-mandates/83045/2 "2017-05-18T12:06:40Z")
Closed on May 18, 2017, 12:06pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.