# The Integration of Severity-level Classification and MITRE ATT\&CK Matrix - Cloud

The extensible dataset underpinning the SkyEye framework is foundational to its practical utility, as it systematically maps nearly 20,000 AWS actions to corresponding severity-level classifications and contextual adversarial behaviors. Within SkyEye, the capability to detect, classify, and categorize all AWS actions into risk levels ranging from **Low, Medium, High,** and **Critical**, to those specifically denoted as **PrivEsc-Vector**, represents a pivotal advancement in threat exposure. By mapping each AWS action with relevant **MITRE ATT\&CK tactics, techniques, and sub-techniques**, the framework facilitates granular, multi-dimensional mapping that illuminates how adversaries might exploit specific permissions to achieve objectives such as data exfiltration, persistence within systems, or the sabotage of production workloads. This alignment with the MITRE ATT\&CK cloud matrix not only enhances methodological rigor but also reinforces both automated detection mechanisms and strategic countermeasures by highlighting concrete adversarial behaviors and attack pathways.

<figure><img src="https://2776680781-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTLXx9wiMo4Qlo5PcjRAd%2Fuploads%2FRUEE3A3AmKslBgG8M6eU%2F24.Risk_Level_and_MITRE_ATTACK.svg?alt=media&#x26;token=867e9308-4e6d-4faa-a895-8204e886adfa" alt=""><figcaption><p>The Integration of Severity-level, Abuse Methodology and MITRE ATT&#x26;CK Matrix (Cloud)</p></figcaption></figure>

A noteworthy aspect of this classification is the thoroughness with which abuse methodologies are delineated for each permission. SkyEye framework maps every AWS action to a structured **Abuse Methodology** description, articulating how a threat actor might employ that permission to achieve lateral movement, privilege escalation, or data destruction. For instance, a **High** or **Critical** classification indicates that an AWS action may allow the modification of critical resources or the near-complete takeover of a specific service, while a **PrivEsc-Vector** label flags permissions that could directly elevate user privileges beyond their original scope. These detailed references, accompanied by example commands to illustrate the abuse, offer a practical vantage point for the teams to anticipate potential attack vectors and construct effective attack simulation. Such clarity not only highlights which permissions are of particular concern but also enables penetration testing teams to gain a complete situational awareness regarding the environment, or security teams to devise proactive incident response actions.

The detailed mapping to **MITRE ATT\&CK tactics, techniques, and sub-techniques** ensures that the final IAM enumeration result provided by SkyEye framework, is immediately actionable. By labeling each permission with a Tactic code (e.g., Privilege Escalation), Technique code (e.g., T1078 for Valid Accounts), and sub-technique code (as applicable), cloud security engineers or penetration tester can focus on the most salient threats in the targeting cloud environment. This layered approach proves beneficial during compromise assessments, facilitating the correlation of known adversary techniques with existing permissions. Consequently, the classification system bridges the gap between theoretical knowledge of adversary behaviors and the practical realities of maintaining secure cloud deployments.

From a defensive perspective, this severity-based categorization guides the development of fine-grained access control policies. Security teams can prioritize the remediation of permissions that have been flagged as Critical or PrivEsc-Vector by restricting or removing them. Additionally, this enables more data-driven policy recommendations, where developers and operations staff can gain better awareness of the privileges they request, thereby aligning their environment with the principle of least privilege. Such alignment reduces the overall attack surface by methodically limiting the exposed hooks that malicious actors might try to exploit. When integrated into continuous deployment pipelines, these disciplined guardrails systematically enforce best practices, promoting a robust security posture.

On the other hand, an offensive or red-team perspective leverages the same classification schema for scenario-based testing and vulnerability exploration. By systematically probing permissions labeled as High or Critical or chaining with the identified permissions labeled as Low or Medium, offensive security team can simulate advanced adversary behaviors, thus validating alert mechanisms and identifying real-world paths to privilege escalation. Having explicit example commands to abuse the identified vulnerabilities shortens the feedback loop between reconnaissance and exploitation phases, thereby improving the sophistication and realism of penetration testing exercises. This cyclical process of assessment and remediation ensures that misconfigurations and dangerous permissions are swiftly discovered, cataloged, and neutralized.

In general, this capability systematically categorizes and illustrates each AWS action’s inherent risk, associated MITRE ATT\&CK mapping, Abuse Methodology description, and sample abuse commands marks a cornerstone in modern cloud security. The ability to visualize and quantify risk in such depth fosters a decisive advantage for organizations striving to maintain compliance, harden their assets, and prevent potential adversaries. As cloud environments evolve in complexity, this synergy of detailed enumeration, severity classification, and actionable intelligence empowers both defenders and ethical adversaries to make informed and strategic decisions, ultimately fortifying the resilience and integrity of AWS-based infrastructures.
