The best AppSec story of the quarter.
Told in the wrong order.
One of the strongest B2B AppSec case studies this quarter, arranged in the wrong order. The Rubrik story has a named company, a named executive and real numbers, a 24-hour SLA and 187 compromised npm packages cleared in 30 minutes. The ad body mentions none of it and turns every hard number into a soft adjective, so “tight SLAs” replaces “24-hour SLA.” The operator quote that would stop the scroll sits unused.
The teardown, on LinkedIn
What the teardown found · tap to open each one
A named customer (Rubrik), a named executive, and hard numbers: a 24-hour SLA and 187 compromised npm packages cleared in 30 minutes. This is the kind of proof most B2B ads never get to use.
The ad body turns the real figures into mush, “tight SLAs” instead of “24-hour SLA,” and leaves the operator quote that would stop the scroll completely unused. The strongest assets are in the story but not in the ad.
Lead with the numbers and the quote: 187 packages in 30 minutes, the named exec’s words, verbatim. Let the proof do the work it was built for.
Questions, answered
This is Marina Kogan’s original teardown of Endor Labs’s live ad. See the full infographic on LinkedIn →
More teardowns
Your ads, roasted the same way
Pull your live ads, score each against your buyer, see where the click leaks.