> ## Documentation Index
> Fetch the complete documentation index at: https://hilt.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Sensitivity list

> Mark the files, destinations, people, and hosts that matter to you, so their findings surface sooner and carry more weight.

The Sensitivity list is where you tell Hilt what matters to you. You supply the judgment — which paths, destinations, people, and hosts are worth extra attention — and Hilt carries that judgment into every finding that touches them.

Find it on [Anomalies](https://hilt.ai/docs/dashboard/anomalies.md) under the **Sensitivity** tab. Maintaining the list requires the **manage alerts** permission.

***

## 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](https://hilt.ai/docs/dashboard/anomalies.md) 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.

> [!NOTE]
>
> 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:

| Kind | What it marks | How it matches |
| - | - | - |
| **Path** | a file or folder | anywhere in a path, an exact file or folder, or by file name |
| **Domain** | a destination by name | that exact domain, or the domain and everything under it (`corp.internal` covers `vault.corp.internal`) |
| **Address** | a destination by number | a single address, or a whole range |
| **Person** | a login name | that login name, exactly |
| **Host** | one machine | that machine, by name |

> [!NOTE]
>
> 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**.

| Classification | Stands for |
| - | - |
| **PCI** | payment card data |
| **PII** | personally identifiable information |
| **PHI** | protected health information |

***

## 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](https://hilt.ai/docs/dashboard/anomalies.md)
* Read the list from an assistant → [MCP server](https://hilt.ai/docs/dashboard/mcp-server.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.