DE102011117855A1 - A method for assessing and mitigating risks through smart phone applications. - Google Patents

A method for assessing and mitigating risks through smart phone applications.

Info

Publication number
DE102011117855A1
DE102011117855A1 DE201110117855 DE102011117855A DE102011117855A1 DE 102011117855 A1 DE102011117855 A1 DE 102011117855A1 DE 201110117855 DE201110117855 DE 201110117855 DE 102011117855 A DE102011117855 A DE 102011117855A DE 102011117855 A1 DE102011117855 A1 DE 102011117855A1
Authority
DE
Germany
Prior art keywords
application
data
user
characterized
method according
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
DE201110117855
Other languages
German (de)
Inventor
wird später genannt werden Erfinder
Original Assignee
Joachim Linz
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Joachim Linz filed Critical Joachim Linz
Priority to DE201110117855 priority Critical patent/DE102011117855A1/en
Publication of DE102011117855A1 publication Critical patent/DE102011117855A1/en
Application status is Withdrawn legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/51Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/52Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
    • G06F21/53Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow by executing in a restricted environment, e.g. sandbox or secure virtual machine
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/55Detecting local intrusion or implementing counter-measures
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/62Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6281Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database at program execution time, where the protection is within the operating system
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/62Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/629Protecting access to data via a platform, e.g. using keys or access control rules to features or functions of an application
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements, e.g. access security or fraud detection; Authentication, e.g. verifying user identity or authorisation; Protecting privacy or anonymity ; Protecting confidentiality; Key management; Integrity; Mobile application security; Using identity modules; Secure pairing of devices; Context aware security; Lawful interception
    • H04W12/12Fraud detection or prevention
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2141Access rights, e.g. capability lists, access control lists, access tables, access matrices
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2149Restricted operating environment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/14Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1408Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
    • H04L63/1425Traffic logging, e.g. anomaly detection

Abstract

The inventive method described herein provides a technical enhancement to cellular customers for protection against malicious applications (apps) that have the potential to communicate personal data of the customer to third parties without the customer noticing. Other dangers come from apps that secretly gain control of the microphone and / or camera and / or communication channels such as mobile network or WLAN and thus spy on the customer's environment or send expensive premium SMS at the expense of the customer. On the other hand, the process offers protection through warnings to the customer, with detailed breakdowns of potential and existing risks. Other variants of the method presented herein provide structures imposed on the applications that do not allow for manipulation of destination addresses or misrepresentation of addresses allegedly used. The assumption of unimpeachable customer input is hereby ensured, d. H. What the customer sees or enters is also taken over and used in the most genuine way.

Description

  • Current situation
  • Applications, also called apps, are very popular because they are useful for many areas of personal and business life.
  • Although the mobile customers hardly want to give up these applications, many have a bad feeling with regard to the risk of being spied on by one or the other application or by manipulation of personal data and / or business data. Apart from spying, some apps also threaten the danger of direct monetary disadvantages. Because some of these malicious apps send SMS or even expensive premium SMS. If the data volume is high, the user's limit can also be exceeded - as long as no sufficient flat rate is booked. Personal data can be sent to dubious destinations (unauthorized servers) - unnoticed by the user, even at night, even if the phone is supposedly unused.
  • Cases are known in which very personal and even intimate images have been accessed and subsequently made public on the Internet - with significant personal harm to those affected. The backers are often in countries where they are legally intangible.
  • Applications can unnoticed by the user turn on the microphone and / or listen to the camera and the user and his environment or photograph or (video) filming.
  • "Sleepers" do not begin their evil activity for some time (weeks or even months) after installation. The user can then no longer easily associate the above-mentioned phenomena or even changes to his telephone bill and can not detect a connection with the download of the malicious application.
  • Within the framework of established processes, the user is granted authorizations (access to data and / or communication channels such as mobile network, WLAN, and / or devices such as camera, microphone, etc.) from the common operating systems of mobile terminals (mobile phones, tablets, etc.). ) is displayed. These permissions are passed on in the interaction of the operating system with devices such as Market-Place or AppStore, from which the applications are typically downloaded. Typically, the mobile phone user sees these permissions after the download and before the installation, usually in connection with the query of confirmation whether the application in question should be installed with the listed permissions.
  • This information about the entitlement is often too concise to be captured by the user in all its implications. It also says very little about what personal information is used when and for what. Also, some permissions are too general. A good example here is the "Internet" permission for a free game in which the developer earns his money through ads. The user tolerates the internet permission because he understands that the ads have to be downloaded from an ad server (advertising server) via the internet. What he can not tell which servers the game is still communicating with.
  • Often far too extensive profiles are requested by the app designers. This causes the user to get the impression that the extensive permissions are quite normal and are needed by every application. The acceptance threshold is lowered by this experience.
  • At the point where the appeal now prevails to install the application, most users put the concerns behind. In fact, there is comparably little abuse of permissions by the apps. At least only a few cases are discovered. This is also because few users are able to analyze the behavior of an app with regard to abuse.
  • While there are many forums where such questions are discussed, they can not know and analyze all of the many hundreds of thousands of apps. There is also a lack of trusting authority that can be trusted on this issue.
  • improvement
  • The inventive method described here is to be associated with the areas of mobile applications, apps, mobile applications, privacy, and telecommunications in general.
  • On the one hand, this method helps to identify malicious applications among the number of applications that have since grown to many hundreds of thousands and, in another form (claim 11-24), to enforce the transparency of the actions of each application and effectively prevent manipulation of access and access rights. The process ensures that the benign applications can be targeted and even more abundant and diverse - but now more relaxed and without hesitation.
  • Procedures 11-24 allow formal unlocking of the detailed access and communication behavior of the applications. To do this, the applications are put into structures that ensure transparent usage for the essential data that needs to be protected against manipulation. The data that must be checked to avert the above-mentioned risks include, for. B .:
    • • Destinations used for communication (links, IP addresses, phone numbers, etc.);
    • • Sensitivity classes used for data access (personal data such as pictures, videos, calendar data, telephone and address books, business documents, passwords, etc.);
    • • identifiers used for resource access (microphone, camera, GPS, receiver, etc.);
    This data is handled by trusted entities that reside on the respective terminal and possibly belong to the operating system, separated from the applications. The applications have only indirect access to these data, such as: B. only by indexes and / or names. The respective application can not directly perform operations on the sizes. It can only give instructions for using the "whole" unaltered size within the given limited functions (eg: use address1 to open a page on the internet, or use resource nameX to turn on the microphone) , These addresses and names of resources are accessible to the user and can be checked at any time and have in some cases come about as input by the user - but without "direct" contact with the application.
  • Mobile terminals that do not use these procedures (11-26) can use procedures 1-10. The latter use a CheckApp installed on the mobile device, which checks the applications before and / or during and / or after installation. This check can be done purely locally from the CheckApp on the mobile device or in cooperation with a ServCheck, which is located on a server according to the procedure. ServCheck and CheckApp can each build their own knowledge database or upload them in whole or in part to the ServCheck, so that the ServCheck can also benefit other mobile devices from the experience of already known applications.
  • In contrast to the methods 11-24, the methods according to 1-10 can not specifically prevent harm to the user, but they give the user the information and transparency to decide whether he installs an app or not.
  • In user-friendly versions of the procedures in 1-10, the user can at any time see the profile and / or the activities and / or the times of the activities and / or whether the activities of the application have taken place with the display off. An easily retrievable table, lists z. As the applications that are installed on the mobile device of the user. Color markers for each application give an overall rating of the potential and / or risk involved. By clicking on an application in the list, the user learns more details about potential and / or existing risks, such as: B.
    • • which volume has been transmitted by the application in the upward and / or downward direction;
    • • which data (pictures, contacts, calendars, etc.) the app has accessed;
    • • which other resources (microphone, camera, etc.) included the application;
    • • which communication channels were used (WLAN, mobile networks, under roaming conditions), and the like.
    The CheckApp can come as a factory installation on the mobile device or it is downloaded by the user. In the latter case, it should be ensured that the download server is controlled and operated by a trustworthy entity. During factory installation, the source of the mobile device should also be trusted - eg. B. from its own mobile network operator, which is subject to the relevant laws of their own country.

Claims (26)

  1. Method for identifying applications that are installed or are being installed on a mobile terminal or are being loaded there, such that the authorizations of each of these applications are checked according to the method by a CheckApp device installed on the mobile terminal and presented to the user of the terminal in more detail this during the installation process of the application by established procedures under the interaction of operating system of the mobile terminal and a market place from which the applications are downloaded or similar facilities to the user, and then the application is further observed, so that is checked whether it establishes or maintains data or voice or SMS connections or other means of communication to the outside or otherwise uses and in case of appropriate traffic this is measured for the respective direction, and too far According to the methodical analyzes, these volumes are stored with directional indicators and with the peer addresses of the respective connection and in conjunction with a process-oriented ServCheck Component that is located on a server according to the method, with which the CheckApp communicates via a mobile network or via WLAN or other networks, are analyzed so that the actually used and / or the registered access rights are fed to a process-related assessment process and additionally the awareness and / or or the criticality of the peer addresses of the considered application are included in the overall evaluation and in the detailed evaluation, such that in addition to an overall rating, a detailed individual rating is visibly created for the user in such a way that it reveals the cost risk for the user from the communication behavior of the application under consideration, and / or the risk of data or personal data leakage to known peer addresses or unknown peer addresses, and to address criticality indicators, including, but not limited to, the Ang abe of the country in which the destination or the destination server with the considered address are located, and / or the development of the risk incurred, such that the CheckApp and / or the ServCheck optionally resort to previously stored analysis results such that it Also, a sleeper application is identified according to the method, which becomes active only after a certain time after installation and the potential risk can be real time delayed.
  2. A method according to claim 1, characterized in that checks the CheckApp before and / or during and / or after the installation of an application on the terminal, such that the CheckApp reads the name and / or the authorization data provided by the operating system of the terminal be obtained from the own local database criteria for a rating and / or by information exchange with the ServCheck of the ServCheck information and / or receives a rating that is more detailed than the authorization profile that the operating system of the respective terminal before or after the Installation is provided in such a way that the CheckApp of this rating and / or the findings from other installations of the application considered on other devices that are stored and / or processed by the ServCheck and the CheckApp of the current device in the for this phase of the procedure recycled form provided displayed to the user.
  3. A method according to claim 1 or 2, characterized in that a multi-dimensional risk assessment is carried out such that these permissions component by component and / or is calculated to each one of the multidimensional sizes, such that the access authorization and / or the accessibility and / or access to the following data and / or functions are, but are not limited to: general personal data, and / or data areas containing personal data, and / or calendar data, and / or address book data, and / or images, and / or videos, and / or documents, and / or emails, and / or email account data, and / or health data, and / or passwords to WLAN and / or banking data and / or e-wallet data.
  4. Method according to Claim 3, characterized in that the additions to communication channels are also included in the multidimensional evaluation such that the authorization and / or the possibility and / or the actual use are included as a Boolean statement and / or from a complex calculation such that the following, but not exclusively, these communication channels to the Internet, and / or to destinations in voice networks, and / or to destinations in data networks, and / or to social networks, and / or to chat groups, and / or to input / output devices in the near and / or long range of the considered mobile terminal are included: mobile network, and / or WLAN, and / or Bluetooth, and / or near-field Communication, and / or infrared channels, and / or SMS, and / or MMS.
  5. A method according to claim 4, characterized in that also volume and / or cost components are included in the assessment, so that the user the potential and / or the risk already occurred generally and / or per communication channel and / or per target and / or per Destination address is displayed in such a way that whether costs for communication and / or for purchases in Market Places and / or E-Shops and / or for ringtones and / or for premium SMS or similar caused or can be caused.
  6. A method according to claim 1-5, characterized in that the state of the mobile terminal is included in the evaluation, so that the user is held opposite to what time an application was active and / or with what, so that is held whether during the activities the application, the display of the mobile device was turned on or off, and / or if the camera and / or the microphone and / or other integrated or connected to the mobile device devices were turned on and / or if they were turned on by the application, and / or whether the application has recorded and / or transmitted communication data or the communication contents or both.
  7. A method according to claim 2-6, characterized in that in the evaluation for the potential risk is taken into account whether on the mobile Entity entities that control the access to data and / or functions and / or resources, so that the potential risk is downgraded, according to the degree of control or prevention of abuse by these entities.
  8. A method according to claim 1-7, characterized in that the information about the experience with an application on a mobile terminal by the CheckApp the ServCheck be notified, such that the operating system version, and / or the hardware version, and / or the fact of whether entities to restrict access to applications are present on the terminal and / or their version and / or their degree of effective control such that the ServCheck transmits this information, with or without evaluation and / or with or without the inclusion of information other mobile devices, other mobile devices directly or after their request is available, so that in later downloads and / or installations of the corresponding application on other mobile devices as early and detailed warning to the user, so that this warning is then even if the terminal does not have its own entities has the opportunity to analyze.
  9. A method according to claim 8, characterized in that the ServCheck also informs the Market Place from which the application is distributed, so that the application is prevented as early as possible on the further distribution and / or the designer of the application of the use of the Market Place is excluded effectively for further distributions.
  10. An arrangement, characterized in that it consists of the following elements a) one or more terminals with a CheckApp or one or more applications or entities with the functionality of the CheckApp; b) one or more servers equipped with one or more ServCheck and / or entities equipped with the functionalities of the ServCheck; c) one or more market places for the distribution of applications to the users; d) one or more mobile networks and / or WLAN networks or other networks and that the elements of the arrangement cooperate according to the method according to claims 1-9, such that the network or networks (d) completely or partially establish the connection between the elements of the arrangement and the communication between the elements (a) to (c) according to the method supported.
  11. Method for preventing covert communication of applications that are installed on mobile terminals, characterized in that all communication connection data that wants to use an application to a ComProtect, which is located on the same terminal as the considered application, before the time of use must be logged in such a way that the ComProtect can not be manipulated by the application and by any other application and the data for the construction and use of communication links either at the time of installation receives and / or partially or completely already by default holds and / or by User input receives all or part, so that the communication data from any application are directly accessible and only directly readable by the user, so that the user the possible communication channels and destination addresses are disclosed and testable, such that the application can not deceive the displayed data compared to the only data available for communication, which are stored exclusively in the ComProtect.
  12. Method according to Claim 11, characterized in that an application can only establish and / or use and / or reduce a communication connection by virtue of the application indirectly notifying ComProtect which connection data from the range of data provided for the application for the current connection or their assembly or disassembly are to be used in such a way that the ComProtect initiates the requested operation itself, so that the connection operation can not be influenced and / or manipulated by the application and / or no other communication data is inserted or advanced in place of the data available in ComProtect according to the method become.
  13. Method according to claim 11-12, characterized in that an application can obtain connection addresses from the user only by addressing the ComProtect and the ComProtect requests the input from the user such that the input of the user is accepted and stored only under the control of the ComProtect and is not directly accessible to the application and can not be manipulated by it.
  14. A method according to claim 13, characterized in that the application and the ComProtect for the respective connection address, which counts for selecting the addresses that are assigned to the application for use, indices and / or names exchange, so that the application the ComProtect targeted for use the address specified by the index and / or name can request, which is necessary from the perspective of the application for the current connection operation, so that the application does not directly access the address and the latter is thus protected from manipulation by the application.
  15. A method according to claim 11-14, characterized in that the ComProtect is part of the operating system, such that the ComProtect receives the same protection against code manipulation as the rest of the operating system, such that the verification of the identity of the operating system is the one the ComProtect implies.
  16. A method for preventing unauthorized access and unauthorized transmission of personal and / or sensitive data by applications that are installed on a mobile terminal, characterized in that all user data associated with respective Sensibility classes and each Sensibility class is a memory marker, which is managed by a StoreProtect class appropriate in such a way that an application discloses all its claimed access rights to data classified in such a way at the installation time of the application with an AccessProfile of the StoreProtect, such that the AccessProfile is securely stored by the StoreProtect against manipulation by applications such that subsequent accesses of the application to data with sensitivity classification , only indirectly via the StoreProtect, so that the StoreProtect checks the current access request of the application against the access rights stored in the AccessProfile, and then either a or in the case of authorization causes the access to be intended, so that only read access controlled by the StoreProtect and / or write access to the data of the respective sensitivity class is possible.
  17. A method according to claim 16, characterized in that a sensitivity class is also assigned to devices or subdevices of a mobile terminal, such that an application through the StoreProtect controlled access to the following devices, but not exclusively to this: a camera and / or a microphone and / or a speaker and / or a thermometer and / or a meter.
  18. A method according to claim 17, characterized in that the StoreProtect after the transmission of the AccessProfil informs the user about the access options of the application and / or the user generally or partially requests confirmation of access rights, such that the given and not given confirmations in the The AccessProfile should be considered and taken into account in subsequent access requests by the application for an OR function or according to predefined or dynamically created truth tables, or the uninstalling of the application is initiated or the pending installation of the application is not permitted.
  19. The method of claim 16-18, characterized in that the StoreProtect assigns individual databases or data blocks for use in a Sensibility class by applications, initiated or confirmed by the user, or releases the access for the corresponding Sensibility class, such that the StoreProtect access by individual applications to certain data or data from other applications as controlled by the user.
  20. A method according to claim 16-19, characterized in that the StoreProtect is part of the operating system such that the StoreProtect receives the same protection against manipulation as the rest of the operating system, such that the verification of the identity of the operating system is that of the StoreProtect implied.
  21. Method for entering user data for applications on mobile devices, characterized in that the application does not directly request the input from the user requires this but indirectly via an InputProtect, which is installed or implemented on the same mobile device as the application, such that the InputProtect at the time of installation of the application receives an input profile with input data and their formats which the application can request from the user, so that the application names the input data to the InputProtect via index and / or name such that the InputProtect requests this data from the user and stores an area that can not be accessed directly by the application, but that can only be used by it, so that the input data are only reused by index and / or name from the application via InputProtect.
  22. A method according to claim 21, characterized in that the input profile also designates resources such that they are recognized by the InputProtect as such and used for accessing various resources from the InputProtect and / or through interaction with the StoreProtect such that the resources Designations according to the user input, and by the application is not falsified, targeted access to the resource intended by the user.
  23. A method according to claim 22, characterized in that the resource is a messaging system and / or mobile banking system and / or an address or an account number within the respective system and / or the content of the message, such that the message through the Application is not falsified and is transmitted according to the input visible to the user.
  24. A method according to claim 23, characterized in that the InputProtect encrypts the correspondingly designated input of the user such that the InputProtect does so directly and / or through interaction with other trusted entities according to the purpose, such that the user's instructions and input for this comprehensible and unadulterated.
  25. Method according to claims 1-24, characterized in that a ConformCheck which is located on the mobile terminal checks the CheckApp and / or the ComProtect and / or the StoreProtect and / or the InputProtect and / or the operating system such that a manipulation of the original functional destination of the respective entity is detected and / or stored and / or visibly displayed to the user and / or transmitted to entities of the mobile network operator and / or the manufacturer of the mobile terminal or other third party.
  26. A method according to claim 25, characterized in that the ConformCheck and a ServConform, which is located on a server, together encrypted test data and / or checksums and / or test algorithms and / or exchange unencrypted, such that the original functional determination of the entities on the basis verified by verified data.
DE201110117855 2011-11-08 2011-11-08 A method for assessing and mitigating risks through smart phone applications. Withdrawn DE102011117855A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
DE201110117855 DE102011117855A1 (en) 2011-11-08 2011-11-08 A method for assessing and mitigating risks through smart phone applications.

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
DE201110117855 DE102011117855A1 (en) 2011-11-08 2011-11-08 A method for assessing and mitigating risks through smart phone applications.
PCT/DE2012/001046 WO2013067989A2 (en) 2011-11-08 2012-10-27 Method for assessing and containing risks from smartphone applications
EP12806337.7A EP2776969A2 (en) 2011-11-08 2012-10-27 Method for assessing and containing risks from smartphone applications
DE201211004653 DE112012004653A5 (en) 2011-11-08 2012-10-27 A method for assessing and mitigating risks through smart phone applications.

Publications (1)

Publication Number Publication Date
DE102011117855A1 true DE102011117855A1 (en) 2013-05-08

Family

ID=47435674

Family Applications (2)

Application Number Title Priority Date Filing Date
DE201110117855 Withdrawn DE102011117855A1 (en) 2011-11-08 2011-11-08 A method for assessing and mitigating risks through smart phone applications.
DE201211004653 Withdrawn DE112012004653A5 (en) 2011-11-08 2012-10-27 A method for assessing and mitigating risks through smart phone applications.

Family Applications After (1)

Application Number Title Priority Date Filing Date
DE201211004653 Withdrawn DE112012004653A5 (en) 2011-11-08 2012-10-27 A method for assessing and mitigating risks through smart phone applications.

Country Status (3)

Country Link
EP (1) EP2776969A2 (en)
DE (2) DE102011117855A1 (en)
WO (1) WO2013067989A2 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102012001101A1 (en) 2012-01-23 2013-07-25 Joachim Linz Method for multilaterally and holistically detecting and improving the quality of mobile services using customer terminals with feedback to the customer.
US9443106B2 (en) 2013-12-13 2016-09-13 Indian Institute Of Technology Madras Filtering means for tracking information flow in android operated devices

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080016339A1 (en) * 2006-06-29 2008-01-17 Jayant Shukla Application Sandbox to Detect, Remove, and Prevent Malware
US20090319998A1 (en) * 2008-06-18 2009-12-24 Sobel William E Software reputation establishment and monitoring system and method
US20110154032A1 (en) * 2005-11-18 2011-06-23 Qualcomm Incorporated Mobile Security System and Method
US20110185428A1 (en) * 2010-01-27 2011-07-28 Mcafee, Inc. Method and system for protection against unknown malicious activities observed by applications downloaded from pre-classified domains

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1971102A1 (en) * 2007-03-14 2008-09-17 Deutsche Telekom AG Method and system for monitoring communication devices to detect malicious software

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110154032A1 (en) * 2005-11-18 2011-06-23 Qualcomm Incorporated Mobile Security System and Method
US20080016339A1 (en) * 2006-06-29 2008-01-17 Jayant Shukla Application Sandbox to Detect, Remove, and Prevent Malware
US20090319998A1 (en) * 2008-06-18 2009-12-24 Sobel William E Software reputation establishment and monitoring system and method
US20110185428A1 (en) * 2010-01-27 2011-07-28 Mcafee, Inc. Method and system for protection against unknown malicious activities observed by applications downloaded from pre-classified domains

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ENCK. W. [et al.] TaintDroid: An Information-Flow Tracking System for Realtime Privacy Monitoring on Smartphones, In Proc. of the USENIX Symposium on Operating Systems Design and Implementation (OSDI), October 2010 in Vancouver,URL: http://appanalysis.org/tdroid10.pdf [abgerufen im Internet am 05.07.2012] *
ONGTANG. M. [et al.]: Semantically Rich Application-Centric Security in Android , 2009 Annual Computer Security Applications Conference, Publication Year: 2009,URL: http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5380692 [abgerufen im Internet am 05.07.2012] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102012001101A1 (en) 2012-01-23 2013-07-25 Joachim Linz Method for multilaterally and holistically detecting and improving the quality of mobile services using customer terminals with feedback to the customer.
US9443106B2 (en) 2013-12-13 2016-09-13 Indian Institute Of Technology Madras Filtering means for tracking information flow in android operated devices

Also Published As

Publication number Publication date
WO2013067989A2 (en) 2013-05-16
WO2013067989A3 (en) 2013-08-08
EP2776969A2 (en) 2014-09-17
DE112012004653A5 (en) 2014-12-31

Similar Documents

Publication Publication Date Title
US8260353B2 (en) SIM messaging client
US10019338B1 (en) User interface with real-time visual playback along with synchronous textual analysis log display and event/time index for anomalous behavior detection in applications
JP6019484B2 (en) Systems and methods for server-bound malware prevention
US9668137B2 (en) Controlling enterprise access by mobile devices
US8615581B2 (en) System for managing devices and method of operation of same
US20140128047A1 (en) System and method for call blocking and sms blocking
US8788655B2 (en) Systems for accepting and approving applications and methods of operation of same
US8745213B2 (en) Managed services platform and method of operation of same
US8612582B2 (en) Managed services portals and method of operation of same
CN101513008B (en) System for implementing safety of telecommunication terminal
US20140373104A1 (en) Data sensitivity based authentication and authorization
US20130061307A1 (en) Method and Apparatus for Accessing Corporate Data from a Mobile Device
Stevens et al. Investigating user privacy in android ad libraries
EP1804418A1 (en) A dynamic password authentication system and the method thereof
CN104380302B (en) Assessment is blocked or allowed to install software applications
US8984604B2 (en) Locally stored phishing countermeasure
US20120036440A1 (en) Supervisory portal systems and methods of operation of same
US9706410B2 (en) Controlling enterprise access by mobile devices
US9104840B1 (en) Trusted security zone watermark
KR20140074252A (en) Secure execution of unsecured apps on a device
US20070186115A1 (en) Dynamic Password Authentication System and Method thereof
US10198581B2 (en) Controlling enterprise access by mobile devices
US20140208397A1 (en) Geographical restrictions for application usage on a mobile device
Delac et al. Emerging security threats for mobile platforms
US9063964B2 (en) Detecting application harmful behavior and grading application risks for mobile devices

Legal Events

Date Code Title Description
R086 Non-binding declaration of licensing interest
R012 Request for examination validly filed
R002 Refusal decision in examination/registration proceedings
R126 Request for further processing allowed
R125 Request for further processing filed
R119 Application deemed withdrawn, or ip right lapsed, due to non-payment of renewal fee

Effective date: 20140603