Launching a job

Red Kite runs its jobs automatically through subscriptions, but you can also run any job on demand. It is useful to:

• re-scan a resource right after a fix, instead of waiting for the next scan;
• run a heavier scan on a single target;
• test a job you are implementing.

Launching a job

1. Go to Automation > Launch.
2. In the right panel, select the Project the results belong to.
3. Pick a job in the Jobs list. Use the search field to find it.
4. Fill the job's parameters in the Input editor. The editor is prefilled with the job's parameters: replace every Change Me value.
5. Click Start.

The Output pane shows the job's logs as it runs. Click Stop to stop it.

For example, to scan the most common ports of a host:

parameters:
  - name: targetIp
    value: 203.0.113.10
  - name: ports
    value: [21, 22, 23, 80, 443, 3389, 8080, 8443]

The parameters of each built-in job are described in Jobs. Parameters can also use secrets, with ${secrets.secretName}.

info

The findings of the job are processed like any other: new resources are created, and the subscriptions may start more jobs from them.

Following the executions

Automation > Executions lists every job execution, manual or automatic, with its project, its start time and its duration. Use the search bar to filter them, for instance job:TcpPortScanningJob.

Queued jobs are hidden by default. Click Show queued jobs as well to see them.

Open an execution to see its details: the number of errors, warnings and findings, and its full logs. A running job can be stopped from the list, with Stop job, or from its details page.

tip

The executions are the best place to understand where a resource comes from: a resource's page links to the job that found it. See Data enrichment.