> For the complete documentation index, see [llms.txt](https://docs.hackenproof.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackenproof.com/good-to-know/hackenproof-vanguard.md).

# HackenProof Vanguard

### HackenProof Vanguard

**What is HackenProof Vanguard?**

HackenProof Vanguard is a community and recognition program for trusted security researchers who actively hunt on HackenProof, share practical knowledge, and contribute to the development of the wider security community.

It brings together researchers who lead by example through their technical expertise, responsible conduct, and willingness to support others.

The program is designed to:

* recognize active and experienced security researchers;
* make practical bug bounty knowledge more accessible;
* support meaningful discussions about vulnerabilities and responsible disclosure;
* help researchers better understand scopes, programs, and bug bounty opportunities;
* create opportunities for researchers to share their work with a wider audience.

### Vanguard Membership

HackenProof Vanguard membership is intended for active and trusted researchers who demonstrate technical expertise, responsible conduct, and a meaningful contribution to the security community.

Membership is offered to selected researchers based on their HackenProof activity, reputation, public contributions, and alignment with the program’s principles.

**Who can become a Vanguard member?**

Potential Vanguard members are evaluated based on several factors, including:

* active participation in HackenProof programs;
* a history of valid vulnerability reports;
* compliance with HackenProof platform and program rules;
* responsible and professional communication;
* contributions to security education or community discussions;
* willingness to share practical knowledge and support other researchers.

Meeting individual criteria does not automatically guarantee admission to the program. Membership is subject to HackenProof’s internal review and program capacity.

**Member responsibilities**

Vanguard members are expected to:

* follow HackenProof platform and program rules;
* respect confidentiality and responsible disclosure requirements;
* communicate accurately and professionally;
* avoid misleading, fabricated, or exaggerated claims;
* clearly separate personal opinions from official HackenProof statements;
* maintain respectful behavior toward clients, researchers, and community members.

Participation does not require members to use scripted messages or publish promotional content they do not genuinely support.

**Membership review**

Membership may be reviewed based on:

* activity within HackenProof and the Vanguard Program;
* compliance with platform rules;
* confidentiality or disclosure violations;
* misleading or inappropriate public behavior;
* actions that may harm researchers, clients, or the wider security community.

HackenProof may suspend or end a membership when program standards are no longer met.

**Voluntary participation**

Participation in HackenProof Vanguard is voluntary.

Members may choose whether to participate in individual content, community, interview, or educational opportunities. Membership does not create an employment, contractor, agency, partnership, or representative relationship with HackenProof.

### Member Opportunities & Benefits

HackenProof Vanguard provides selected opportunities to recognize members, support their work, and increase the visibility of useful security research.

Benefits may vary depending on member activity, platform rules, internal eligibility criteria, and the availability of specific opportunities.

**Free submission credits**

Vanguard members may receive access to selected free submission credits on HackenProof.

Availability, quantity, and usage conditions may depend on:

* active program requirements;
* platform rules;
* member eligibility;
* participation in qualifying Vanguard activities.

Submission credits are a program benefit and are not guaranteed compensation.

**Vanguard profile badge**

Members receive a visible HackenProof Vanguard achievement on their HackenProof profile.

The badge recognizes their participation in the program and their contribution to the security community.

**Visibility through HackenProof channels**

HackenProof may amplify selected public contributions from Vanguard members through its official channels.

Examples include:

* technical posts;
* educational threads;
* research notes;
* responsible vulnerability write-ups;
* bug bounty insights;
* community contributions.

Amplification is selected individually and is not guaranteed for every publication.

**HackenProof Blog contributions**

Vanguard members may submit content for publication on the HackenProof Blog, including:

* technical articles;
* vulnerability research;
* bug bounty write-ups;
* educational guides;
* research methodologies;
* security community insights.

All submissions are subject to editorial, confidentiality, and security review before publication.

**Researcher features**

Selected members may be featured through:

* researcher spotlights;
* interviews;
* profile stories;
* community pages;
* educational campaigns;
* other HackenProof publications.

Features are based on relevance, availability, and editorial selection.

**Community activities**

Members may be invited to participate in:

* AMAs;
* X Spaces;
* interviews;
* community discussions;
* educational initiatives;
* researcher spotlights;
* other HackenProof community activities.

Participation in individual opportunities is optional.

### Community Contribution

HackenProof Vanguard supports researchers who contribute to the growth, development, and education of the security community.

Members are encouraged to share practical knowledge based on their real experience with bug bounty hunting, vulnerability research, reporting, and responsible disclosure.

There is no single required content format. Contributions should reflect each member’s expertise, interests, and communication style.

**Sharing practical experience**

Vanguard members may share lessons and observations related to:

* vulnerability discovery;
* bug bounty methodologies;
* report preparation;
* proof-of-concept development;
* program communication;
* remediation and disclosure;
* common mistakes and useful research practices.

Content should be based on real experience and should not present speculation as confirmed fact.

**Creating educational security content**

Members may contribute through formats such as:

* social media posts;
* technical threads;
* articles and write-ups;
* videos;
* research notes;
* community discussions;
* presentations or interviews.

Educational content should provide useful context, practical knowledge, or a clear technical perspective.

**Helping other researchers**

Vanguard members may help researchers:

* discover relevant bug bounty opportunities;
* understand program scopes and rules;
* improve vulnerability reports;
* navigate disclosure requirements;
* develop stronger research practices;
* learn from practical examples.

Members should provide guidance responsibly and avoid encouraging actions that violate program rules or create security risks.

**Supporting meaningful discussions**

Vanguard members can contribute to constructive discussions around:

* vulnerability classes;
* reporting quality;
* severity and impact;
* responsible disclosure;
* security research methods;
* the development of the bug bounty ecosystem.

Discussions should remain professional, evidence-based, and respectful toward clients and other researchers.

**Authenticity and independence**

Vanguard is not based on scripted promotion.

Members are encouraged to express honest opinions and share both positive experiences and constructive feedback. Participation in the program does not require members to endorse every HackenProof product, decision, or announcement.

### Content Guidelines

Vanguard content should be based on genuine experience, technical knowledge, and responsible communication.

These guidelines apply when members publish content connected to HackenProof, the Vanguard Program, HackenProof programs, or benefits received through the program.

**Use real experience**

Content should reflect the member’s own experience, knowledge, or clearly identified analysis.

Members should not:

* invent research results;
* present unverified claims as facts;
* exaggerate achievements or vulnerability impact;
* imply access to information they do not have;
* publish misleading comparisons or conclusions.

**Communicate accurately**

Technical information should be explained as accurately as possible.

When information is incomplete or uncertain, members should make that clear. Corrections should be made when meaningful errors are identified.

**Maintain professional communication**

Members should communicate respectfully toward:

* researchers;
* HackenProof clients;
* program teams;
* triagers;
* developers;
* community members.

Constructive criticism is welcome, but harassment, personal attacks, threats, or intentionally harmful behavior are not acceptable.

**Distinguish personal opinions**

Vanguard members share their own opinions and experiences.

Unless explicitly authorized, members must not:

* present personal statements as official HackenProof positions;
* make commitments on behalf of HackenProof;
* represent themselves as HackenProof employees or official spokespersons;
* provide official interpretations of platform or program policies.

**Disclose Vanguard participation**

Members should clearly disclose their participation in the HackenProof Vanguard Program when content is connected to:

* program benefits;
* partnerships or coordinated activities;
* visibility or amplification provided by HackenProof;
* other material support received through the program.

The disclosure should clearly explain the member’s relationship with the program.

**Technical write-ups**

Technical write-ups connected to HackenProof programs must follow all applicable disclosure and confidentiality requirements.

Approval must be obtained before publishing program-related vulnerability information that has not already been authorized for public disclosure.

**Responsibility for published content**

Members remain responsible for content published through their personal accounts, websites, communities, or external platforms.

Participation in HackenProof Vanguard does not transfer responsibility for a member’s claims, opinions, legal obligations, or third-party content to HackenProof.

### Confidentiality & Responsible Disclosure

Vanguard membership does not change the confidentiality requirements of HackenProof programs.

Members must continue to follow all program rules, non-disclosure requirements, disclosure timelines, and responsible research practices.

**Undisclosed vulnerabilities**

Members must never publish details of a vulnerability before disclosure has been authorized.

This includes:

* vulnerability descriptions;
* technical exploitation details;
* proof-of-concept code;
* affected endpoints or contracts;
* screenshots or report excerpts;
* information that could allow others to reproduce the issue.

**Private scopes and reports**

Members must not share:

* private or invite-only program scopes;
* vulnerability reports;
* private program instructions;
* internal comments or communications;
* unpublished remediation information;
* confidential platform materials.

Information must not be shared with third parties unless explicitly permitted.

**Client-sensitive information**

Members must protect information that could expose or create risk for a HackenProof client.

This includes technical, operational, business, infrastructure, and user-related information obtained through participation in a program.

**Approval before publication**

Members must obtain approval before publishing a technical write-up connected to a HackenProof program or finding when disclosure has not already been authorized.

Approval may include review of:

* technical details;
* disclosure timing;
* screenshots and report excerpts;
* client references;
* remediation information;
* affected assets and scope details.

Submitting content for review does not guarantee approval for publication.

**Responsible disclosure requirements**

Members must:

* report vulnerabilities through the approved HackenProof process;
* avoid accessing unnecessary data;
* stop testing when continued activity could create harm;
* follow the rules of the relevant program;
* allow the program sufficient time to investigate and remediate;
* respect all disclosure decisions and timelines.

**Security risks**

Members must not publish content that could create an active security risk for:

* a client;
* a program;
* a user;
* an affected system;
* the wider community.

When uncertain whether information can be published, members should treat it as confidential until permission is provided.

**Confidentiality violations**

A confidentiality or responsible disclosure violation may result in:

* removal of content;
* suspension or termination of Vanguard membership;
* restrictions on HackenProof account activity;
* actions permitted under the applicable program rules or agreements.

### Program Terms

HackenProof Vanguard is a voluntary recognition and community program operated by HackenProof.

These terms describe the general nature of participation and the relationship between HackenProof and Vanguard members.

**No employment or agency relationship**

Participation in HackenProof Vanguard does not create an employment, contractor, partnership, agency, or representative relationship.

Vanguard members are not authorized to:

* act on behalf of HackenProof;
* enter into agreements for HackenProof;
* make official commitments;
* issue official statements;
* represent themselves as HackenProof employees or agents.

**Independent participation**

Members independently decide whether and how to participate in available activities.

They remain responsible for:

* their own public content;
* their personal opinions and claims;
* compliance with applicable laws;
* tax obligations connected to any benefits or compensation they receive;
* compliance with third-party platform rules.

**Program benefits**

Benefits are provided as recognition, access, or selected community opportunities.

They are not guaranteed compensation and may:

* depend on eligibility criteria;
* be limited in quantity;
* vary between members;
* change over time;
* be unavailable in some cases;
* be discontinued without replacement.

Membership itself does not guarantee payment, credits, publication, promotion, or participation in specific activities.

**Public content and amplification**

HackenProof may repost, reference, or feature public content created by Vanguard members.

Where additional rights or approvals are required, they may be agreed upon separately.

Amplification through HackenProof channels does not mean that HackenProof endorses every statement or opinion expressed by a member.

**Program changes**

HackenProof may update:

* program requirements;
* membership criteria;
* available benefits;
* participation guidelines;
* community activities;
* these program terms.

HackenProof may also pause or discontinue the Vanguard Program when necessary.

**Membership termination**

HackenProof may suspend or terminate membership due to:

* prolonged inactivity;
* platform or program violations;
* confidentiality breaches;
* irresponsible disclosure;
* misleading or harmful public claims;
* abusive or inappropriate behavior;
* actions that may damage researchers, clients, HackenProof, or the wider community.

Members may also choose to leave the program.

**Relationship with other HackenProof rules**

Vanguard membership does not replace or override:

* HackenProof Terms of Service;
* individual bug bounty program rules;
* confidentiality obligations;
* disclosure requirements;
* platform policies;
* any separate agreement applicable to a member.

Where requirements differ, the stricter confidentiality and security obligation should be followed.