# US 10,482,272 B2 · System and method for receiving user data using a data entry mechanism activated for an application > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,482,272 B2 - Document ID: US10482272B2 - Status: Granted - Kind: B2 - Application number: 16/248,862 - Filed: 2019-01-16 - Published: 2019-05-16 - Granted: 2019-11-19 - Earliest claimed: 2015-02-20 - Assignees: AO Kaspersky Lab - Applicants: AO Kaspersky Lab - Inventors: Konstantin M. Filatov; Alexey P. Komissarov; Victor V. Yablokov; Olga O. Inozemtseva - Web page: https://patentgrep.com/patent/US10482272B2 ## CPC - G06F 21/62: Protecting access to data via a platform, e.g. using keys or access control rules - G06F 21/31: User authentication - G06F 21/51: at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability - 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 2221/031: Protect user input by software means - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Disclosed are systems and methods for receiving user input using a data entry mechanism activated for an application. An example method comprises detecting, by a hardware processor, an activity state of the application during an execution of the application on a user device, determining security requirements associated with the activity state, wherein the security requirements comprise properties for the data entry mechanism, selecting a data entry mechanism corresponding to the determined security requirements associated with the activity state, activating the selected data entry mechanism for receiving user input for the application, wherein the selected data entry mechanism is governed according to the properties of the security requirements associated with the activity state, receiving the user input in accordance with the activated data entry mechanism, and displaying a modified version of the user input according to the properties of the security requirements. ## Claims ### Claim 1 A method for receiving user input using a data entry mechanism activated for an application, the method comprising: detecting, by a hardware processor, an activity state of the application during an execution of the application on a user device; determining, by the hardware processor, security requirements associated with the activity state, wherein the security requirements comprise properties for the data entry mechanism; selecting, by the hardware processor, a data entry mechanism corresponding to the determined security requirements associated with the activity state; activating, by the hardware processor, the selected data entry mechanism for receiving user input for the application, wherein the selected data entry mechanism is governed according to the properties of the security requirements associated with the activity state; receiving, by the hardware processor, the user input in accordance with the activated data entry mechanism; and displaying, by the hardware processor, a modified version of the user input according to the properties of the security requirements. ### Claim 2 (depends on 1) The method of claim 1, wherein the selection of the data entry mechanism includes determining one or more of: a data entry device, a data entry field, an interface for transmission of data from the data entry device to the data entry field, a mechanism for storing entered data on the data entry device and the application, a mechanism for displaying the entered data in the data entry field, a mechanism for checking an integrity of the entered data, a mechanism for checking an integrity of the application, an interface for transmission of the entered data to the application, and an interface for transmission of the entered data to an external device. ### Claim 3 (depends on 2) The method of claim 2, wherein the determination of the data entry field includes determining one or more of: ready-made classes, procedures, functions, and constants to be provided to the application. ### Claim 4 (depends on 1) The method of claim 1, wherein the security requirements further comprise requirements for using an integrity check of the application. ### Claim 5 (depends on 1) The method of claim 1, wherein the properties of the security requirement indicate a form of entered characters, the form of entered characters comprising one or more of obfuscated characters and blank characters, and wherein a variable order of characters in the data entry mechanism changes after successive character entries. ### Claim 6 (depends on 1) The method of claim 1, wherein the security requirements include one or more of static security requirements and dynamic security requirements. ### Claim 7 (depends on 6) The method of claim 6, wherein static security requirements are specified during a creation of the application, and dynamic security requirements and associated data entry mechanisms are specified by a third-party security application during the execution of the application. ### Claim 8 A system for receiving user input using a data entry mechanism activated for an application, the system comprising: a user device, which is in a particular activity state during an execution of an application; and a hardware processor configured to: detect the activity state of the application; determine security requirements associated with the activity state, wherein the security requirements comprise properties for the data entry mechanism; select a data entry mechanism corresponding to the determined security requirements associated with the activity state; activate the selected data entry mechanism for receiving user input for the application, wherein the selected data entry mechanism is governed according to the properties of the security requirements associated with the activity state; receive the user input in accordance with the activated data entry mechanism; and display a modified version of the user input according to the properties of the security requirement. ### Claim 9 (depends on 8) The system of claim 8, wherein the configuration for the selection of the data entry mechanism includes a configuration for determining one or more of: a data entry device, a data entry field, an interface for transmission of data from the data entry device to the data entry field, a mechanism for storing entered data on the data entry device and the application, a mechanism for displaying the entered data in the data entry field, a mechanism for checking an integrity of the entered data, a mechanism for checking an integrity of the application, an interface for transmission of the entered data to the application, and an interface for transmission of the entered data to an external device. ### Claim 10 (depends on 9) The system of claim 9, wherein the determination of the data entry field includes determining one or more of: ready-made classes, procedures, functions, and constants to be provided to the application. ### Claim 11 (depends on 8) The system of claim 8, wherein the security requirements further comprise requirements for using an integrity check of the application. ### Claim 12 (depends on 8) The system of claim 8, wherein the properties of the security requirement indicate a form of entered characters, the form of entered characters comprising one or more of obfuscated characters and blank characters and wherein a variable order of characters in the data entry mechanism changes after successive character entries. ### Claim 13 (depends on 8) The system of claim 8, wherein the security requirements include one or more of static security requirements and dynamic security requirements. ### Claim 14 (depends on 13) The system of claim 13, wherein the static security requirements are specified during a creation of the application, and the dynamic security requirements and associated data entry mechanisms are specified by a third-party security application during the execution of the application. ### Claim 15 A non-transitory computer readable medium storing instructions thereon, that when executed perform a method for receiving a user input using a data entry mechanism activated for an application, the method comprising: detecting, by a hardware processor, an activity state of the application during an execution of the application on a user device; determining, by the hardware processor, security requirements associated with the activity state, wherein the security requirements comprise properties for the data entry mechanism; selecting, by the hardware processor, a data entry mechanism corresponding to the determined security requirements associated with the activity state; activating, by the hardware processor, the selected data entry mechanism for receiving user input for the application, wherein the selected data entry mechanism is governed according to the properties of the security requirements associated with the activity state; receiving, by the hardware processor, the user input in accordance with the activating data entry mechanism; and displaying, by the hardware processor, a modified version of the user input according to the properties of the security requirement. ### Claim 16 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the selection of the data entry mechanism includes determining one or more of: a data entry device, a data entry field, an interface for transmission of data from the data entry device to the data entry field, a mechanism for storing entered data on the data entry device and the application, a mechanism for displaying the entered data in the data entry field, a mechanism for checking an integrity of the entered data, a mechanism for checking an integrity of the application, an interface for transmission of the entered data to the application, and an interface for transmission of the entered data to an external device. ### Claim 17 (depends on 16) The non-transitory computer readable medium of claim 16, wherein the determination of the data entry field includes determining one or more of: ready-made classes, procedures, functions, and constants to be provided to the application. ### Claim 18 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the security requirements further comprise requirements for using an integrity check of the application. ### Claim 19 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the properties of the security requirement indicate a form of entered characters, the form of entered characters comprising one or more of obfuscated characters and blank characters and wherein a variable order of characters in the data entry mechanism changes after successive character entries. ### Claim 20 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the security requirements include one or more of static security requirements and dynamic security requirements.