crt.sh and Email
Who this is for: anyone checking whether Liitora connects crt.sh and Email, and what a library workflow that does so can access.
Before you start: nothing, to read this page. Each workflow below lists the connections and company variables it needs.
Library workflows that connect them
Section titled “Library workflows that connect them”One library workflow connects crt.sh and Email.
New certificates for your domains
Section titled “New certificates for your domains”Every hour, check crt.sh for new certificates on your domains and alert security, since a new certificate can be a phishing site or shadow IT.
| What | Details |
|---|---|
| Publisher | Liitora (Published by Liitora) |
| Signature | Liitora signs version 1.0.0 and its content hash sha256:f2311d47aaceaa2a333ab35016cd04e980f1e39443808239dfdef23c1d50b7ff, and checks both again before it copies the workflow into your company. |
| Connections | crtsh: Reads crt.sh’s public certificate search. No sign-in.security-chat: Posts a short alert to your chat tool’s incoming webhook. |
| Company variables | company_domains, security_email |
| Secrets | None |
| Sends out | Email, Webhook posts |
| Personal data | None. Certificate records name domains and issuers, not people. |
| Checks | Liitora checked that the connections, company variables, secrets and saved state it declares match what the workflow uses. Its 3 tests pass against the real test runner. |
Read the full trust page of New certificates for your domains.