> For the complete documentation index, see [llms.txt](https://docs.kerberus.com/kerberus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kerberus.com/kerberus/sentinel3/how-is-it-different/built-by-security-experts.md).

# Built by security experts

## Not all Web3 security solutions are created equal.

The evident security challenges in Web3 led to the creation of many solutions. *Most of them are not pioneered by security experts*. Developers or Web3 experts create them.

Cybersecurity is a highly complex niche of computer science. People seeking to become cybersecurity experts should first accumulate vast knowledge of operating systems, network protocols, and development. On top of that, they must dedicate years to learning and practicing hacking techniques, defensive mechanisms, best practices, and compensating controls. Furthermore, a deep understanding of human weaknesses and behavioral patterns is needed when designing security mechanisms.

[**This isn't the case for Sentinel3, pioneered by true security experts**](/kerberus/sentinel3/team.md).

> Example: our founder, Danor, performed penetration tests for a new endpoint protection software (used by companies to prevent their employees from running unauthorized programs). Clearly, the security architect wasn't an expert, as it took Danor only 5 minutes to completely bypass the protection. What was the security vulnerability? When the software detected an unauthorized application, it showed a popup announcing this program was unauthorized. Danor discovered a hidden, disabled button on this popup that bypassed the protection (most likely designed for support purposes).
>
> \
> **Developer mindset**: I've learned that to access a button, it must be enabled and visible. If I hide and disable it, the user will never be able to use it.<br>
>
> **Attacker/hacker mindset**: I've spent years of my life learning the operating system's deepest levels to perform actions that are not accessible to regular users. If there's a button, I will find a way to discover it and use it.
>
> **Security expert mindset**: I've spent years of my life learning the operating system's deepest levels to understand all possible access mechanisms. When I want to block something, I must cover all possible scenarios.


---

# 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.kerberus.com/kerberus/sentinel3/how-is-it-different/built-by-security-experts.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.