Everything Elasticsearch needs to be enterprise-ready

Search Guard met all of our needs and more. Not only have we found open source tools that meet our needs, but we've found a partner that's worked with us through the development of the new platform. They've been responsive and engaged every step of the way.

Security is paramount to the protection of our customer's data. ICHEC chose Search Guard to protect its ELK-Stack environment because of its Single Sign-On authentication integration, access control measures and audit features. The licensing model is also flexible enough as we continue to grow our services.

Security is the prerequisite for every project in the IT industry, especially when it comes to data. HEAnet chooses Search Guard to protect its ELK cluster because it provides node-to-node encryption (TLS) and more features such as multi-tenancy, compliance, unlike its competitors who only provide security on the REST layer.

The Steinbuch Centre for Computing at KIT is using Search Guard to secure Elasticsearch instances operated in the World Wide LHC Computing Grid Tier-1 center "GridKa" and in the Large Scale Data Facility. Without fine-grained access control we would be unable to expose Elasticsearch to individual users or use single instances for both private and public data. The multitenancy features for Kibana offered by Search Guard are specially useful, enabling us to also use Kibana for public dashboards.

Search Guard makes it possible for us to use the ELK-Stack in a productive environment. We chose Search Guard primarily because of the Active Directory and role-permission features. We find their licensing model incredibly helpful, as well as the fact that we are able to use an unlimited amount of nodes.

We have chosen SearchGuard because it matches our values of technical rigor, openness, and auditability. It has enabled us to ensure that data in transit is secure against eavesdropping in off-prem environments, to implement verifiable and granular access to our Elastic clusters, and most importantly to give our analysts access to restricted data sets with confidence that PII remains protected and confidential.

In 2019 we planned to install one large logging infrastructure cluster for about 100TB of data. Not as SIEM, but mainly to have logs available centrally for developers and admins. We chose one Elasticsearch instance as a large log repository. We decided to install the 8 data nodes and 10 VMs with one contractor. He proposed two solutions to us for the "role-based access control" software. After testing, we quickly adopted SearchGuard. We actually send all our critical logs to this cluster. About 15 users can log in to the system and see what they are looking for. With SearchGuard we can easily limit access to the logs of their applications only. The right segregation is working well, and we are happy with the solution we chose for the user's access control.