Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions docs/books/disa_stig/disa_stig_part2.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,9 +66,9 @@ And will output an HTML report:

## Generating Remediation Bash Scripts

Next we will generate a scan, and then use the results of the scan to generate a bash script to remediate the system based on the DISA stig profile. I do not recommend using automatic remediation, you should always review the changes before actually running them.
Next, we will generate a scan, and then use the results of the scan to generate a bash script to remediate the system based on the DISA stig profile. I do not recommend using automatic remediation, you should always review the changes before actually running them.

1) Generate an scan on the system:
1) Generate a scan on the system:
```
sudo oscap xccdf eval --results disa-stig-scan.xml --profile stig /usr/share/xml/scap/ssg/content/ssg-rl8-ds.xml
```
Expand All @@ -89,7 +89,7 @@ The resulting script will include all the changes it would make the system.

You can also generate remediation actions in ansible playbook format. Let's repeat the section above, but this time with ansible output:

1) Generate an scan on the system:
1) Generate a scan on the system:
```
sudo oscap xccdf eval --results disa-stig-scan.xml --profile stig /usr/share/xml/scap/ssg/content/ssg-rl8-ds.xml
```
Expand All @@ -106,7 +106,7 @@ You can also generate remediation actions in ansible playbook format. Let's repe

## About The Author

Scott Shinn is the CTO for Atomicorp, and part of the Rocky Linux Security team. He has been involved with federal information systems a
t the White House, Department of Defense, and Intelligence Community since 1995. Part of that was creating STIG’s and the requirement th
at you use them and I am so very sorry about that.
Scott Shinn is the CTO for Atomicorp, and part of the Rocky Linux Security team. He has been involved with federal information systems at
the White House, Department of Defense, and Intelligence Community since 1995. Part of that was creating STIG’s and the requirement
that you use them and I am so very sorry about that.