AWS prescriptive-guidance documentation change
Summary
Updated documentation links, added markdown links to backup audit reports and AWS Backup reporting resources, modified section headers to include step numbers and explicit reference to immutable storage
Security assessment
The changes enhance documentation about monitoring/alerting best practices and explicitly reference security controls like immutable storage. While improving security guidance, there's no evidence of addressing a specific vulnerability.
Diff
diff --git a/prescriptive-guidance/latest/security-best-practices/monitor-alert.md b/prescriptive-guidance/latest/security-best-practices/monitor-alert.md index e707b994b..22c1117bf 100644 --- a//prescriptive-guidance/latest/security-best-practices/monitor-alert.md +++ b//prescriptive-guidance/latest/security-best-practices/monitor-alert.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Top 10 security best practices for securing backups in AWS](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Top 10 security best practices for securing backups in AWS](introduction.html) @@ -9 +9 @@ -Backup jobs can fail. A failed job, such as backup, restore, or copy task, might impact on subsequent steps in a process. When the initial backup job fails, there’s a high probability that other succeeding tasks will also fail. In such a scenario, you can best understand the course of events through monitoring and notification. Monitoring and alerting can provide organizational awareness for your backup jobs, which helps you respond to backup failures. +Backup jobs can fail. A failed job, such as backup, restore, or copy task, might impact on subsequent steps in a process. When the initial backup job fails, there's a high probability that other succeeding tasks will also fail. In such a scenario, you can best understand the course of events through monitoring and notification. Monitoring and alerting can provide organizational awareness for your backup jobs, which helps you respond to backup failures. @@ -37 +37 @@ You can implement backup monitoring for your workloads by integrating AWS Backup -You can use AWS Backup Audit Manager to automatically generate evidence of your daily backup audit reports for each account and Region. You can also scale your backup monitoring across multiple accounts by using a set of automation templates and dashboards (known as the backup observer solution) to obtain aggregated daily cross-account multi-Region AWS Backup reporting. +You can use AWS Backup Audit Manager to automatically generate evidence of your daily [backup audit reports](https://docs.aws.amazon.com/aws-backup/latest/devguide/working-with-audit-reports.html) for each account and Region. You can also scale your backup monitoring across multiple accounts by using a set of automation templates and dashboards (known as the backup observer solution) to obtain aggregated daily cross-account multi-Region [AWS Backup reporting](https://aws.amazon.com/blogs/storage/obtain-aggregated-daily-cross-account-multi-region-aws-backup-reporting/). @@ -45 +45 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Safeguard backups +Step 6. Safeguard backups using immutable storage @@ -47 +47 @@ Safeguard backups -Audit backup configuration +Step 8. Audit backup configuration