> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/events-and-notifications/security.md). # Security Alert rules for vehicle and asset security: auto-geofencing, unauthorized movement, car alarm, tracker detach, case intrusion, vibration, and padlock events. The **Security** section covers alert rules that protect vehicles and assets against theft, tampering, and unauthorized access. * [**Auto-geofencing**](/docs/user/guide/events-and-notifications/security/auto-geofencing.md): Auto-creates a geofence around a parked vehicle and alerts if it moves without the ignition on. * [**Bracelet or ankle sensor**](/docs/user/guide/events-and-notifications/security/bracelet-or-ankle-sensor.md): Alerts when a GPS bracelet or ankle sensor is removed without authorization. * [**Car alarm**](/docs/user/guide/events-and-notifications/security/car-alarm.md): Notifies when a vehicle's car alarm triggers, detected through the GPS device's connected input. * [**Case intrusion**](/docs/user/guide/events-and-notifications/security/case-intrusion.md): Alerts when the GPS device's case is opened or tampered with. * [**Locking and unlocking padlock**](/docs/user/guide/events-and-notifications/security/lockingunlocking-padlock.md): Notifies when a GPS-enabled smart lock is locked or unlocked. * [**Tracker detach**](/docs/user/guide/events-and-notifications/security/tracker-detach.md): Alerts when a GPS device is removed from the vehicle or asset it monitors. * [**Unauthorized movement**](/docs/user/guide/events-and-notifications/security/unauthorized-movement.md): Alerts when a stationary vehicle starts moving without authorization. * [**Vibration sensor**](/docs/user/guide/events-and-notifications/security/vibration-sensor.md): Detects continuous vibrations on a parked vehicle via the GPS device's accelerometer. --- # 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://navixy.com/docs/user/guide/events-and-notifications/security.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.