Skip to main content
Solved

Compliance setting cannot be changed

  • January 28, 2025
  • 5 replies
  • 5 views

n_lecchi
Forum|alt.badge.img+15

Once established, it is no longer possible to change any configuration of the compliance set. It would be nice to have the ability to change it.

Best answer by JanVozenilek85

I would change the timeout of Enforce Screen Saver from 20 (1200 sec) to 3 minutes.


I see, thank you for the details. We do for sure plan to introduce customising Organization defined values (ODVs) during both benchmark creation and afterwards before we launch the capability into full production.

5 replies

JanVozenilek85
Forum|alt.badge.img+9

Absolutely! What specifically would you be changing in your case?


n_lecchi
Forum|alt.badge.img+15
  • Author
  • Contributor
  • January 29, 2025

I would change the timeout of Enforce Screen Saver from 20 (1200 sec) to 3 minutes.


JanVozenilek85
Forum|alt.badge.img+9

I would change the timeout of Enforce Screen Saver from 20 (1200 sec) to 3 minutes.


I see, thank you for the details. We do for sure plan to introduce customising Organization defined values (ODVs) during both benchmark creation and afterwards before we launch the capability into full production.


dan-snelson
Forum|alt.badge.img+30
  • Honored Contributor
  • January 29, 2025

Absolutely! What specifically would you be changing in your case?


I just edited the "CIS Level 2 (Monitor and Enforce) - Sequoia com.apple.loginwindow" Configuration Profile `LoginwindowText` from "Center for Internet Security Test Message" to something more appropriate for our organization.


JanVozenilek85
Forum|alt.badge.img+9

I just edited the "CIS Level 2 (Monitor and Enforce) - Sequoia com.apple.loginwindow" Configuration Profile `LoginwindowText` from "Center for Internet Security Test Message" to something more appropriate for our organization.


Sure, manually editing the specific configuration profile is an option - just be aware that such changes are not propagated back into the Compliance module and will be lost with next update of your benchmark (e.g. when you edit it in the future and the objects get re-generated).