4 ms·
> This really is only relevant if your site is hosting untrusted content. I thought designing for security meant both removing privileges and preventing escala
by erikpukinskis 11y ago
> This really is only relevant if your site is hosting untrusted content.
I thought designing for security meant both removing privileges and preventing escalation of privileges? I might think my site doesn't host untrusted content, but I might turn out to be wrong about that.
It's worth thinking about what checklists are traditionally used for:
Checklists are a form of risk mitigation that comes out of the disaster investigation world (the FAA is the checklist OG in my mind). The idea is not to create a document that handles every possible situation and every possible corner case, preventing the need for human thought or expertise. The idea is to build up, over a period of time, lists of crucial things which
a) have some chance of getting forgotten and
b) can't be constrained through design
and put them in lists small enough to tick through regularly. It's a way of catching brain farts before they kill someone, not an attempt to replace proper engineering.