Skip to main content
Solved

CIS L1 Baseline - Jamf Compliance Editor - Login Window Policy Issue

  • March 6, 2025
  • 3 replies
  • 69 views

RDowson
Forum|alt.badge.img+9

When I deploy the CIS L1 baseline via JCE I'm having an issue with the following:

9.16. Configure Login Window to Show A Custom Message.

When I change the default text from "Center for Internet Security Test Message" to anything else, I get a compliance failure. How do I change this message to something more relevant without it flagging up as a compliance fail?

 

Best answer by patrickj

The compliance script that runs via policy is what determines if a device is compliant. The login window text is hardcoded into the compliance script as a base64 encoded string. If you want the compliance script to show compliant for your updated string you need to update the script. I believe if you use the Jamf Compliance Editor and update the value there it is supposed to automatically update it but you could update the script yourself if needed (or if it failed for some reason).

 

You would be looking for this section in the script: 

You would want to update roughly 8 instances of the current value in that section. For example: 

 

 

3 replies

Shyamsundar
Forum|alt.badge.img+13
  • Jamf Heroes
  • March 6, 2025

I too have this issue, As i don't have much time to dig into it, i have added this in the exception. 


patrickj
Forum|alt.badge.img+10
  • Contributor
  • Answer
  • March 6, 2025

The compliance script that runs via policy is what determines if a device is compliant. The login window text is hardcoded into the compliance script as a base64 encoded string. If you want the compliance script to show compliant for your updated string you need to update the script. I believe if you use the Jamf Compliance Editor and update the value there it is supposed to automatically update it but you could update the script yourself if needed (or if it failed for some reason).

 

You would be looking for this section in the script: 

You would want to update roughly 8 instances of the current value in that section. For example: 

 

 


RDowson
Forum|alt.badge.img+9
  • Author
  • Contributor
  • March 7, 2025

The compliance script that runs via policy is what determines if a device is compliant. The login window text is hardcoded into the compliance script as a base64 encoded string. If you want the compliance script to show compliant for your updated string you need to update the script. I believe if you use the Jamf Compliance Editor and update the value there it is supposed to automatically update it but you could update the script yourself if needed (or if it failed for some reason).

 

You would be looking for this section in the script: 

You would want to update roughly 8 instances of the current value in that section. For example: 

 

 


Thanks. I've updated the profile and uploaded the script to Jamf again. That seems to have got it working.