From ecd09c7324ae428b2eb2a3d75413b8eb3dfef946 Mon Sep 17 00:00:00 2001 From: Dana Wang Date: Wed, 17 Jul 2024 08:19:21 -0500 Subject: [PATCH] Update process/security_baseline.md Co-authored-by: Marcela Melara Signed-off-by: Dana Wang --- process/security_baseline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process/security_baseline.md b/process/security_baseline.md index 60b18a1a..1a3a9ca1 100644 --- a/process/security_baseline.md +++ b/process/security_baseline.md @@ -55,7 +55,7 @@ To navigate these constraints, the following operating principles are adopted: * **Strong Bias Towards Automation and Automatability** * **Objective**: Enhance security by default and position security as an enabler rather than an inhibitor. * **Approach**: Prioritize automation and automatability to manage dependencies and vulnerabilities more effectively.[[Know, Prevent, Fix](https://security.googleblog.com/2021/02/know-prevent-fix-framework-for-shifting.html)], [[software supply chain transparency logical model](https://github.com/guacsec/guac?tab=readme-ov-file)] - * **Minimal, Achievable, and Practical Baseline Requirements** + * **Minimal, Achievable, and Practical Security Baseline Requirements** * **Objective**: Design a security baseline that balances software reliability, performance, cost, and security. * **Approach**: * Ensure the Security Baseline is minimal and achievable with current technology.