mirror of
https://github.com/usnistgov/macos_security.git
synced 2026-02-03 14:03:24 +00:00
Generate remediation scripts rather than depend on check script #13
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @RobertHammen on GitHub.
Problem to solve
I want to separate out remediation from detection. So ideally, after Generate Guidance, there would be a scripts folder (alongside jamfpro, mobileconfigs, preferences) that would have the scripts to:
as well as others.
Intended users
For organizations with more granular controls, separating the fix from the check is desirable. Not to mention, I'm currently struggling to get a working/functional copy of the ssh config script, from any of {Excel file, PDF, check script}.
Testing
I can't think of any downside to this, the scripts basically exist (without the shebang, which is a whole other issue where folks assume bash when the scripts are zsh - even the Excel document references "bash" as a keyword, which is confusing).
@rs1278 commented on GitHub:
While this doesn't do exactly what you're requesting, I think your need here will be met with this tool:
https://trusted.jamf.com/docs/establishing-compliance-baselines
You don't need JAMF to use it and it automatically pulls from this git to stay up to date. The tool does have a very useful feature that automatically uploads the script and configuration profiles to JAMF, but you can upload the build assets to any MDM solution.
When you build your baseline, a script is created that is tailored to only the controls you selected. The default run mode of the script is to audit/detect, and it will fix/remediate if you add the
--fixflag.