You won’t find any argument to the contrary from me. (Although I would nitpick that you could relax some of those points in certain circumstances. For example y

You won’t find any argument to the contrary from me. (Although I would nitpick that you could relax some of those points in certain circumstances. For example you may not necessarily need or want to have your OOB backups of your wiki encrypted if you variously don’t have credential-type secrets in it, or have satisfactory enough physical safeguards for your use case. But we could probably argue that kind of nuance back and forth for eternity.) It’s just that it’s fairly common to see such circular dependencies. I’ve seen many sitiations where one team just assumes that another team is looking after these things and that “it’s someone else’s responsibility” or some such. I am certainly not defending that. Plenty of teams see things like backup as something that is somewhere else in the stack. Plenty of executives just assume their technologists are baking these capabilities into product. A lot of junior people haven’t really been given a solid education on these areas and it’s not uncommon to see newer-to-career people making basic mistakes like conflating synchronization and backup, or geo-redundancy with wholesale BCDR.