From db9341149ca24113f6a25b72b6c3e3756cc1a2c0 Mon Sep 17 00:00:00 2001 From: rivassec Date: Wed, 9 Sep 2026 18:38:10 -0700 Subject: [PATCH] Shorten IAM-analyzer post summary under 160-char cap --- content/testing-an-iam-analyzer-against-its-own-claims.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/testing-an-iam-analyzer-against-its-own-claims.md b/content/testing-an-iam-analyzer-against-its-own-claims.md index 37d044af..94cd90ed 100644 --- a/content/testing-an-iam-analyzer-against-its-own-claims.md +++ b/content/testing-an-iam-analyzer-against-its-own-claims.md @@ -5,7 +5,7 @@ Category: DevSecOps Tags: aws, iam, security-tooling, testing, devsecops Slug: testing-an-iam-analyzer-against-its-own-claims Og_image: images/og/testing-an-iam-analyzer-against-its-own-claims.png -Summary: I validated my client-side IAM blast-radius analyzer against a published catalog of privilege-escalation methods I did not write, and a harness that attacks its own tests. Twice, a green build hid a wrong answer. +Summary: I checked my IAM blast-radius analyzer against a catalog I did not write and a harness that attacks its own tests. Twice, a green build hid a wrong answer. Cover: images/covers/testing-an-iam-analyzer-against-its-own-claims.png [TOC]