List declared in-scope PCI assets.

Args: asset_type: ALL, IP, DNS, or VIRTUALHOST.

This is declared scope -- configuration, not observation. It says nothing about whether a host responded to a scan.

Per-host PCI Pass/Fail status. The primary way to iterate hostnames.

Args: offset: 1-based record offset. 0 is invalid. limit: Rows per page, 1-1000. dns: Filter to a single hostname. compliance_status: Filter by "Pass" or "Fail". fetch_all: Walk every page rather than returning one.

There is deliberately no ip filter: Qualys ignores the documented spelling and no working one has been confirmed, so an ip argument would appear to narrow the results while returning every row.

Returns total_count so growth in scope is always visible.

List vulnerability findings as compact rows.

Args: offset: 1-based record offset. limit: Rows per page, 1-1000. ip: Filter by IP, CIDR, or range. dns: Filter by hostname. qid: Filter by Qualys ID. title: Keyword search on the finding title. severity: Any of CONFIRMED_HIGH, CONFIRMED_MED, CONFIRMED_LOW, POTENTIAL_HIGH, POTENTIAL_MED, POTENTIAL_LOW. false_positive: Any of Requested, Rejected, Expired. pci_fail_vulns: True to return only findings that fail PCI. fetch_all: Walk every page rather than returning one.

Prose fields are deliberately absent; call pci_get_vuln for one finding's threat, impact, and solution text.

Full detail for one vulnerability finding, including prose fields.

Args: detection_id: The finding's id from pci_list_vulns -- not its qid.

List PCI scans, newest first.

Args: offset: 1-based record offset. limit: Rows per page, 1-1000.

Detail for one scan.

Args: scan_id: The scan's scan_id from pci_list_scans.

active_hosts is an aggregate count. The API exposes no per-host alive/dead breakdown, so none is reported.

Download a scan's report PDF and return the path it was saved to.

Args: scan_id: The scan's scan_id from pci_list_scans.

PDF is the only format Qualys offers here. The bytes are written to disk and only a path is returned -- a PDF is not usable as tool output.

A 404 is the normal case, not a failure. Reports must be generated in the Qualys console first, and generation is a write operation this server does not perform. A 404 means only "no report has been generated for this scan yet". It does not mean the scan is missing, and it is not a compliance finding -- do not report it as one.