updating the screenshots to use the right component (updating example…

…s to be based off of most recent GPOS SRG Signed-off-by: Will <will@dower.dev>
mitre · Nov 15, 2024 · 23deaa1 · 23deaa1
1 parent d6072fd
commit 23deaa1
Show file tree

Hide file tree

Showing 10 changed files with 9 additions and 8 deletions.
diff --git a/src/assets/img/component_metadata.png b/src/assets/img/component_metadata.png
diff --git a/src/assets/img/component_view.png b/src/assets/img/component_view.png
diff --git a/src/assets/img/create_component.png b/src/assets/img/create_component.png
diff --git a/src/assets/img/created_component.png b/src/assets/img/created_component.png
diff --git a/src/assets/img/members_view.png b/src/assets/img/members_view.png
diff --git a/src/assets/img/open_component.png b/src/assets/img/open_component.png
diff --git a/src/assets/img/start_new_project_filled_out.png b/src/assets/img/start_new_project_filled_out.png
diff --git a/src/courses/guidance/05.md b/src/courses/guidance/05.md
@@ -44,6 +44,8 @@ Click it and begin to fill out the details for our project. You can make the Tit
 
 3. When you are finished, click Create Project. You'll be taken to the Project view for the workspace you just created, which is currently empty. We should fix that.
 
+
+
 ### 5.1.4 Role-Based Access Control
 
 Before we create a Component, though, let's configure Role-Based Access Control (RBAC).
@@ -64,6 +66,9 @@ Write and approve changes to a Control.
 ::: details Admin
 Full control of a Project or Component. Lock Controls, revert controls, and manage members. You'll note that the Project's creator is automatically an admin.
 :::
+
+![Members View](../../assets/img/members_view.png)
+
 ::: tip Adding Colleagues
 If you have any colleagues taking the class with you, you may want to add them as a reviewer now (note that you can only add members to a project if they have registered to the Vulcan instance already).
 :::

diff --git a/src/courses/guidance/06.md b/src/courses/guidance/06.md
@@ -90,10 +90,6 @@ On the right-hand side of the Vulcan window, if we don't have a requirement sele
 
 ![Component Metadata](../../assets/img/component_metadata.png)
 
-We can edit the metadata for the entire component here, or even add links or other tags as part of the Component Additional Questions section.
-
-![Adding Component Questions](../../assets/img/add_questions_modal.png)
-
 6. On the left side of the page, scroll down to the section titled "All Controls". These are all of the requirements in the SRG we selected earlier.
 
 The left-hand side of the Vulcan window shows us the list of each requirement in the Component, and can be filtered by keyword, control status (which we will discuss in the next section) or review status. Note that each control is labeled with the STIG ID prefix that you gave this Component earlier. You can click on the requirement IDs in this view to see their contents.

diff --git a/src/courses/guidance/07.md b/src/courses/guidance/07.md
@@ -35,7 +35,7 @@ You'll see a view of the requirement's text fields, like the vulnerability discu
 ![An Unedited Requirement](@/../../../assets/img/selected_control.png)
 
 Note how all of these text fields are:
-- Pre-populated with the underlying SRG data for the general requirement (in this case SRG-OS-000004-GPOS-00004)
+- Pre-populated with the underlying SRG data for the general requirement (in this case SRG-OS-000366-GPOS-00153)
 - Grayed-out and uneditable at present.
 
 We can't edit these text fields yet because we haven't yet told Vulcan if this requirement is even applicable to our Component. Let's fix that.
@@ -88,7 +88,7 @@ flowchart TB
 ```
 
 ### 7.3.2 Our First Requirement Status
-3. Let's pick a status for RHEL-09-000003. We will do this by reading the SRG requirement and determining if it applies to this particular component, and if so, if it is an innate feature of the system or not.
+3. Let's pick a status for RHEL-09-000130. We will do this by reading the SRG requirement and determining if it applies to this particular component, and if so, if it is an innate feature of the system or not.
 
 The requirement's title is *"The operating system must audit all account creations."*
 
@@ -108,7 +108,7 @@ We would consider this requirement **Applicable - Configurable.** The system is
 
 4. Based on our decision, let's edit the status field in the Component editing screen.
 ::: details Changing status
-![Updating the Status on RHEL-09-000003](@/../../../assets/img/assigning_status.png)
+![Updating the Status on RHEL-09-000130](@/../../../assets/img/assigning_status.png)
 
 Hint: Most SRG requirements wind up being applicable to Components. A handful may be either Not Applicable, Inherently Met or Inherently Not Met. We still have to check.
 :::
@@ -119,7 +119,7 @@ Before we do that, let's investigate a the Status field a bit more.
 
 ### 7.3.3 Another Requirement Status
 
-5. Let's skip ahead and pick an example with a different status. On the sidebar, click on RHEL-09-000045.
+5. Let's double back and pick an example with a different status. On the sidebar, click on RHEL-09-000045.
 
 ![RHEL-09-000045](@/../../../assets/img/inherently_met_control.png)