What marking does
Marking an entry has three visible effects. A finding that touches something on your list:- Surfaces sooner and sits higher in the Anomalies queue, so it reaches you before less pressing work.
- Carries a chip that names what is at stake — including PCI, PII, or PHI when you have classified the entry.
- Says so in its written story, calling the item out as on the Sensitivity list.
What it does not do
Marking is weighting, not alerting. Adding an entry raises no new alerts, blocks nothing, and collects nothing new. The same events flow in as before — the list only changes how much they weigh and how prominently their findings appear.Well-known credential locations are always watched, with or without a list.
What you can mark
Five kinds of entry, each with a few ways to match:Login names and exact addresses give the most precise signal; ranges are best for marking a whole network.
Sensitivity level
Each entry has a sensitivity level: how strongly it weighs. A higher level pushes its findings further up the queue and holds them there longer. You choose how much an entry should count — there is nothing to calculate.Classification
A classification names what is at stake, and every finding that touches the entry shows it. A PCI entry makes its findings say PCI; the same holds for PII and PHI.Importing from a spreadsheet
To add many entries at once, import them from an Excel spreadsheet. Map your columns to the fields Hilt expects. Any columns you do not map are kept with the entry for context — they are never used to match. Rows Hilt cannot read are skipped, and each skipped row is reported back to you with the reason.Adding people
When you add a person, Hilt suggests login names it has seen active in your fleet. A name it has not seen is accepted exactly as you typed it and starts matching immediately.Related
- Findings queue → Anomalies
- Read the list from an assistant → MCP server