Story
GitLab
McGraw HillMcGraw Hill Runs Secure Delivery with GitLab
McGraw Hill, a communication services organization in the United States, uses GitLab Registry from GitLab to support secure delivery for developers and AppSec.
A GitLab Registry rollout at McGraw Hill 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 |
|---|---|
| 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 Registry is the governed place developers and AppSec use for secure delivery |
Story
McGraw Hill 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.
McGraw Hill 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.
