AWS prescriptive-guidance documentation change
Summary
Updated author attribution format and corrected quotation mark styling
Security assessment
Changes are stylistic/formatting updates with no security content modifications. The Checkov scanning context remains unchanged regarding security implications.
Diff
diff --git a/prescriptive-guidance/latest/patterns/centralized-custom-checkov-scanning.md b/prescriptive-guidance/latest/patterns/centralized-custom-checkov-scanning.md index 8fd07821a..24d279ef3 100644 --- a//prescriptive-guidance/latest/patterns/centralized-custom-checkov-scanning.md +++ b//prescriptive-guidance/latest/patterns/centralized-custom-checkov-scanning.md @@ -9 +9 @@ SummaryPrerequisites and limitationsArchitectureToolsBest practicesEpicsRelated - _Created by Benjamin Morris (AWS)_ + _Benjamin Morris, Amazon Web Services_ @@ -158 +158 @@ Checkov scanning provides useful information about potential security misconfigu -There are several ways to address this problem, including better messaging about the long-term value of security scanning and clearer documentation about how to deploy secure infrastructure. These are important “soft” approaches to DevSecOps collaboration that can be seen as the solution to this problem’s root cause. However, you can also use technical controls such as a `CODEOWNERS` file as guardrails to help keep developers on the right path. +There are several ways to address this problem, including better messaging about the long-term value of security scanning and clearer documentation about how to deploy secure infrastructure. These are important "soft" approaches to DevSecOps collaboration that can be seen as the solution to this problem’s root cause. However, you can also use technical controls such as a `CODEOWNERS` file as guardrails to help keep developers on the right path.