Kinnaird McQuade

https://o365blog.com/aadkillchain/

https://github.com/Cloud-Architekt/AzureAD-Attack-Defense

https://six2dez.gitbook.io/pentest-book/enumeration/cloud/azure

Probably start with the people from this list: https://link.medium.com/RLzHl2HxDbb

Build failed due to missing data folder at root directory

2

Hi, I found a fix for this but unfortunately I don't have time to pull/modify/push etc., so I figured I would put it here so you can make the quick...

I've avoided conditions this far to avoid complication and I think that was the right decision. But it would make sense to make an exception for a few specific cases...

It's pretty unnecessary to include that in the package itself and the git history.

skip-resource-constraints does not hold precedence over other fields

2

If I specify an s3 object path under `write` and then specify `s3:PutObject` under `skip-resource-constraints`, then I get an IndexError. Example template: ```yaml mode: crud write: - 'arn:aws:s3:::mybucket*/*' skip-resource-constraints: -...

API output schema should be consistent but that's not the case for query/actions `query action-table --service s3 --name GetObject` returns a dictionary: ``` {"s3": [{"action": "s3:GetObject", "description": "Grants permission to...

## What does this PR do? * Updates Python dependencies