> For clean Markdown of this page, append .md to its URL. For the complete documentation index, see https://www.superagent.sh/llms.txt.


Review whether plugins, jobs, and other isolated workloads stay within their assigned permissions.

# Execution sandbox isolation in code


[← Back to attack scenarios](https://www.superagent.sh/docs/products/red-teaming/attack-scenarios)

A plugin or background job may run in an environment with a limited view of the host. This scenario checks whether the code and configuration enforce the intended isolation.

Use it for repositories that run isolated or less trusted workloads. Findings identify the boundary that failed and the kind of host resource or capability the workload could reach.

The app lists this scenario as **Escape a plugin, job, or execution sandbox** (`REPO-12`) in [Repository Red Teaming](https://www.superagent.sh/docs/products/red-teaming/repositories).

## Standards and guidance

[CWE-653 Improper Isolation or Compartmentalization](https://cwe.mitre.org/data/definitions/653.html)

---
Source: https://www.superagent.sh/docs/products/red-teaming/attack-scenarios/repository-sandbox-isolation
Index: https://www.superagent.sh/llms.txt
