> 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/configuration-client/site-installation/access-zones/configuring-strict-anti-tailigating.md).

# Configuring Strict Anti-tailigating

### Introduction

The ‘Strict Anti-tailgating’ feature enables sites to disallow cardholders to exit from a zone if they are not recorded as having entered the zone.

### Procedure

1. Click **Configure** from the menu bar, then **Access Zones**.

   The **Access Zone** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. Highlight the Access Zone you want to enforce strict anti-tailgating for.
3. **Right click** and select **Properties**.
4. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a9544e401e969fee6df1a671798f3e69c85aded4%2Faczone_advanced.png?alt=media)
5. Check the **Check for tailgating on exit from zone** checkbox.

   The **Strict Anti-tailgating enforcement** and **Use single Controller** checkboxes become enabled and a new **Anti-passback** tab appears.

   The Controller will maintain an "out of zone" list of Cardholders for the Access Zone. If the Access Zone is part of an Access Zone Group, then only one "out of zone" list is maintained for the Master Zone of the Access Zone Group.

   **Note:** While this is configured here on the Access Zone, the anti-tailgating response is configured on the Access Group.
6. Check the **Strict Anti-tailgating enforcement** checkbox.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2d0509b5d96e9d9a38a42df695dac19b36f46783%2Fstrictantitailgating.png?alt=media)

   While the **Check for tailgating on exit from zone** option only disallows exit if someone has already exited, the **Strict Anti-tailgating enforcement** option disallows exit for anyone who is not recorded as having entered. To achieve this, it persists the list of who is in the zone (Controller 6000 and 7000 variants).

   The list is also persisted for anti-passback (Controller 6000 and 7000 variants), so with Controller restarts it no longer forgets that the cardholder has already entered. Zone counts are also persisted (Controller 6000 and 7000 variants), so with Controller restarts the zone count will not be set back to zero, and outputs triggered by different zone count states will remain in the same state as prior to the restart. If you have anti-passback enabled for a while and then turn on anti-tailgating, it should work as intended straight away because it will have already tracked who is in the zone. However, make sure you do not turn that off, apply, and then turn on strict anti-tailgating, because the instant you apply changes with them off, the persistence will be cleared.

   Hence upon enabling the option, anyone already in the zone may be denied exit. To mitigate this issue, you can do any of the following:

   * Turn on anti-passback for perhaps a day first, so that it can work out who is in the zone (as it uses the same list), OR
   * Only turn the option on at a time when the zone is empty, OR
   * Change the anti-tailgating response on Access Groups to the "No action" or "Log an event" setting, until say about one day has passed, before changing it back again. This is the least preferable option as you would have to change all access groups that grant access into that zone.

   **Note:** The controller persistence list is cleared by turning off anti-passback and strict anti-tailgating. There is no need to turn off standard anti-tailgating.
7. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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/configuration-client/site-installation/access-zones/configuring-strict-anti-tailigating.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.
