Skip to content
QCecuring

Sensors

Sensors

Section titled “Sensors”

The Sensors page manages your deployed sensor instances, their scanner assignments, and scan run history.

hidden Sensors page showing registered sensors with status and last scan time

Sensor Registration

Section titled “Sensor Registration”

Sensors are registered in the platform when they first push data to the API. Each sensor is identified by its API key.

To register a new sensor:

  1. Navigate to Sensors → Add Sensor
  2. Provide a name and description
  3. Generate an API key
  4. Use the API key in your sensor config file
# Use the generated API key in your sensor config
apiUrl: http://your-api-host:9090
apiKey: generated-api-key-here

Sensor List

Section titled “Sensor List”

The sensor table shows:

ColumnDescription
NameSensor identifier
StatusOnline/Offline (based on recent activity)
Scanner TypeWhat scanner is assigned
Last ScanTimestamp of most recent scan run
Assets FoundTotal assets discovered by this sensor

Scanner Assignments

Section titled “Scanner Assignments”

Assign scanner configurations to sensors from the UI. This defines what each sensor scans when triggered.

hidden Scanner assignment dialog showing scanner type selection and configuration

Available scanner types:

  • HTTPS Endpoint Scanner
  • File System Scanner
  • SSH Key Scanner
  • Windows Certificate Store Scanner
  • Source Code Scanner
  • Binary Scanner
  • AWS Scanner
  • Active Directory / LDAP Scanner

Scan Runs

Section titled “Scan Runs”

View the history of all scan executions:

ColumnDescription
SensorWhich sensor ran the scan
Scanner TypeType of scanner used
StartedScan start timestamp
DurationHow long the scan took
StatusSuccess, Failed, or Running
Assets FoundNumber of assets discovered in this run

Click a scan run to see the detailed results — which assets were discovered, updated, or newly found.

hidden Scan run detail showing discovered assets and scan metadata

Triggering Scans

Section titled “Triggering Scans”

Scans can be triggered in multiple ways:

  1. Manual — Click “Run Scan” on a sensor from the UI
  2. CLI — Run the sensor JAR with a config file
  3. Scheduled — Configure scan schedules in Alerts & Schedules
  4. Cron — External scheduler (cron, Task Scheduler) running the sensor JAR

API Key Management

Section titled “API Key Management”

Each sensor authenticates with the API using an API key sent in the request header. Keys can be:

  • Generated from the Sensors page
  • Rotated (generate new, update sensor config, revoke old)
  • Revoked (immediately blocks the sensor from pushing data)
Section titled “Related”