I feel like I’ve seen a question like this before, and fidelity insurance was the answer. It seems to fit the scenario best, but I hope I’m recalling it correctly!
I’m a bit confused about the other options. I thought customer liability policies were more about protecting against claims from customers, not internal fraud.
This one seems pretty straightforward - it's clearly a social engineering threat, where someone is trying to trick me into giving up my login credentials.
The key here is to create the PodSecurityPolicy first, then use the RBAC components to bind it to the ServiceAccount. The ClusterRole and ClusterRoleBinding allow you to apply the policy cluster-wide, rather than just in a single namespace. Take it one step at a time, and make sure to test each piece as you go.
Gracia
4 months agoJerry
4 months agoBrande
4 months agoMarguerita
5 months agoKerry
5 months agoKanisha
5 months agoAshton
5 months agoJettie
5 months agoShaunna
5 months agoGilberto
5 months agoTyra
5 months agoJeanice
5 months ago