3 ms·
Making a change to secure a site further is fairly invisible: you make the change, and hopefully nothing breaks. If you're the type of company to blog about you
by JoshTriplett 9y ago
Making a change to secure a site further is fairly invisible: you make the change, and hopefully nothing breaks. If you're the type of company to blog about your tech stack, you might make a post on it, but otherwise you just hope nothing goes wrong. And while a major security breach will get you in the news, an army of angry customers will hurt you too.
So, it's not surprising that the features that have gotten the most adoption (like HTTPS itself) are those that show up visibly in browsers, get direct publicity, or unlock access to other things. Features like CSP, while quite useful, don't make the news when you adopt them, and don't unlock any key functionality.
- onion2k 9y agoThat's exactly right and it's a useful lesson. Browser vendors and internet infrastructure engineers need to do more than simply make security tools available - the tools need to be publicised and visible too or they won't be adopted. Sites need to actually break if they're not using necessary security options, or at least show a warning to the user.
- JoshTriplett 9y agoPerhaps, just as browsers have started to take steps to show insecure HTTP as actually insecure, rather than just an absence of security indications, it might make sense to introduce such measures for other features as well. For instance, perhaps browsers could phase in requirements for the most critical security features (e.g. secureonly cookies) to be marked as secure at all, and some of the features (such as CSP) to be marked as EV.