From f3dc1cdc37ae0121bf2dcf1b54a31d23720e4e92 Mon Sep 17 00:00:00 2001 From: Christian Cleberg Date: Sat, 21 Feb 2026 22:03:56 -0600 Subject: add image to latest post (#12) * update post title * add screenshot to auditing-aws-passwords post --- content/blog/2026-02-21-auditing-aws-passwords.org | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'content/blog/2026-02-21-auditing-aws-passwords.org') diff --git a/content/blog/2026-02-21-auditing-aws-passwords.org b/content/blog/2026-02-21-auditing-aws-passwords.org index 95778cb..503fc4a 100644 --- a/content/blog/2026-02-21-auditing-aws-passwords.org +++ b/content/blog/2026-02-21-auditing-aws-passwords.org @@ -98,6 +98,10 @@ The metadata block is what ties this evidence to a specific account and point in time. The ~aws_caller_identity~ field shows who ran the script and in which account. +#+caption: Policy Evaluation Results +#+attr_html: :alt Terminal output of evaluate_policy.py showing the interactive prompts and pass/fail summary for each password policy rule. +[[https://img.cleberg.net/blog/20260221-auditing-aws-password-policy/results.webp]] + * Step 2: Evaluate the Policy Pass the JSON file to the evaluation script: -- cgit v1.2.3