> 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/welcome/readme/security-is-core-of-hackenproof.md).

# Security is Core of HackenProof

At HackenProof, security isn't just a feature — it's the foundation. We are committed to safeguarding our clients' data, researchers' identities, and the integrity of our platform through globally recognized standards and best practices.

### Security Standards We Follow

* **ISO/IEC 27001 Certified**. We are officially certified under ISO/IEC 27001, the international standard for establishing, implementing, and maintaining an Information Security Management System (ISMS).
* **ISO 29147** **– Vulnerability Disclosure**. We implement structured processes for receiving and managing vulnerability reports securely and transparently.
* **ISO 30111 – Vulnerability Handling**. Our triage and remediation workflows follow best practices for assessing, verifying, and resolving vulnerabilities.
* **ISO/IEC 27002 – Information Security Controls.** Our platform incorporates many of the recommended information security controls from ISO/IEC 27002.
* **GDPR Compliance – General Data Protection Regulation.** We are fully compliant with the EU General Data Protection Regulation (GDPR). Our data protection framework ensures lawful processing, transparency, user consent management, data minimization, and robust protection of personal information across all our systems and operations.<br>

### Security Features at HackenProof

We integrate robust security mechanisms directly into the platform to protect user data and facilitate safe vulnerability coordination:

* End-to-end encryption of reports&#x20;
* Two Factor Authentication (2FA)
* Auth (Google/GitHub)
* User Login History Tracking
* Role -Based Access Control (RBAC) to programs

### Vulnerability Classification at HackenProof

At HackenProof, we follow a structured and transparent **vulnerability classification framework** to ensure fair and consistent evaluation of all reported issues. This system helps both researchers and program owners clearly understand the severity and business impact of vulnerabilities.

* Read the full guid&#x65;**:** [Vulnerability Classification Documentation](/bug-bounty/vulnerability-classification.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hackenproof.com/welcome/readme/security-is-core-of-hackenproof.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.