Secure forensic data collection on mobile devices
AssigneeModeOne Technologies Inc.
InventorsMatthew Rasmussen, Jason Purviance, Ryan Frye, William Baldisser
Life of this patent
Estimating the term…
Abstract
Embodiments of the inventive subject matter are directed to systems and methods designed to facilitate data collection from a target device. By installing software on a target device and then granting that application system-level access to the target device, embodiments of the inventive subject matter can safely, and cryptographically securely, grant access to files on the target device via uniquely generated uniform resource locators.
Claims16
A method of data collection, comprising the steps of:
- presenting, on a first device, a dialogue requesting user permission for privileged file system access;
- in response to receiving the user permission, sending, by the first device, a request to a server for generation of a handshake token;
- receiving, on the first device, the handshake token generated by the server;
- displaying, on the first device, the handshake token;
- presenting, on a second device, a request to input the handshake token;
- wherein the first device is separate from the second device;
- authenticating an associated session using the handshake token;
- determining, on the first device, available data collection sources;
- presenting, on the second device, a user-interface to select one or more data sources for collection from the first device;
- determining, on the first device, a count and size of files associated with the one or more data sources;
- generating a cryptographically signed token;
- generating a first uniform-resource locator using the cryptographically signed token and using a first file identifier;
- on the first device, using the first uniform-resource locator, sending to the server a second file identifier and data associated with the second file identifier;
- and
- validating, on the server, that the second file identifier matches the first file identifier.
A method data collection from a target device, comprising the steps of:
- receiving user permission for privileged file system access on the target device;
- sending, by the target device to a server, a handshake token request;
- receiving, by the target device, a handshake token generated by the server in response to the handshake token request;
- receiving, by the target device, a message indicating authentication of a session based on the handshake token;
- determining, on the target device, available data collection sources;
- receiving, by the target device, a selection of data collection sources from the server;
- receiving, by the target device, a first uniform-resource locator generated by the server using a cryptographically signed token;
- on the target device, using the first uniform-resource locator, sending to the server a first file identifier and data associated with a second file identifier;
- and
- receiving, on the target device, a message from the server indicating that the second file identifier matches the first file identifier.
A method data collection from a target device, comprising the steps of:
- receiving user permission for privileged file system access on the target device;
- sending, by the target device to a server, a handshake token request;
- receiving, by the target device, a handshake token generated by the server in response to the handshake token request;
- authenticating, on a second device, a session using the handshake token;
- wherein the target device is separate from the second device;
- presenting, on the second device, a user-interface to select one or more data collection sources for collection on the target device;
- generating, by the server, a first uniform-resource locator using a cryptographic token and a first file identifier;
- on the first device, using the first uniform-resource locator, sending to the server a second file identifier and data associated with the second file identifier;
- and
- validating, on the server, that the second file identifier matches the first file identifier.
Dependencies are inferred from the claim text.