Vineet Tiruvadi, MD, PhD on Nostr: npub19d9p0…kf02p curious why you say that? eg it's not always baked in, but plenty ...
npub19d9p04u4xfysdy92fycw947jrca3xve2gnsauysshzewxvmz8dms6kf02p (npub19d9…f02p) curious why you say that?
eg it's not always baked in, but plenty of startups use Docker + have SOC2/more rigorous security compliance. They/we handeled security updates pretty seamlessly.
And sometimes containerization can make sometime more secure by forcing more systems thinking and disincentivizing holes - it's never timeless, but it makes the effort-to-maintain at a fixed level of security less.
I am assuming you're not making a security-through-obscurity argument, which more eloquent folks have addressed: https://www.okta.com/identity-101/security-through-obscurity/
To be clear, I see maintainance and security as independent processes that are often linked, but not identically the same, so a bit unclear of the shift.
eg it's not always baked in, but plenty of startups use Docker + have SOC2/more rigorous security compliance. They/we handeled security updates pretty seamlessly.
And sometimes containerization can make sometime more secure by forcing more systems thinking and disincentivizing holes - it's never timeless, but it makes the effort-to-maintain at a fixed level of security less.
I am assuming you're not making a security-through-obscurity argument, which more eloquent folks have addressed: https://www.okta.com/identity-101/security-through-obscurity/
To be clear, I see maintainance and security as independent processes that are often linked, but not identically the same, so a bit unclear of the shift.