Email and Software inventory
Who this is for: anyone checking whether Liitora connects Email and Software inventory, 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 Email and Software inventory.
Known exploited vulnerabilities digest
Section titled “Known exploited vulnerabilities digest”Every weekday morning, match new entries in CISA’s Known Exploited Vulnerabilities catalog against your software inventory and email security a CSV of the matches.
| What | Details |
|---|---|
| Publisher | Liitora (Published by Liitora) |
| Signature | Liitora signs version 1.0.0 and its content hash sha256:4899a9098dc357f08572dc4df797fbc491a8ecae29461c33922fd41c00952a0b, and checks both again before it copies the workflow into your company. |
| Connections | cisa-kev: Reads CISA’s public Known Exploited Vulnerabilities feed. No sign-in.software-inventory: Reads your software inventory. Read-only for this workflow. |
| Company variables | security_email |
| Secrets | None |
| Sends out | |
| Personal data | The name of each matching system’s owner, as your inventory records it. |
| Checks | Liitora checked that the connections, company variables, secrets and saved state it declares match what the workflow uses. Its 4 tests pass against the real test runner. |
Read the full trust page of Known exploited vulnerabilities digest.