PDQ adds ticketing integrations, macOS vulnerability management and APIs

PDQ rolled out new features aimed at helping IT teams close support tickets faster and manage endpoint risk across Windows and macOS. The release adds Zendesk, ServiceNow and Halo integrations, expands vulnerability management to Mac devices, and introduces APIs for connected workflows.

Why it matters: - IT teams can now move device data, remediation actions, and vulnerability information across support and security workflows with fewer manual steps. - The update is designed to cut time spent switching tools, reduce targeting errors, and speed up ticket resolution. - Mixed Windows and macOS environments now have a more unified path for vulnerability management and reporting.

What happened: - PDQ announced new ticketing integrations with Zendesk, ServiceNow, and Halo. - The company extended its vulnerability management workflow to macOS. - PDQ introduced APIs for custom fields, vulnerability data, and deployment statuses. - The release also added several endpoint management updates, including macOS process visibility, bulk vulnerability ignoring, group-scoped reports, adjustable lookback windows, and CSV-based group creation.

The details: - The new ticketing integrations join existing PDQ connections with Jira, Freshservice, and Freshdesk. - Authorized technicians can view a requester’s device details inside the ticket, deploy software, open the device in PDQ, or launch remote access. - PDQ says the ticketing integrations are available to Premium customers. - The macOS vulnerability workflow lets admins view vulnerable software, inspect affected devices, and deploy available fixes from the same interface used for Windows. - CVE details now show whether a vulnerability affects Windows, macOS, or both. - When a supported macOS Package Library package is available, teams can use PDQ remediation recommendations and deployment workflows to address vulnerable third-party applications. - A single deployment can remediate supported applications across both Windows and macOS devices. - Existing vulnerability management functions, including automation, role-based access controls, audit logs, and reporting, also apply to macOS. - The Custom Fields API lets external systems read and update device metadata stored in PDQ. - Teams can use that API to sync ownership, business context, email addresses, and asset data from configuration management databases, asset platforms, directories, and internal systems. - The Vulnerabilities API lets teams pull vulnerability data into reporting, ticketing, compliance, security, and automation workflows. - The Deployment Status API exposes deployment success and failure data for tracking, reporting, and follow-up actions. - PDQ said all three APIs will also be available through its Zapier integration. - The macOS Processes tab lets admins view running processes on individual Mac devices directly in PDQ. - Bulk vulnerability ignoring lets teams dismiss multiple vulnerabilities at once. - Group-scoped vulnerability reports let admins narrow reports to selected device groups for specific teams, departments, customers, or business units. - CSV group creation lets admins build device groups from CSV data.

Between the lines: - The release pushes PDQ further toward a single operational layer for endpoint management, support, and security. - By exposing more data through APIs, PDQ is making it easier for customers to connect the platform to broader automation and reporting systems. - The macOS expansion suggests PDQ is trying to serve organizations that no longer run a Windows-only fleet.

What's next: - Premium customers can begin using the new ticketing integrations and APIs as they are rolled out. - IT teams using macOS devices can now apply the same vulnerability workflows already available on Windows. - PDQ’s Zapier support for the new APIs should give teams another path to automate endpoint workflows without building custom integrations.

The bottom line: - PDQ is betting that tighter ticketing links, cross-platform vulnerability management, and more open APIs will make endpoint operations faster and less fragmented.