Before you start
- An Iru API token with MCP turned on and permissions that cover the calls below (recipe 1).
- Prism categories for FileVault, Application Firewall and Gatekeeper & XProtect cover macOS. Device information covers every platform Prism collects from.
- This pack gathers device data. It doesn't claim to satisfy any compliance framework, so match each field to your auditor's request yourself.
Prompt for your agent
Build me a pre-audit evidence pack from Prism. Pull these four categories, paging with limit and offset until you have every device: GET /api/v1/prism/filevault GET /api/v1/prism/application_firewall GET /api/v1/prism/gatekeeper_and_xprotect GET /api/v1/prism/device_information For each Mac, show me the serial number, key_escrowed, the firewall status, gatekeeper_status, xprotect_version and os_version, plus last_collected_at for each category. Tell me which devices are missing from any category. Stop and wait for my approval before you request any export. After I approve, request exports with POST /api/v1/prism/export for the categories that API accepts, then check each one with GET /api/v1/prism/export/{export_id} until it succeeds and give me the signed_url.
Steps
Pull the four categories
Each call returns up to 300 device records per request. Use
limitandoffsetto page, andblueprint_idsordevice_familiesto narrow the scope.GET/api/v1/prism/filevaultGET/api/v1/prism/application_firewallGET/api/v1/prism/gatekeeper_and_xprotectGET/api/v1/prism/device_informationSource: Prism
Read the evidence fields
FileVault returns
key_escrowed. Application Firewall returnsblock_all_incoming,stealth_mode,loggingandallow_signed_applications. Gatekeeper & XProtect returnsgatekeeper_status,xprotect_versionandmalware_removal_tool_version. Device information returnsos_versionanddisplay_os_version.Every row also carries
last_collected_at, which shows when Prism last collected that data. Keep it in the pack.Source: Iru API: Prism FileVault, Application firewall, Gatekeeper and XProtect, Device information
Request the exports after you approve
The export call takes one category per request. Its documented categories include
device_informationandgatekeeper_and_xprotect, but notfilevaultorapplication_firewall.For FileVault and Application Firewall, save the call results from the previous step, or in the web app open the category in Prism and select Export CSV, choose Current View or All Attributes, then select Start export.
POST/api/v1/prism/exportApproval requiredThe agent lists the exports it plans to request and waits for your go.
Source: Iru API: Request category export
Check each export and download it
An export starts as
pending. Read it back untilstatusissuccess, then download the CSV fromsigned_url.GET/api/v1/prism/export/{export_id}Source: Iru API: Get category export
Check it worked
- Each export reaches
statussuccessand has asigned_url. - Every row in the pack shows a
last_collected_atdate.
Common pitfalls
- FileVault and Gatekeeper & XProtect collect every 15 minutes. Application Firewall collects every 15 minutes or every 24 hours, and Devices collect every 24 hours on Apple platforms. Note the collection time in your pack.
- The FileVault category grays out when you filter Prism to iOS, and Gatekeeper & XProtect is limited to Mac.
- Share the CSV through your normal evidence process.
FAQ
Which Prism calls cover FileVault, firewall, Gatekeeper and OS version?
GET /api/v1/prism/filevault, /application_firewall, /gatekeeper_and_xprotect and /device_information. The first three cover macOS.
Can I export FileVault and firewall data through the API?
The documented export categories don't include them. Save the call results, or use Export CSV on the category in Prism.
How current is the data?
FileVault and Gatekeeper & XProtect collect every 15 minutes. Devices collect every 24 hours on Apple platforms. Each row shows last_collected_at.
Does this pack satisfy a compliance framework?
The recipe gathers device data and makes no compliance claim. Map each field to your auditor's request yourself.