Story
GitLab
DR HortonGitLab at DR Horton: Developer Security
DR Horton, a consumer discretionary organization in the United States, uses GitLab Registry from GitLab to support secure delivery for developers and AppSec.
A GitLab Registry rollout at DR Horton took secure delivery out of inboxes and into a named queue.
“In the United States, developers and AppSec already knew where developer security went wrong: too many copies, too little ownership, and a close process that waited on the loudest inbox.”
“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 | Named workflow replaces ad hoc routing for developer security |
| Risk and compliance | Developers and AppSec work from the same GitLab Registry record for developer security |
| Capability | Secure delivery stays visible to adjacent teams through GitLab Registry |
Story
DR Horton did not need another dashboard that nobody opened. It needed secure delivery to move. In the United States, developers and AppSec already knew where developer security went wrong: too many copies, too little ownership, and a close process that waited on the loudest inbox.
GitLab Registry from GitLab is now in that path. GitLab is a DevSecOps platform that combines source control, CI/CD, security scanning, and planning in one application. The company treats it as production tooling for secure delivery, which is why developers and AppSec live in it rather than exporting from it once a quarter.
DR Horton can show how developer security is handled today. That is the value: a repeatable way to run secure delivery on software the rest of the industry already recognizes.
