Blog

Project updates, technical deep dives, and community stories from the Cartography team.

·Alex Chantavy

Mapping production AI agents to IAM roles, tools, and network exposure

Open source Cartography now discovers AI agents in container images and connects them to IAM roles, tools, and network exposure in the infrastructure graph.

Read more →
·Daksh Rathore

Cartography Now Maps Permissions Across All Three Major Clouds: My LFX Mentorship Journey

How I extended Cartography's Resource Permission Relationships feature from AWS to Azure and GCP during my LFX Mentorship, enabling security teams to query 'who can access what' across all three clouds.

Read more →
·Alex Chantavy

Cartography Joins the CNCF

Cartography is now a Cloud Native Computing Foundation Sandbox project.

Read more →
·Alex Chantavy

Container Vuln Management with Minimal Burnout (BSidesSF 2023)

Conference talk at BSides SF 2023 on sustainable container vulnerability management using Cartography.

Read more →
·Alex Chantavy

Cartography: Using Graphs to Improve and Scale Security Decision-Making (CNCF Security Day 2020)

Conference talk at CNCF Security Day 2020 on using graph-based approaches for security at scale.

Read more →
·Alex Chantavy

Vulnerability Management at Lyft: Enforcing the Cascade

How Lyft uses Cartography for vulnerability management at scale.

Read more →
·Marco Lancini

Mapping Moving Clouds: How to Stay on Top of Your Ephemeral Environments with Cartography

A guide to using Cartography to maintain visibility over dynamic cloud environments.

Read more →
·Alex Chantavy

IAM Whatever You Say IAM

Using Cartography to see who has access to what.

Read more →
·Sacha Faust

Cartography: Automating Security Visibility and Democratization (BSides 2019)

Conference talk at BSides SF 2019 on how Cartography automates security visibility.

Read more →
2025 © Cartography Project Authors. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page.