3 ms·
> It’s obviously concerning that a CA would have such a long-running issue and that they would be unable to assess its scope after being alerted to it and condu
by nailer 11y ago
> It’s obviously concerning that a CA would have such a long-running issue and that they would be unable to assess its scope after being alerted to it and conducting an audit. Therefore we are firstly going to require that as of June 1st, 2016, all certificates issued by Symantec itself will be required to support Certificate Transparency.
Symantec said they did an audit, Google spent 'a few minutes' and found many more mississued certificates just from the CT logs. In other words, Symantec can't audit themselves, so Google now require public issuance logs for all their certificates.
> [Google] expect Symantec to undergo a Point-in-time Readiness Assessment and a third-party security audit.
This is a massive (and justifiable) smack in the face to Symantec.
Disclaimer: we're a Symantec competitor, as you may have realised:
https://certsimple.com/blog/seal-in-search https://certsimple.com/blog/seal-in-search
https://certsimple.com/blog/sgc-ssl-certificates https://certsimple.com/blog/sgc-ssl-certificates
- sarciszewski 11y agoYes, and a very well-deserved one.
- Sir_Cmpwn 11y agoWhat is a "Point-in-time Readiness Assessment"? I googled it and found it in the requirements for some CAs, but not what it actually is.
- thenewwazoo 11y ago"Point-in-time" is a term of art for audit. It basically means that a third party will attest to a given state at a given time. They're in contrast to "continuous" audits, which is more focused on auditing records over a period of time, or on a recurring basis. A "point-in-time readiness assessment" is kind of redundant, but it basically means getting a third party to come look at their CA (processes, procedures, standards, implementation) and assert on Symantec's behalf that it meets some criteria.
- Sir_Cmpwn 11y agoThanks for clarifying.