Data quality issues. #18

Closed
opened 2026-01-19 18:28:56 +00:00 by michael · 1 comment
Owner

Originally created by @WmJHarrison on GitHub.

os_information_validation.yaml:

mobileconfig value is “false” which is not consistent with a null value for all others.

icloud_calendar_disable.yaml:

check contains escape character for new line in the heredoc which is causing conversion to json to fail.

Consider changing osascript from using heredoc to -e statements.

Originally created by @WmJHarrison on GitHub. os_information_validation.yaml: mobileconfig value is “false” which is not consistent with a null value for all others. icloud_calendar_disable.yaml: check contains escape character for new line in the heredoc which is causing conversion to json to fail. Consider changing osascript from using heredoc to -e statements.
Author
Owner

@brodjieski commented on GitHub:

Good afternoon!

for the mobileconfig: key in the rule files, allowed values are either "true" or "false". This indicates if the rule has any settings that can be applied with a configuration profile. Looking through the rule files, there are no rules that have a null value for this key.

The escape character is used in the check: field for all of the rules we have that evaluate managed preferences. This is supported in shell to facilitate multi line commands. We decided to use this syntax for better readability in the generated PDF, as well as to support more complex checks that involve additional logic to evaluate. While the majority of the commands could be shifted away from heredoc, some would remain. There are no immediate plans to move every check away from using heredoc syntax.

@brodjieski commented on GitHub: Good afternoon! for the `mobileconfig:` key in the rule files, allowed values are either "true" or "false". This indicates if the rule has any settings that can be applied with a configuration profile. Looking through the rule files, there are no rules that have a null value for this key. The escape character is used in the check: field for all of the rules we have that evaluate managed preferences. This is supported in shell to facilitate multi line commands. We decided to use this syntax for better readability in the generated PDF, as well as to support more complex checks that involve additional logic to evaluate. While the majority of the commands could be shifted away from heredoc, some would remain. There are no immediate plans to move every check away from using heredoc syntax.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: usnistgov/macos_security#18