whx
/
killchain-compendium
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

typos

This commit is contained in:
gurkenhabicht 2024-02-08 23:10:46 +01:00
parent b92573666f
commit 5be2a146ef
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Enumeration/AWS.md
View File

@ -56,7 +56,7 @@ If the ACL is set to
Permissions are granted directly through user accounts or indirectly through
roles the user has joined.
<img src="./include/iam-intro-users-and-groups.diagram.png" alt="Policy evaluation" width="100%" height="auto">
<img src="./include/iam-intro-users-and-groups.diagram.png" alt="Policy evaluation" width="auto" height="auto">
Gaining access to important roles like maintenance opens the door to higher permissions.
An always unique AWS Account ID has a length of 12 digits.
@ -91,7 +91,7 @@ Policy evaluation can be found in the [AWS docs](https://docs.aws.amazon.com/IAM
The following graph is taken from the documentation, it shows the evaluation
logic inside an account
<img src="./include/PolicyEvaluationHorizontal111621.png" alt="Policy evaluation" width="100%" height="auto">
<img src="./include/PolicyEvaluationHorizontal111621.png" alt="Policy evaluation" width="80%" height="auto">
Policies like `assume-role` and `switch-role` can lead to the gain of roles
with higher permissions