AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb link, fixed apostrophe formatting in employee misuse example, and changed section title to 'Increasing adoption in related fields'
Security assessment
Minor editorial changes to existing security examples (incident response/monitoring). No new security vulnerabilities or features are introduced or documented.
Diff
diff --git a/prescriptive-guidance/latest/strategy-cybersecurity-positive-risk/examples.md b/prescriptive-guidance/latest/strategy-cybersecurity-positive-risk/examples.md index 38ee645ae..90148d727 100644 --- a//prescriptive-guidance/latest/strategy-cybersecurity-positive-risk/examples.md +++ b//prescriptive-guidance/latest/strategy-cybersecurity-positive-risk/examples.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Positive risk within cybersecurity](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Positive risk within cybersecurity](introduction.html) @@ -58 +58 @@ Another example of positive risk in cybersecurity is the implementation of incid - 2. Increased network traffic could lead to detecting employee misuse of resources by accessing content that isn’t work-related, such as music and video streaming services. These activities consume network bandwidth and can negatively impact network and application performance. + 2. Increased network traffic could lead to detecting employee misuse of resources by accessing content that isn't work-related, such as music and video streaming services. These activities consume network bandwidth and can negatively impact network and application performance. @@ -84 +84 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Increasing adoption +Increasing adoption in related fields