CI/CD Attack Surface Lab
Investigate the relationship between source repositories, automated workflows, credentials, and cloud infrastructure.
Objective
Understand the security assumptions represented by this environment and develop an evidence-based explanation of how they can fail.
Scenario
You are investigating a fictional environment where an apparently ordinary workflow has created an unexpected security condition. Your task is to understand the path, not merely reach a predetermined answer.
Environment
Starting Information
You begin with the environment description, basic access appropriate to the scenario, and the artifacts explicitly provided by the lab. Avoid assuming that every interesting clue is already known to you.
Investigation
- What services are exposed?
- What identities exist?
- Which credentials or tokens are available?
- What trust relationships exist?
- What happens when the relevant component executes?
- What evidence does the activity leave behind?
Research Tasks
- Map the architecture and trust boundaries.
- Identify the security-relevant assumption.
- Reproduce the behavior in the controlled environment.
- Collect evidence supporting your conclusion.
- Describe a practical defensive control.
Detection
Ask: What would a defender see? Record endpoint, network, identity and application evidence where available.
Mitigation
Ask: How would you prevent this attack? Prefer controls that reduce privilege or remove unnecessary trust rather than relying on a single detection rule.
Further Investigation
Change one assumption at a time. What happens if the identity has fewer permissions, the workflow runs from another branch, or the attacker has only temporary access?