> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/security/network-security-groups/how-tos/view-nsgs.md).

# View Network Security Groups

To view the list of NSGs that are associated with a data center, follow these steps:

1\. In the **DCD**, go to **Menu** > **Security** > **Network Security Groups**.

2\. Select a data center from the **Showing results for datacenter:** drop-down list to view the NSGs associated with it.

![List of NSGs](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-c1eb900ce9a5f04eb5a1a2d0bac8c568e39b058e%2Fnsg-list.png?alt=media)

{% hint style="success" %}
**Result:** A list of security groups is displayed. The table also displays the network security group's name, state, the number of servers or NICs attached to it, the total number of rules defined for the respective NSG, and whether it is a default group. You can select a specific data center to view all its associated NSGs, copy the respective NSG's UUID, attach an NSG to a server or an NIC, set the group as a default group, create new custom groups, or delete existing security groups.
{% 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.ionos.com/cloud/security/network-security-groups/how-tos/view-nsgs.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.