Q1. How will Elastic's recent acquisition of build.security benefit customers? What new capabilities has Elastic acquired—or strengthened—through the purchase?
build.security provided dev and security teams with the platform they long-needed for putting security guardrails at the right places in their pipelines, from code, to test, to cloud. By harnessing the power of Open Policy Agent, a CNCF graduated open source project, build.security made it easy for developers to describe their security policies-as-code and integrate those policies with their cloud native technologies. OPA's developer-focused culture and DNA made it a perfect fit for Elastic's free and open vision, providing the community with all the search, observability and security capabilities they need.
In the near future, Elastic's users will be able to leverage their existing Elastic agent and cloud integrations to opt-in and add security and compliance capabilities with a click of a button. Moreover, leveraging policy-as-code will provide Elastic's enterprise users with the customization and flexibility they require when complying with multiple security benchmarks such as CIS, GDPR, HIPAA and other unique corporate policies.
Q2. What are the biggest challenges organizations face when it comes to their ability to enforce consistent security policies from the endpoint to workloads in the cloud?
Almost every company today is a software company, and almost all software is developed in the cloud. Developing software to run in the cloud is different from doing the same for on-premise environments. The security perimeter has shifted and evolved to a state where identity takes precedence. From the moment new code is introduced into a git repository, all the way to the point of time when it is deployed and executed in a cloud container, it's vulnerable for supply chain attacks, mostly around identity and authorization.
For example:
- Is the developer authorized to change the specific code section?
- Do the proposed code changes comply with the company's policies around cloud misconfiguration, network policies, GDPR, etc?
- Is the workload using a docker image downloaded from a trusted docker repository?
- Is the docker container running with special privileges?
- Does the workload have the right resource limits, preventing it from disrupting other workloads in the cluster?
OPA and policy-as-code in general are perfect tools when it comes to providing a systematic, automated and holistic approach for these questions. The vast ecosystem of integrations, which are all community driven and open sourced, together with the ability to “write your own” policies that fit into the unique and custom requirement that almost every company has, brought the policy-as-code approach to high levels of adoption. The grand vision is to have these hooks along the whole CI/CD pipeline, from code, to build, to deploy, to runtime - with the right security and compliance checks, all defined as code and enforced in real time.
Q3. Why is it important for Elastic to be at Black Hat Europe 2021? What is Elastic's main messaging at the event from a security perspective?
Elastic is the only free and open limitless XDR solution in the market today, and, being at Black Hat allows us to share this message with the broader security industry, as well as allowing users to speak to our experts and ask any questions they may have. It's important for users to understand the benefits of an open platform, and gain an understanding of all the features built into our technology stack, and how it might benefit their organization.