Insufficient CI/CD Logging and Visibility
The pipeline is where code becomes production, and it logged almost nothing.
What Is Insufficient CI/CD Logging and Visibility?
The pipeline is where code becomes production, and it is routinely the least observed system in the organisation. You'll try to reconstruct the out-of-band deploy from the first exercise weeks after it happened and find you cannot, because who triggered it, which credential it used and what it shipped were never recorded, then instrument the delivery plane so the same question finally has an answer.
What You'll Learn in Insufficient CI/CD Logging and Visibility
- The pipeline is often the least observed system, so an intrusion through it is not merely undetected but unreconstructable afterwards.
- Who triggered a run, which credential it used and what it deployed must be recorded durably, off the runner and beyond any investigation window.
- Link every deployed artifact to its run and commit, so the question of which commit is running in production always has an answer.
- Alert on anomalies such as a deploy with no run, a run outside working hours, or a first-time runner.
Insufficient CI/CD Logging and Visibility — Training Steps
-
Weeks after the fact
In the first exercise, Bob deployed a locally built image straight to production, past every gate, using the release token. That was three weeks ago. He is long gone. All that is left is the result: production runs a version with no run behind it. Veldrin now has to reconstruct what happened, from whatever the pipeline recorded.
-
Reconstruct the intrusion
Veldrin's incident review needs the full picture of the out-of-band deploy: who triggered it, which credential it used, what artifact it shipped, and which commit that artifact came from. Alice is asked to reconstruct it.
-
The one surviving clue
Alice starts where the evidence is. The register shows production on a version with no run behind it. It confirms the deploy skipped the pipeline, and that is all it confirms.
-
The log is gone
Alice goes to the deploy log on the runner. The out-of-band deploy was three weeks ago, and the log rotates after seven days, so the entries she needs are already gone.
-
Nothing was recorded
Alice opens the pipeline's audit view, which is meant to show what each deploy did. For this deploy it shows gaps: the run log is gone, and the next things she needs were never recorded at all.
-
Which credential, which commit
The two questions the incident review most needs are the two the pipeline never recorded: which credential the deploy used, and what the deployed artifact traces back to.
-
Why it cannot be reconstructed
-
What the pipeline records
The fix is to instrument the delivery plane. Alice opens the pipeline's observability config, where almost nothing is turned on.
-
Instrument the delivery plane
Alice turns on durable run and deploy logs kept off the runner, secret-access logging, artifact-to-run traceability, and alerts on anomalous delivery events.
-
Read the instrumented pipeline
Now the pipeline keeps a durable record of every run and deploy, logs every credential use, links every artifact to its run and commit, and alerts the moment a deploy arrives with no run behind it.
Security Framework Coverage
OWASP CI/CD Top 10
- CICD-SEC-10 Insufficient Logging and Visibility
CWE
- CWE-778 Insufficient Logging
- CWE-223 Omission of Security-relevant Information
CIS Controls
- CIS 8 Audit Log Management
- CIS 16 Application Software Security
NIST CSF
- PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind
- PR.PS Platform Security
- DE.AE Adverse Event Analysis
NICE Framework
- DD-WRL-004 Secure Systems Development
- IO-WRL-005 Systems Administration