> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/siem-integrations/sso-and-identity/duo-security.md).
# Duo Security
Integrating **Duo Single Sign-On (SSO)** with **ThreatDefence** enables secure, centralized user authentication for the platform, leveraging Duo’s strong multi-factor authentication and policy enforcement.
This integration streamlines user access while maintaining compliance and reducing identity-based risks across the organization.
***
## Step 1. Configure API Permissions
1. Navigate to **Dashboard → Applications → Admin API**.
2. To create the Admin API application: Log into the Duo Admin Panel as an administrator with the "Owner" role and navigate to Applications. Click Protect an Application and locate the entry for Admin API in the applications list. Click Protect to the far-right to configure the application and get your integration key, secret key, and API hostname. You'll need this information to update the config.yml file later. Scroll down to the "Permissions" section of the page and deselect all permission options other than Grant read log. Optionally specify which IP addresses or ranges are allowed to use this Admin API application in Networks for API Access. If you do not specify any IP addresses or ranges, this Admin API application may be accessed from any network.
Click Save.
1. Select **Grant Read log** permission.
***
## Step 2. Configure ThreatDefence Integration
Provide the following information to your ThreatDefence representative at\
📧 ****:
* Integration Key
* Secret Key
* API Hostname
***
## Support
For questions or assistance, please contact:\
📧 ****
---
# 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.threatdefence.com/siem-integrations/sso-and-identity/duo-security.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.