Zdx Audit Software Inventory

zdx_list_software()```text
**Filter by location:**
```textzdx_list_software(location_id=["<location_id>"])```text
**Filter by department:**
```textzdx_list_software(department_id=["<department_id>"])```text
**Filter by geolocation:**
```textzdx_list_software(geo_id=["<geo_id>"])```text
**Filter by specific users:**
```textzdx_list_software(user_ids=["<user_id_1>", "<user_id_2>"])```text
**Filter by specific devices:**
```textzdx_list_software(device_ids=["<device_id_1>", "<device_id_2>"])```text
**Combine filters for targeted audits:**
```textzdx_list_software(  location_id=["<location_id>"],  department_id=["<department_id>"])```text
---
### Step 2: Get Software Version Details
For a specific software package, get detailed version distribution and device breakdown.
```textzdx_get_software_details(software_key="<software_name_and_version>")```text
**Filter by scope:**
```textzdx_get_software_details(  software_key="Google Chrome 120.0.6099.130",  location_id=["<location_id>"])```text
```textzdx_get_software_details(  software_key="Microsoft Teams",  department_id=["<department_id>"])```text
---
### Step 3: Cross-Reference with Device Data
For specific devices of interest, get full device details.
```textzdx_get_device(device_id="<device_id>")```text
To find devices owned by a specific user:
```textzdx_list_devices(emails=["[email protected]"])```text
To find devices in a specific location:
```textzdx_list_devices(location_id=["<location_id>"])```text
---
### Step 4: Present Audit Report
Assemble the `__ZDX_DATA__` payload defined in the *Data Payload Contract* and render it through `./templates/report.html.template` (see the **HTML OUTPUT** section). The template already produces the inventory table, KPI cards, compliance percentages, color coding, search/sort, and CSV export — do **not** hand-author any HTML or markdown table here.
What you DO write is the `analysis` block inside the payload. **Do not skip it.** This is what makes the audit useful:
- **`analysis.summary`** (3–5 sentences): the fleet's compliance posture. Cite the ratio of up-to-date vs. outdated software. Call out patterns (e.g., "Outdated Chrome is concentrated in APAC offices, suggesting MDM policy gaps in that region"). Quote actual counts from the `kpis` block.- **`analysis.rootCause`** (1–3 sentences per EOL / vulnerable group): explain the risk concretely (e.g., "Java 8 is end-of-life with 200+ known CVEs. The 12 devices running it are exposed to remote code execution vulnerabilities").- **`analysis.remediation`** (4–6 items): label each with a priority bucket and a concrete action.
| Priority | Apply to | Action ||---|---|---|| `Immediate` | EOL software | Immediate upgrade plan. Identify device owners, schedule maintenance windows, push updates via MDM. || `Investigate` | Vulnerable versions | Cross-reference with known CVEs. Prioritize devices in sensitive departments (Finance, Engineering). || `Monitor` | One version behind | Schedule automated updates via MDM or software distribution tools. || `Communicate` | Borderline current versions | Confirm auto-update policies are in place; report status to security/compliance. |
---
## Common Audit Scenarios
### Security Vulnerability Assessment
When a CVE is announced for a specific software version:
1. List software inventory filtered by the affected software name2. Get details to identify exact versions installed3. Cross-reference affected versions with CVE data4. List impacted devices by location and department
```textExample: CVE-2024-XXXXX affects Chrome < 120.0.6099.130
zdx_list_software()→ Find "Google Chrome" entries
zdx_get_software_details(software_key="Google Chrome 119.0.6045.199")→ Identify all devices running the vulnerable version
Report:  Vulnerable Devices: 45  Locations: Tokyo (25), Singapore (20)  Priority: HIGH - Immediate patch required```text
### Patch Rollout Progress
Track how a software update is rolling out across the organization:
1. List software and find the old and new versions2. Compare device counts between versions3. Filter by location to identify offices lagging behind
```textPatch Rollout: Chrome 120.0.6099.130  Deployed: 312 devices (87.4%)  Pending: 45 devices (12.6%)    By Location:    San Jose: 100% deployed    New York: 100% deployed    London: 95% deployed    Tokyo: 72% deployed ← lagging    Singapore: 68% deployed ← lagging```text
### Department-Specific Audit
For compliance requirements specific to a department:
```textzdx_list_software(department_id=["<finance_dept_id>"])```text
Useful for auditing regulated departments (Finance, Healthcare, Legal) that may have specific software requirements.
### License Compliance
Count software installations to verify license compliance:
```textzdx_list_software()→ Count installations of licensed software
Example:  Adobe Acrobat Pro: 142 devices installed  Licensed seats: 150  Remaining: 8 seats available```text
---
## Edge Cases
### No Software Data Available
```textNo software inventory data available for the specified filters.
Possible causes:- ZDX agent version doesn't support software inventory- Software inventory collection is not enabled- The filtered scope (location/department) has no active devices
Action: Verify ZDX software inventory is enabled in the admin portal.```text
### Large Inventory
If the software list is very long:
- Focus on key categories: browsers, security tools, collaboration apps, runtimes- Filter by location or department to narrow scope- Prioritize EOL or outdated versions
---
## Quick Reference
**Primary workflow:** List Software → Filter by Scope → Get Version Details → Cross-Reference Devices → Report
**Tools used:**
- `zdx_list_software()` -- organization-wide inventory- `zdx_list_software(location_id, department_id, ...)` -- filtered inventory- `zdx_get_software_details(software_key)` -- version details for a package- `zdx_list_devices(emails, location_id, ...)` -- find specific devices- `zdx_get_device(device_id)` -- device details
**Filter options (available on both list and details):**
- `location_id` -- ZDX location IDs- `department_id` -- department IDs- `geo_id` -- geolocation IDs- `user_ids` -- specific user IDs- `device_ids` -- specific device IDs
**Related skills:**
- [Troubleshoot User Experience](../troubleshoot-user-experience/) -- if software issues affect user experience- [Analyze Application Health](../analyze-application-health/) -- if outdated software correlates with poor app scores