[GH-ISSUE #619] Restoring Hardened Operating System to Original State #92

New issue

Open

opened 2026-03-03 14:29:27 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 14:29:27 +03:00

Owner

Originally created by @esnavarro on GitHub (May 27, 2025).
Original GitHub issue: https://github.com/konstruktoid/hardening/issues/619

Originally assigned to: @konstruktoid on GitHub.

Hi Sir konstruktoid,

This is to inquire if there is a supported method or procedure to revert a hardened operating system back to its original, non-hardened state. We are currently evaluating some changes and would like to understand if a rollback or restoration is feasible without a full reinstallation. I apply the hardening procedure to our production environment our system vendor requested if possible the temporary disabling the os lockdown. If such a process exists, we humbly request, could you please provide a necessary steps to remove the hardening?

Originally created by @esnavarro on GitHub (May 27, 2025). Original GitHub issue: https://github.com/konstruktoid/hardening/issues/619 Originally assigned to: @konstruktoid on GitHub. Hi Sir konstruktoid, This is to inquire if there is a supported method or procedure to revert a hardened operating system back to its original, non-hardened state. We are currently evaluating some changes and would like to understand if a rollback or restoration is feasible without a full reinstallation. I apply the hardening procedure to our production environment our system vendor requested if possible the temporary disabling the os lockdown. If such a process exists, we humbly request, could you please provide a necessary steps to remove the hardening?

kerem commented

2026-03-03 14:29:28 +03:00

Author

Owner

@konstruktoid commented on GitHub (May 27, 2025):

Hi @esnavarro, there's no way to rollback the changes made automatically. The code is a non-idempotent shell script mainly used for testing, if you're planning to configure production systems I suggest you use an more suitable solution such as Ansible.

I suggest you contact your system vendor to narrow down which configuration changes are causing issues, and update those settings without requiring an reinstallation.

@konstruktoid commented on GitHub (May 27, 2025): Hi @esnavarro, there's no way to rollback the changes made automatically. The code is a non-idempotent shell script mainly used for testing, if you're planning to configure production systems I suggest you use an more suitable solution such as Ansible. I suggest you contact your system vendor to narrow down which configuration changes are causing issues, and update those settings without requiring an reinstallation.