# Hiding Runtime Info

By default, SecretVM exposes multiple data points through its built-in web server running on port 29343, such as:

* CPU attestation (via /cpu endpoint)
* Docker-compose file (via /docker-compose endpoint)
* Logs (via /logs endpoint)
* Resource usage (via /resources endpoint)
* List of running docker containers (via /services endpoint)

However, there are use cases where the SecretVM owner wants to keep the workload private from the public, and only share it with select few.

This is where the "Hide Runtime Info" setting provides its value:

<figure><img src="/files/aDK1SYDDmurGpR2JSNs1" alt=""><figcaption></figcaption></figure>

If the developer still wants to access those endpoints, they can provide a secret access token, and still be able to access those endpoints by providing teh token as Authorization Bearer or ?token parameter.

**Note:** the /cpu attestation endpoint cannot be hidden and is always present on the machine


---

# Agent Instructions: 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:

```
GET https://docs.scrt.network/secret-network-documentation/secretvm-confidential-virtual-machines/launching-a-secretvm/hiding-runtime-info.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
