> 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/dns-security/cloudflare-dns.md). # CloudFlare DNS Security ThreatDefence integrates with **Cloudflare DNS Security** to ingest DNS query and policy enforcement logs.\ This integration provides visibility into malicious domains, blocked queries, phishing attempts, and user DNS activity. *** ## Integration Method Cloudflare DNS logs are delivered via **AWS SQS (Simple Queue Service)**.\ Cloudflare Logpush exports DNS security logs into an AWS SQS queue, which ThreatDefence securely ingests into the SIEM platform. For setup, follow the [AWS SQS Integration Guide](/siem-integrations/public-cloud/aws-sqs.md). *** ## Prerequisites * A Cloudflare Enterprise account with **DNS Security Logpush** enabled. * Access to an AWS account to configure **SQS queues**. * Cloudflare account permissions to create and manage **Logpush jobs**. * ThreatDefence-provided SQS subscription details for integration. *** ## Next Steps 1. Configure Cloudflare DNS Security **Logpush** to deliver logs to your AWS SQS queue. 2. Follow the [AWS SQS integration steps](/siem-integrations/public-cloud/aws-sqs.md) to prepare the queue. 3. Send the SQS queue details (ARN, region, access keys if applicable) to 📧 ****. 4. ThreatDefence engineers will validate ingestion and confirm DNS logs are flowing into the platform. *** --- # 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.threatdefence.com/siem-integrations/dns-security/cloudflare-dns.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.