Skip to content

Creating Jobs

The Jobs page is used to create on-demand scan jobs that PII Scanner agents retrieve and execute. A job represents a single request for a specific registered agent to scan a defined file path for selected PII classes and forward any detected matches to a configured target destination.

Understanding scan jobs:

Jobs are the core unit of work in PII Scanner. When a job is created it is saved with a status of Queued. The assigned agent retrieves the job on its next poll cycle, executes the scan, forwards detected PII matches to the configured target in real time, and reports the result back to the server.

Scan results are not stored on the PII Scanner Server — all detected PII matches are forwarded directly and exclusively to the configured target destination as they are found during the scan.

Prerequisites:

Before creating a job confirm the following:

  • At least one PII Scanner Agent is registered and showing as Online in the Clients page
  • At least one target is configured in the Targets page
  • At least one PII class is enabled in the PII Classes page
  • The intended agent has read access to the file path to be scanned

Accessing the Jobs page:

  1. Log in to the PII Scanner Server web interface at https://<server-name>:52766
  2. Navigate to Jobs in the main navigation

Creating a new scan job:

  1. Click Add Job
  2. Configure the job details:

Job Name (required) A descriptive identifier for the scan:

Examples:

Q2 2026 HR File Server Scan

Incident Response — FileServer01 — June 2026

New Share Baseline — Finance Department

Client (required) Select the registered agent that will execute the scan from the dropdown list. The selected agent must:

  • Be currently Online
  • Have read access to the specified scan path

Path to Scan (required) The full path to the directory or file to scan:

Windows examples:

C:SharedDocuments

\fileserver01departmentshr

D:ProjectsLegal

Linux examples:

/mnt/shares/documents

/home/shared/data

/opt/company/archives

Include Extensions (optional) A comma-separated list of file extensions to limit the scan to. Leave blank to scan all file types:

Examples:

*.docx, *.xlsx, *.pdf

*.txt, *.csv, *.log

*.doc, *.xls, *.ppt

PII Classes (required) Select one or more enabled PII classes to detect during the scan. Use the selector to choose from the available enabled classes. The agent applies all selected patterns to every file it scans.

Target Host (required) Select the configured target destination where scan results will be forwarded. Results are sent in real time as matches are found during the scan.

  1. Click Queue Job

The job is saved with a status of Queued and the assigned agent will claim and begin the job on its next poll cycle.

Job statuses:

Once created, a job progresses through the following statuses:

Status Description Badge Color
Queued Job created and waiting for the agent to claim it Gray
Running Agent is actively scanning the specified path Yellow
Succeeded Scan completed successfully Green
Failed Scan encountered an error and did not complete Red

Monitoring job progress:

While a scan is running, monitor its progress from the Jobs page:

  1. Navigate to Jobs
  2. Locate the running job — it will show a status of Running
  3. Review the job details:
Field Description
Job Name The descriptive name assigned at creation
Client The agent executing the scan
Path The directory being scanned
Status Current job state with color-coded badge
Created When the job was created
Started When the agent claimed and began the job
Completed When the scan finished
Records Processed Number of files scanned

Stored job data:

Each job record tracks the following on the server:

  • Selected client
  • Scan path
  • Optional file extensions
  • Selected PII class IDs
  • Target destination ID
  • Payload sent to the agent
  • Result returned from the agent
  • Records processed count
  • Job timestamps

Viewing scan results:

Scan results are forwarded to LT Auditor MP in real time and are not stored on the PII Scanner Server. To view results:

  1. Log in to the LT Auditor MP Web UI
  2. Navigate to View
  3. Select the PII Scanner environment and category
  4. Set the date range to cover the scan period
  5. Filter by source or job name to locate the relevant results
  6. Each result record includes:
    • File path where PII was found
    • PII class that matched
    • Timestamp of detection

Investigating failed jobs:

If a job shows a status of Failed:

  1. Review the result returned from the agent in the job record for error details

Check the agent logs for more specific error information:

Linux:

 cat /opt/bluelance/scanner/scanner.log

 Windows:

 C:Program FilesBlue Lance 2-0LTA_PII_Scanner_Agentlogs

Common failure causes:

Cause Resolution
Agent offline when job was claimed Confirm agent is Online before creating jobs
Agent lacks read access to the scan path Review file system permissions for the agent service account
Network path not accessible Confirm the agent can reach the network share
Target destination unreachable Verify target host connectivity from the PII Scanner Server
No enabled PII classes selected Confirm selected PII classes are still enabled

Best practices:

  • Always confirm the assigned agent is Online before creating a job — a job assigned to an Offline agent will remain Queued indefinitely
  • Use descriptive job names that include the scope, date, and purpose so the jobs list serves as an auditable record of scanning activity
  • Start with focused scans of high-risk directories before expanding coverage to broader file system paths
  • Leave the Include Extensions field blank for incident response scans where maximum coverage is needed
  • Monitor job progress from the Jobs page and begin reviewing results in LT Auditor MP as the scan runs — results are forwarded in real time and do not require the job to complete before they are visible
  • For recurring scans of the same path use the Schedules feature rather than manually creating the same job repeatedly

[Your administrator should document all scan jobs and their results as part of your organization’s data discovery program to support compliance audits.]