# Deployment and SOC 2

**URL:** <https://discuss.elastic.co/t/deployment-and-soc-2/170219>\
**Category:** Elasticsearch\
**Created:** [February 27, 2019, 6:13pm UTC](https://discuss.elastic.co/t/deployment-and-soc-2/170219 "2019-02-27T18:13:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![agx](https://avatars.discourse-cdn.com/v4/letter/a/e19adc/32.png) [@agx](https://discuss.elastic.co/u/agx)\
**Post date:** [February 27, 2019, 6:13pm UTC](https://discuss.elastic.co/t/deployment-and-soc-2/170219/1 "2019-02-27T18:13:04Z")

</div>

We've been having a discussion around here on how to best deploy Elastic that complies with our SOC 2 requirements. In a nutshell, SOC 2 requires all our environments to be separate.

We are using Elastic for log aggregation and monitoring. It is not a core component or essential part of our product, and our product can exist perfectly fine without Elastic.

I'm of the opinion that since ES is not a required part of our product stack, that it is reasonable/acceptable to deploy a single instance of Elasticsearch and to use Spaces and Security to control access to the data.

I am curious to know how folks in a similar situation (SOC2, ES only for log aggregation, multiple environments) are handling the deployment of Elastic in their companies.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 27, 2019, 6:13pm UTC](https://discuss.elastic.co/t/deployment-and-soc-2/170219/2 "2019-03-27T18:13:09Z")

</div>

Closed on March 27, 2019, 6:13pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.