How do you identify and protect the “Crown Jewels” of your architecture?
Yeah. I'm glad you brought that up, Anthony. I think you articulated well, that data flow sometimes really becomes that crown jewel data flow. That's a real salient point that I think we should all remember. If you do that crown jewel flow, then you can figure out how deep you go. Consider below the operating system, security firmware bios, right? In some contexts, highly critical. Half of the folks I’ve talked to said, "I'm not going to go deal with it on my PC servers or whatever because I don't have the time. And I'm just going to assume when I buy the laptop from Dell, they're doing a good enough job, right?"
They're not.
Yeah, trust me, I know. I always bring up below the operating system vulnerabilities, because I think it's a supply chain risk that permeates our infrastructure pretty broadly from cloud to on-prem: the printers to laptops, to desktops, let alone IoT. As buyers, we need to apply that third-party risk pressure onto the device manufacturers in order to have them prove they're doing a good job at that stack level that nobody's looking at.
Content you might like
-summaries of content
-slide outlines
-abstracts
-citations.
-Beauti.Ai for slide preparation
-Chat GPT 4
-Styluschat
< 1 month9%
2-3 months50%
4-6 months18%
> 6 months24%
Production45%
Backup65%
Replication33%
Non-production DBs (Dev, Training, QA, etc.)30%