Citizens expect public digital services to be useful, usable, and secure. When the security of these services are compromised and exploited by malicious actors, real people are put at risk of any number of cyber-related crimes, such as identity theft. As stewards of public trust, the government must hold itself to the highest, most appropriate levels of security standards in order to protect the people it serves. Unfortunately, the combination of limited resources and expanding attack surface areas are creating even more opportunities for adversaries. To counteract this trend, more and more organizations are embracing the use of bug bounties, a crowdsourced approach to security research. Through the power of the crowd, bug bounties can uncover 8x more critical vulnerabilities than traditional penetration testing and security assessments.

At Skylight, we know firsthand how integrating bug bounties into government’s DevSecOps processes — even before systems are deployed into production (“shift-left security”) — can produce far more robust and secure services. That’s why we’re excited to announce our new bug bounty solution.

Some background

For those new to crowdsourced approaches to white hacking, bug bounties are programs in which organizations pay rewards to independent security researchers who find and report hackable vulnerabilities in their systems. The first official pay-for-bugs program was launched by Netscape in 1995. Since then, Google (Security Reward Programs), Facebook (Bug Bounty), Microsoft (Bug Bounty Programs), and many other high-tech companies have launched their own successful programs. In 2016, bug bounties made their way into the federal government for the first time when the Department of Defense (DoD) launched the “Hack the Pentagon” pilot. The DoD ended up resolving more than 138 unique vulnerabilities found by 58 different security researchers. Recognizing the success of the DoD’s pilot, several other agencies have begun looking into and experimenting with bug bounty programs — such as Hack the Army and Hack the Air Force. Not to be outdone, even Congress is looking into formalizing the use of bug bounties as a standard federal security practice.

How we can support you

For most government organizations, bug bounty programs represent a new approach to protecting their digital ecosystems. Spinning up and running your own successful bug bounty program is certainly manageable; however, there are a number of moving pieces that must be carefully orchestrated. We’re here to help you learn and master that process. Our support services cover the entire lifecycle of a bug bounty program.

Four phases of Skylight's bug bounty lifecycle support services.


Our Bug Bounty Bootcamp is a one-day event that instructs you and other stakeholders on what bug bounties are and how to plan and execute a successful program, covering all the key areas that must be addressed. As part of this training, we dive deep into several different case studies (such as Google’s Security Reward Programs and DoD’s Hack the Pentagon), survey and demo commercial bug bounty platforms, facilitate a collaborative workshop in which we launch a mock program, and assess whether your organization is ready for a bug bounty program. Our aim is to equip you with all the critical knowledge, tools, and templates that you need to move forward successfully.

The great thing about this Bootcamp is that it’s scoped and priced within the federal government’s micropurchase threshold.

Design & Preparation

Based on what your specific organizational needs and testing requirements are, we work with you to design and prepare for a successful bug bounty program. If this is your first one, we recommend starting out with a pilot program to test the waters. Some of the key activities at this stage include:

  • Assembling the bug bounty team who will support the program (for example, engaging key stakeholders from across the organization, responding to bug reports, making awards, and building relationships with the security research community), including the team’s leader (for example, Chief Information Security Officer) who will own and champion the program.
  • Setting the initial scope of the assessment. That is, what digital assets (such as 3–5 public-facing websites, all web services under a particular domain, or a highly-sensitive system in pre-production) and bug types (for example, XSS or SQL injection) you want — and don’t want — researchers to focus on.
  • Determining what type of program you want to run. For example, it could be private (invite-only) or public (open to the collective intelligence of thousands) coupled with a Vulnerability Disclosure Program (open-door policy to anyone who wants to report a security flaw).
  • Calibrating the rewards structure based on your available budget.
  • Choosing and setting up a bug bounty platform — such as Bugcrowd or HackerOne — for receiving, organizing, analyzing, understanding, and offering rewards for vulnerability reports from third-party researchers. (We don’t recommend trying to build-out and manage this infrastructure yourself.)
  • Priming your vulnerability management processes to handle the influx of new reports that will need to be triaged and remediated. This includes highlighting how triages are handled and designating remediation teams.
  • Crafting your policy/rules page. This page commonly contains your disclosure policy, rules of engagement, scope, service-level agreements (such as time to respond to a new report and time to bounty after validation), and other important information.


Once you’re fully prepared, we work with you to launch and iterate on your program. A few of the main activities include:

  • Receiving vulnerability reports from security researchers and coordinating the validation, prioritization, and remediation of those reported flaws within the target service-level agreements.
  • Adjusting elements of the program (for example, policy/rules page or bounty amounts), if need be, to ensure researchers are hitting the right targets and reporting the types of bugs that you want to see.
  • Incentivizing more participation and increasing the volume of reports through such actions as increasing the scope, adding more hackers, and increasing the bounty amounts.

Scaling & Improvement

Over the course of the launch stage, you’ll gain valuable experience running bug bounties within the context of your organization. You should have ironed out a lot of the major kinks and be in a position to ramp the program up and leverage it to drive improvements to your organization’s security culture and coding practices. Some of the key activities at this stage include:

  • Scaling the program. This could mean increasing the scope to include more digital assets and types of bugs, opening it up to more hackers, increasing the bounty rewards, or any combo thereof. In doing so, you might need to iterate through the design & preparation and launch phases again.
  • Optimizing bug bounty and vulnerability management processes to handle a larger volume of reports.
  • Leveraging bug bounty data to perform an analysis of the root causes behind systemic issues (for example, XSS keeps popping-up) with your existing security and software development practices. This is particularly useful for gaining insight into the performance of specific contractors.

Let’s get secure!

If you’re interested in chatting with us about how we could support your bug bounty initiative, we’d love to hear from you.