Story
GitLab
FirstEnergyFirstEnergy Extends GitLab Issues Across Secure Delivery
FirstEnergy, a utilities organization in the United States, uses GitLab Issues from GitLab to support secure delivery for developers and AppSec.
Developers and AppSec at FirstEnergy review developer security in GitLab Issues rather than in personal files.
“Developers and AppSec needed a system that would still make sense after the original project team moved on.”
“GitLab is a DevSecOps platform that combines source control, CI/CD, security scanning, and planning in one application.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Productivity | Handoffs in secure delivery sit in a shared queue instead of a mailbox trail |
| Risk and compliance | Fewer stalled items because developer security has a clear owner |
| Risk and compliance | GitLab Issues is the governed place developers and AppSec use for secure delivery |
Story
Inside FirstEnergy, secure delivery used to depend on whoever still had the latest file. That pattern is common in utilities groups working out of the United States. Developers and AppSec needed a system that would still make sense after the original project team moved on.
FirstEnergy uses GitLab Issues from GitLab as the working layer for developer security. GitLab is a DevSecOps platform that combines source control, CI/CD, security scanning, and planning in one application. The practical change is simple: secure delivery has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What FirstEnergy gets from GitLab is a durable place to run secure delivery and a way for developers and AppSec to see the same developer security at the same time.
