jlj7

Completely tone-deaf. Those mock-ups would be pretty scary, were I visually-impaired (as an example): accidents waiting to happen everywhere; chaos, from a guide dog's perspective (if they were lucky enough to have one).

One wheelchair in all the mock-ups; and one of the smaller ones at that, that you can't zoom in on.

No prams. Anywhere.

This one's tricky, I'll admit, but, well, it looks really crowded. Any thought to low-arousal environments?

I guess this was designed. But for who?

I... don't know what to say about this right now. I'm reading the AdNauseam paper, to see whether that helps.

This has... disturbed me.

I was thinking of on-call support being a key part of the overall concept of HA, but, yes, good point: much of this risk can be mitigated, even with OSS.

Great article.

I would point out, though, that the disadvantages listed against Secrets as a Service need not apply to Hashicorp's Vault:

1) Single point of failure: Vault Enterprise offers high availability solutions that should be able to mitigate much of this (at a cost, of course).

2) Codebase must be changed: Vault (and Consul) really shine here: Consul Template -- and Envconsul -- can be used to seamlessly integrate legacy code with Vault.

3) System-level access must be protected carefully: Well, this is always true, but Vault gives you more options than many others here as well: based on risk assessments, you can choose to limit the secrets you issue, particularly when you're talking about system-level access. You can have very short TTLs, one-time-use wrappers that limit the exposure of said secrets, etc.

(I don't mean to sound like a shill, BTW. It's just that these points easily jumped to mind, having just certified as a Vault Associate. YMMV. :-) )

I didn't know about Terraform graph. Thanks for the tip!