> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/alarm-zones/use-alarm-zones-for-perimeter-security.md).

# Use alarm zones for perimeter security

Configure perimeter members, responses, and safe arming.

## Use alarm zones for perimeter security

Perimeter sensors are alarm-zone members. These include Z20 vibration sensors, fence energiser zones, and gate tampers.

A typical site uses:

* One default alarm zone per controller for general access-control items.
* Dedicated perimeter alarm zones for fence and gate devices.
* Perimeter action plans for breach response and escalation.

Use a perimeter-specific action plan. It can instruct operators to call patrol, escalate to the SOC, and capture CCTV. Generic door-alarm responses do not provide enough context.

### Avoid common mistakes

1. Attach every door, reader, and tamper input to an alarm zone.
2. Keep every alarm zone on one controller.
3. Use **Fail to arm** for perimeter zones unless an exception is justified.
4. Provide manual override for schedule-controlled zones.

For monitoring integration, the alarm-zone Group Identifier maps to alarm transmission. See [Alarm Transmission - Monitoring](/knowledge-hub/products/cc-software/configure/alarm-transmission/alarm-transmission-monitoring.md).

### Related scenarios

* [Test alarm zones](/knowledge-hub/products/cc-software/configure/configuration-scenarios/scenario-alarm-zone-testing.md).
* [Stop door-open-too-long alarms](/knowledge-hub/products/cc-software/configure/configuration-scenarios/scenario-stopping-the-door-open-too-lo.md).


---

# 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://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/alarm-zones/use-alarm-zones-for-perimeter-security.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.