> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/enterprise-guide/event-reporting/firewall.md).

# Firewall Configuration

Ingress Requirements for direct SIEM push

For customers who are receiving inbound events and Automator device approval requests from the Keeper production environment, restrict inbound traffic to only accept connections from the following IP addresses:

### **US / Global**

* **34.194.242.137/32**
* **18.235.39.229/32**
* **54.208.20.102/32**
* **34.203.159.189/32**

### **EU / Dublin**

* **54.246.149.209/32**
* **34.250.37.43/32**
* **52.210.163.45/32**
* **54.246.185.95/32**

### **AU / Sydney**

* **54.206.253.126/32**
* **3.104.102.101/32**
* **3.106.40.41/32**
* **54.206.208.132/32**

### **US / GovCloud**

* **18.253.101.55/32**
* **18.253.102.58/32**
* **18.252.135.74/32**
* **18.253.212.59/32**

### **CA / Canada Hosted Customers**

* **35.182.155.224/32**
* **35.182.216.11/32**
* **15.223.136.134/32**

### **JP / Tokyo Hosted Customers**

* **35.74.131.237/32**
* **54.150.11.204/32**
* **52.68.53.105/32**

After external logging is established, it might be automatically put on pause if the external system becomes unavailable and number of events in the queue reaches a threshold of 50. If this happens, you will have to manually resume the external logging after correcting the issue. We recommend setting up an alert for the "Paused Audit Log Sync" event so you get notified if the external logging is paused.


---

# 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.keeper.io/enterprise-guide/event-reporting/firewall.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.