Edge types

Source can attach/replace the identity a compute resource runs as, including updating a workflow/orchestration service's execution identity. Also applies to data resources (caches, databases) where an identity is used for encryption or service-to-service auth. Produced both by explicit normalization (attach/assign permissions on target resources) and by derived rules (e.g., CanPassIdentity + CanModifyConfiguration on target).

Source can create a new compute resource bound to target identity (create + pass identity).

Source can deploy new workloads to a platform (then attach identity).

Attacker-controlled code can run with the target identity's privileges. Canonical derived escalation edge.

Source can run OS-level commands on a host/container/managed runtime (agent, run-command, exec, session-pool exec). Notebook targets cover managed notebook instances (Vertex AI Workbench, SageMaker) whose kernels execute arbitrary code as the instance's runtime identity.

Generalized 'can get code running on this resource' (superset of command/deploy/modify).

Source can directly invoke the target (completes an ExecutesAs escalation when code already attacker-controlled or config changed). Messaging sources include service-to-service invocations (API Gateway invoking Lambda, EventBridge invoking Lambda, etc.).

Source can change the executable content a compute resource runs, including orchestration workflows and logic apps that are executable definitions. Produced by explicit normalization (code-update permissions) and by derived rules (supply-chain code-injection paths).

Source can change config (env vars, layers, startup command, identity binding) to gain execution or escalate. Produced by explicit normalization (control-plane config-update permissions) and by derived rules (trigger hijacking, notification redirection).

Source can create a schedule/trigger to drive execution (persistence + trigger creation).

Source can start a stopped resource (needed to realize CONDITIONAL execution edges).

Source can cause the target to execute (event source, schedule). Includes triggering compute workloads and orchestration workflows. AnalyticsService sources cover analytics engines that invoke compute as part of query execution (e.g. an Athena federated query invoking its Lambda data-source connector).

A workload (Compute or Messaging) runs under the target identity. Zero-cost link (a fact, not an action) enabling CanExecuteAs derivations. Includes orchestration workflows, logic apps, and event consumers running as a specified identity.