Skip to content
storyUnited StatesUtilitiesProductivityRisk and compliance

Story

GitLab@FirstEnergy

FirstEnergy 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.

Value results

CategoryValue result
ProductivityHandoffs in secure delivery sit in a shared queue instead of a mailbox trail
Risk and complianceFewer stalled items because developer security has a clear owner
Risk and complianceGitLab 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.

Relationship map

FirstEnergy uses GitLab, Sage, New Relic, Hexagon, Splunk, Oracle, OpenText, CrowdStrike, Palantir, ADP. Shared with 1Password, Agilent Technologies, Airbnb, Alcoa, American Airlines. Industry: Utilities. Value: Productivity, Risk and compliance. Drag nodes, filter types, or expand a node to follow more commonalities.

100%

Similar stories

Search Valuerepo

Search stories, solutions, customers, and more.

Type to search stories, solutions, and companies

↑↓Navigate↵OpenEscClose

View all