Skip to main content

We continue in our efforts to streamline compliance benchmarks workflows and unify the reporting. Today, we are proud to announce two new highly demanded exports within the Compliance capability in Jamf Pro - something you have been asking for since the initial launch of Compliance in April.

  1. Auditing documentation: Holding the benchmark settings as configured by the admin, this set of documents is aimed to serve for compliance audits purposes. Those of you already using Jamf Compliance Editor or mSCP are familiar with these - now the adoc, pdf, html, and xlsx documents for each supported OS version are available right under Compliance Configuration tab in Jamf Pro.
  2. Compliance status: After enabling the computer-level compliance reporting in July, you can now export the overall compliance status, i.e. number of passing and failing computers for each rule in a benchmark, into csv file - very similar to the one produced by Compliance baselines in Jamf Protect. With this export, you can report compliance against a configured benchmark regularly and keep historical records of adopting compliance over your fleet.

Both new exporting capabilities are available now in supported Jamf Pro instances (11.18 is required for compliance reporting).

Additional note based on feedback from Tony Young:

Should you observe missing mSCP revision in the generated auditing documents (appears as unspecified on the title PDF page), please check your benchmark which most likely shows Update Available. If you go to Rules, you will see changes that happened since your last update - check (and modify) them, save the draft, and deploy the benchmark. Once you get the auditing documents again, the revision will appear as expected.


Reply