CloudGraph cli VS cartography

Looks similar to https://github.com/cloudgraphdev/cli

Honestly, half baked and not very useful at all. If you want an actual single GraphQL based API for ALL of your AWS services, plus CSPM (CIS 1.2, 1.3, 1.4, PCI, and NIST) check out https://github.com/cloudgraphdev/cli. Completely free OSS

https://github.com/cloudgraphdev/cli the GraphQL API for K8s, AWS, GCP, and Azure

Check out https://github.com/cloudgraphdev/cli. It supports a vast majority of AWS services and creates a type-safe GraphQL definition of your entire account

If you are looking for a type-safe asset inventory of your GCP footprint(s) you can check out https://github.com/cloudgraphdev/cli. Along with the asset inventory (which you can query via GraphQL) it will also check for CIS 1.2 compliance failures.

CloudGraph can give you a type-safe asset inventory (plus CIS 1.2 compliance checks) for all of your resources on GCP: https://github.com/cloudgraphdev/cli

Some great suggestions here. I would also suggest running some tool like: https://github.com/cloudgraphdev/cli with the AWS CIS policy pack so you can ensure you are following best practices.

You can use a tool like [CloudGraph](https://github.com/cloudgraphdev/cli) to do this pretty easily.

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