A collection of native security controls for major cloud platforms mapped to MITRE ATT&CK techniques to enable threat-informed defense decisions.
Security Stack Mappings is a collection of structured data that maps native security controls of major cloud platforms to adversary techniques in the MITRE ATT&CK® framework. It helps organizations understand which built-in security capabilities are most effective against specific threats, enabling threat-informed defense decisions. The project provides mappings for Azure, AWS, and GCP with standardized methodology and tools.
Security professionals, cloud architects, and threat intelligence analysts working with Azure, AWS, or GCP who need to understand how native security controls mitigate specific ATT&CK techniques.
It provides vendor-agnostic, standardized mappings that enable data-driven security decisions, unlike platform-specific documentation. The open methodology and tools allow organizations to extend mappings consistently.
🚨ATTENTION🚨 The Security Stack Mappings have migrated to the Center’s Mappings Explorer project. See README below. This repository is kept here as an archive.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides standardized mappings for Azure, AWS, and GCP native security controls, enabling cross-platform comparisons. The README includes dedicated HTML summaries and YAML files for each cloud provider.
Includes pre-built ATT&CK Navigator layers for visual exploration of control mappings, as listed in the platform-specific directories. This facilitates intuitive threat visualization without manual setup.
Offers a documented methodology and scoring rubric for consistent mappings, detailed in the docs folder. This encourages community contributions and ensures reproducible, vendor-agnostic assessments.
Uses a defined YAML format for mapping files, ensuring consistency and interoperability. The mapping data format specification allows for easy parsing and integration into security tools.
Mappings are based on outdated ATT&CK releases (e.g., Azure on v8.2, AWS on v9.0), and the README admits a follow-on project is needed for updates. This limits relevance against emerging threats.
Scoping decisions explicitly omit third-party security controls available on cloud platforms, as noted in each platform's section. This reduces utility for hybrid security environments.
Requires familiarity with ATT&CK, cloud security concepts, and Python for tool usage, making it less accessible. The methodology docs assume prior knowledge, and setup isn't plug-and-play.