The Principle of Least Privilege with ArgoCD and Crossplane
Katharina Sick, Senior Software Engineer at Dynatrace๐ป๐๐จ
The Principle of Least Privilege with ArgoCD and Crossplane
Katharina Sick, Senior Software Engineer at Dynatrace๐ป๐๐จ
Jerome Saltzer, Communications of the ACM (1974)
๐ Better overall security
๐ก๏ธ Smaller attack surface
๐ง๏ธ Less malware propagation
๐ Better stability
๐ค Compliance
๐ Never trust, always verify
๐ Least privilege
โ๏ธ Assume breach
๐ฉโ๐ป๐ค
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
namespace: default
name: pod-reader
rules:
- apiGroups: [""]
resources: ["pods"]
verbs: ["get", "watch", "list"]
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: read-pods
namespace: default
subjects:
- kind: User
name: alex
apiGroup: rbac.authorization.k8s.io
roleRef:
kind: Role
name: pod-reader
apiGroup: rbac.authorization.k8s.io
๐ฏ Keep repository configuration on point
โ Use ArgoCD projects to provide boundaries
๐ Declare policies to prevent misuse
๐ฎ Simplify the user interface for clear policies
๐ฑ Provide development environments
๐ก Least privilege not only applies to the user interface
๐ผ Favor composite resources over managed resources
๐๏ธ Use dedicated provider configurations
๐ฅ Handling emergencies
๐ Golden path vs golden cage
๐ซ Always reiterate
๐ Least privilege is just the start