> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/aikido-device-protection/using-aikido-endpoint/block-public-package-registries.md).

# Block Public Package Registries

When you route package traffic through a private registry, developers can still bypass the setup by pointing their package manager directly at the public registry. Device Protection enforces that all traffic goes through your approved private registry instead.

## How it works

Device Protection monitors network traffic on each device. When a request goes directly to a public package registry, it is blocked at the network level before the package is downloaded.

## Prerequisites

* Aikido Device Protection deployed on developer machines. See [Deploying Device Protection](/aikido-device-protection/deploying-aikido-endpoint/device-protection-mdm-guides.md).
* Your private registry added under [Custom Registries](/aikido-device-protection/using-aikido-endpoint/custom-registries.md), so installs through it keep working once the public registry is blocked.

## Configure the block

1. Go to [Device Protection and open the Settings tab](https://app.aikido.dev/endpoint-protection/settings).
2. Click the ecosystem you want to block.
3. Turn on **Block All Installs**.

Repeat for every ecosystem you route through a private registry.

{% hint style="warning" %}
It can take up to 10 minutes for changes to sync to all devices.
{% endhint %}

Need to let a specific package or team through? Add an exception under the same ecosystem. See [Configuring Installation Policies](/aikido-device-protection/using-aikido-endpoint/configuring-installation-policies.md#exceptions).


---

# 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://help.aikido.dev/aikido-device-protection/using-aikido-endpoint/block-public-package-registries.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.