Security Compliance Management known issues

These are the known issues for the Security Compliance Management (SCM) 1.x, 2.x, and 3.x releases.

Incompatibility with stdlib v9.0 and v9.1

Puppet Security Compliance Management is not compatible with stdlib versions 9.0 and 9.1.

Reports export null data when custom profile filter is applied

Exported reports are empty if a custom profile has been selected on the Profiles quick filter.

Running scan tasks in Puppet Enterprise (PE)

Security Compliance Management uses Puppet Enterprise tasks to run compliance scans on nodes. Although you can see the scan tasks in Puppet Enterprise, we advise against running these tasks from Puppet Enterprise because this practice can have unforeseen effects on both Puppet Enterprise and Security Compliance Management. Instead, run all CIS scans from Security Compliance Management. You can view the scan results in both products.

Was this page helpful?

We’re sorry to hear that!
Please tell us why so we can help. Enter your feedback and email. This form is sent to the Puppet docs team. We ask for your email as we might contact you regarding your feedback. If you need help with the product itself, visit Puppet Support or ask in Puppet Community on Slack. Feedback:

Email Address:

To learn about how Puppet uses your personal information, visit our privacy policy.

If you leave us your email, we may contact you regarding your feedback. For more information on how Puppet uses your personal information, see our privacy policy.

See an issue? Please file a JIRA ticket in our [DOCUMENTATION] project.