As I understand it, Certificate Transparancy provides proof to the client that the presented certificate is publicly accessible in CT logs. The certificate being in the logs enables a domain owner to detect that a certificate has been issued for its domain that was not requested by him, which would be worrying.
The domain owner can then exchange a few harsh words with the certificate authority to get the malicious certificates revoked and possibly understand what is going on. If executed perfectly, this can bring down malicious certificates in hours/days instead of months/never - so far so good.
My question is, how is a domain owner expected to check for certificates issued for the domain it owns in practice?
I understand that it is theoretically possible to do so, but I don't believe many domain owners actively monitor CT logs?
Are domain owners supposed to periodically review the certificates issued to their domain? Are there tools available to get a notification when a certificate linked to a given domain is added to the logs?
In small to medium sized business I simply don't expect this to be a topic on the radar of the IT/security teams. In very large organisations, I would expect it would be hard to centrally monitor this as many departments may be able to request (legitimate) certificates for the websites/apps they manage for the business.
But without the domain owners monitoring the CT logs, anyone that can coerce a CA to issue a illegit certificate could also sign it in a CT log without being noticed – which would make the whole system pointless.