diff --git a/src/courses/delta/02.md b/src/courses/delta/02.md index 83d63d375..ab2b3d388 100644 --- a/src/courses/delta/02.md +++ b/src/courses/delta/02.md @@ -9,10 +9,10 @@ author: Daniel Medina, George Dias To conduct the delta process, the following items are needed: -1. An InSpec profile +1. An InSpec profile: a. Clone or download an existing profile from a repository source to your local environment. b. See [What is an InSpec Profile](../beginner/02.md#what-is-an-inspec-profile) for additional information. -2. A guidance file (XCCDF) +2. A guidance file (XCCDF): a. Download either a DISA STIG or a CIS Benchmark from the appropriate site. ::: note Using Generated Profile Stubs diff --git a/src/courses/delta/03.md b/src/courses/delta/03.md index e50705798..939d01a0e 100644 --- a/src/courses/delta/03.md +++ b/src/courses/delta/03.md @@ -60,7 +60,6 @@ The `delta` process extends the capabilities of the `update_controls4delta` proc b - For controls which a match is found, the describe block (code) within the old control is mapped over to the new control 3. Detailed logging a - report file (.md), mapping statistics (CliProcessOutput.log) -
You can invoke the command as such: @@ -68,8 +67,6 @@ You can invoke the command as such: saf generate delta -X ./baseline_Y_xccdf_guidance_file.xml -J baseline_X_summary.json -o new_baseline_Y_controls_directory -M -c baseline_X_controls_directory ``` -
- ::: tip Optional Fuzzy Matching Flags The `-M` and `-c` flags can be removed if not using fuzzy matching feature. ::: diff --git a/src/courses/delta/06.md b/src/courses/delta/06.md index c74b8cafc..b1cabe291 100644 --- a/src/courses/delta/06.md +++ b/src/courses/delta/06.md @@ -185,8 +185,6 @@ The current available commands for testing are: bundle exec rake pre_commit_checks # Ensure the controls are ready to be committed into the repo ``` -
- :::note Profile Controls Formatting In the past, `cookstyle` format was used. However, support for `cookstyle` formatted profiles is limited and is geared more towards Chef cookbooks. Profile controls are written in ruby code, hence `rubocop` is preferred. :::