Re:Bye Bye Mongo, Hello Postgres
by AlexCoventry on Thursday December 20, 2018 @01:02AM
(#18722812)
> the choice between "run an entire data centre ourselves, store everything there"
If those were the only two choices, you might be right. But the resources needed for the actual CMS functionality sound modest enough to run independently of the main website.
> the client computer that connects to the CMS is just as, or more likely to be compromised
That's faulty reasoning.
> That's faulty reasoning.
Why? It's an obvious potential point of compromise.
Re:Bye Bye Mongo, Hello Postgres
by AlexCoventry on Thursday December 20, 2018 @08:41AM
(#18724767)
Sorry, I misunderstood. I read it as saying "We're going to get hacked via this other vector, anyway, so why bother?" I see your point, now.
After all, the client computer that connects to the CMS is just as, or more likely to be compromised. I wouldn't be surprised if the coverage (or at least parts of it) were edited on airgapped laptops.