3 years ago

Category: Software, Business, Security, Data, Kubernetes

The responsibility and even accountability for security is rapidly shifting in the direction of DevOps engineers, as they have a view into the broad architecture of the processes and systems used to deploy microservices. Our customer discussions and xOps project engagements indicate that going forward, DevOps engineers and DevSecOps processes are going to be even more accountable for security.

The benefits are that: Nevertheless, one of the biggest problems in this world of identities for microservices is propagated across multiple environments, compute types, and a hybrid cloud.

Trust in microservices in general, which is a key aspect of DevSecOps and DevOps, is a set of processes and architecture that defines how to authenticate microservices in this new distributed systems environment, whether Kubernetes is used or not.

And that is actually the gist of the security problem; the fact that you have all of those new components, each one of them can create an attack surface within your architecture, means that there is a constant need to validate that they are not compromised and that there are no unrecognized microservices in your environment.