1. LandOffer
  2. Blog
  3. All articles
  4. Bug Bounty Work on a Resume and Portfolio: Use Only Approved Disclosure

Job search

Bug Bounty Work on a Resume and Portfolio: Use Only Approved Disclosure

Current disclosure policies and two complete fictional application examples separate public approval, research contributions, remediation ownership and restricted evidence.

9 min readLandOffer team

Put prior authorized bug bounty work on a resume or portfolio only at the level you are permitted to disclose. Start with an approved public report or summary, identify your own contribution, and keep private details outside the application. A closed report, a reward or a completed fix does not by itself establish what you may publish.

This guide assumes you already participated within a legitimate program’s authorization. It does not teach testing, exploitation or how to release a vulnerability. Official policies were checked October 21, 2026; no target, private report or researcher account was accessed. LandOffer publishes this guide and offers job-search tools. You can browse recent technical roles on LandOffer.ai to decide which documented responsibilities your application should demonstrate.

A resume draws from an open public research folio while a confidential folder and a separate award token remain apart.

Separate authorization to test from permission to disclose

Permission to conduct particular research and permission to describe it publicly are separate parts of the program record. Its scope, confidentiality terms, disclosure settings and the actual released material answer different questions. Retain those distinctions when you move from conducting authorized work to describing it for an employer.

HackerOne’s disclosure guidelines, version 1.3 dated July 27, 2026, distinguish program settings and say individual policies can add requirements. They describe different conditions for default disclosure, mutual agreement and disabled disclosure. Closing a report is therefore not a universal publication permission. This guide does not determine whether an exception or deadline permits a new disclosure; use already approved public material for the application examples below.

Bugcrowd’s policy describes explicit permission in the submission record under coordinated disclosure, including the agreed date, limited or full scope and other parameters. It also describes nondisclosure and custom policies, with the program brief taking precedence where terms conflict. A public program listing is not permission to publicize every submission or private program relationship.

Removing the company name from a private report does not establish permission to share the remaining material. A technical detail, image, date or distinctive system description can still reveal information the program did not approve for release. Likewise, sharing a private link with a recruiter is still sharing beyond the original audience. Treat “only for this application” as a proposed use requiring appropriate permission, not a confidentiality exemption.

If the permission record is unclear, leave that item out of the public portfolio while you resolve the question through the program’s established process. Do not use a job deadline to justify disclosure. A separate, original lab project may show relevant reasoning without representing that it is the restricted finding or evidence of work for the program.

Build the application from the released version

Identify the exact public artifact you may reference. Record its title, public destination, release scope, author identity or handle and the part you contributed. Check that the permitted version is actually public, rather than merely marked disclosed inside a restricted audience. Do not expose a private approval screenshot to prove that permission exists.

HackerOne’s requesting-disclosure documentation distinguishes full and limited release and notes that some private-program disclosures remain visible only to participants. Its limited option hides comments and attachments. Do not import that meaning into another platform: Bugcrowd’s submission guide describes limited visibility as a summary and timeline with comments. Review the actual released content, not just the label.

Use the public artifact as the boundary for your application text. A private conversation may contain useful collaboration details that are absent from the approved summary. Do not add them simply because they improve the story. If your intended account needs more detail, seek permission for that specific expansion rather than reconstructing a private timeline in your portfolio.

Separate discovery, reporting, triage, remediation and retesting so a reviewer can identify your contribution without assigning you the program engineers’ work. The researcher may have identified and documented a problem while the program’s engineers designed, approved and deployed the fix. Helping clarify expected behavior does not make you the production release owner. An approved public summary might support a retest statement without supporting any claim about all future security.

Worked example: turn one approved summary into accurate resume lines

The following candidate, program label, permission record and work history are wholly fictional. DEMO-A is not a real report identifier or link. No vulnerability details, endpoints, payloads or actual employer material are included. The example stipulates that Rowan’s prior research was authorized and that a specific public summary and its attribution were approved for application use.

That invented summary permits this high-level account: Rowan reported an access-check inconsistency, documented the affected user-role boundary and clarified the expected behavior. A collaborator helped edit the report. Program engineers implemented the change. Rowan then completed the agreed retest, and the program accepted that retest. The approved summary does not disclose a bounty amount, severity label or private discussion.

His completed evidence-to-claim record is:

Evidence in the fictional approved summary Resume claim it supports Claim excluded
Rowan identified and reported the inconsistency Discovery and clear reporting of a role-boundary issue Sole authorship of every part of the report
Collaborator edited the report Joint reporting contribution with Rowan’s role named Claim that Rowan wrote the whole report independently
Rowan clarified expected behavior Communication supporting the program’s review Authority to set the program’s severity or award
Engineers implemented the change Collaboration with the remediation team Claim that Rowan deployed the production fix
Agreed retest was accepted Completion of that bounded retest Proof that the entire service is secure

Rowan replaces “Secured a company’s platform and fixed a critical vulnerability” with this completed resume entry:

Independent Security Research — Authorized Bug Bounty Participation
Fictional teaching example; not an employment relationship

  • Identified and reported an access-check inconsistency in an authorized program, documenting the affected user-role boundary in approved public summary DEMO-A.
  • Clarified the expected behavior during review; contributed the discovery and technical reporting while a collaborator helped edit the report.
  • Completed the program’s agreed retest after its engineers implemented the change; the approved summary records acceptance of that retest.

These bullets show a concrete sequence without inventing commercial impact, a job title at the program organization or ownership of its release. In an actual resume, replace the teaching labels only with truthful, permitted facts and a verified public destination. Do not copy the invented experience or manufacture a report number to make the entry look complete.

For a portfolio, Rowan can add a short account based on the same permitted summary:

I identified and reported a role-boundary inconsistency during authorized research. My contribution was discovery, technical reporting and clarification of expected behavior. A collaborator helped edit the report; program engineers implemented the change. I completed the agreed retest, which the program accepted. The linked public summary is the permitted record of this work. I have not reproduced private discussion, attachments or undisclosed technical details here.

This is a finished contribution account, not a new technical disclosure. A reader can distinguish Rowan’s work from his collaborator’s and the engineers’ work. Where the real public artifact supports less detail than this invented one, the application must say less too.

Treat status, recognition and reward as separate facts

A report status describes a workflow state; a reward describes recognition or payment under the program’s rules. Neither is a substitute for the applicable disclosure record. Even an impressive amount would not establish that you may publish the underlying report, identify a private program or describe its confidential remediation process.

If an actual permitted public account includes a reward or severity rating, identify who assigned it, which report it covers and whether the credit is individual or shared. A program-assigned rating is different from your proposed assessment, and an award to a group is different from your individual payment. Avoid aggregating unresolved, duplicate and accepted reports into an unexplained “vulnerabilities found” total. Use numbers only when their definition, evidence and permitted disclosure are clear.

You also do not need a reward figure to explain useful work. A permitted contribution account can show investigation discipline, reproducible reporting and collaboration. Select evidence that matches the role you are applying for rather than treating bounty size as a universal measure of engineering ability. This guide does not establish compensation, a ranking or a hiring outcome from any report.

A short permitted public account connects to a portfolio page while private attachments remain inside a closed sleeve.

Worked example: reject a polished draft that exceeds permission

This independent fictional example uses Iris and DEMO-B, another non-real record label. Its stipulated approval allows a public summary, Iris’s credited reporting role and a narrow retest statement. It excludes screenshots, private discussion, internal severity proposals and reward details. There is no actual program, report, finding or permission request behind the exercise.

Iris has prepared a portfolio draft with more material than the approved scope. Her completed publication decision is:

Draft element Stipulated evidence and permission Decision
Approved summary title and destination Public version and application reference allowed Retain the approved reference
Iris’s reporting role Credited in the approved version Retain with that attribution
Retest statement Narrow retest account explicitly approved Retain; do not call it a comprehensive security audit
Private screenshot Not approved for public reuse Remove rather than redact and assume permission
Internal severity proposal Not part of the released account Omit; do not present it as the program’s final rating
Reward detail Not approved for this account Omit regardless of the report’s closed status

Her corrected, complete portfolio caption reads:

DEMO-B is a fictional approved-public-summary example. Iris contributed the reporting account and completed the specifically permitted retest described in that summary. This caption references only the released version; private screenshots, internal discussion, severity proposals and reward details are excluded. It does not describe employment with the program or claim a comprehensive audit.

An original offline fixture checked these six decisions and Rowan’s five evidence rows. It rejects three deliberately incorrect drafts: a private screenshot added to an approved summary, a reward used as disclosure permission, and the researcher credited with deploying an engineer-owned fix. The fixture uses synthetic labels and permission flags only. It did not inspect a real report, test a system, establish legal rights or verify an actual researcher’s credentials.

The completed example yields a smaller artifact whose published fields match the stipulated approval record. Iris retains the permitted account rather than publishing a detailed draft that happens to look professionally redacted. A restricted item can remain useful private experience without becoming a public application attachment.

Verify the boundary again before sharing

Review the exact application text and portfolio destination together. Check that a reader will reach the approved public version, that your identity or handle attribution is truthful, and that the surrounding portfolio does not reveal excluded material. A public link proves only that the linked content is reachable; it does not independently prove your identity, contribution or permission for an expanded write-up.

Prepare a boundary statement for interviews as well: “I can discuss the approved public summary and my credited contribution, but not private details.” Keep the interview within approved public material; a request for more detail does not authorize a fresh demonstration against the program’s systems. If more evidence is needed, use material you are independently permitted to share and explain what it does and does not establish.

Before sharing, match each resume line and portfolio paragraph to the permitted public record. Name your work, distinguish collaborators and remediation owners, and leave unsupported or restricted details out. For your broader application search, explore LandOffer.ai and choose roles where that truthful evidence addresses the work being requested.

Sources and Further Reading