Skip to content

Persistence

The adversary is trying to maintain their foothold.

Persistence consists of techniques that adversaries use to keep access to systems across restarts, changed credentials, and other interruptions that could cut off their access. Techniques used for persistence include any access, action, or configuration changes that let them maintain their foothold on systems, such as replacing or hijacking legitimate code or adding startup code.

In cloud environments, adversaries persist by creating new IAM users or roles, attaching policies that grant backdoor access, deploying long-lived API keys, or modifying identity federation settings. They may also create resources like Lambda functions or scheduled tasks that maintain their access even if initial credentials are revoked.

View Persistence on MITRE ATT&CK →

AWS PutImage

Pushes a container image to ECR, potentially introducing backdoored images into the deployment pipeline.

Cloud Service: AWS - ECR
Tactics:
Techniques:

AWS PutRule

Creates an EventBridge rule that triggers on specific events, used for persistent execution of Lambda or other targets.

Cloud Service: AWS - EventBridge
Tactics:
Techniques: