You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 27, 2024. It is now read-only.
Installed SCAP-Workbench on MacOS and Windows platforms and in both cases, I loaded different content and the next window only shows the list of rules and you can customize them, and then a big "SCAN" button on the bottom left but nothing where it gives me the ability to export remediation role for the selected profile.
Export remediation role for the selected profile
After you select a profile, you can export a remediation role to a file. Bash scripts, Ansible playbooks and Puppet manifests are the formats supported. The output file will contain all remediations for rules selected by the profile that are available. As the content of the remediation role solely depends on the profile, it is referred to as profile-based remediation role.
The possibility to save remediations to a file puts you in charge - you can examine it, edit it and decide what remediations to apply. However, the result-based remediations export produces output that fits your system better. See [view-and-analyze-results] to learn more about it.
Be aware that remediations may not be implemented in all formats. The most widely supported formats are bash scripts and Ansible playbooks.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Installed SCAP-Workbench on MacOS and Windows platforms and in both cases, I loaded different content and the next window only shows the list of rules and you can customize them, and then a big "SCAN" button on the bottom left but nothing where it gives me the ability to export remediation role for the selected profile.
The documentation from here states:
The text was updated successfully, but these errors were encountered: