For SOC analysts and IT teams
Check what you run against today's exploited list, in the chat
Print a list of the important software on a machine, paste it into the Lattice Analyst, and read which of today's CISA entries may concern it. Nothing is sent until you paste.
4 minute read
The three steps
- Install lattice-scan on the machine: from the signed apt repository or from PyPI (the commands are in the guide on choosing a channel). The inventory block is in version 0.4.8 and later.
- Run `lattice-scan inventory --share`. It reads the machine and prints one block of the important software: the kernel, what listens on the network and which package owns it, the images and snaps, and the main server software. It is read only and sends nothing anywhere.
- Open the Lattice Analyst, choose My products, paste the whole block and save it, or paste it straight into the chat. Checking it needs the free account.
lattice-scan inventory --share # the block, ready to copy
lattice-scan inventory --share --no-feed # without asking the CISA list which items to include
lattice-scan inventory --share --max-lines 120
lattice-scan posture # what the machine exposes: ports, firewall, SSH, servicesWhat the Analyst does with it
- It reads the block, and also a raw `dpkg -l`, `rpm -qa`, `pip freeze`, `npm ls -g`, `snap list` or `docker images` listing, and says what it read and how old the inventory is.
- It compares each item with today's, this week's and the still-open CISA entries using the same name matching as the command line, and lists the matches by CISA's due date. A match is a lead for you to check, not a finding.
- For a match it reads the CVE's own record and says whether your version is inside a range the record lists, outside it, or could not be compared.
- When you ask whether a CVE concerns you, the saved inventory travels with that one question and is used the same way. It is kept in your browser only, up to 8 KB, and is written to no log.
Read the answer with these limits in mind
- No match is not proof of absence: it covers only what you pasted, and the block holds the important software, not every package.
- A Linux distribution can fix a flaw and keep the same version number. Read the package's changelog and the vendor's notice before you decide.
- A due date is CISA's deadline for US federal agencies. For everyone else it is a signal of priority.
- The posture output is a set of signals for a person to read. Each can be harmless, and a normal user cannot read firewall rules, so run it as root for that part.
Then ask
Paste `lattice-scan posture` to read what the machine exposes and what to check next. Ask about any CVE in the answer for the first-response analysis. The inventory block is described field by field in the lattice-scan repository.
Where to go next
- The IT check — Reference material tells you what is known. The check tells you where your own estate stands.
- IT and security for small firms — The service behind the reference layer: someone who looks after your own estate.
- OCO, the cyber graph behind this — Lattice serves public knowledge. OCO is the product that works on a real estate.
- Get a Lattice trial key — read the beta terms first.