Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cyberstrikeus/T1613_container-and-resource-discovery
Adversaries may attempt to discover containers and other resources that are available within a containers environment.
Passed 15 of 22 test cases with the skill, and 8 of 22 without it.
and 6 more in the full report
7 fixed8 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
In the Docker container and resource discovery test script, what tag is assigned to the container image when built from the Atomic Red Team source?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies t1613 as the container image tag. | Missed | Passed |
The instructions your model reads when the skill loads.
Adversaries may attempt to discover containers and other resources that are available within a containers environment. Other resources may include images, deployments, pods, nodes, and other information such as the status of a cluster.
These resources can be viewed within web applications such as the Kubernetes dashboard or can be queried via the Docker and Kubernetes APIs. In Docker, logs may leak information about the environment, such as the environment’s configuration, which services are available, and what cloud provider the victim may be utilizing. The discovery of these resources may inform an adversary’s next steps in the environment, such as how to perform lateral movement and which methods to utilize for execution.
Platforms: Containers
The following tests are from Atomic Red Team and provide actionable ways to test this technique:
Adversaries may attempt to discover containers and other resources that are available within a containers environment.
Supported Platforms: containers
docker build -t t1613 $PathtoAtomicsFolder/T1613/src/
docker run --name t1613_container --rm -d -t t1613
docker ps
docker stats --no-stream
docker inspect $(docker ps -l -q --filter ancestor=t1613)
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.