Tekromancer on Nostr: Found a weird control in AWS Security Hub's CIS Benchmark 3 findings. It reports "IAM ...
Found a weird control in AWS Security Hub's CIS Benchmark 3 findings. It reports "IAM Access Analyzer external access analyzer should be enabled", even if it *is* enabled, but in another account and with organization-wide scope. Support's advice is to disable the control.
Fine. It seems like an edge case (albeit maybe a common one for orgs with multiple accounts). I only mention it here to put it in the back of your mind in case you hit it, too.
Published at
2024-09-04 15:22:52Event JSON
{
"id": "03a824c73a88e5d5ae7608f65aeb0240940adef3e3340daf195b777f4654f566",
"pubkey": "8e62fbcc6147b475c3ee74999ea7bd16176f22e92b3aa86556a91033e24aab33",
"created_at": 1725463372,
"kind": 1,
"tags": [
[
"proxy",
"https://freeradical.zone/users/tek/statuses/113079967612064218",
"activitypub"
]
],
"content": "Found a weird control in AWS Security Hub's CIS Benchmark 3 findings. It reports \"IAM Access Analyzer external access analyzer should be enabled\", even if it *is* enabled, but in another account and with organization-wide scope. Support's advice is to disable the control.\n\nFine. It seems like an edge case (albeit maybe a common one for orgs with multiple accounts). I only mention it here to put it in the back of your mind in case you hit it, too.",
"sig": "cbf5444e5282079d9b9b0400548f41b24ddb7084040bdd0e168d82360ae175b91ba9703524ad2fc0d4373523b59a2c450989a8eec5b3439db3c07e4f5105e87f"
}
