ScoutSuite VS cartography

Prowler and ScoutSuite are a good start for cloud stuff.

Another solution might be ScoutSuite, they have support for all major clouds - aws,gcp and azure. But its probably not maintained as well. ScoutSuite

If you're planning to use Active Directory and/or Azure AD, run ADRecon/AzureADRecon and Bloodhound frequently and review in depth. Run ScoutSuite frequently and review as part of a normal operational cycle (e.g., at weekly team meetings make the results available and set aside 15 minutes to discuss and make assignments). Look critically at where these three tools overlap within two or three degrees of separation from your jump hosts (e.g., hosts/nodes that are one or two devices away and users/security groups that are one or two devices away) for help prioritizing when you have too many high-risk/high-impact items to look through.

https://github.com/nccgroup/ScoutSuite (I used it for GCP one time, but I can't say if it good for AWS)

I'd take a look at ScoutSuite. It runs on your infra and spits back a remarkably readable report.

If you could get a read-only (audit?) account you could use ScoutSuite to pull the accounts and review them: https://github.com/nccgroup/ScoutSuite

ScoutSuite – Multi-Cloud Security Auditing Tool

Cartography (Python application) will get you part of the way there, in that it will discover the state of the environment, record node information and relationships in a graph database, and can be easily extended. You can also then easily write queries about the relationships of various resources to answer questions like “what can I reach from VPC X”. Drawing diagrams though is very hard to do well without extra input.

Build an asset inventory of the cloud environment. (using an OSS project called cartography)

The project is still early, so we’d love your feedback! We’ve based our cloud asset inventory on another great OSS project called cartography. So far, we’ve added misconfiguration checks and common identity-based attack paths. Up next on our roadmap are network/access graph visualizations, vulnerability scanning, and secret scanning!

The first step involved in threat modelling is to build an architecture diagram of the system you are protecting. This also involves building a list of assets in the system. You cannot protect something which you don’t have visibility over. We can use tools such as CloudMapper from the previous step for building an architecture diagram of an AWS cloud environment. There are similar tools for threat modeling for other cloud service providers like Cartography.

Lyft made a tool called Cartography, which scrapes your AWS Account(s) and inserts representations of many of your cloud resources into a Neo4j (graph) database. This makes it easy to query and discover how things are connected in your account.

Recently, we at Cloudanix made open source contributions to the Cartography project by Lyft. We contributed to the pre-existing AWS module by adding support for KMS and API gateway. Since the Cartography project did not have support for Microsoft Azure, we started from scratch to add that capability to Cartography. We added support for Azure services like CosmosDB, SQL, Storage, and Virtual Machines.

[2] https://github.com/lyft/cartography