> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/saas-data-monitoring/inventory/trusted-ips.md).
# Trusted IPs
IT teams generally work with a defined list of trusted IP ranges they allocate and manage. These IPs are valid indicators of a legitimate network, while IPs outside these ranges are considered to be non-trusted.
DoControl enables you to manage trusted organization IPs in CIDR format. Classless Inter-Domain Routing (CIDR) is a range of IP addresses a network uses.
{% hint style="info" %}
* DoControl supports only IPv4 IP addresses.
* Learn more about configuring trusted IPs with [DoControl videos](/docontrol-user-guide/help/videos.md#domains-and-trusted-ips).
{% endhint %}
## Use cases
By managing trusted organization IPs, DoControl enables your organization to reduce risk and address potential threats:
* Use workflows to detect and validate events according to trusted IPs.
* Flag events that don't originate from trusted IPs. Such events could indicate potential account takeover.
* Set a condition in workflows to disallow specific activity; for example, if an actor logins from an untrusted IP or country.
* Set a condition in workflows to reduce the exposure to non-trusted IPs.
* Adhere to compliance requirements and regulatory policies.
## Manage IP ranges
You can add, remove or update trusted IP ranges. You need to define a list of trusted IPs before creating [workflow conditions](#use-trusted-ips-in-workflow-conditions) that refer to trusted IPs.
{% hint style="info" %}
* You must enter IP ranges in valid CIDR format. Otherwise, an invalid input error is displayed.
* DoControl supports only IPv4 IP addresses.
{% endhint %}
#### To add trusted IPs in CIDR format:
1. Select **Inventory > Domains and IPs > Trusted IPs**.
2. Enter the IP range in valid CIDR format. For example: 10.0.0.1/24
3. Click **Add**. The IP range is added to the list of CIDR ranges. DoControl automatically calculates and displays these values:
Column
Description
Example
CIDR range
A range of IP addresses a network uses
10.0.0.1/24
First IP address
First IP in the range
10.0.0.1
Last IP address
Last IP in the range
10.0.0.254
Total IPs in range
Total number of IPs in the range
256
#### To update IP ranges:
1. Select **Inventory > Domains and IPs > Trusted IPs**.
2. Click on the relevant CIDR range in the left column.
3. Modify the values. The CIDR range is automatically updated.
#### To delete IP ranges:
1. Select **Inventory > Domains and IPs > Trusted IPs**.
2. For the relevant CIDR range, click the **Trash** icon on the right.
## Use trusted IPs in workflow conditions
After you define your list of trusted organization IPs, you can use them as conditions in workflows.
1. Define your organization's list of trusted IPs. See [Manage IP ranges](#manage-ip-ranges).
2. Create a workflow; for example with a change user access event.
3. Add a condition that checks if the event's IP originates from the non-trusted IPs list.
4. Use either one of these comparators to filter specific IPs:
* In trusted IPs: True or false
* Not in trusted IPs: True or false
{% hint style="success" %}
Tip: By filtering specific IPs that your organization doesn't allow, you can detect potential account takeover attacks, and also address compliance requirements.
{% endhint %}
{% hint style="info" %}
Note: Not all SaaS events contain IP fields.
{% endhint %}
---
# 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.docontrol.io/docontrol-user-guide/saas-data-monitoring/inventory/trusted-ips.md?ask=&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.
