Story
GitLab
OutreachOutreach Extends GitLab Issues Across Secure Delivery
Outreach, an information technology organization in the United States, uses GitLab Issues from GitLab to support secure delivery for developers and AppSec.
GitLab Issues became the place Outreach uses to catch dependency and code issues while the change is still in review.
“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 |
|---|---|
| Risk and compliance | Developers and AppSec work from the same GitLab Issues record for developer security |
| Risk and compliance | Developer security can be reviewed without waiting on a personal export |
| Capability | Secure delivery stays visible to adjacent teams through GitLab Issues |
Story
Inside Outreach, secure delivery used to depend on whoever still had the latest file. That pattern is common in information technology 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.
Outreach 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 Outreach 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.
