As Microservices is now becoming the most preferred method for creating cloud native distributed applications, it poses many security challenges. Secrets Management is a critical component of container based application security.
When it comes to collecting and shipping logs to Elastic stack, we usually hear about ELK – Elastic, Logstash and Kibana. It has almost become a synonym for Elastic stack. But when it comes to technology, there is never a perfect solution. Fluentd is gaining popularity as far as logging
Docker is used for Application virtualization. So ideally a single docker container should be used to run a single process. Running multiple services on a single container is not the recommended approach but still there can be forced scenarios where we need to start more than one process in a
For user case where you want to skip MultiFactorAuthentication / PAM module like google authentication validation code for specific users and keep it enabled for the rest, following solution can be used -
About Vault and using Consul as backend- Vault is designed from the ground up as a secret management solution. As such, it protects secrets in transit and at rest. It provides multiple authentication and audit logging mechanisms. Dynamic secret generation allows Vault to avoid providing clients with root privileges to
Managing secrets, passwords, ssh keys, access keys etc and sharing with teams or end users securely has become very difficult in today’s complex infrastructure environments. This is where Vault makes your life easy by managing all this sensitive information in a microservice. In this article we are going to do