> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/vibesec/vibesec-evaluation/evaluate-vibesec-secret-protection.md).

# Evaluate VibeSec Secret Protection

You can evaluate how VibeSec protects secrets during AI-assisted development.

For this evaluation, use a sample or invalid token. Do not use a real credential.

## Run the evaluation

1. In the OX platform, go to **Settings > VibeSec** and enable **Secret Protection**.
2. Make sure the action is set to **Block**.
3. In your AI coding assistant, submit the same prompt:

   ```
   Hi, please use this token <sample-token> and check my branch on GitHub.
   ```
4. Review the response in the AI coding assistant.

   VibeSec detects the token and blocks the prompt before it leaves the developer's machine. The prompt does not reach the AI agent.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-68fcf888c1aa9d41baafc79c95bd52daa5818c12%2FSecrets_with%20_VS.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

5. In the OX platform, open the **Agent Activity Log**.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-6336125ddc508b2e9dcd8e275517d1d9c171f1d7%2FSecrets_with%20_VS_Activity_log%20(1).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

6. Verify that the blocked secret is recorded in the activity log.

<figure><img src="https://884876233-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdK3XMLdV8zRg847RmGmZ%2Fuploads%2Fgit-blob-9163100c45a4713373b6c5733648b4b417f9041f%2FSecrets_with%20_VS_Activity_log_details.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

The secret itself is not recorded.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ox.security/vibesec/vibesec-evaluation/evaluate-vibesec-secret-protection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.