Remote permissions monitoring and control
A security application may monitor applications attempting to be installed on a user device. In one example, various steps may include at least one of: receiving an application access operation on a computing device, identifying at least one application action associated with the application access operation, retrieving an application security profile stored in memory, identifying at least one application security restriction in the application security profile related to the at least one application action, restricting the at least one application action from occurring based on the at least one application security restriction and notifying a pre-registered device responsive to restricting the at least one application action.
Latest IBM Patents:
This application relates to application blocking and more particularly to retrieving a security profile that is used to determine whether to permit an application install on a computing device or notify a third party regarding a status related to the application.
BACKGROUNDApplications with requirements can overwhelm a user of a computing device. For example, downloading an application may trigger a request for multiple permissions to be accepted. A user may not be aware of the ramifications of permitting such an action to occur during an installation procedure.
During an application access operation or install procedure, the application may seek access to various controls, permissions and other features of a user's device and profile causing security and privacy issues. The various requests instantiated during an application may not be handled properly due to the amount of information or number of requests presented by the application.
SUMMARYOne example embodiment may include a method that includes at least one of receiving an application access operation on a computing device, identifying at least one application action associated with the application access operation, retrieving an application security profile stored in memory, identifying at least one application security restriction in the application security profile related to the at least one application action, restricting the at least one application action from occurring based on the at least one application security restriction and notifying a pre-registered device responsive to restricting the at least one application action.
Another example embodiment may include an apparatus that includes a receiver configured to receive an application access operation and a processor configured to perform at least one of identify at least one application action associated with the application access operation, retrieve an application security profile stored in memory, identify at least one application security restriction in the application security profile related to the at least one application action, restrict the at least one application action from occurring based on the at least one application security restriction, and notify a pre-registered device responsive to restricting the at least one application action.
Yet another example embodiment may include a non-transitory computer readable storage medium configured to store instructions that when executed causes a processor to perform at least one of receiving an application access operation on a computing device, identifying at least one application action associated with the application access operation, retrieving an application security profile stored in memory, identifying at least one application security restriction in the application security profile related to the at least one application action, restricting the at least one application action from occurring based on the at least one application security restriction, and notifying a pre-registered device responsive to restricting the at least one application action.
It will be readily understood that the instant components, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of at least one of a method, apparatus, and system, as represented in the attached figures, is not intended to limit the scope of the application as claimed, but is merely representative of selected embodiments.
The instant features, structures, or characteristics as described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, the usage of the phrases “example embodiments”, “some embodiments”, or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment. Thus, appearances of the phrases “example embodiments”, “in some embodiments”, “in other embodiments”, or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
In addition, while the term “message” may have been used in the description of embodiments, the application may be applied to many types of network data, such as, packet, frame, datagram, etc. The term “message” also includes packet, frame, datagram, and any equivalents thereof. Furthermore, while certain types of messages and signaling may be depicted in exemplary embodiments they are not limited to a certain type of message, and the application is not limited to a certain type of signaling.
Example embodiments provide an application and/or software procedure which identifies potential risks and determines whether to block, pause, and/or request third party approval for a particular application install on a particular device. One example procedure may include an extension to a computer program on a mobile device that manages the installation of applications, the extensions may utilize a central profile linked to the mobile device, and the extended function cross-references a profile against access requested by the to-be-installed application. The profile may be stored on a remote server, the device or a third party device linked to the device based on the permissions setup by the third party, such as a parent, guardian or security service which is setup to protect the device from malicious or unwanted application access.
The application installation can be delayed (paused) or prevented altogether until approved by the designated third party as defined in the setup user profile for that device. The security application of the example embodiments may be a relatively small sized application (i.e., memory requirements) and may be installed to operate in the background processes with no visible interface or indicators. In general, the application will not be readily removable or may be password protected to prevent installation by a child or subject who is being monitored by a third party for safety and concern purposes. Anytime an application installation, modification and/or update operation is attempting to be performed on a monitored device, the application may retrieve the specific profile settings to ensure the application is not attempting to access information specifically being monitored by the user profile settings. For example, the user profile may prohibit photos and other media, location services and personal information from being shared with any application access operations unless specific permission has been authorized by a third party device. However, the various other settings and permissions requested by an application during an installation may be permissible and would not invoke a notification being created and sent to the designated third party.
In the example of
The customized user profile stored in memory (described herein) may have one or more of the permissions flagged as requiring approval from the third party who setup the profile including the action(s) to be performed. For example, an action sequence may be performed to include one or more of: 1) block installation(s), 2) create and send notification(s) with application name(s), permission(s) currently flagged, 3) approval request option (i.e., button to respond and approve or deny), etc. The action sequence can be customized to display the flagged information and any information the third party user may require prior to overriding the security measure and permitting the monitored user to complete the installation.
In operation, the user phone 210 contacts the application store 222 across the network 212 and another installation mechanism may attempt to load the application pre-installation menu which identifies the amount of memory the application will require and/or the permissions/requirements requested or needed in order to enable the installation 232. The install applet or package/module/software currently operating on the phone may inspect all the information the application is seeking to access and then retrieve the user profile for that device 210 from an internal memory, a remote server and/or the third party device 220 and/or 230. The information about the access operation (i.e., list of permissions) is matched against the information in the profile. If the access is a positive match, for example, access to a module and/or a function (such as a camera) is part of the application permissions requested and if that is one of the audited items in the profile list, then the action(s) to be performed are retrieved as well. These action can include examples such as ‘gain permission from a secondary party’ or ‘pop up to warn before installing’ or ‘deny the installation of the app after presenting a pop up on why the app is being denied’, etc. If any of the actions require permission from the third party, the interested parties 220 and/or 230 identified in the profile by name, number, status (i.e., parent, guardian), are then notified. The notifications 234 and/or 236 are sent accordingly to notify and request permission to proceed. The third parties may have certain statuses, such as senior or junior where one party can grant permission at a junior status but the senior party can override that decision within a predetermined period of time, for example. Otherwise the junior party's permission may be enacted and the application may be installed thereafter without requiring communication from the senior party.
In the event that there is no match between requested permissions and monitored permissions within the user profile, then the information is sent back to permit the install to proceed, and the application is installed accordingly. If there is a match on the access function but the action is to warn, then the information is sent back to the device and a menu may be provided to require explicit permission. In this case, the user takes an overt action to allow or enact the install via one or more of: by speaking into their device, selecting a menu option or any other known affirmation procedure, and the access and installation can then proceed.
In the event that there is a match and the action is a secondary approval then a notification or message (such as an SMS) can be sent to the secondary phone(s) and the user either approves the install or does not approve the install. The information is then sent back to the original application install phone 210. The phone application (or an off-board process communicably coupled to the phone) inspects what is received from the message contents. If the secondary control says to not install, an alert is received (optionally) and no install is permitted. If an install is permitted, then the application is installed. This can also be set up by having the user profile resident on the phone and locked so the application and profile cannot be removed. When enabled on the device, the modified ‘store’ applet or package/module/software would scan for access to certain functions (e.g., camera usage, access to address book, access to photos, etc.). If unauthorized functionality was requested, approval would be needed by a registered third party. The application could use the same process to warn an adult about giving out access too quickly for applications that they are installing on their own device as security is an issue for anyone, not just children.
One example embodiment may include a system and method for a mobile device to manage the installation of applications based upon access to functions on the mobile device. This example includes a central profile that is linked to the mobile device and which cross-references the user profile against requested to-be-installed application and its requested permissions. The install may be suspended, blocked or delayed until approved by a third party. The factors to be considered in the profile include the resources that an application may request access to being managed by the approver. The installation completes upon approval via an SMS message from the approver or is rejected depending on the contents of the message received back at the device.
In another example embodiment, a method may include at least one of receiving an application access operation on a computing device, identifying at least one application action associated with the application access operation, retrieving an application security profile stored in memory, identifying at least one application security restriction in the application security profile related to the at least one application action, restricting the at least one application action from occurring based on the at least one application security restriction and notifying a pre-registered device responsive to restricting the at least one application action. The receiving the application access operation on the computing device can include receiving an install request message, and each of the application actions are associated with a separate permission response.
The method can further comprise: notifying the pre-registered device by creating a notification based on the at least one application action and transmitting the notification to the pre-registered device, and permitting (optionally automatically) the at least one application action to be performed, and the at least one application action includes at least one of: a download, an install, access to location information, access to contacts, access to an e-mail account, access to an instant message account, access to a social network profile, access to photographs, access to multi-media, and access to documents. The restricting the at least one application action from occurring can prevent an installation of the application from occurring on the computing device.
The embodiments herein may be implemented in hardware, in a computer program executed by a processor, in firmware, or in a combination of the above. A computer program may be embodied on a computer readable medium, such as a storage medium. For example, a computer program may reside in random access memory (“RAM”), flash memory, read-only memory (“ROM”), erasable programmable read-only memory (“EPROM”), electrically erasable programmable read-only memory (“EEPROM”), registers, hard disk, a removable disk, a compact disk read-only memory (“CD-ROM”), or any other form of storage medium known in the art.
An exemplary storage medium may be coupled to the processor such that the processor may read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (“ASIC”). In the alternative, the processor and the storage medium may reside as discrete components. For example,
As illustrated in
Although an exemplary embodiment of at least one of a system, method, and non-transitory computer readable medium has been illustrated in the accompanied drawings and described in the foregoing detailed description, it will be understood that the application is not limited to the embodiments disclosed, but is capable of numerous rearrangements, modifications, and substitutions as set forth and defined by the following claims. For example, the capabilities of the system of the various figures can be performed by one or more of the modules or components described herein or in a distributed architecture and may include a transmitter, receiver or pair of both. For example, all or part of the functionality performed by the individual modules, may be performed by one or more of these modules. Further, the functionality described herein may be performed at various times and in relation to various events, internal or external to the modules or components. Also, the information sent between various modules can be sent between the modules via at least one of: a data network, the Internet, a voice network, an Internet Protocol network, a wireless device, a wired device and/or via plurality of protocols. Also, the messages sent or received by any of the modules may be sent or received directly and/or via one or more of the other modules.
One skilled in the art will appreciate that a “system” could be embodied as a personal computer, a server, a console, a personal digital assistant (PDA), a cell phone, a tablet computing device, a smartphone or any other suitable computing device, or combination of devices. Presenting the above-described functions as being performed by a “system” is not intended to limit the scope of the present application in any way, but is intended to provide one example of many embodiments. Indeed, methods, systems and apparatuses disclosed herein may be implemented in localized and distributed forms consistent with computing technology.
It should be noted that some of the system features described in this specification have been presented as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very large scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, graphics processing units, or the like.
A module may also be at least partially implemented in software for execution by various types of processors. An identified unit of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions that may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module. Further, modules may be stored on a computer-readable medium, which may be, for instance, a hard disk drive, flash device, random access memory (RAM), tape, or any other such medium used to store data.
Indeed, a module of executable code could be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
It will be readily understood that the components of the application, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the detailed description of the embodiments is not intended to limit the scope of the application as claimed, but is merely representative of selected embodiments of the application.
One having ordinary skill in the art will readily understand that the above may be practiced with steps in a different order, and/or with hardware elements in configurations that are different than those which are disclosed. Therefore, although the application has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent.
While preferred embodiments of the present application have been described, it is to be understood that the embodiments described are illustrative only and the scope of the application is to be defined solely by the appended claims when considered with a full range of equivalents and modifications (e.g., protocols, hardware devices, software platforms etc.) thereto.
Claims
1. A method, comprising:
- initiating an install procedure of an application on a computing device;
- detecting application permissions requested by the application from the computing device during the install procedure;
- determining a flag has been set on an application permission from among the detected application permissions based on an application security profile;
- temporarily blocking the install procedure of the application from continuing on the computing device based on the flagged application permission;
- identifying, by a security module installed on the computing device where the application is temporarily blocked, a phone number of a remote user device stored within a security profile of the computing device; and
- transmitting, via a network, a request to the remote user device based on the identified phone number, the request comprising an identification of the flagged application permission and a request for a user input via the remote user device to resume the temporarily blocked install procedure;
- receiving, by the security module installed on the computing device where the application is temporarily blocked, a response from the remote user device indicating whether or not to allow the application to access to the flagged application permission.
2. The method of claim 1, comprising receiving an application access operation on the computing device which comprises receiving an install request message.
3. The method of claim 1, wherein the flagged application permission comprises one or more of permission for in-app purchases and permission to access a contacts list stored on the computing system.
4. The method of claim 1, wherein the transmitting the request comprises transmitting a prompt to a user interface of the remote user device which requests a user input from a guardian.
5. The method of claim 1, wherein the flagged application permission comprises one or more of access to location information, access to contacts, access to an e-mail account, access to an instant message account, access to a social network profile, access to photographs, access to multi-media, and access to documents.
6. The method of claim 1, wherein the method further comprises displaying a list of the detected application permissions requested during the install procedure via a user interface of the computing device.
7. The method of claim 1, wherein the detecting comprises intercepting the application permissions requested by the application via a security module that is installed locally on the computing device.
8. The method of claim 4, wherein the input from the guardian overrides the temporarily blocked install procedure on the computing device.
9. An apparatus, comprising:
- a processor configured to:
- initiate an install procedure of an application on a computing device;
- detect application permissions requested by the application from the computing device daring the install procedure;
- determine a flag has been set on an application permission from among the detected application permissions based on an application security profile;
- temporarily block the install procedure of the application from continuing on the computing device based on the flagged application permission;
- identify, by a security module installed on the computing device where the application is temporarily blocked, a phone number of a remote user device stored within the application security profile; and
- a network interface configured to transmit, via a network, a request to the remote user device based on the identified phone number, the request comprising an identification of the flagged application permission and a request for a user input via the remote user device to resume the temporarily install procedure;
- receiving, by the security module installed on the computing device where the application is temporarily blocked, a response from the remote user device indicating whether or not to allow the application to access to the flagged application permission.
10. The apparatus of claim 9, wherein the processor is further configured to receive an application access operation on the computing device which comprises receipt of an install request message.
11. The apparatus of claim 9, wherein the flagged application permission comprises one or more of permission for in-app purchases and permission to access a contacts list stored on the computing system.
12. The apparatus of claim 9, wherein the request comprises a prompt transmitted to a user interface of the remote user device which requests a user input from a guardian.
13. The apparatus of claim 9, wherein the flagged application permission comprises one or more of access to location information, access to contacts, access to an e-mail account, access to an instant message account, access to a social network profile, access to photographs, access to multi-media, and access to documents.
14. The apparatus of claim 9, wherein the processor is further configured to display a list of the detected application permissions requested during the install procedure via a user interface of the computing device.
15. The apparatus of claim 12, wherein the input from the guardian overrides the temporarily blocked install procedure on the computing device.
16. A non-transitory computer readable storage medium configured to store instructions that when executed causes a processor to perform:
- initiating an install procedure of an application on a computing device;
- detecting application permissions requested by the application from the computing device during the install procedure;
- determining a flag has been set on an application permission from among the detected application permissions based on an application security profile;
- temporarily blocking the install procedure of the application from continuing on the computing device based on the flagged application permission;
- identifying, by a security module installed on the computing device where the application is temporarily blocked, a phone number of a remote user device stored within a security profile of the computing device; and
- transmitting, via a network, a request to the remote user device based on the identified phone number, the request comprising an identification of the flagged application permission and a request for a user input via the remote user device to resume the temporarily blocked install procedure;
- receiving, by the security module installed on the computing device where the application is temporarily blocked, a response from the remote user device indicating whether or not to allow the application to access to the flagged application permission.
17. The non-transitory computer readable storage medium of claim 16, comprising receiving an application access operation on the computing device which comprises receiving an install request message.
18. The non-transitory computer readable storage medium of claim 16, wherein the flagged application permission comprises one or more of permission for in-app purchases and permission to access a contacts list stored on the computing system.
19. The non-transitory computer readable storage medium of claim 16, wherein the transmitting the request comprises transmitting a prompt to a user interface of the remote user device which requests a user input from a guardian.
20. The non-transitory computer readable storage medium of claim 16, wherein the flagged application permission comprises one or more of access to location information, access to contacts, access to an e-mail account, access to an instant message account, access to a social network profile, access to photographs, access to multi-media, and access to documents.
21. The non-transitory computer readable storage medium of claim 19, wherein the input from the guardian overrides the temporarily blocked install procedure on the computing device.
| 7739682 | June 15, 2010 | Badenell |
| 20070204039 | August 30, 2007 | Inamdar |
| 20080120611 | May 22, 2008 | Aaron |
| 20130040629 | February 14, 2013 | Sprigg |
| 20130054803 | February 28, 2013 | Shepard |
| 20130132565 | May 23, 2013 | Cetin et al. |
| 20130143512 | June 6, 2013 | Hernandez |
| 20130260721 | October 3, 2013 | Carney |
| 20130305379 | November 14, 2013 | Udani |
| 20150040246 | February 5, 2015 | Yuen et al. |
- List of IBM Patents or Patent Applications Treated as Related, Nov. 19, 2019.
- Michael Bender et al., “Remote Permissions Monitoring and Control”, U.S. Appl. No. 15/201,546, filed Jul. 4, 2016.
Type: Grant
Filed: Oct 16, 2019
Date of Patent: Nov 1, 2022
Patent Publication Number: 20200050752
Assignee: International Business Machines Corporation (Armonk, NY)
Inventors: Michael Bender (Rye Brook, NY), Rhonda L. Childress (Austin, TX), David B. Kumhyr (Austin, TX), Michael John Spisak (East Northport, NY)
Primary Examiner: Jeffrey C Pwu
Assistant Examiner: Helai Salehi
Application Number: 16/655,181
International Classification: G06F 21/00 (20130101); G06F 21/51 (20130101); G06F 21/62 (20130101); G06F 8/60 (20180101);
