Skip to content
All recipes

Build a weekly vulnerability report grouped by severity

Pull vulnerability detections, keep the ones from the past week and group them by severity into a short report.

Open in Claude Open in ChatGPT
Product
Vulnerability Management
Platforms
macOS, Windows
Effect
Read-only
Agent access
Iru MCP or the Iru API

Before you start

  • An Iru API token with MCP turned on and permissions that cover the calls below (recipe 1).
  • Macs or Windows devices covered by Vulnerability Management.

Prompt for your agent

Pull my vulnerability detections from Iru with GET /api/v1/vulnerability-management/detections. Keep the detections from the past seven days and group them by severity. For each severity, show how many detections, how many distinct CVEs and how many distinct devices, then list the CVE IDs with their CVSS scores and the names of the affected software. Tell me which field you used for the date and which field you used for severity. Each call returns at most 300 records, so keep following the next cursor until you have read every record, and tell me how many you read.

Steps

  1. Pull the detections

    Each detection carries cve_id, cvss_score, cvss_severity, name, version, device_id, device_name and blueprint_name. A request returns at most 300 records, and the response gives a next link for the following page.

    GET/api/v1/vulnerability-management/detections

    Source: Iru API: List Detections

  2. Keep the past week

    The filter parameter lists detection_datetime as an attribute you can filter on, but the response example shows first_detection_date and latest_detection_date instead. Have the agent name the date field it used, and whether it counted new detections or detections seen again this week.

    Source: Iru API: List Detections

  3. Group by severity

    Have the agent group the detections by cvss_severity. The web app uses the severities Critical, High, Medium and Low, so ask for them in that order.

    To compare the totals with the web app, open the Vulnerabilities page and read the Vulnerabilities by severity card. You can filter the list by First Detected and Severity, then select Export CSV.

    Source: Vulnerability Management

Common pitfalls

  • Devices scan every 15 minutes and matching runs hourly, so a detection from the last hour may not appear yet.
  • Decide whether the report counts detections, CVEs or devices, and ask the agent to say which one it counted.
  • Excluded devices don't count toward affected-device totals in the web app, so check that your agent's totals match.

FAQ

Which API call lists vulnerability detections?

GET /api/v1/vulnerability-management/detections lists detections across the fleet, and each one carries cvss_severity and cvss_score.

Can I filter detections by date in the API?

The filter parameter lists detection_datetime, but the response example shows first_detection_date and latest_detection_date, so the agent names the date field it used.

How many detections does one call return?

At most 300 records. The response gives a next link, so the agent keeps paging until it has read every record.

How often does the detection data refresh?

Devices scan every 15 minutes and matching runs hourly, so allow up to an hour for new detections.

Next steps

Sources

Stay up to date

Iru's bi-weekly collection of articles, videos, and research to keep IT & Security teams ahead of the curve.