> 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/content-security/cloudflare.md). # CloudFlare ThreatDefence integrates with **Cloudflare** to ingest security logs and events for monitoring, detection, and incident response.\ This integration provides visibility into DNS queries, WAF activity, DDoS mitigation, and Zero Trust events. *** ## Integration Method Cloudflare log delivery is supported through **AWS SQS (Simple Queue Service)**.\ Logs are pushed by Cloudflare into an AWS SQS queue, which ThreatDefence then consumes securely 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 **Logpush** enabled. * Access to an AWS account to configure **SQS queues**. * Cloudflare account with sufficient permissions to configure **Logpush jobs**. * ThreatDefence-provided instructions for SQS subscription and integration verification. *** ## Next Steps 1. Configure Cloudflare **Logpush** to deliver events into your AWS SQS queue. 2. Ensure the queue is configured according to the [AWS SQS integration steps](/siem-integrations/public-cloud/aws-sqs.md). 3. Send the queue details (ARN, region, and access keys if applicable) to 📧 ****. 4. ThreatDefence engineers will validate ingestion and confirm visibility of Cloudflare events. *** --- # 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/content-security/cloudflare.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.