Thread by @dinodaizovi

One benefit of studying adjacent disciplines is that you can find some really good ideas to borrow and apply.

For example, SRE studies failure and resilience a lot (e.g. cascading failures). What does a cascading *security* failure look like in your env?

infoq.com/presentations/…

For example, imagine that there is a security failure whereby a malicious entity can launch malware on an authorized user's machine (I know, suspend your disbelief).

How far can they get on their goals using the authorized access of the most privileged users in your environment?

For the purposes of this analysis, consider exploiting another vulnerability or violating another security boundary to be the limit of the analysis. Assume they have user's creds and can reauth.

How many users in your env have unilateral access to RCE your entire endpoint fleet?

If you think about security through the lens of resilience, any capability to maliciously side-effect your entire fleet at once is a strategic risk.

Perhaps changes should cascade through segments of the fleet with separate individuals' manual approvals at 1%, 10%, 50%, etc.

Or just have a gazillion Active Directory Domain Admin accounts for whatever systems management infra or tasks are needed. You do you.