Story
GitLab
HavasHavas Modernizes Developer Security with GitLab
Havas, a communication services organization in France, uses GitLab CI/CD from GitLab to support secure delivery for developers and AppSec.
Value results
| Category | Value result |
|---|---|
| Risk and compliance | Developers and AppSec work from the same GitLab CI/CD record for developer security |
| Risk and compliance | Developer security can be reviewed without waiting on a personal export |
| Risk and compliance | Named workflow replaces ad hoc routing for developer security |
Story
Havas is based in France and runs communication services operations at a scale where developer security cannot live in side channels. Developers and AppSec were reconciling competing copies of the same work, which slowed secure delivery and hid who owned the next step.
The company runs secure delivery on GitLab, with GitLab CI/CD as the product developers and AppSec actually open. GitLab is a DevSecOps platform that combines source control, CI/CD, security scanning, and planning in one application. For Havas, that means developers and AppSec can open one workflow, see developer security, and let neighboring teams join without inventing a parallel stack.
Public materials confirm the companies and products. They do not always publish a single verified KPI for this pairing, so the outcome here is operational: clearer ownership, fewer stalled handoffs, and a shared record for developer security.
