Aruba Networks Commits to ONGOING PRIVATE BUG BOUNTY FOR BETTER DEVICE SECURITY

Download Case Study

As Aruba Networks scaled its operations to meet growing demand, it knew that product and application security needed to be prioritized.

After bringing in a dedicated team and carrying out multiple expensive third-party testing engagements, they still needed more eyes looking at the expanding attack surface.

Aruba decided to harness the collective power of human intelligence through Bugcrowd’s Ongoing Private Bug Bounty Program.

Challenge:

After evaluating its current testing capabilities and organizational goals, Aruba was struggling to get the coverage it required for its growing portfolio of products.

Solution with Bugcrowd:

Aruba was able to tailor its vulnerability testing pool based on specific skill sets, has more direct communication with a smaller group of testers, while still taking advantage of the crowdsourced model.
Because of its consistency and transparency, Aruba has received consistent attention from the researcher community over the last few years.

Program Results:

As one of the first organizations to utilize an Ongoing Private Bug Bounty to test hardware, Aruba has been recognized by the security research community for its commitment and innovation. Read the full case study below to learn more about Aruba’s bug bounty programs.

We have products that cover a wide variety of applications that utilize various technologies, so we need security testing that can cover all those areas. Bugcrowd’s Ongoing Private Bug Bounty is the best way to get the coverage. Of course, this entire line of thinking starts with the premise that we think product security is of the utmost importance – we want to find the problems before someone else does so that we can help keep our customers secure.
Jon Green Vice President & Chief Technologist of Security

Program Facts

Industry
Technology
Program Type
Private Bug Bounty

Empower Your Security Team With a Crowd of White Hat Hackers to Find and Fix Vulnerabilities in Your Code Before the Bad Guys Do.