# US 11,308,201 B2 · MDM-based persistent security monitoring > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,308,201 B2 - Document ID: US11308201B2 - Status: Granted - Kind: B2 - Application number: 16/782,695 - Filed: 2020-02-05 - Published: 2020-08-06 - Granted: 2022-04-19 - Earliest claimed: 2019-02-05 - Assignees: Sennco Solutions, Inc. - Applicants: Sennco Solutions, Inc. - Inventors: Brian Peacock; Dale R. Liff; Stephen M. Strom; George Liff - Web page: https://patentgrep.com/patent/US11308201B2 ## CPC - G06F 21/51: at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability - H04L 63/1408: {by monitoring network traffic (monitoring network traffic per se H04L43/00)} - G06F 21/54: by adding security routines or objects to programs - G06F 21/554: {involving event detection and direct action} - G06F 21/57: Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities - G06F 21/88: Detecting or preventing theft or loss - H04W 12/122: Counter-measures against attacks; Protection against rogue devices - H04W 12/37: Managing security policies for mobile devices or for controlling mobile applications - G06F 2221/2151: Time stamp - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A method of establishing security monitoring functionality on a device on retail display includes obtaining, by a processor of a server computer, a mobile device management (MDM) startup message from the device, determining, by the processor, whether the device is enrolled for MDM supervision, and if the device is enrolled for the MDM supervision, downloading, by the processor to the device, configuration data to support the MDM supervision and implementation of the security monitoring functionality. ## Claims ### Claim 1 A method of establishing security monitoring functionality on a device on retail display, the method comprising: obtaining, by a processor of a server computer, a mobile device management (MDM) startup message from the device; determining, by the processor, whether the device is enrolled for MDM supervision; and when the device is enrolled for the MDM supervision, downloading, by the processor to the device, configuration data to support the MDM supervision and implementation of the security monitoring functionality; wherein the configuration data comprises instructions of a non-persistent security monitoring application on the device, the non-persistent securing monitoring application being configured to monitor the device for a security trigger event, and wherein persistence of the security monitoring functionality is established despite the non-persistent security monitoring application via operation of the device in a supervised mode in accordance with the MDM supervision. ### Claim 2 (depends on 1) The method of claim 1, wherein the configuration data comprises instructions of an MDM agent on the device, the MDM agent being configured to cause the device to enter into a locked state upon receipt of a command from the server computer. ### Claim 3 (depends on 1) The method of claim 1, wherein the non-persistent security monitoring application is further configured to communicate with a further server computer to indicate that the non-persistent security monitoring application is operational. ### Claim 4 (depends on 1) The method of claim 1, wherein the non-persistent security monitoring application is further configured to provide a single-application mode in which the device resides in response to an MDM command from the server computer to enter a locked state. ### Claim 5 (depends on 1) The method of claim 1, wherein the device is configured to enable remote supervision via data stored in persistent memory, the data leading to the device sending the MDM startup message. ### Claim 6 (depends on 5) The method of claim 5, wherein the data causes the device to contact an enrollment service, the enrollment service identifying the server computer as an MDM service for the device. ### Claim 7 (depends on 1) The method of claim 1, further comprising: determining, by the processor, whether the device has previously been provided with the MDM supervision by the server computer; when the device has not been previously provided with the MDM supervision, adding, by the processor, the device to an MDM service list of the server computer; and when the device has been previously provided with the MDM supervision, directing the device to enter into a locked mode after downloading the configuration data. ### Claim 8 (depends on 1) The method of claim 1, wherein obtaining the MDM startup message occurs while the device is implementing a boot sequence. ### Claim 9 (depends on 1) The method of claim 1, wherein obtaining the MDM startup message comprises receiving the MDM startup message from the device. ### Claim 10 A method of establishing security monitoring functionality on a device on retail display, the method comprising: obtaining, by a processor of a server computer, a mobile device management (MDM) startup message from the device, the MDM startup message being sent by the device as a result of a boot sequence implemented by the device; determining, by the processor, whether the device is enrolled for MDM supervision; and when the device is enrolled for the MDM supervision, downloading, by the processor to the device, configuration data to support the MDM supervision and implementation of the security monitoring functionality; wherein the configuration data comprises instructions of a non-persistent security monitoring application on the device, the non-persistent securing monitoring application being configured to monitor the device for a security trigger event, and wherein persistence of the security monitoring functionality is established despite the non-persistent security monitoring application via operation of the device in a supervised mode in accordance with the MDM supervision. ### Claim 11 (depends on 10) The method of claim 10, wherein the configuration data comprises instructions of an MDM agent on the device, the MDM agent being configured to cause the device to enter into a locked state upon receipt of a command from the server computer. ### Claim 12 (depends on 10) The method of claim 10, wherein the non-persistent security monitoring application is further configured to communicate with a further server computer to indicate that the non-persistent security monitoring application is operational. ### Claim 13 (depends on 10) The method of claim 10, wherein the non-persistent security monitoring application is further configured to provide a single-application mode in which the device resides in response to an MDM command from the server computer to enter a locked state. ### Claim 14 (depends on 10) The method of claim 10, wherein the device is configured to enable remote supervision via data stored in persistent memory, the data leading to the device sending the MDM startup message. ### Claim 15 (depends on 14) The method of claim 14, wherein the data causes the device to contact an enrollment service, the enrollment service identifying the server computer as an MDM service for the device. ### Claim 16 (depends on 10) The method of claim 10, further comprising: determining, by the processor, whether the device has previously been provided with the MDM supervision by the server computer; when the device has not been previously provided with the MDM supervision, adding, by the processor, the device to an MDM service list of the server computer; and when the device has been previously provided with the MDM supervision, directing the device to enter into a locked mode after downloading the configuration data. ### Claim 17 A system for establishing security monitoring functionality for a device on retail display, the system comprising: a memory on which security provisioning instructions and mobile device management (MDM) instructions are stored; and a processor configured to execute the MDM instructions to implement a MDM service for the device; wherein the processor is configured via execution of the security provisioning instructions to—obtain a mobile device management (MDM) startup message from the device; determine whether the device is enrolled for MDM supervision; and when the device is enrolled for the MDM supervision, download configuration data to support the MDM supervision and implementation of the security monitoring functionality, wherein the configuration data comprises instructions of a non-persistent security monitoring application on the device, the non-persistent securing monitoring application being configured to monitor the device for a security trigger event, and wherein persistence of the security monitoring functionality is established despite the non-persistent security monitoring application via operation of the device in a supervised mode in accordance with the MDM supervision. ### Claim 18 (depends on 17) The system of claim 17, wherein: the processor is configured via execution of the security provisioning instructions to determine whether the device has previously been provided with the MDM supervision; and the processor is configured via execution of the MDM instructions to direct the device to enter into a locked mode after the configuration data is downloaded when the device has been previously provided with the MDM supervision.