How to Secure Your Node.js Containers on Kubernetes With Best Practices - Deepu K Sasidharan

Security

Secure your Node.js containers on Kubernetes with best practices, including image updates, non-root users, security scanning, audit logging, network policies, secret storage, authentication, and more.

Key takeaways

Use official verified images and keep them up to date
Run containers with non-root users to limit access
Use Docker bench for security scanning
Enable audit logging for the cluster
Use Kubernetes network policies to control traffic
Use secrets to store sensitive data
Use role-based access control (RBAC) and attribute-based access control (ABAC) for authorization
Use OpenID Connect (OIDC) for authentication
Monitor and audit traffic and resources
Use resource quotas and limit ranges to prevent resource exhaustion
Use a least privileged user as much as possible
Use a trusted registry for non-official images
Use Docker ignore files to exclude sensitive files
Use dump init to terminate applications properly
Use OIDC to secure the Kubernetes control plane
Use RBAC to secure secrets
Use ABAC to define role-based access control
Use OIDC to secure the cluster
Use Kubernetes network policies to isolate traffic between namespaces
Use secrets to store sensitive data
Rotate infrastructure credentials frequently
Use a least privileged user as much as possible
Monitor and audit traffic and resources
Use resource quotas and limit ranges to prevent resource exhaustion
Use a trusted registry for non-official images
Use Docker ignore files to exclude sensitive files
Use dump init to terminate applications properly

How to Secure Your Node.js Containers on Kubernetes With Best Practices - Deepu K Sasidharan

More talks