> 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/case-intrusion.md). # Case intrusion The **Case intrusion** rule is designed for GPS devices that support an alert when the device's case is tampered with or opened, ensuring that you are immediately notified of any unauthorized access to your devices. This rule is vital for enhancing the security and protection of valuable cargo during transit or storage. By using GPS devices equipped with the **Case intrusion** rule, you can add an extra layer of security to safeguard your assets. ## Rule settings This rule is entirely dependent on the device's capabilities and hardware configuration. There are no specific settings to configure within the rule itself. For common settings, see [Rules and alerts](/docs/user/guide/events-and-notifications.md). ## System operation details * **Reset timer.** The **Case intrusion** alert has a 1-minute reset timer, meaning the alert doesn't trigger more often than once every minute. If an event occurs during the reset period, it is omitted from the Navixy platform, including in reports. * **Multiple devices.** You can select multiple GPS devices that trigger notifications when a tampering event occurs. The only requirement is that the selected GPS devices must support Tamper Detection events and have this feature integrated into the platform. * **GPS-independent event alert.** This rule operates independently of GPS coordinates. If the platform receives a tampering event from a GPS device without valid GPS data, the event is still counted as valid and displayed, regardless of whether it occurred inside or outside of a geofence. In such cases, the Inside/Outside radio button settings for geofences are ignored to ensure that potentially critical events are not missed. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://navixy.com/docs/user/guide/events-and-notifications/security/case-intrusion.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.