Skip to content

Shorten IAM-analyzer post summary under 160-char cap #54

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rivassec merged 1 commit into from
Sep 10, 2026
Merged

Shorten IAM-analyzer post summary under 160-char cap #54

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/testing-an-iam-analyzer-against-its-own-claims.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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]
Expand Down
Loading