2 ms·
If it ain't broke(1), standard operating procedure is not to fix it. So a lot of corps (and orgs, and individual devs) end up on TLS <1.2 without giving it any
by shadowgovt 5y ago
If it ain't broke(1), standard operating procedure is not to fix it. So a lot of corps (and orgs, and individual devs) end up on TLS <1.2 without giving it any thought.
It can even be hard to reach them... A lot of stuff gets automated, and it takes a level of discipline to avoid routing some of the low-level error messaging to /dev/null (or its spiritual sister, an infolog nobody ever reads) that surprisingly many institutions lack.
(1) Security is extra-hard, because it ain't broke until it's broken into from the point of view of the end user.