CAPEC-546: Incomplete Data Deletion in a Multi-Tenant Environment
Attack Pattern ID: 546
An adversary obtains unauthorized information due to insecure or incomplete data deletion in a multi-tenant environment. If a cloud provider fails to completely delete storage and data from former cloud tenants' systems/resources, once these resources are allocated to new, potentially malicious tenants, the latter can probe the provided resources for sensitive information still there.
Likelihood Of Attack
This table shows the other attack patterns and high level categories that are related to this attack pattern. These relationships are defined as ChildOf and ParentOf, and give insight to similar items that may exist at higher and lower levels of abstraction. In addition, relationships such as CanFollow, PeerOf, and CanAlsoBe are defined to show similar attack patterns that the user may want to explore.
Standard Attack Pattern - A standard level attack pattern in CAPEC is focused on a specific methodology or technique used in an attack. It is often seen as a singular piece of a fully executed attack. A standard attack pattern is meant to provide sufficient details to understand the specific technique and how it attempts to accomplish a desired goal. A standard level attack pattern is a specific type of a more abstract meta level attack pattern.
The cloud provider must not assuredly delete part or all of the sensitive data for which they are responsible.The adversary must have the ability to interact with the system.
The adversary requires the ability to traverse directory structure.
This table specifies different individual consequences associated with the attack pattern. The Scope identifies the security property that is violated, while the Impact describes the negative technical impact that arises if an adversary succeeds in their attack. The Likelihood provides information about how likely the specific consequence is expected to be seen relative to the other consequences in the list. For example, there may be high likelihood that a pattern will be used to achieve a certain impact, but a low likelihood that it will be exploited to achieve a different impact.
Cloud providers should completely delete data to render it irrecoverable and inaccessible from any layer and component of infrastructure resources.
Deletion of data should be completed promptly when requested.
A Related Weakness relationship associates a weakness with this attack pattern. Each association implies a weakness that must exist for a given attack to be successful. If multiple weaknesses are associated with the attack pattern, then any of the weaknesses (but not necessarily all) may be present for the attack to be successful. Each related weakness is identified by a CWE identifier.
Sensitive Information Uncleared Before Debug/Power State Transition
Relevant to the ATT&CK taxonomy mapping (see
[REF-461] Kopo M. Ramokapane, Awais Rashid
and Jose M. Such. "Assured Deletion in the Cloud: Requirements, Challenges and Future Directions". Association for Computing Machinery (ACM). Proceedings of the 2016 ACM on Cloud Computing Security Workshop. <https://nms.kcl.ac.uk/jose.such/pubs/Assured_deletion.pdf>.