You record which firewalls, servers and network devices your company runs. CyberTell reports when a vulnerability becomes known for one of them or the vendor stops delivering updates.
Inventory of the systems in use with vendor, product and version from the catalogue of the CVE database. Daily match against the CVE list (cvelistV5) and CISA KEV with version comparison: affected, please check or possibly affected. Findings with severity from KEV and CVSS, fixed version and status workflow; bundled notification by email and push from a selectable threshold, optionally as a ticket. End of support per release branch from endoflife.date or your own entry, with advance warning 180, 90 and 30 days ahead. Inventory suggestions from the device inventory, the attack surface and connected firewalls. Applications from one or more dependency files (requirements.txt, package.json, pom.xml, go.mod, Cargo.lock and more) with per-package matching via OSV.dev (PyPI, npm, Maven, Go, crates.io, Packagist, RubyGems, NuGet) and per-file updates when a file is re-read; Dockerfile and docker-compose.yml contribute the container images as catalogue products.
Use it forLearn in time which of your systems needs an update.
Use it forVulnerability and lifecycle monitoring of your own infrastructure without tracking vendor advisories yourself.
ID.AM-2Produce an inventory of all of the software platforms/licences and applications within your organisation.ID.RA-1Identify the (technical) vulnerabilities of your assets, and document them.ID.RA-2Share intelligence regularly in fora and other bodies to stay up to date about cybersecurity threats.RS.AN-5Processes are established to receive, analyze and respond to vulnerabilities disclosed to the organization from internal and external sources (e.g. internal testing, security bulletins, or security researchers).