PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

How HackerOne Positively Influences Zebra’s Software Development Life Cycle

hackerone.com | blog | #bug-bounty | #pentesting | #appsec | #vdp | #hackerone | #sdlc | #zebra
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

Zebra's Jasyn Voshell explains how combining hacker-powered pentests, bug bounty, and a VDP improved the SDLC, giving real-time visibility into findings instead of waiting for final pentest reports.
Published
Collected

Related coverage

blog · hackerone.com
Critical PHP Vulnerabilities: What Security Teams Need to Know
Learn about the critical PHP vulnerabilities, HackerOne’s response, and the rise in reports. Review patching guidance and coordinated disclosure practices.
blog · tenzai.com
An open-weight model powered the #1 HackerOne VDP research operation
Tenzai's AI hacker topped the world's largest bug bounty leaderboard on GLM 5.2, a model anyone can download, and the offensive capability once limited to a few frontier labs is now within anyone's reach.
blog · netspi.com
A Checklist for Application Security Program Maturity
A phased checklist for building AppSec maturity: keep practices current with SDLC and DevOps changes, benchmark against industry data, and use roadmaps to prioritize remediation.
blog · netspi.com
Build Strong Relationships Between Development and Application Security Teams to Find and Fix Vulnerabilities Faster
Bridging the DevSecOps divide: with 71% of AppSec pros citing developers who skip early security work, the post urges empathy and shared incentives between development and security teams.
blog · netspi.com
Four Application Security Myths – Debunked
Debunks four application security myths—'an AppSec team is optional,' 'we're too small'—and shows how small teams, governance, and security champions programs can embed security into the SDLC.
blog · netspi.com
Make it Easy on the Development Team
NetSPI examines why development and application security teams clash over deadlines and findings, offering five steps to make security testing participation easier and less adversarial for developers.
Back