We manage security baselines across a device fleet, and each update means manually finding new or obsolete settings and putting our exceptions back. How do you compare versions and carry exceptions forward without checking everything by hand?
How do you make security baseline updates less painful?
Answers
Keep the published baseline untouched and version it separately from your local exceptions. Export each release into a consistent format, commit it to Git, and keep the exceptions in an overlay file. Then a script can compare the old baseline, the new baseline, and your overlay to flag added, removed, and changed settings, along with exceptions that need another look.
Where possible, match settings on a stable identifier such as a CSP path, registry key, or rule ID rather than the display name. Names and grouping can change between releases. The messy part is normalizing the exports first, especially if their formatting isn't consistent.
Reply to this answer
If these are Intune security baseline profiles, check the built-in Update Version option. You can choose to accept baseline changes while keeping existing setting customizations. It creates a copy on the new version, with new settings taking their default values.
That saves some re-entry, but review the new defaults and test the copied profile before wider deployment. Carrying a customization forward doesn't prove it's still needed.
Reply to this answer
Give each exception a reason, an owner, and a review date. Otherwise the comparison may preserve a setting that was only changed to get an old application working and nobody remembers why.
When a baseline changes or removes a setting, flag any exception tied to it for review. That gives someone a specific decision to make instead of just carrying everything forward forever.
_t63+quendavo.8:
A review date alongside the exception sounds useful. The diff tells us what changed, but not whether the old reason still applies.
Reply to this answer
A spreadsheet can be a reasonable starting point if scripting the whole process is too much. Import the baseline settings CSV, give each setting a register entry, and map subsequent releases against it. Blank matches can point you toward new settings, while missing entries need checking for removals or renames.
Keep an eye on inconsistent formatting and renamed settings, though. A spreadsheet can organize the review, but it won't necessarily eliminate it.
Reply to this answer
The source and export format matter a lot. If the published change information is thin, some manual review may still be unavoidable. You could also look at other sources such as CIS Controls or STIGs, but check what they provide and how it can be exported before building your process around them.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Nuvdeli-8m:
Layering the baseline and exceptions can work with GPOs, but don't assume every policy system handles overlapping assignments the same way. Check how conflicts are resolved before deploying the overlay.