From ebf007fee1a3cee29f65bc6a7a064dc0050579da Mon Sep 17 00:00:00 2001 From: Shivani Karikar Date: Mon, 9 Dec 2024 00:11:10 -0500 Subject: [PATCH] User 2 - Duplicate graphic removed Signed-off-by: Shivani Karikar --- src/courses/user/02.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/courses/user/02.md b/src/courses/user/02.md index 05e9adbcd..277a0c715 100644 --- a/src/courses/user/02.md +++ b/src/courses/user/02.md @@ -35,5 +35,3 @@ headerDepth: 3 As illustrated in the picture below, the process for developing automated security tests starts with requirements documents like SRGs, STIGs, or CIS Benchmarks, which are written in human-readable language. These documents are then implemented as code. We need that code to record test results in a standardized format so that we can easily export our security data to a platform where it can be used to make informed decisions (such as the Heimdall visualization app). This challenge is what the [MITRE Security Automation Framework](https://saf.mitre.org) (MITRE SAF) was developed to address. It simplifies the journey from a Requirement Document to an automated test profile and back again, making it easier to navigate. - -![The SAF Lifecycle](../../assets/img/saf-lifecycle.jpg)