Given the sanctions against Russia, it seems that CAs are now ceasing issuance for Russian domains and even going so far as to revoke certificates previously issued for Russian domains. Here are some for a Russian bank revoked by Thawte CA: crt.sh/?id=5828347935
This is of course problematic because websites still need certificates and they have to come from somewhere. It seems now that Russia intends to setup a government operated CA. You can download the Root Certificate at the 3rd button here: gosuslugi.ru/tls
The CA was only created 1st March 2022 and is valid for 10 years:
The Root CA doesn't have any name constraints which means it's capable of issuing certificates for any domain that exists, not just Russian domains. This has raised the concern that it could be used to intercept and decrypt the traffic of Russian citizens. pastebin.com/1fxQXTuc
On a technical level, this wouldn't be any different from the efforts by the Kazakhstan government to intercept and decrypt the traffic of citizens in 2019 and again in 2020: blog.mozilla.org/netpolicy/2020…
I'm considering changing the grading criteria on @securityheaders to allow an A+ grade with a CSP that contains unsafe-inline in the style-src directive. What are your thoughts?
This is largely because I've not seen any significant threats posed by inline styles, and, even popular frameworks like Angular require unsafe-inline in the style-src directive: angular.io/guide/security…
I'm tempted to allow the A+ because I don't want it to be unreasonable to achieve the best possible grade. I want the A+ to be the best that site operators can reasonably do to protect themselves and their visitors.
@fastly have been working on building their own Certificate Authority called Certainly. Their request to be included in the Mozilla Root Store was made in Aug last year [1]. Nothing unusual about that, but becoming a new Root CA is a *long* process..
I've you've attended our TLS/PKI Training [2], you'll know all about this process, but it will take a few years before the new Root CA is widely trusted.
The first delay is getting approved by all of the Root Stores operators. The second delay is actually distributing the new Root Certificates to all clients via updates. I've talked extensively about this problem in the past! [3][4][5][6]
It's been a while since I've had chance to sit down and produce a report on the security of the Top 1 Million sites, but thanks to @Venafi's support, the crawler project lives on and a brand new report is out! venafi.com/blog/crawler-r…
It takes a lot of resources to gather this data and a lot of time to analyse it all and write the report, so genuinely, it wouldn't have happened without them. There hasn't been a report for 18+ months so let's take a look at what changed! 😎
HTTPS adoption continues to surge 🔐📈
72% of sites in the Top 1M are now actively redirecting HTTP --> HTTPS 🤩
We're using more HTTPS right now than at any point in history... 😮
I also recall @zeeg once talking about customers on a $50/mo sub wanting custom legal terms / NDAs / security reviews etc... but I can't find the tweet. It'd take us years to recoup the cost of onboarding them.
The latest one today is "Dear Scott, we signed up to your service and now as our supplier your are required to x, y and z". Security questionnaire, supplier questionnaire, NDA, provide various compliance certs if we have them and they need our invoices in a different format 🤷♂️