cartography VS ZeusCloud

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

It’s part of an open source cloud security platform we’re maintaining. Inspired by discussions with folks in the cloud sec community sharing challenges around assessing blast radius, potential lateral movements, and IAM context around alerts they receive.

Just launched an IAM access visualizer that displays access relationships between AWS identities and resources. It’s part of an open source cloud security platform we’re maintaining.

- An interactive access explorer view that shows you how IAM users/roles can access S3 buckets, EC2 instances, etc. for blast radius analysis

We know other cloud security products exist. But, in our experience, they’re often inaccessible or fail to show you sufficient context behind security findings. The project is still early - we’ve focused so far on infra misconfiguration and identity risks. Looking to add vulnerabilities to the attack paths through tools like Project Discovery (nuclei) and Burpsuite next.

Check out our GitHub (Licensed Apache 2.0): https://github.com/Zeus-Labs/ZeusCloud

ZeusCloud is an open-source cloud security platform that thinks like an attacker! It find security risks in your cloud environment, prioritizes them, and helps you remediate them.

(I'm building an open-source CSPM called ZeusCloud. We use SecurityAudit right now. We'll probably add optional permissions for new features like workload analysis.)

- Monitoring compliance - track your PCI DSS, SOC 2, GDPR, CIS goals.

We know there are many cloud security tools out there, but in our experience they are limited in scope (focused on just misconfiguration or identity or vulnerability), provide limited context about risks, or are hard to access.

The project is still early, so we’d love your feedback! So far, we’ve added misconfiguration checks and common identity-based attack paths for AWS. Up next on our roadmap are network/access graph visualizations, vulnerability scanning, and secret scanning!

Check out our GitHub (Licensed Apache 2.0): https://github.com/Zeus-Labs/ZeusCloud

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 for AWS. Up next on our roadmap are network/access graph visualizations, vulnerability scanning, and secret scanning!Check out our GitHub (Licensed Apache 2.0): https://github.com/Zeus-Labs/ZeusCloudPlay around with our Sandbox environment: https://demo.zeuscloud.ioGet Started (free/self-hosted): https://docs.zeuscloud.io/introduction/get-startedHappy to answer any questions and would love any constructive feedback!