Appearance
Glossary
One name for each object the console shows (DLP-735, DLP-736). A reader who meets two words assumes two objects, and asks which one they are looking at. When a sentence needs a name, it uses the one here.
apps/dashboard/src/copy.test.ts enforces the retired words below in the console's copy. That covers JSX text, the attributes a person reads, and quoted sentences. It does not cover identifiers, API paths or comments, so /api/v1/enrollment-tokens and a component named Corpora keep their names. A new retired word belongs in that test and in this file, together.
| Name | What it is | Retired words |
|---|---|---|
| Endpoint | A computer running the MyDLP agent, enrolled in this organisation. The Endpoints destination lists them. | "device" for this object, in the Endpoints destination (DLP-768) |
| Device | Removable media - a USB stick, an external disk - as Device control approves or refuses it. | |
| Enrol, enrolment | Joining an endpoint to the organisation with an enrolment token. British spelling, as behaviour and organisation are; enrolled and enrolling are spelt the same either way. The agent's command is dlp-agent enroll --token, typed as shown. | enroll, enrollment |
| Classification | The area where detectors, classifications, exact data and document fingerprints are defined, and a single classification within it. | Data classification |
| Fingerprint set | A named, versioned set of documents whose fingerprints endpoints match against. The page is Document fingerprints. | corpus, corpora |
| Test set | The labelled documents a detector's quality is measured against. Not a fingerprint set: "corpus" named both, which is why it is retired. | corpus |
| Scan | One execution of discovery against one location. A repeating scan is a series of scans. Remediation's run is a plan's, a different object. | run (in Discovery) |
| Incident delivery | Where incidents are forwarded: a SIEM, a webhook, a tracker. One target is an incident destination. | integration(s), in copy |
| Report destination | Where a scheduled report is delivered. Separate from incident destinations by design: a report destination never receives the incident feed. | |
| Behaviour analysis | The Analytics page of what the organisation's data activity looks like. | |
| Named individuals | The Settings panel that decides whether that analysis may name a person, with the basis recorded. | "Behaviour analysis" as this panel's label |
| Repeats | Incidents grouped because the same person, endpoint or policy keeps producing them, at two scales: repeats within minutes (the strip above the queue) and repeats over days (the grouped view). ADR-0055. | burst |
| Related | Incidents a person linked, suggestions offered with a reason, and recurrences of a closed incident, on the record. | |
| Events | The operations inside one incident, listed on its Events tab. | correlated events |
The storage keys a browser keeps (mydlp.devices.*), the ?device= address parameter and the CSV's column keys still say "device": they are names code and saved preferences depend on, not copy, and renaming a storage key would silently reset every saved layout.