Why HackerOne Acquired Pull Request and What It Means for Our Customers
hackerone.com | vulnerability | #devsecops | #code-review | #hackerone | #acquisition | #pullrequest | #attack-resistance
Summary
Over 70% of organizations claim to build security into development, yet under 25% of issues surface there. HackerOne explains how acquiring PullRequest adds code review to its attack resistance stack.
- Published
- Collected
--- id: 2770 title: "Why HackerOne Acquired Pull Request and What It Means for Our Customers" source_domain: hackerone.com source_url: "https://www.hackerone.com/blog/why-hackerone-acquired-pull-request-and-what-it-means-our-customers" published_at: "2022-05-03T18:59:59Z" tags: ["devsecops", "code-review", "hackerone", "acquisition", "pullrequest", "attack-resistance"] phying_url: "https://phying.com/item/2770" lang: en --- # Why HackerOne Acquired Pull Request and What It Means for Our Customers ## Summary Over 70% of organizations claim to build security into development, yet under 25% of issues surface there. HackerOne explains how acquiring PullRequest adds code review to its attack resistance stack. ## Intelligence Metadata - **Sources:** hackerone.com - **Published:** 2022-05-03T18:59:59Z - **Original:** https://www.hackerone.com/blog/why-hackerone-acquired-pull-request-and-what-it-means-our-customers - **Phying News:** https://phying.com/item/2770