> For the complete documentation index, see [llms.txt](https://docs.ethernity.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ethernity.cloud/ethernity-node-quickstart/security.md). # Security Considerations The Ethernity NODE runs tasks that are requested through the blockchain smart contract. This allows anybody to run their own software freely as long as it can be bundled inside a docker container. In order to prevent abuse, the node restricts by default all outgoing connectivity of the full virtualization layer. Only to the required services are permitted: blockchain RPC, ipfs node, docker registry. Further restrictions can be applied by the node operator by updating the source code which is licensed AGLP v3. Additional restrictions can include: running tasks requested only by a set of wallet addresses or running tasks containing only desired docker images. Node operators are responsible for maintaining and enforcing their own set of rules. Running a node requires generating two keypairs that represent the identity of your node and you are fully responsible to keep it safe. Do not share this information, or store it unencrypted outside the node configuration. --- # 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.ethernity.cloud/ethernity-node-quickstart/security.md?ask=&goal= ``` `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.