Jobs

Jobs

Overview

The Jobs page provides a centralized view of all scanning activity happening across your attack surface. In the Praetorian Guard Platform (PGP), a job represents a single scanning capability executing against a specific target — for example, a port scan running against an IP address, a Nuclei vulnerability scan running against a web application, or a web crawler mapping the endpoints of a discovered service.

Jobs are the unit of work behind Guard's continuous security scanning. Every time Guard scans an asset, it creates one or more jobs that execute the appropriate capabilities for that asset type. The Jobs page lets you monitor the progress and outcomes of these jobs in real time. It displays the last 24 hours of scanning activity, giving you a rolling window into recent and active scan operations.

How Jobs Are Created

Jobs are created in two ways:

  • Automated scheduling — Guard's background scheduler continuously creates jobs based on your attack surface. As assets are discovered, the scheduler dispatches the appropriate scanning capabilities against them. The timing and intensity of automated jobs are governed by your scan windows and rate limit settings, configured under Settings > Scan Settings. For more details, see the Scan Windows and Scan Limits articles in the documentation.

  • Manual triggers — You can initiate scans directly from the Assets page by selecting one or more assets and choosing a scan action (such as Comprehensive Scan, Port Scan, Web Scan, or Web Crawl). These manual triggers create jobs that execute immediately, regardless of scan window settings.

The Jobs Table

When you navigate to the Jobs page, you'll see a table displaying all jobs in the system. Each row represents a single job with the following information:

  • Source — The source system or scanner executing the job.

  • Job Name — The scanning capability being run (e.g., portscan, nuclei, crawler, screenshot, fingerprint).

  • Target — The destination IP address, domain, or URL being scanned.

  • Source IP — The IP address of the PGP scanner performing the job.

  • Status — A color-coded icon indicating the current state of the job.

Job Statuses

A job will be in one of four states:

  • Queued — The job is waiting to be dispatched. Jobs enter the queue when scheduled and are dispatched based on your rate limit settings and available scanner capacity.

  • Running — The job is currently executing against its target.

  • Completed — The job has finished successfully. Any findings from the scan are processed and routed to the Vulnerabilities page.

  • Failed — The job encountered an error during execution. Hover over a failed job to see the error details in a tooltip.

Search and Filtering

A search bar at the top of the page lets you find specific jobs. The search works across multiple fields, including job names, DNS entries, and source systems. Results update automatically as you type.

To focus on specific job states, use the Status filter on the left side of the screen. This filter displays the count of jobs in each state, making it easy to spot issues at a glance — for example, a spike in failed jobs.

When jobs fail, the Failed Reasons filter groups similar failures together, helping you identify systemic issues rather than investigating each failure individually.

Job Control

The Jobs page provides two levels of control over scanning activity:

System-Wide Control

At the top of the page, a Pause Jobs button (or Resume Jobs if already paused) controls all automated job scheduling. When you pause jobs:

  • New automated scans will not be created

  • Currently running jobs will complete normally

  • Manual job execution remains available

  • A confirmation dialog will appear before the change takes effect

Individual Job Control

Each job entry includes a refresh icon that allows you to manually re-run that specific job. You cannot re-run a job that is currently running or queued.

Auto-Refresh

The Jobs page automatically refreshes every 15 seconds to keep the displayed information current. When jobs are running normally (not paused), a countdown timer shows when the next scheduled scan cycle will occur, displayed in hours and minutes.

Traffic Attribution

Each job includes identifying information that helps your security operations team distinguish PGP scanning activity from potential threats in your logs:

  • Source IP — The IP address of the PGP scanner performing the job

  • Job Type — The specific capability being used

  • Target — The destination being scanned

PGP scanners also include identifying HTTP headers and user agents in their requests. You can find your unique scan attribution header under Settings > Scan Header. For full details on scan traffic identification and allowlisting, see the Network Traffic Attribution article in the documentation.

Troubleshooting Failed Jobs

When jobs fail, you can:

  1. Hover over the job entry to see the full error message in a tooltip

  2. Use the Failed Reasons filter to find similar failures

  3. Re-run the job manually using the refresh icon if the issue appears temporary

  4. Check the job's target and source information to identify configuration issues

Support

If you encounter issues with the Jobs page or need assistance, contact our support team at support@praetorian.com.