Import Queue¶
Software that arrived from an integration waits here until someone approves it. Nothing goes into your inventory from an integration without passing through this queue.
Products → Import Queue.
Why there is a queue at all¶
An integration reports what it found on a machine. Some of it is software you want tracked, and some of it is noise: a bundled runtime, a vendored library, a one-off tool. Letting all of it in makes the inventory bigger and the findings less useful.
The queue is the place to decide, once, per item.
What each item carries¶
| Field | What it is |
|---|---|
| Vendor and Product | What the integration reported |
| Detected version | The version it found |
| Available versions | Versions published for that software |
| Match confidence | How sure SentriKat is about the software identity it matched |
| Organization | Which organization it would land in |
| Criticality | How important this software is to you |
| Source | Which integration reported it |
Working the queue¶
For each item:
Approve creates the product in your inventory and starts matching findings against it.
Reject discards it. It will come back if the integration reports it again. To stop that, use Exclusions.
Before approving, two fields are worth a look.
The version. You can pick one of the available versions instead of the detected one. Leaving it unset tracks every version, which is what you want when the same software is installed at different versions across machines.
The match confidence. A low number means SentriKat is not sure it matched the right published identity. Approving it anyway means the findings attached to it may belong to different software with a similar name. If the confidence is low, check the identity in CPE Review first.
Statuses¶
| Status | What it means |
|---|---|
| Pending | Waiting for you |
| Approved | In your inventory, with a product created |
| Rejected | Discarded |
| Duplicate | Already in your inventory |
| Error | Could not be processed. The item says why |
Duplicates are marked automatically rather than shown as new work.
Keeping it short¶
A queue nobody empties stops being a queue. Two habits keep it useful:
- clear it after adding a new integration, when it is at its longest
- reject with an exclusion when you know the software will keep being reported, instead of rejecting the same item every week