From 67beb4e8c46e5e5c0e31cdfb0ad55476d19e9af4 Mon Sep 17 00:00:00 2001 From: Tomasz Mikulski Date: Tue, 12 Sep 2023 17:37:15 +0200 Subject: [PATCH] Fix broken http link to presentation - use https (#4405) --- src/data/best-practices/aws/content/security-audit.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/data/best-practices/aws/content/security-audit.md b/src/data/best-practices/aws/content/security-audit.md index 4163ee0b2..41aa738c8 100644 --- a/src/data/best-practices/aws/content/security-audit.md +++ b/src/data/best-practices/aws/content/security-audit.md @@ -2,4 +2,4 @@ > Set up automated security auditing. -It's important to keep track of changes in your infrastructure's security settings. One way to do this is to first set up a security auditer role ([JSON template](https://gist.github.com/bigsnarfdude/d0758b4fd335085623be)), which will give anyone assigned that role read-only access to any security related settings on your account. You can then use this rather [fantastic Python script](https://gist.github.com/jlevy/cce1b44fc24f94599d0a4b3e613cc15d), which will go over all the items in your account and produce a canonical output showing your configuration. You set up a cronjob somewhere to run this script, and compare its output to the output from the previous run. Any differences will show you exactly what has been changed in your security configuration. It's useful to set this up and just have it email you the diff of any changes. (Source: Intrusion Detection in the Cloud - [Presentation](http://awsmedia.s3.amazonaws.com/SEC402.pdf)) +It's important to keep track of changes in your infrastructure's security settings. One way to do this is to first set up a security auditer role ([JSON template](https://gist.github.com/bigsnarfdude/d0758b4fd335085623be)), which will give anyone assigned that role read-only access to any security related settings on your account. You can then use this rather [fantastic Python script](https://gist.github.com/jlevy/cce1b44fc24f94599d0a4b3e613cc15d), which will go over all the items in your account and produce a canonical output showing your configuration. You set up a cronjob somewhere to run this script, and compare its output to the output from the previous run. Any differences will show you exactly what has been changed in your security configuration. It's useful to set this up and just have it email you the diff of any changes. (Source: Intrusion Detection in the Cloud - [Presentation](https://awsmedia.s3.amazonaws.com/SEC402.pdf))