@@ -380,6 +380,24 @@ to remediate each of them.
380
380
381
381
The rules that were remediated will show up as *fixed* in the rule result list.
382
382
383
+ === Export remediation role for the selected profile
384
+
385
+ After you select a profile, you can export a remediation role to a file.
386
+ Bash scripts, Ansible playbooks and Puppet manifests are the formats supported.
387
+ The output file will contain all remediations for rules selected by the profile
388
+ that are available.
389
+ As the content of the remediation role solely depends on the profile,
390
+ it is referred to as profile-based remediation role.
391
+
392
+ The possibility to save remediations to a file puts you in charge -
393
+ you can examine it, edit it and decide what remediations to apply.
394
+ However, the result-based remediations export produces output
395
+ that fits your system better.
396
+ See <<view-and-analyze-results>> to learn more about it.
397
+
398
+ Be aware that remediations may not be implemented in all formats.
399
+ The most widely supported formats are bash scripts and Ansible playbooks.
400
+
383
401
=== Evaluate
384
402
385
403
Everything is set up we can now start the evaluation. Click the *Scan*
@@ -424,7 +442,8 @@ which will clear all results.
424
442
425
443
=== View and Analyze Results
426
444
427
- After evaluation finishes, you should see three new buttons: *Clear*, *Save Results* and *Show Report*.
445
+ After evaluation finishes, you should see three new buttons:
446
+ *Clear*, *Save Results*, *Generate remediation role* and *Show Report*.
428
447
429
448
****
430
449
Pressing Clear will *permanently* destroy scan results! This action cannot
@@ -470,6 +489,17 @@ However, ARF files are not as well supported by SCAP toolchains as XCCDF result
470
489
XCCDF result files can be generated from ARF files, this operation is called *ARF splitting*.
471
490
****
472
491
492
+ Opening the *Generate remediation role* pop-up menu will let you to save
493
+ result-based remediations to a file.
494
+ The output file will contain all available remediations for rules
495
+ that have failed the scan, so it should fit your needs better
496
+ than profile-based remediations.
497
+ As the saved content is based on actual scan results,
498
+ it is referred to as results-based remediation role.
499
+
500
+ If you scan with a customized profile, you may encounter an error -
501
+ see <<known-issues>> for a workaround.
502
+
473
503
== Notable shortcuts
474
504
475
505
=== Main Window
@@ -494,6 +524,20 @@ Both while opening the files and when scanning. This option is discouraged and
494
524
should only be used by content creators and/or people who really know what they
495
525
are doing.
496
526
527
+ == Known issues
528
+
529
+ === Result-based remediations of tailored profiles
530
+
531
+ Saving remediation roles to the disk may not work for a customized profile. Specifically, it won't work if you add additional rules to it.
532
+ If this limitation affects you, follow these steps:
533
+
534
+ Remark: You will need to use the oscap command-line utility, which is bundled together with scap-workbench.
535
+
536
+ 1. Save the scan results
537
+ 2. Save your profile customization to a file using the "File->Save customization only" option.
538
+ 3. Run this command: oscap xccdf generate fix --output <role filename> --result-id '' --tailoring-file <saved-customization> <saved-result>.
539
+ Refer to oscap xccdf generate fix -h if you want other than Bash output.
540
+
497
541
== Where to Get Help?
498
542
499
543
You ask for help with the application using
0 commit comments