# US 2023/0054097 A1 · Obtaining device posture of a third party managed device > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2023/0054097 A1 - Document ID: US20230054097A1 - Status: Published application - Kind: A1 - Application number: 17/881,493 - Filed: 2022-08-04 - Published: 2023-02-23 - Earliest claimed: 2019-09-12 - Assignees: Mobileiron, Inc. - Applicants: Mobileiron, Inc. - Inventors: Suresh Kumar Batchu; Mohammad Aamir - Web page: https://patentgrep.com/patent/US20230054097A1 ## CPC - G06K 7/1417: {2D bar codes} - H04W 12/77: Graphical identity - H04L 63/067: {using one-time keys (cryptographic mechanisms or cryptographic arrangements for generation of one-time passwords H04L9/0863)} - H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)} - H04L 63/0838: {using one-time-passwords} - H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication - H04W 12/043: using a trusted network node as an anchor - H04W 12/069: using certificates or pre-shared keys - H04W 12/71: Hardware identity - H04W 60/04: using triggered events - G06K: GRAPHICAL DATA READING (image or video recognition or understanding G06V); PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Techniques are disclosed to obtain device posture of a third party managed device. In various embodiments, a unique identifier of the third party managed device is embedded in a registration communication sent from a third party managed device to an access node associated with a first party management entity. The registration communication is sent from the third party managed device to the access node. The access node is configured to store data associating the unique identifier with the third party managed device, and to use the unique identifier to obtain from the third party management entity device posture information for the third party managed device. ## Claims ### Claim 1 A system, comprising: a communication interface; and a processor coupled to the communication interface and configured to: embed in a registration communication sent from a third party managed device configured to be managed by a third party management entity to an access node associated with a first party management entity a unique identifier of the third party managed device; send the registration communication sent from the third party managed device to the access node; and publish a management agent of the third party managed devices as an authenticator upon successful completion of a registration process with which the registration communication is associated; wherein the access node is configured to store data associating the unique identifier with the third party managed device, and to use the unique identifier to obtain from the third party management entity device posture information for the third party managed device. ### Claim 2 (depends on 1) The system of claim 1, wherein the registration communication comprises a Fast Identity Online (FIDO) registration response. ### Claim 3 (depends on 1) The system of claim 1, wherein the registration communication sent from the third party managed device to the access node associated with the first party management entity is sent at least in part in response to a registration challenge sent to the third party managed device at least in part in response to a communication received by the access node from a first party managed device associated with the first party management entity. ### Claim 4 (depends on 3) The system of claim 3, wherein the third party managed device is configured to send the communication at least in part in response to user input. ### Claim 5 (depends on 4) The system of claim 4, wherein the user input comprises scanning a QR or other code displayed on a display comprising the third party managed device. ### Claim 6 (depends on 4) The system of claim 4, wherein QR or other code encodes information that includes a session identifier. ### Claim 7 (depends on 6) The system of claim 6, wherein the access node is configured to include the session identifier in the registration challenge. ### Claim 8 (depends on 4) The system of claim 4, wherein the third party managed device is paired with the first party managed device via Bluetooth or another protocol, the user input comprises an input entered via the third party managed device, and the communication is sent by the first party managed device at least in part in response to a Bluetooth or other communication sent by the third party managed device to the first party managed device at least in part in response to the user input. ### Claim 9 (depends on 8) The system of claim 8, wherein the Bluetooth or other communication includes a session identifier. ### Claim 10 (depends on 1) The system of claim 1, wherein the processor is configured to embed the unique identifier of the third party managed device in the registration communication at least in part by installing on the third party managed device a management agent associated with the first party management entity. ### Claim 11 (depends on 1) The system of claim 1, wherein the registration communication includes a one-time access (OTA) token sent by the access node to the third party managed device in response to a communication received from a first party managed device associated with a same user with which the third party managed device is associated. ### Claim 12 (depends on 1) The system of claim 1, wherein the access node is configured to store the data associating the unique identifier with the third party managed device in a user record associated with the third party managed device. ### Claim 13 (depends on 1) The system of claim 1, wherein the unique identifier is included in a client data portion or field of the registration communication. ### Claim 14 (depends on 1) The system of claim 1, wherein the unique identifier comprises a physical address. ### Claim 15 (depends on 14) The system of claim 14, wherein the physical address comprises a MAC address. ### Claim 16 A method, comprising: embedding in a registration communication sent from a third party managed device configured to be managed by a third party management entity to an access node associated with a first party management entity a unique identifier of the third party managed device; sending the registration communication sent from the third party managed device to the access node; and publish a management agent of the third party managed devices as an authenticator upon successful completion of a registration process with which the registration communication is associated; wherein the access node is configured to store data associating the unique identifier with the third party managed device, and to use the unique identifier to obtain from the third party management entity device posture information for the third party managed device. ### Claim 17 (depends on 16) The method of claim 16, wherein the unique identifier comprises a MAC or other physical address. ### Claim 18 (depends on 16) The method of claim 16, wherein the registration communication sent from the third party managed device to the access node associated with the first party management entity is sent at least in part in response to a registration challenge sent to the third party managed device at least in part in response to a communication received by the access node from a first party managed device associated with the first party management entity. ### Claim 19 (depends on 18) The method of claim 18, wherein the first party managed device is configured to send the communication at least in part in response to user input. ### Claim 20 A computer program product embodied in a non-transitory computer readable medium, the computer program product comprising computer instructions for: embedding in a registration communication sent from a third party managed device configured to be managed by a third party management entity to an access node associated with a first party management entity a unique identifier of the third party managed device; sending the registration communication sent from the third party managed device to the access node; and publish a management agent of the third party managed devices as an authenticator upon successful completion of a registration process with which the registration communication is associated; wherein the access node is configured to store data associating the unique identifier with the third party managed device, and to use the unique identifier to obtain from the third party management entity device posture information for the third party managed device.