Nothing Special   »   [go: up one dir, main page]

US20170163664A1 - Method to secure protected content on a mobile device - Google Patents

Method to secure protected content on a mobile device Download PDF

Info

Publication number
US20170163664A1
US20170163664A1 US14/959,492 US201514959492A US2017163664A1 US 20170163664 A1 US20170163664 A1 US 20170163664A1 US 201514959492 A US201514959492 A US 201514959492A US 2017163664 A1 US2017163664 A1 US 2017163664A1
Authority
US
United States
Prior art keywords
content
mobile device
request
displayed
received
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.)
Abandoned
Application number
US14/959,492
Inventor
Durga Nagalla
Alexander Deeb
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bottomline Technologies Inc
Original Assignee
Bottomline Technologies DE Inc
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 Bottomline Technologies DE Inc filed Critical Bottomline Technologies DE Inc
Priority to US14/959,492 priority Critical patent/US20170163664A1/en
Assigned to BOTTOMLINE TECHNOLOGIES (DE) INC. reassignment BOTTOMLINE TECHNOLOGIES (DE) INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NAGALLA, Durga, DEEB, Alexander
Priority to TW105138854A priority patent/TWI787159B/en
Priority to PCT/US2016/064689 priority patent/WO2017096206A1/en
Priority to US16/388,242 priority patent/US11496490B2/en
Assigned to BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT reassignment BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT NOTICE OF GRANT OF SECURITY INTEREST IN PATENTS Assignors: BOTTOMLINE TECHNOLOGIES (DE), INC.
Publication of US20170163664A1 publication Critical patent/US20170163664A1/en
Assigned to BOTTOMLINE TECHNLOGIES, INC. reassignment BOTTOMLINE TECHNLOGIES, INC. CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: BOTTOMLINE TECHNOLOGIES (DE), INC.
Assigned to BOTTOMLINE TECHNOLOGIES (DE), INC. reassignment BOTTOMLINE TECHNOLOGIES (DE), INC. RELEASE OF SECURITY INTEREST IN REEL/FRAME: 040882/0908 Assignors: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Priority to US17/970,250 priority patent/US20230045087A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • 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/1416Event detection, e.g. attack signature detection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • 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/1441Countermeasures against malicious traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/66Substation equipment, e.g. for use by subscribers with means for preventing unauthorised or fraudulent calling
    • H04M1/667Preventing unauthorised calls from a telephone set
    • H04M1/67Preventing unauthorised calls from a telephone set by electronic means
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/12Detection or prevention of fraud
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/30Security of mobile devices; Security of mobile applications
    • H04W12/37Managing security policies for mobile devices or for controlling mobile applications
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR 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
    • G06F21/554Detecting local intrusion or implementing counter-measures involving event detection and direct action
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR 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
    • G06F21/56Computer malware detection or handling, e.g. anti-virus arrangements
    • G06F21/566Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR 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/6245Protecting personal data, e.g. for financial or medical purposes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/70Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
    • G06F21/88Detecting or preventing theft or loss

Definitions

  • the present invention relates to data security and, more particularly, to a method and system for securing electronic data on a mobile device.
  • Mobile devices are frequently being used to access sensitive and protected data. For example, healthcare professionals are able to receive the results of medical tests, view diagnostic images, and review patient records using mobile devices. As the amount of electronic data has dramatically increased over the past decade, so have the number of data breaches, resulting in billions of private records being stolen. For this reason, much research has gone into improved methods of securing data.
  • the methods for protecting data described above do not adequately protect user data.
  • the above security measures do nothing to prevent a user that has the correct access credentials from copying and transferring protected data.
  • This problem is particularly prevalent in mobile devices where a user (authorized or otherwise) can simply perform a screen capture of the protected data. At this point, the user is free to transfer the screen capture of the protected data.
  • This is a problem unique to mobile devices in that the devices are frequently taken into public and are capable of accessing sensitive data. In this way, if a user leaves their phone unlocked in public, a third party can pick up the phone and take a screen capture of the data. The screen capture can be transferred from the phone without the user ever being aware.
  • Mobile devices unlike personal computers and physical paperwork, are taken frequently into public places and are more likely to be left unattended on a table, in a bag, etc. than a print out of sensitive data or a computer would be.
  • the present disclosure provides a method for securing data by detecting a request to record content, determining whether the content to be recorded is protected, notifying a third party that a security breach has been detected, and performing a remedial action.
  • a mobile device configured to prevent electronic data from being compromised.
  • the mobile device includes: a non-transitory computer readable memory, a network interface, a display configured to display protected content and non-protected content, and a processor.
  • the processor is configured to access protected content and detect a security breach.
  • the processor detects a security breach by: receiving a request to record content currently displayed on the display; detecting the content displayed on the display when the request to record currently displayed content was received; and determining that the content displayed on the display when the request was received is the protected content. If a security breach is detected, the processor notifies a third party via the network interface that the security breach occurred and performs a remedial action.
  • the content is determined to be protected content if an application executed by the processor and generating the content being displayed is flagged as a protected application.
  • the processor is configured to determine that the content displayed on the display when the request was received is the protected content by: notifying an application generating the content being displayed that the request to record content was received and receiving from the application an indication that the content being displayed is the protected content.
  • the notification that the security breach occurred includes information identifying at least one of the mobile device or a user of the mobile device.
  • the identifying information includes at least one of a username, a geo-location of the device, a device identifier, or an image captured by a camera of the mobile device after the request to record was received.
  • the notification to the third party includes multiple notifications sent to different network locations.
  • the notification that the security breach occurred includes a record of the content displayed on the display when the request was received.
  • the remedial action includes at least one of deleting data stored on the mobile device, capturing an image of a user of the mobile device when the request to capture a screen shot was received, disabling the mobile device, or disabling login credentials used to access the protected content.
  • the processor performs the remedial action after receiving a request via the network interface to perform the remedial action.
  • a method to prevent data viewed on a mobile device from being compromised includes receiving a request to record content currently displayed on a display of the mobile device and detecting the content displayed on the display when the request to record currently displayed content was received. The method also includes determining if the content displayed on the display when the request was received is the protected content. If the content displayed when the request was received is the protected content: the method notifies a third party via a network interface of the mobile device that the security breach occurred and performs a remedial action.
  • the content is determined to be protected content if an application generating the content being displayed is flagged as a protected application.
  • the content displayed on the display when the request was received is determined to be the protected content by: notifying an application generating the content being displayed that the request to record content was received and receiving from the application an indication that the content being displayed is the protected content.
  • the notification that the security breach occurred includes information identifying at least one of the mobile device or a user of the mobile device.
  • the identifying information includes at least one of a username, a geo-location of the device, a device identifier, or an image captured by a camera of the mobile device after the request to record was received.
  • the notification that the security breach occurred includes a record of the content displayed on the display when the request was received.
  • the remedial action includes at least one of deleting data stored on the mobile device, capturing an image of a user of the mobile device when the request to capture a screen shot was received, disabling the mobile device, or disabling login credentials used to access the protected content.
  • the remedial action is performed after receiving a request to perform the remedial action.
  • a system configured to prevent data viewed on a mobile device from being compromised.
  • the system includes a mobile device including: a non-transitory computer readable memory, a network interface, and a display.
  • the mobile device also includes a processor configured to access protected content and detect a security breach by: receiving a request to record content currently displayed on the display, detecting the content displayed on the display when the request to record currently displayed content was received;, and determining that the content displayed on the display when the request was received is the protected content. If a security breach is detected, the processor sends a notification to a third party computer via the network interface. The notification indicates that the security breach occurred.
  • the system also includes a third party computer.
  • the third party computer includes a communication interface configured to communicate with the network interface of the mobile device and receive the notification from the mobile device and a processor.
  • the processor of the third party computer is configured to: receive the notification from the communication interface, determine the nature of the protected content displayed on the display when the request was received, based on the nature of the protected content and the user of the mobile device, determine a remedial action to perform, and send an indication of the remedial action to perform to the mobile device.
  • the notification includes information regarding the protected content displayed on the display when the request was received and a user of the mobile device.
  • the processor of the mobile device is further configured to perform the remedial action indicated by the third party computer.
  • FIG. 1 is a block diagram representing a system for protecting electronic data accessed via a mobile device.
  • FIG. 2 is a ladder diagram illustrating communication between the operating system, application, display, and server within the system of FIG. 1 .
  • FIG. 3 is a flow diagram representing a method for protecting electronic data accessed via a mobile device.
  • each element with a reference number is similar to other elements with the same reference number independent of any letter designation following the reference number.
  • a reference number with a specific letter designation following the reference number refers to the specific element with the number and letter designation and a reference number without a specific letter designation refers to all elements with the same reference number independent of any letter designation following the reference number in the drawings.
  • circuits may be implemented in a hardware circuit(s), a processor executing software code or instructions which are encoded within computer readable media accessible to the processor, or a combination of a hardware circuit(s) and a processor or control block of an integrated circuit executing machine readable code encoded within a computer readable media.
  • the term circuit, module, server, application, or other equivalent description of an element as used throughout this specification is, unless otherwise indicated, intended to encompass a hardware circuit (whether discrete elements or an integrated circuit block), a processor or control block executing code encoded in a computer readable media, or a combination of a hardware circuit(s) and a processor and/or control block executing such code.
  • the present disclosure provides a method and device for securing data accessed by a mobile device.
  • the mobile device detects a request to record content displayed on a display of the mobile device. A determination is then made regarding whether the content that was displayed on the screen when the request to record was received is protected content. If the displayed content was protected, then a third party is notified that a security breach has been detected. A remedial action is also performed regarding the security breach.
  • FIG. 1 depicts a system 10 for preventing electronic data from being compromised.
  • the system prevents protected content from being copied and transferred from the mobile device.
  • the system 10 includes a mobile device 12 and a server 14 .
  • the mobile device 12 includes a processor 20 and a memory 22 storing an application 24 and an operating system 28 .
  • the application 24 and operating system 28 are executable programs that are executed by the processor 20 of the mobile device 12 .
  • the application 24 generates content that is displayed on a display 30 of the mobile device. Some of the content displayed on the display 30 is the protected content.
  • the server 14 may be a computer system of one or more computers or servers.
  • the mobile device 12 may comprise a cellular phone, smart phone, tablet, or any other portable electronic device capable of executing the application 24 and operating system 28 .
  • the mobile device 12 and server 14 each include at least a processor, a network interface, and non-transitory computer readable medium.
  • the computer readable medium may include encoded thereon instructions for interfacing with the corresponding network interface and reading and writing data to the corresponding computer readable medium.
  • the computer readable medium may also include computer programs (including the application 24 ) comprising instructions embodied thereon that are executed by the corresponding processor.
  • the mobile device 12 includes a display 30 configured to display protected content and non-protected content.
  • the display 30 may comprise any suitable display for rendering content, such as a liquid crystal display (LCD), organic light-emitting diode (OLED), light-emitting diode (LED), electronic ink (E-ink), etc.
  • the content displayed by the display 30 may be determined by the operating system 28 and/or applications executed by the processor 20 of the mobile device 12 .
  • the application 24 may access protected content 26 stored on the server 14 and display the protected content on the display 30 .
  • the processor 20 is configured to access the protected content 26 .
  • the processor 20 may execute the application 24 that accesses protected content 26 stored on the server 14 .
  • the protected content 26 may be stored on the non-transitory computer readable medium 22 of the mobile device 12 and accessed by the application 24 .
  • the processor 20 may have various implementations.
  • the processor 20 may include any suitable device, such as a programmable circuit, integrated circuit, memory and I/O circuits, an application specific integrated circuit, microcontroller, complex programmable logic device, other programmable circuits, or the like.
  • the processor 20 may also include a non-transitory computer readable medium, such as random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), or any other suitable medium.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • the processor 20 may be communicatively coupled to the computer readable medium 22 and network interface 32 through a system bus, mother board, or using any other suitable structure known in the art.
  • the processor 20 is also configured to detect a security breach.
  • the processor 20 detects the security breach by receiving a request 56 to record content currently displayed on the display 30 .
  • the request 56 to record content may comprise a user attempting to perform a screen capture of content currently being displayed on the display 30 .
  • the request 56 to perform a screen capture may be initiated by a user pressing a predefined combination of keys on an input 34 of the mobile device 12 . For example, by simultaneously pushing a physical power button and a physical home screen button of the mobile device 12 .
  • the processor 20 Upon receiving the request 56 to record content currently displayed, the processor 20 is configured to determine whether the content displayed on the display 30 when the request was received is protected content 26 . That is, the processor 20 is configured to determine whether the displayed content was protected content or non-protected content. The processor 20 may determine that the content being displayed is protected content 26 if an application 24 (executed by the processor 20 ) generating the content being displayed is flagged as a protected application. That is, the application 24 may be flagged as a protected application such that any content being generated by the application 24 is assumed to be protected content 26 .
  • An application 24 may be flagged as a protected application if the process id, the name of the application, the location and name of the executable file, or any other suitable identifying characteristic of the application is stored in a database or list of protected applications stored on the non-transitory computer readable medium 22 .
  • the processor 20 may notify the application 24 generating the content that a request 56 to record was received.
  • the application 24 may then indicate whether the content being displayed was protected content 26 when the request 56 was received.
  • an application 24 that displays both protected and non-protected content may determine the type of content that was being displayed when the request 56 was received.
  • the application 24 may notify the operating system 28 whether the content was protected content 26 .
  • the application 24 may determine whether content currently displayed is protected content 26 based on an identifier associated with the content, the location the content was accessed from, or using any other tag or identifier capable of labeling content as protected content or non-protected content.
  • the application 24 may also store a historical record of when protected content was displayed over a limited duration of time. For example, the application 24 may store a record of when protected content was displayed over the past 10 seconds, 2 seconds, 1 second, 200 milliseconds, or any other suitable duration of time.
  • the processor 20 determines that a security breach is detected. If a security breach is detected, the processor 20 is configured to optionally notify a third party that the security breach occurred and/or perform a remedial action.
  • the mobile device 12 may notify a third party computer (e.g., the server 14 ) that a security breach occurred via the network interface 32 . That is, the processor 20 may cause the network interface 32 to send a notification via a network 44 that the security breach occurred.
  • the network 44 may comprise a private network, the internet, a wired network, a wireless network, or any other suitable network allowing the mobile device 12 and the third party to communicate with one another.
  • the mobile device 12 is not limited to notifying a single computer device that a security breach occurred, but may instead notify multiple devices (e.g., more than one server) that a security breach occurred. That is, the notification to the third party may include multiple notifications sent to different network locations.
  • the parties notified when a breach occurred may be determined by the application 24 generating the protected content 26 . Additionally, the parties contacted may be determined based upon the content being displayed when the security breach occurred. For example, there may be multiple tiers of protected content 26 (e.g., low, medium, and high). In this example, if a security breach occurred while low tier protected content 26 was displayed, then a first server 14 a may be notified.
  • a second server 14 b (in place of or in addition to the first server 14 a ) may be notified (or no notification may be sent). If a security breach occurred while high tier protected content 26 was displayed, then a third server 14 c (in place of or in addition to the first server 14 a and second server 14 b ) may be notified.
  • the notification that the security breach occurred may include information identifying at least one of the mobile device or a user of the mobile device.
  • the identifying information may include any suitable information for identifying the mobile device 12 or a user of the mobile device, including a username used to sign into the mobile device 12 or used to access the protected content 26 , a geo-location of the device 12 , a device identifier, or an image captured by a camera of the mobile device after the request to record was received.
  • the device identifier may comprise a MAC address, a serial number, or any information used to uniquely identify the mobile device 12 .
  • the notification that the security breach occurred may additionally or alternatively include a record of the content displayed on the display when the security breach occurred.
  • the processor 20 is also configured to perform a remedial action upon detecting a security breach.
  • the remedial action may be performed before, after, or in place of notifying a third party as described previously.
  • the remedial action may include deleting data stored on the mobile device, capturing an image of a user of the mobile device when the request to capture a screen shot was received, disabling the mobile device, and/or disabling login credentials used to access the protected content.
  • the remedial action may be specified by the application 24 or may be initiated by the third party notified of the security breach.
  • the server 14 may instruct the processor 20 to perform a given remedial action. This instruction may be sent to the mobile device 12 via the network 44 .
  • the processor 20 performs the remedial action after receiving a request via the network interface 44 to perform the remedial action.
  • a default remedial action may be initiated by the application 24 (e.g., disabling login credentials) and instruction to perform an additional or alternative remedial action (e.g., disabling the mobile device) may be sent by the third party.
  • the third party computer receiving the notification of the security breach includes a communication interface configured to communicate with the network interface of the mobile device and receive the notification from the mobile device.
  • the third party computer also includes a processor configured to receive the notification from the communication interface.
  • the notification includes information regarding the protected content displayed on the display when the request was received and a user of the mobile device.
  • the processor determines the nature of the protected content displayed on the display when the request was received. For example, the processor may determine the nature of the protected content displayed by comparing the displayed content to the content stored on the third party computer. Based on the nature of the protected content and the user of the mobile device, the processor determines a remedial action to perform. The processor may determine the remedial action by using a lookup table. Finally, the third party computer sends an indication of the remedial action to perform to the mobile device 12 .
  • FIG. 2 depicts communication of data within the mobile device 12 and between the mobile device 12 and the server 14 .
  • the application 24 running on the mobile device 12 optionally sends a request for protected content 52 to the server 14 .
  • a request for protected content 52 may be sent to the server 14 .
  • the server 14 receives the request 52 and, assuming that all required security procedures are satisfied (e.g., the user authenticates with the server), protected content 26 is sent to the application 24 .
  • the protected content 52 may be stored within the memory 22 of the mobile device 12 .
  • the application 24 may access the protected content 26 directly from the memory 22 without sending a request for protected content 52 to the server 14 .
  • the application 24 Upon receiving the protected content 54 , the application 24 causes the display 30 to display the protected content 26 .
  • the mobile device 12 also includes a device input 34 . If the operating system 28 receives a request to record displayed content 56 from the device input 34 , then the request 56 may be passed to the application 24 . Alternatively, as opposed to passing the request to record 56 to the application 24 , the operating system 28 may request information regarding the content displayed at the time that the request to record content 56 was received. In either case, the application 24 may notify the operating system 28 that a security breach occurred 28 if the content being displayed when the request to record 56 was received was protected content. The application 24 may alternatively or additionally notify the server 14 if a security breach 28 occurred.
  • instructions to perform a remedial action 60 may be received.
  • the instructions may be received by at least one of the server 14 , the operating system 28 , or the application 24 .
  • the instructions to perform the remedial action 60 may be provided by at least one of the server 14 , the operating system 28 , or the application 24 .
  • the application 24 may contain a list of default remedial actions to perform until further instructions are received from the operating system 28 or the server 14 .
  • the application 24 may be configured to only display non-protected content until further instructions are received from the server 14 .
  • the server 14 may then send instructions to perform a remedial action, such as locking down the application 24 so that no content is accessible through the application 24 .
  • FIG. 3 a block diagram is shown depicting a method 100 for securing data by detecting a request to record content.
  • the method 100 determines in decision block 104 whether a request to record content currently displayed on a display of the mobile device was received. If a request was not received, then the method returns back to decision block 104 . If a request was received, then process block 108 is performed.
  • process block 108 the content displayed on the display when the request to record currently displayed content was received is detected.
  • process block 110 it is determined whether the content displayed on the display when the request was received is protected content or non-protected content.
  • the type of content displayed may be determined by the application 24 generating the content being displayed. For example, if the application 24 is identified as a protected application, then any content displayed by the application 24 is determined to be protected content. Alternatively, the application 24 may be polled to determine whether the content being displayed when the request was received is protected content.
  • decision block 112 if the displayed content is non-protected content, then the method returns to decision block 104 . If the displayed content is protected content, then the method 100 moves to process block 114 .
  • a third party is notified that a security breach has occurred.
  • the notification that the security breach occurred may include information identifying at least one of the mobile device or a user of the mobile device.
  • the notification that a security breach occurred may alternatively or additionally include a record of the content displayed on the display when the request was received.
  • a remedial action is performed. As described above the remedial action may be performed only after receiving a request to perform the remedial action.
  • the method 100 may run as a background process on the mobile device 12 .
  • the method 100 may be included as a part of the operating system 28 , the application 24 , or as a standalone application.
  • Data (e.g., the request for protected content 52 , the protected content 26 , notification that a security breach occurred 58 , and remedial action 60 ) may be transferred over a network 44 connecting the mobile device 12 and the server 14 .
  • the network 44 may be at least one of a TCP/IP network or a system bus.
  • the network 44 would comprise the system bus connecting the USB port and the memory 22 of the mobile device 12 .
  • the network 44 is not limited to a single LAN, but may comprise any suitable network of devices.
  • the predefined areas 80 may comprise a collection of LANs, a Bluetooth Network, the Internet, etc.
  • the transmission of data may be transmitted using any suitable protocol (e.g., TCP/IP, Bluetooth, SMTP, HTTP, SSL, PPP, IMAP, or any other suitable network protocol).
  • any suitable protocol e.g., TCP/IP, Bluetooth, SMTP, HTTP, SSL, PPP, IMAP, or any other suitable network protocol.
  • the processor of the mobile device 12 may identify the location of the corresponding device using a global positioning system (GPS) device, cellular triangulation, WI-FI positioning, or any other suitable technique or device to determine location.
  • GPS global positioning system
  • each of the processors may include any suitable device, such as a programmable circuit, integrated circuit, memory and I/O circuits, an application specific integrated circuit, microcontroller, complex programmable logic device, other programmable circuits, or the like.
  • Each of the processors may also include a non-transitory computer readable medium, such as random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), or any other suitable medium. Instructions for performing the methods described above may be stored in the non-transitory computer readable medium and executed by the respective processor identified in the description of the method.
  • Each of the processors may be communicatively coupled to the respective computer readable medium and network interface through a system bus, mother board, or using any other suitable structure known in the art.
  • the network interfaces of the mobile device 12 , server 14 , and predetermined server 14 may each be communicatively coupled to one or more other host devices 12 and receiving devices 14 via a network 44 .
  • the network 44 may be an open network, such as the Internet, a private network, such as a virtual private network, or any other suitable network.
  • Each of the network interface may be configured to transmit and/or receive data.
  • each of the network interfaces may comprise a wireless network adaptor, an Ethernet network card, or any suitable device for performing network based communication between devices.
  • Each of the network interface may be communicatively coupled to the respective computer readable medium such that each network interface is able to send data stored on the respective computer readable medium across the network 44 and store received data on the respective computer readable medium.
  • Each of the network interface may also be communicatively coupled to the respective processor such that the processor is able to control operation of the network interface.
  • the respective network interfaces, computer readable medium, and processors may be communicatively coupled through a system bus, mother board, or using any other suitable manner as will be understood by one of ordinary skill in the art.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)
  • Telephone Function (AREA)
  • Information Transfer Between Computers (AREA)
  • Alarm Systems (AREA)

Abstract

A method and device for securing data accessed by a mobile device. The mobile device detects a request to record content displayed on a display of the mobile device. A determination is then made regarding whether the content that was displayed on the screen when the request to record was received is protected content. If the displayed content was protected, then a third party is notified that a security breach has been detected. A remedial action is also performed regarding the security breach.

Description

    TECHNICAL FIELD
  • The present invention relates to data security and, more particularly, to a method and system for securing electronic data on a mobile device.
  • BACKGROUND OF THE INVENTION
  • Mobile devices are frequently being used to access sensitive and protected data. For example, healthcare professionals are able to receive the results of medical tests, view diagnostic images, and review patient records using mobile devices. As the amount of electronic data has dramatically increased over the past decade, so have the number of data breaches, resulting in billions of private records being stolen. For this reason, much research has gone into improved methods of securing data.
  • Current methods for protecting data generally utilize sophisticated encryption schemes and/or multi-factor authentication in order to ensure that only authorized users gain access to the data. These current methods “trigger” on “who” is accessing the data and the current methods are typically constructed and deployed as “layers” of security starting potentially as true physical layers at the perimeter and culminating as encrypt/decrypt schemes.
  • SUMMARY OF THE INVENTION
  • The methods for protecting data described above do not adequately protect user data. For example, the above security measures do nothing to prevent a user that has the correct access credentials from copying and transferring protected data. This problem is particularly prevalent in mobile devices where a user (authorized or otherwise) can simply perform a screen capture of the protected data. At this point, the user is free to transfer the screen capture of the protected data. This is a problem unique to mobile devices in that the devices are frequently taken into public and are capable of accessing sensitive data. In this way, if a user leaves their phone unlocked in public, a third party can pick up the phone and take a screen capture of the data. The screen capture can be transferred from the phone without the user ever being aware. Mobile devices, unlike personal computers and physical paperwork, are taken frequently into public places and are more likely to be left unattended on a table, in a bag, etc. than a print out of sensitive data or a computer would be.
  • The present disclosure provides a method for securing data by detecting a request to record content, determining whether the content to be recorded is protected, notifying a third party that a security breach has been detected, and performing a remedial action.
  • According to one aspect of the disclosure, there is provided a mobile device configured to prevent electronic data from being compromised. The mobile device includes: a non-transitory computer readable memory, a network interface, a display configured to display protected content and non-protected content, and a processor. The processor is configured to access protected content and detect a security breach. The processor detects a security breach by: receiving a request to record content currently displayed on the display; detecting the content displayed on the display when the request to record currently displayed content was received; and determining that the content displayed on the display when the request was received is the protected content. If a security breach is detected, the processor notifies a third party via the network interface that the security breach occurred and performs a remedial action.
  • Alternatively or additionally, the content is determined to be protected content if an application executed by the processor and generating the content being displayed is flagged as a protected application.
  • Alternatively or additionally, the processor is configured to determine that the content displayed on the display when the request was received is the protected content by: notifying an application generating the content being displayed that the request to record content was received and receiving from the application an indication that the content being displayed is the protected content.
  • Alternatively or additionally, the notification that the security breach occurred includes information identifying at least one of the mobile device or a user of the mobile device.
  • Alternatively or additionally, the identifying information includes at least one of a username, a geo-location of the device, a device identifier, or an image captured by a camera of the mobile device after the request to record was received.
  • Alternatively or additionally, the notification to the third party includes multiple notifications sent to different network locations.
  • Alternatively or additionally, the notification that the security breach occurred includes a record of the content displayed on the display when the request was received.
  • Alternatively or additionally, the remedial action includes at least one of deleting data stored on the mobile device, capturing an image of a user of the mobile device when the request to capture a screen shot was received, disabling the mobile device, or disabling login credentials used to access the protected content.
  • Alternatively or additionally, the processor performs the remedial action after receiving a request via the network interface to perform the remedial action.
  • According to another aspect of the disclosure, there is provided a method to prevent data viewed on a mobile device from being compromised. The method includes receiving a request to record content currently displayed on a display of the mobile device and detecting the content displayed on the display when the request to record currently displayed content was received. The method also includes determining if the content displayed on the display when the request was received is the protected content. If the content displayed when the request was received is the protected content: the method notifies a third party via a network interface of the mobile device that the security breach occurred and performs a remedial action.
  • Alternatively or additionally, the content is determined to be protected content if an application generating the content being displayed is flagged as a protected application.
  • Alternatively or additionally, the content displayed on the display when the request was received is determined to be the protected content by: notifying an application generating the content being displayed that the request to record content was received and receiving from the application an indication that the content being displayed is the protected content.
  • Alternatively or additionally, the notification that the security breach occurred includes information identifying at least one of the mobile device or a user of the mobile device.
  • Alternatively or additionally, the identifying information includes at least one of a username, a geo-location of the device, a device identifier, or an image captured by a camera of the mobile device after the request to record was received.
  • Alternatively or additionally, the notification that the security breach occurred includes a record of the content displayed on the display when the request was received.
  • Alternatively or additionally, the remedial action includes at least one of deleting data stored on the mobile device, capturing an image of a user of the mobile device when the request to capture a screen shot was received, disabling the mobile device, or disabling login credentials used to access the protected content.
  • Alternatively or additionally, the remedial action is performed after receiving a request to perform the remedial action.
  • According to a further aspect of the disclosure, there is provided a system configured to prevent data viewed on a mobile device from being compromised. The system includes a mobile device including: a non-transitory computer readable memory, a network interface, and a display. The mobile device also includes a processor configured to access protected content and detect a security breach by: receiving a request to record content currently displayed on the display, detecting the content displayed on the display when the request to record currently displayed content was received;, and determining that the content displayed on the display when the request was received is the protected content. If a security breach is detected, the processor sends a notification to a third party computer via the network interface. The notification indicates that the security breach occurred. The system also includes a third party computer. The third party computer includes a communication interface configured to communicate with the network interface of the mobile device and receive the notification from the mobile device and a processor. The processor of the third party computer is configured to: receive the notification from the communication interface, determine the nature of the protected content displayed on the display when the request was received, based on the nature of the protected content and the user of the mobile device, determine a remedial action to perform, and send an indication of the remedial action to perform to the mobile device. The notification includes information regarding the protected content displayed on the display when the request was received and a user of the mobile device. The processor of the mobile device is further configured to perform the remedial action indicated by the third party computer.
  • A number of features are described herein with respect to embodiments of this disclosure. Features described with respect to a given embodiment also may be employed in connection with other embodiments.
  • For a better understanding of the present disclosure, together with other and further aspects thereof, reference is made to the following description, taken in conjunction with the accompanying drawings. The scope of the disclosure is set forth in the appended claims, which set forth in detail certain illustrative embodiments. These embodiments are indicative, however, of but a few of the various ways in which the principles of the disclosure may be employed.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram representing a system for protecting electronic data accessed via a mobile device.
  • FIG. 2 is a ladder diagram illustrating communication between the operating system, application, display, and server within the system of FIG. 1.
  • FIG. 3 is a flow diagram representing a method for protecting electronic data accessed via a mobile device.
  • DETAILED DESCRIPTION OF THE INVENTION
  • The present invention is now described in detail with reference to the drawings. In the drawings, each element with a reference number is similar to other elements with the same reference number independent of any letter designation following the reference number. In the text, a reference number with a specific letter designation following the reference number refers to the specific element with the number and letter designation and a reference number without a specific letter designation refers to all elements with the same reference number independent of any letter designation following the reference number in the drawings.
  • It should be appreciated that many of the elements discussed in this specification may be implemented in a hardware circuit(s), a processor executing software code or instructions which are encoded within computer readable media accessible to the processor, or a combination of a hardware circuit(s) and a processor or control block of an integrated circuit executing machine readable code encoded within a computer readable media. As such, the term circuit, module, server, application, or other equivalent description of an element as used throughout this specification is, unless otherwise indicated, intended to encompass a hardware circuit (whether discrete elements or an integrated circuit block), a processor or control block executing code encoded in a computer readable media, or a combination of a hardware circuit(s) and a processor and/or control block executing such code.
  • The present disclosure provides a method and device for securing data accessed by a mobile device. The mobile device detects a request to record content displayed on a display of the mobile device. A determination is then made regarding whether the content that was displayed on the screen when the request to record was received is protected content. If the displayed content was protected, then a third party is notified that a security breach has been detected. A remedial action is also performed regarding the security breach.
  • FIG. 1 depicts a system 10 for preventing electronic data from being compromised. In particular, the system prevents protected content from being copied and transferred from the mobile device. The system 10 includes a mobile device 12 and a server 14. The mobile device 12 includes a processor 20 and a memory 22 storing an application 24 and an operating system 28. The application 24 and operating system 28 are executable programs that are executed by the processor 20 of the mobile device 12. The application 24 generates content that is displayed on a display 30 of the mobile device. Some of the content displayed on the display 30 is the protected content.
  • The server 14 may be a computer system of one or more computers or servers. The mobile device 12 may comprise a cellular phone, smart phone, tablet, or any other portable electronic device capable of executing the application 24 and operating system 28. The mobile device 12 and server 14 each include at least a processor, a network interface, and non-transitory computer readable medium. The computer readable medium may include encoded thereon instructions for interfacing with the corresponding network interface and reading and writing data to the corresponding computer readable medium. The computer readable medium may also include computer programs (including the application 24) comprising instructions embodied thereon that are executed by the corresponding processor.
  • The mobile device 12 includes a display 30 configured to display protected content and non-protected content. The display 30 may comprise any suitable display for rendering content, such as a liquid crystal display (LCD), organic light-emitting diode (OLED), light-emitting diode (LED), electronic ink (E-ink), etc. The content displayed by the display 30 may be determined by the operating system 28 and/or applications executed by the processor 20 of the mobile device 12. For example, the application 24 may access protected content 26 stored on the server 14 and display the protected content on the display 30.
  • The processor 20 is configured to access the protected content 26. For example, as explained above, the processor 20 may execute the application 24 that accesses protected content 26 stored on the server 14. Alternatively, the protected content 26 may be stored on the non-transitory computer readable medium 22 of the mobile device 12 and accessed by the application 24.
  • As will be understood by one of ordinary skill in the art, the processor 20 may have various implementations. For example, the processor 20 may include any suitable device, such as a programmable circuit, integrated circuit, memory and I/O circuits, an application specific integrated circuit, microcontroller, complex programmable logic device, other programmable circuits, or the like. The processor 20 may also include a non-transitory computer readable medium, such as random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), or any other suitable medium. The processor 20 may be communicatively coupled to the computer readable medium 22 and network interface 32 through a system bus, mother board, or using any other suitable structure known in the art.
  • The processor 20 is also configured to detect a security breach. The processor 20 detects the security breach by receiving a request 56 to record content currently displayed on the display 30. The request 56 to record content may comprise a user attempting to perform a screen capture of content currently being displayed on the display 30. The request 56 to perform a screen capture may be initiated by a user pressing a predefined combination of keys on an input 34 of the mobile device 12. For example, by simultaneously pushing a physical power button and a physical home screen button of the mobile device 12.
  • Upon receiving the request 56 to record content currently displayed, the processor 20 is configured to determine whether the content displayed on the display 30 when the request was received is protected content 26. That is, the processor 20 is configured to determine whether the displayed content was protected content or non-protected content. The processor 20 may determine that the content being displayed is protected content 26 if an application 24 (executed by the processor 20) generating the content being displayed is flagged as a protected application. That is, the application 24 may be flagged as a protected application such that any content being generated by the application 24 is assumed to be protected content 26. An application 24 may be flagged as a protected application if the process id, the name of the application, the location and name of the executable file, or any other suitable identifying characteristic of the application is stored in a database or list of protected applications stored on the non-transitory computer readable medium 22.
  • Alternatively or additionally, the processor 20 may notify the application 24 generating the content that a request 56 to record was received. The application 24 may then indicate whether the content being displayed was protected content 26 when the request 56 was received. In this way, an application 24 that displays both protected and non-protected content may determine the type of content that was being displayed when the request 56 was received. Upon determining the type of content displayed when the request 56 was received, the application 24 may notify the operating system 28 whether the content was protected content 26. For example, the application 24 may determine whether content currently displayed is protected content 26 based on an identifier associated with the content, the location the content was accessed from, or using any other tag or identifier capable of labeling content as protected content or non-protected content. The application 24 may also store a historical record of when protected content was displayed over a limited duration of time. For example, the application 24 may store a record of when protected content was displayed over the past 10 seconds, 2 seconds, 1 second, 200 milliseconds, or any other suitable duration of time.
  • If it is determined that the content being displayed when the request 56 was received is protected content 26, then the processor 20 determines that a security breach is detected. If a security breach is detected, the processor 20 is configured to optionally notify a third party that the security breach occurred and/or perform a remedial action.
  • The mobile device 12 may notify a third party computer (e.g., the server 14) that a security breach occurred via the network interface 32. That is, the processor 20 may cause the network interface 32 to send a notification via a network 44 that the security breach occurred. As will be understood by one of ordinary skill in the art, the network 44 may comprise a private network, the internet, a wired network, a wireless network, or any other suitable network allowing the mobile device 12 and the third party to communicate with one another.
  • The mobile device 12 is not limited to notifying a single computer device that a security breach occurred, but may instead notify multiple devices (e.g., more than one server) that a security breach occurred. That is, the notification to the third party may include multiple notifications sent to different network locations. The parties notified when a breach occurred may be determined by the application 24 generating the protected content 26. Additionally, the parties contacted may be determined based upon the content being displayed when the security breach occurred. For example, there may be multiple tiers of protected content 26 (e.g., low, medium, and high). In this example, if a security breach occurred while low tier protected content 26 was displayed, then a first server 14 a may be notified. If a security breach occurred while medium tier protected content 26 was displayed, then a second server 14 b (in place of or in addition to the first server 14 a) may be notified (or no notification may be sent). If a security breach occurred while high tier protected content 26 was displayed, then a third server 14 c (in place of or in addition to the first server 14 a and second server 14 b) may be notified.
  • The notification that the security breach occurred may include information identifying at least one of the mobile device or a user of the mobile device. The identifying information may include any suitable information for identifying the mobile device 12 or a user of the mobile device, including a username used to sign into the mobile device 12 or used to access the protected content 26, a geo-location of the device 12, a device identifier, or an image captured by a camera of the mobile device after the request to record was received. The device identifier may comprise a MAC address, a serial number, or any information used to uniquely identify the mobile device 12. The notification that the security breach occurred may additionally or alternatively include a record of the content displayed on the display when the security breach occurred.
  • The processor 20 is also configured to perform a remedial action upon detecting a security breach. The remedial action may be performed before, after, or in place of notifying a third party as described previously. The remedial action may include deleting data stored on the mobile device, capturing an image of a user of the mobile device when the request to capture a screen shot was received, disabling the mobile device, and/or disabling login credentials used to access the protected content. The remedial action may be specified by the application 24 or may be initiated by the third party notified of the security breach. For example, upon receiving the notification of the security breach, the server 14 may instruct the processor 20 to perform a given remedial action. This instruction may be sent to the mobile device 12 via the network 44. In this example, the processor 20 performs the remedial action after receiving a request via the network interface 44 to perform the remedial action. In one example, a default remedial action may be initiated by the application 24 (e.g., disabling login credentials) and instruction to perform an additional or alternative remedial action (e.g., disabling the mobile device) may be sent by the third party.
  • In one embodiment, the third party computer receiving the notification of the security breach includes a communication interface configured to communicate with the network interface of the mobile device and receive the notification from the mobile device. The third party computer also includes a processor configured to receive the notification from the communication interface. In this embodiment, the notification includes information regarding the protected content displayed on the display when the request was received and a user of the mobile device. The processor determines the nature of the protected content displayed on the display when the request was received. For example, the processor may determine the nature of the protected content displayed by comparing the displayed content to the content stored on the third party computer. Based on the nature of the protected content and the user of the mobile device, the processor determines a remedial action to perform. The processor may determine the remedial action by using a lookup table. Finally, the third party computer sends an indication of the remedial action to perform to the mobile device 12.
  • FIG. 2 depicts communication of data within the mobile device 12 and between the mobile device 12 and the server 14. In the figure, the application 24 running on the mobile device 12, optionally sends a request for protected content 52 to the server 14. For example, if a user requests to view their bank statement or other financial data, a request for protected content 52 may be sent to the server 14. The server 14 receives the request 52 and, assuming that all required security procedures are satisfied (e.g., the user authenticates with the server), protected content 26 is sent to the application 24. Alternatively, the protected content 52 may be stored within the memory 22 of the mobile device 12. In this example, the application 24 may access the protected content 26 directly from the memory 22 without sending a request for protected content 52 to the server 14.
  • Upon receiving the protected content 54, the application 24 causes the display 30 to display the protected content 26. The mobile device 12 also includes a device input 34. If the operating system 28 receives a request to record displayed content 56 from the device input 34, then the request 56 may be passed to the application 24. Alternatively, as opposed to passing the request to record 56 to the application 24, the operating system 28 may request information regarding the content displayed at the time that the request to record content 56 was received. In either case, the application 24 may notify the operating system 28 that a security breach occurred 28 if the content being displayed when the request to record 56 was received was protected content. The application 24 may alternatively or additionally notify the server 14 if a security breach 28 occurred.
  • After it is determined that a security breach 28 occurred, instructions to perform a remedial action 60 may be received. The instructions may be received by at least one of the server 14, the operating system 28, or the application 24. The instructions to perform the remedial action 60 may be provided by at least one of the server 14, the operating system 28, or the application 24. For example, the application 24 may contain a list of default remedial actions to perform until further instructions are received from the operating system 28 or the server 14. For example, the application 24 may be configured to only display non-protected content until further instructions are received from the server 14. The server 14 may then send instructions to perform a remedial action, such as locking down the application 24 so that no content is accessible through the application 24.
  • Turning to FIG. 3, a block diagram is shown depicting a method 100 for securing data by detecting a request to record content. Following the start of the method 100 in process block 102, the method 100 determines in decision block 104 whether a request to record content currently displayed on a display of the mobile device was received. If a request was not received, then the method returns back to decision block 104. If a request was received, then process block 108 is performed.
  • In process block 108, the content displayed on the display when the request to record currently displayed content was received is detected. In process block 110, it is determined whether the content displayed on the display when the request was received is protected content or non-protected content. As described above, the type of content displayed may be determined by the application 24 generating the content being displayed. For example, if the application 24 is identified as a protected application, then any content displayed by the application 24 is determined to be protected content. Alternatively, the application 24 may be polled to determine whether the content being displayed when the request was received is protected content. In decision block 112, if the displayed content is non-protected content, then the method returns to decision block 104. If the displayed content is protected content, then the method 100 moves to process block 114.
  • In process block 114, a third party is notified that a security breach has occurred. As described above, the notification that the security breach occurred may include information identifying at least one of the mobile device or a user of the mobile device. The notification that a security breach occurred may alternatively or additionally include a record of the content displayed on the display when the request was received. In process block 116, a remedial action is performed. As described above the remedial action may be performed only after receiving a request to perform the remedial action.
  • The method 100 may run as a background process on the mobile device 12. The method 100 may be included as a part of the operating system 28, the application 24, or as a standalone application.
  • Data (e.g., the request for protected content 52, the protected content 26, notification that a security breach occurred 58, and remedial action 60) may be transferred over a network 44 connecting the mobile device 12 and the server 14. The network 44 may be at least one of a TCP/IP network or a system bus. For example, when a user attempts to transfer data via a USB port, the network 44 would comprise the system bus connecting the USB port and the memory 22 of the mobile device 12.
  • As will be understood by one of ordinary skill in the art, the network 44 is not limited to a single LAN, but may comprise any suitable network of devices. For example, the predefined areas 80 may comprise a collection of LANs, a Bluetooth Network, the Internet, etc.
  • As will be understood by one of ordinary skill in the art, the transmission of data (e.g., the request for protected content 52, the protected content 26, notification that a security breach occurred 58, and remedial action 60) may be transmitted using any suitable protocol (e.g., TCP/IP, Bluetooth, SMTP, HTTP, SSL, PPP, IMAP, or any other suitable network protocol).
  • The processor of the mobile device 12 may identify the location of the corresponding device using a global positioning system (GPS) device, cellular triangulation, WI-FI positioning, or any other suitable technique or device to determine location.
  • As will be understood by one of ordinary skill in the art, the processors of the mobile device 12 and server 14 may have various implementations. For example, each of the processors may include any suitable device, such as a programmable circuit, integrated circuit, memory and I/O circuits, an application specific integrated circuit, microcontroller, complex programmable logic device, other programmable circuits, or the like. Each of the processors may also include a non-transitory computer readable medium, such as random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), or any other suitable medium. Instructions for performing the methods described above may be stored in the non-transitory computer readable medium and executed by the respective processor identified in the description of the method. Each of the processors may be communicatively coupled to the respective computer readable medium and network interface through a system bus, mother board, or using any other suitable structure known in the art.
  • The network interfaces of the mobile device 12, server 14, and predetermined server 14 may each be communicatively coupled to one or more other host devices 12 and receiving devices 14 via a network 44. The network 44 may be an open network, such as the Internet, a private network, such as a virtual private network, or any other suitable network. Each of the network interface may be configured to transmit and/or receive data.
  • As will be understood by one of ordinary skill in the art, each of the network interfaces may comprise a wireless network adaptor, an Ethernet network card, or any suitable device for performing network based communication between devices. Each of the network interface may be communicatively coupled to the respective computer readable medium such that each network interface is able to send data stored on the respective computer readable medium across the network 44 and store received data on the respective computer readable medium. Each of the network interface may also be communicatively coupled to the respective processor such that the processor is able to control operation of the network interface. The respective network interfaces, computer readable medium, and processors may be communicatively coupled through a system bus, mother board, or using any other suitable manner as will be understood by one of ordinary skill in the art.
  • Although the invention has been shown and described with respect to certain exemplary embodiments, it is obvious that equivalents and modifications will occur to others skilled in the art upon the reading and understanding of the specification. It is envisioned that after reading and understanding the present invention those skilled in the art may envision other processing states, events, and processing steps to further the objectives of system of the present invention. The present invention includes all such equivalents and modifications, and is limited only by the scope of the following claims.

Claims (18)

What is claimed is:
1. A mobile device configured to prevent electronic data from being compromised, the mobile device comprising:
a non-transitory computer readable memory;
a network interface;
a display configured to display protected content and non-protected content; and
a processor configured to:
access protected content;
detect a security breach by:
receiving a request to record content currently displayed on the display;
detecting the content displayed on the display when the request to record currently displayed content was received; and
determining that the content displayed on the display when the request was received is the protected content; and
if a security breach is detected:
notify a third party via the network interface that the security breach occurred; and
perform a remedial action.
2. The mobile device of claim 1, wherein the content is determined to be protected content if an application executed by the processor and generating the content being displayed is flagged as a protected application.
3. The mobile device of claim 1, wherein the processor is configured to determine that the content displayed on the display when the request was received is the protected content by:
notifying an application generating the content being displayed that the request to record content was received; and
receiving from the application an indication that the content being displayed is the protected content.
4. The mobile device of claim 1, wherein the notification that the security breach occurred includes information identifying at least one of the mobile device or a user of the mobile device.
5. The mobile device of claim 4, wherein the identifying information includes at least one of a username, a geo-location of the device, a device identifier, or an image captured by a camera of the mobile device after the request to record was received.
6. The mobile device of claim 1, wherein the notification to the third party includes multiple notifications sent to different network locations.
7. The mobile device of claim 1, wherein the notification that the security breach occurred includes a record of the content displayed on the display when the request was received.
8. The mobile device of claim 1, wherein the remedial action comprises at least one of deleting data stored on the mobile device, capturing an image of a user of the mobile device when the request to capture a screen shot was received, disabling the mobile device, or disabling login credentials used to access the protected content.
9. The mobile device of claim 1, wherein the processor performs the remedial action after receiving a request via the network interface to perform the remedial action.
10. A method to prevent data viewed on a mobile device from being compromised, the method comprising:
receiving a request to record content currently displayed on a display of the mobile device;
detecting the content displayed on the display when the request to record currently displayed content was received;
determining if the content displayed on the display when the request was received is the protected content;
if the content displayed when the request was received is the protected content:
notify a third party via a network interface of the mobile device that the security breach occurred; and
perform a remedial action.
11. The method of claim 10, wherein the content is determined to be protected content if an application generating the content being displayed is flagged as a protected application.
12. The method of claim 10, wherein the content displayed on the display when the request was received is determined to be the protected content by:
notifying an application generating the content being displayed that the request to record content was received; and
receiving from the application an indication that the content being displayed is the protected content.
13. The method of claim 10, wherein the notification that the security breach occurred includes information identifying at least one of the mobile device or a user of the mobile device.
14. The method of claim 13, wherein the identifying information includes at least one of a username, a geo-location of the device, a device identifier, or an image captured by a camera of the mobile device after the request to record was received.
15. The method of claim 10, wherein the notification that the security breach occurred includes a record of the content displayed on the display when the request was received.
16. The method of claim 10, wherein the remedial action comprises at least one of deleting data stored on the mobile device, capturing an image of a user of the mobile device when the request to capture a screen shot was received, disabling the mobile device, or disabling login credentials used to access the protected content.
17. The method of claim 10, wherein the remedial action is performed after receiving a request to perform the remedial action.
18. A system configured to prevent data viewed on a mobile device from being compromised, the system including:
the mobile device comprising:
a non-transitory computer readable memory, a network interface, and
a display; and
a processor configured to:
access protected content;
detect a security breach by:
receiving a request to record content currently displayed on the display;
detecting the content displayed on the display when the request to record currently displayed content was received; and
determining that the content displayed on the display when the request was received is the protected content; and
if a security breach is detected, sending a notification to a third party computer via the network interface, wherein the notification indicates that the security breach occurred; and
the third party computer comprising:
a communication interface configured to communicate with the network interface of the mobile device and receive the notification from the mobile device;
a processor configured to:
receive the notification from the communication interface, wherein the notification includes information regarding the protected content displayed on the display when the request was received and a user of the mobile device;
determine the nature of the protected content displayed on the display when the request was received;
based on the nature of the protected content and the user of the mobile device, determine a remedial action to perform;
send an indication of the remedial action to perform to the mobile device;
wherein the processor of the mobile device is further configured to perform the remedial action indicated by the third party computer.
US14/959,492 2015-12-04 2015-12-04 Method to secure protected content on a mobile device Abandoned US20170163664A1 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
US14/959,492 US20170163664A1 (en) 2015-12-04 2015-12-04 Method to secure protected content on a mobile device
TW105138854A TWI787159B (en) 2015-12-04 2016-11-25 Devices, methods and systems to secure protected content by providing notification of data security breach
PCT/US2016/064689 WO2017096206A1 (en) 2015-12-04 2016-12-02 Method to secure protected content on a mobile device
US16/388,242 US11496490B2 (en) 2015-12-04 2016-12-02 Notification of a security breach on a mobile device
US17/970,250 US20230045087A1 (en) 2015-12-04 2022-10-20 Method for Remedying a Security Breach on a Mobile Device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US14/959,492 US20170163664A1 (en) 2015-12-04 2015-12-04 Method to secure protected content on a mobile device

Related Child Applications (2)

Application Number Title Priority Date Filing Date
PCT/US2016/064689 Continuation WO2017096206A1 (en) 2015-12-04 2016-12-02 Method to secure protected content on a mobile device
US16/388,242 Continuation US11496490B2 (en) 2015-12-04 2016-12-02 Notification of a security breach on a mobile device

Publications (1)

Publication Number Publication Date
US20170163664A1 true US20170163664A1 (en) 2017-06-08

Family

ID=57590868

Family Applications (3)

Application Number Title Priority Date Filing Date
US14/959,492 Abandoned US20170163664A1 (en) 2015-12-04 2015-12-04 Method to secure protected content on a mobile device
US16/388,242 Active 2038-06-28 US11496490B2 (en) 2015-12-04 2016-12-02 Notification of a security breach on a mobile device
US17/970,250 Abandoned US20230045087A1 (en) 2015-12-04 2022-10-20 Method for Remedying a Security Breach on a Mobile Device

Family Applications After (2)

Application Number Title Priority Date Filing Date
US16/388,242 Active 2038-06-28 US11496490B2 (en) 2015-12-04 2016-12-02 Notification of a security breach on a mobile device
US17/970,250 Abandoned US20230045087A1 (en) 2015-12-04 2022-10-20 Method for Remedying a Security Breach on a Mobile Device

Country Status (3)

Country Link
US (3) US20170163664A1 (en)
TW (1) TWI787159B (en)
WO (1) WO2017096206A1 (en)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10601867B2 (en) * 2016-06-23 2020-03-24 Fujitsu Limited Attack content analysis program, attack content analysis method, and attack content analysis apparatus
US11163955B2 (en) 2016-06-03 2021-11-02 Bottomline Technologies, Inc. Identifying non-exactly matching text
US20210352105A1 (en) * 2016-12-15 2021-11-11 Interwise Ltd. Deception using screen capture
US11238053B2 (en) 2019-06-28 2022-02-01 Bottomline Technologies, Inc. Two step algorithm for non-exact matching of large datasets
US11269841B1 (en) 2019-10-17 2022-03-08 Bottomline Technologies, Inc. Method and apparatus for non-exact matching of addresses
US11416713B1 (en) 2019-03-18 2022-08-16 Bottomline Technologies, Inc. Distributed predictive analytics data set
US11449870B2 (en) 2020-08-05 2022-09-20 Bottomline Technologies Ltd. Fraud detection rule optimization
US11496490B2 (en) 2015-12-04 2022-11-08 Bottomline Technologies, Inc. Notification of a security breach on a mobile device
US11544798B1 (en) 2021-08-27 2023-01-03 Bottomline Technologies, Inc. Interactive animated user interface of a step-wise visual path of circles across a line for invoice management
US11694276B1 (en) 2021-08-27 2023-07-04 Bottomline Technologies, Inc. Process for automatically matching datasets
US11762989B2 (en) 2015-06-05 2023-09-19 Bottomline Technologies Inc. Securing electronic data by automatically destroying misdirected transmissions

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107180204A (en) * 2017-07-04 2017-09-19 惠州Tcl移动通信有限公司 A kind of method, storage device and mobile terminal for preventing information stolen

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050021650A1 (en) * 2003-07-24 2005-01-27 International Business Machines Corporation Method and system for multiple-party, electronic mail receipts
US8429745B1 (en) * 2011-09-23 2013-04-23 Symantec Corporation Systems and methods for data loss prevention on mobile computing systems
US8844059B1 (en) * 2011-02-15 2014-09-23 Symantec Corporation Method and apparatus for preventing data loss through screen capture
US20150264573A1 (en) * 2014-03-12 2015-09-17 Accenture Global Services Limited Secure distribution of electronic content

Family Cites Families (153)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4575793A (en) 1983-08-19 1986-03-11 Cxi, Inc. Personal-computer to 3270 system interfacing apparatus
US5228122A (en) 1990-01-24 1993-07-13 International Business Machines Corporation Method for bypassing user unwanted display screens from a host controlled terminal
AU5953394A (en) 1992-12-17 1994-07-04 Legent Corporation System and method for generating local area network operating statistics
EP0639814B1 (en) 1993-08-20 2000-06-14 Canon Kabushiki Kaisha Adaptive non-literal textual search apparatus and method
TW299410B (en) 1994-04-04 1997-03-01 At & T Corp
US5600735A (en) 1994-05-10 1997-02-04 Motorola, Inc. Method of recognizing handwritten input
US5634008A (en) 1994-07-18 1997-05-27 International Business Machines Corporation Method and system for threshold occurrence detection in a communications network
US5970482A (en) 1996-02-12 1999-10-19 Datamind Corporation System for data mining using neuroagents
US6205416B1 (en) 1996-04-01 2001-03-20 Openconnect Systems Incorporated Server and terminal emulator for persistent connection to a legacy host system with direct OS/390 host interface
US5912669A (en) 1996-04-29 1999-06-15 Netmanage, Inc. Screen navigation method
US5790798A (en) 1996-05-31 1998-08-04 Witness Systems, Inc. Method and apparatus for simultaneously monitoring computer user screen and telephone activity from a remote location
US5862341A (en) 1996-07-03 1999-01-19 Net Manage, Inc. Screen identification method
US5845369A (en) 1996-10-22 1998-12-08 Dunchock; Richard Stephen Eye glass holder
US6044401A (en) 1996-11-20 2000-03-28 International Business Machines Corporation Network sniffer for monitoring and reporting network information that is not privileged beyond a user's privilege level
US6049833A (en) 1997-08-29 2000-04-11 Cisco Technology, Inc. Mapping SNA session flow control to TCP flow control
US20040193512A1 (en) 1998-09-24 2004-09-30 Parmeshwar Gobin Web based integrated customer interface for invoice reporting
US20020056043A1 (en) 1999-01-18 2002-05-09 Sensar, Inc. Method and apparatus for securely transmitting and authenticating biometric data over a network
US6708163B1 (en) 1999-02-24 2004-03-16 Hillol Kargupta Collective data mining from distributed, vertically partitioned feature space
US6256737B1 (en) 1999-03-09 2001-07-03 Bionetrix Systems Corporation System, method and computer program product for allowing access to enterprise resources using biometric devices
US6523016B1 (en) 1999-04-12 2003-02-18 George Mason University Learnable non-darwinian evolution
EP1192716B1 (en) 1999-05-27 2009-09-23 Tegic Communications, Inc. Keyboard system with automatic correction
DE60045552D1 (en) 1999-06-30 2011-03-03 Apptitude Inc METHOD AND DEVICE TO MONITOR THE NETWORK TRANSPORT
WO2001025908A2 (en) 1999-10-01 2001-04-12 Accenture Llp Presentation service architectures for netcentric computing systems
US20030233305A1 (en) 1999-11-01 2003-12-18 Neal Solomon System, method and apparatus for information collaboration between intelligent agents in a distributed network
US6845369B1 (en) 2000-01-14 2005-01-18 Relevant Software Inc. System, apparatus and method for using and managing digital information
US7299281B1 (en) * 2000-01-27 2007-11-20 Inbit, Inc. Method and system for activating and capturing screen displays associated with predetermined user interface events
US6707942B1 (en) 2000-03-01 2004-03-16 Palm Source, Inc. Method and apparatus for using pressure information for improved computer controlled handwriting recognition, data entry and user authentication
US7263506B2 (en) 2000-04-06 2007-08-28 Fair Isaac Corporation Identification and management of fraudulent credit/debit card purchases at merchant ecommerce sites
AU2001257400A1 (en) 2000-04-28 2001-11-12 Internet Security Systems, Inc. System and method for managing security events on a network
US6930978B2 (en) 2000-05-17 2005-08-16 Deep Nines, Inc. System and method for traffic management control in a data transmission network
US7380272B2 (en) 2000-05-17 2008-05-27 Deep Nines Incorporated System and method for detecting and eliminating IP spoofing in a data transmission network
US7114008B2 (en) 2000-06-23 2006-09-26 Cloudshield Technologies, Inc. Edge adapter architecture apparatus and method
US20020065915A1 (en) 2000-11-30 2002-05-30 Anderson Elizabeth A. System and method for server-host connection management to serve anticipated future client connections
US6687693B2 (en) 2000-12-18 2004-02-03 Ncr Corporation Architecture for distributed relational data mining systems
US7190348B2 (en) 2000-12-26 2007-03-13 International Business Machines Corporation Method for touchscreen data input
US6894979B1 (en) 2001-04-24 2005-05-17 Crossroads Systems, Inc. Network analyzer/sniffer with multiple protocol capabilities
US7634557B2 (en) 2001-04-30 2009-12-15 Netwitness Corporation Apparatus and method for network analysis
US6675164B2 (en) 2001-06-08 2004-01-06 The Regents Of The University Of California Parallel object-oriented data mining system
US7047297B2 (en) 2001-07-17 2006-05-16 Mcafee, Inc. Hierarchically organizing network data collected from full time recording machines and efficiently filtering the same
US20030041042A1 (en) 2001-08-22 2003-02-27 Insyst Ltd Method and apparatus for knowledge-driven data mining used for predictions
US6754550B2 (en) 2001-10-18 2004-06-22 Hurco Companies, Inc. Toleranced digitizing method
GB2386802A (en) 2002-03-18 2003-09-24 Hewlett Packard Co Auditing of secure communication sessions over a communication network
US7092941B1 (en) 2002-05-23 2006-08-15 Oracle International Corporation Clustering module for data mining
US20080104007A1 (en) 2003-07-10 2008-05-01 Jerzy Bala Distributed clustering method
US7308436B2 (en) 2002-07-10 2007-12-11 Inferx Corporation Distributed data mining and compression method and system
AU2003263989A1 (en) 2002-08-05 2004-02-23 Metaedge Corporation Spatial intelligence system and method
US7174462B2 (en) 2002-11-12 2007-02-06 Intel Corporation Method of authentication using familiar photographs
US7941849B2 (en) 2003-03-21 2011-05-10 Imprivata, Inc. System and method for audit tracking
KR100982511B1 (en) 2003-10-08 2010-09-16 삼성전자주식회사 Apparatus and method for remote controlling
IL176551A (en) 2004-01-07 2012-09-24 Intellinx Ltd Apparatus and method for monitoring and auditing activity of a legacy environment
EP1706960B1 (en) 2004-01-07 2014-09-17 Intellinx Ltd. Apparatus and method for monitoring and auditing activity of a legacy environment
US7266537B2 (en) 2004-01-14 2007-09-04 Intelligent Results Predictive selection of content transformation in predictive modeling systems
US20050177483A1 (en) 2004-02-11 2005-08-11 Tradebeam, Inc. Negotiation and fulfillment of insurance conditions and release of goods for export
US7822598B2 (en) 2004-02-27 2010-10-26 Dictaphone Corporation System and method for normalization of a string of words
US20060155751A1 (en) 2004-06-23 2006-07-13 Frank Geshwind System and method for document analysis, processing and information extraction
US7730521B1 (en) 2004-09-23 2010-06-01 Juniper Networks, Inc. Authentication device initiated lawful intercept of network traffic
US20060101048A1 (en) 2004-11-08 2006-05-11 Mazzagatti Jane C KStore data analyzer
US20060229822A1 (en) 2004-11-23 2006-10-12 Daniel Theobald System, method, and software for automated detection of predictive events
US8731983B2 (en) 2005-02-24 2014-05-20 Sap Ag System and method for designing effective business policies via business rules analysis
KR101015352B1 (en) 2005-05-27 2011-02-16 샤프 가부시키가이샤 Display device
US7860783B2 (en) 2005-11-07 2010-12-28 Fair Isaac Corporation Account-level fraud detector and associated methods
US20120151553A1 (en) 2005-11-16 2012-06-14 Azos Ai, Llc System, method, and apparatus for data cognition incorporating autonomous security protection
KR100935776B1 (en) 2005-12-23 2010-01-06 인터내셔널 비지네스 머신즈 코포레이션 Method for evaluating and accessing a network address
US20070277224A1 (en) 2006-05-24 2007-11-29 Osborn Steven L Methods and Systems for Graphical Image Authentication
US20100169958A1 (en) 2006-10-13 2010-07-01 Univeristy Of Idaho Method for generating and using composite scene passcodes
US8229875B2 (en) 2007-04-11 2012-07-24 Oracle International Corporation Bayes-like classifier with fuzzy likelihood
US7864751B2 (en) 2007-08-14 2011-01-04 Greenberg Albert G Traffic engineering method, system and computer program product for managing traffic over dynamic networks during both normal and unexpected traffic scenarios
US8558663B2 (en) 2007-11-30 2013-10-15 Bank Of America Corporation Integration of facial recognition into cross channel authentication
KR100933679B1 (en) 2007-12-28 2009-12-23 성균관대학교산학협력단 Graphic password input device and method of embedded system using wheel interface
US8232973B2 (en) 2008-01-09 2012-07-31 Apple Inc. Method, device, and graphical user interface providing word recommendations for text input
WO2009121417A1 (en) 2008-04-04 2009-10-08 Telefonaktiebolaget Lm Ericsson (Publ) Method and device for access to a directory
US8392975B1 (en) 2008-05-29 2013-03-05 Google Inc. Method and system for image-based user authentication
US8515862B2 (en) 2008-05-29 2013-08-20 Sas Institute Inc. Computer-implemented systems and methods for integrated model validation for compliance and credit risk
US7979426B2 (en) 2008-06-05 2011-07-12 Samsung Electronics Co., Ltd. Clustering-based interest computation
US8683582B2 (en) 2008-06-16 2014-03-25 Qualcomm Incorporated Method and system for graphical passcode security
JP5535230B2 (en) 2008-10-23 2014-07-02 アビニシオ テクノロジー エルエルシー Fuzzy data manipulation
KR20100060192A (en) 2008-11-27 2010-06-07 삼성전자주식회사 Apparatus and method for controlling locking function with a direction sensor in a portable device
US8941466B2 (en) 2009-01-05 2015-01-27 Polytechnic Institute Of New York University User authentication for devices with touch sensitive elements, such as touch sensitive display screens
US8638939B1 (en) 2009-08-20 2014-01-28 Apple Inc. User authentication on an electronic device
US8229876B2 (en) 2009-09-01 2012-07-24 Oracle International Corporation Expediting K-means cluster analysis data mining using subsample elimination preprocessing
WO2011027352A1 (en) 2009-09-03 2011-03-10 Mcafee, Inc. Network access control
US8606227B2 (en) 2009-09-22 2013-12-10 At&T Intellectual Property I, L.P. Secure access to restricted resource
KR20110066508A (en) 2009-12-11 2011-06-17 삼성전자주식회사 Method and apparatus for inputting integrated iogging in portable terminal
EP2531930A1 (en) 2010-02-01 2012-12-12 Ginger Software, Inc. Automatic context sensitive language correction using an internet corpus particularly for small keyboard devices
US20110251951A1 (en) 2010-04-13 2011-10-13 Dan Kolkowitz Anti-fraud event correlation
CA3007805C (en) 2010-04-29 2019-11-26 The Regents Of The University Of California Pathway recognition algorithm using data integration on genomic models (paradigm)
TWI409679B (en) 2010-06-04 2013-09-21 Au Optronics Corp Optical touch panel and touch display panel and touch input method thereof
KR101520455B1 (en) 2010-11-04 2015-05-21 뉘앙스 커뮤니케이션즈, 인코포레이티드 Spell-check for a keyboard system with automatic correction
US8997172B2 (en) * 2010-11-08 2015-03-31 Citrix Systems, Inc. Controlling information disclosure during application streaming and publishing
US20120124662A1 (en) 2010-11-16 2012-05-17 Baca Jim S Method of using device motion in a password
JP5649169B2 (en) 2010-11-22 2015-01-07 インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Machines Corporation Method, apparatus and computer program for moving object by drag operation on touch panel
CN102004878A (en) * 2010-11-22 2011-04-06 北京北信源软件股份有限公司 Anti-screenshot technology-based file data protection method
US8650624B2 (en) 2010-12-16 2014-02-11 Blackberry Limited Obscuring visual login
WO2013002821A1 (en) * 2011-06-30 2013-01-03 Intel Corporation System and method for controlling access to protected content
US8776213B2 (en) 2011-07-07 2014-07-08 Bottomline Technologies (De), Inc. Mobile application security system and method
US9537848B2 (en) 2011-07-07 2017-01-03 Bottomline Technologies, Inc. Application security system and method
US8955154B2 (en) 2011-07-08 2015-02-10 Credibility Corp. Single system for authenticating entities across different third party platforms
US9020250B2 (en) 2011-09-19 2015-04-28 Haileo, Inc. Methods and systems for building a universal dress style learner
US8886925B2 (en) * 2011-10-11 2014-11-11 Citrix Systems, Inc. Protecting enterprise data through policy-based encryption of message attachments
US20130117246A1 (en) 2011-11-03 2013-05-09 Sebastien Cabaniols Methods of processing text data
US9384493B2 (en) 2012-03-01 2016-07-05 Visa International Service Association Systems and methods to quantify consumer sentiment based on transaction data
US8881005B2 (en) 2012-04-20 2014-11-04 King Abdulaziz City For Science And Technology Methods and systems for large-scale statistical misspelling correction
US20140067656A1 (en) 2012-09-06 2014-03-06 Shlomo COHEN GANOR Method and system for fraud risk estimation based on social media information
US9489627B2 (en) 2012-11-19 2016-11-08 Bottomline Technologies (De), Inc. Hybrid clustering for data analytics
US20140149130A1 (en) 2012-11-29 2014-05-29 Verizon Patent And Licensing Inc. Healthcare fraud detection based on statistics, learning, and parameters
US9123106B2 (en) * 2012-12-13 2015-09-01 Microsoft Technology Licensing, Llc Watermarking screen capture content
US9699271B2 (en) * 2013-01-29 2017-07-04 Blackberry Limited Method and apparatus for suspending screen sharing during confidential data entry
WO2014145395A2 (en) 2013-03-15 2014-09-18 Rohter Consulting LLC System and method for consumer fraud protection
US9626493B2 (en) 2013-06-08 2017-04-18 Microsoft Technology Licensing, Llc Continuous digital content protection
WO2015013954A1 (en) 2013-08-01 2015-02-05 Google Inc. Near-duplicate filtering in search engine result page of an online shopping system
US9544306B2 (en) * 2013-10-29 2017-01-10 Airwatch Llc Attempted security breach remediation
US9519758B2 (en) * 2014-02-04 2016-12-13 Pegasus Media Security, Llc System and process for monitoring malicious access of protected content
US20150348041A1 (en) 2014-06-02 2015-12-03 Bottomline Technologies (De) Inc. Fraud scoring method and system for use with payment processing
CN104077539A (en) * 2014-07-09 2014-10-01 肖龙旭 Screen capture prevention method based on program windows
US9690847B2 (en) 2014-08-07 2017-06-27 Google, Inc. Selecting content using query-independent scores of query segments
US9589074B2 (en) 2014-08-20 2017-03-07 Oracle International Corporation Multidimensional spatial searching for identifying duplicate crash dumps
US10152680B1 (en) 2014-09-26 2018-12-11 Square, Inc. Appointment and payment handling
US9898610B1 (en) * 2014-10-22 2018-02-20 State Farm Mutual Automobile Insurance Company System and method for concealing sensitive data on a computing device
CN104408376A (en) * 2014-10-28 2015-03-11 深圳市大成天下信息技术有限公司 File protection method, equipment and system
US9443102B2 (en) * 2015-01-19 2016-09-13 International Business Machines Corporation Protecting content displayed on a mobile device
US9691085B2 (en) 2015-04-30 2017-06-27 Visa International Service Association Systems and methods of natural language processing and statistical analysis to identify matching categories
US20160352759A1 (en) 2015-05-25 2016-12-01 Yan Zhai Utilizing Big Data Analytics to Optimize Information Security Monitoring And Controls
US11762989B2 (en) 2015-06-05 2023-09-19 Bottomline Technologies Inc. Securing electronic data by automatically destroying misdirected transmissions
US10511605B2 (en) 2015-06-05 2019-12-17 Bottomline Technologies (De), Inc. Method for securing electronic data by restricting access and transmission of the data
US10545920B2 (en) 2015-08-04 2020-01-28 International Business Machines Corporation Deduplication by phrase substitution within chunks of substantially similar content
US10242258B2 (en) 2015-09-30 2019-03-26 Microsoft Technology Licensing, Llc Organizational data enrichment
US10045092B2 (en) * 2015-10-16 2018-08-07 Disney Enterprises, Inc. Device-resident content protection
US9818116B2 (en) 2015-11-11 2017-11-14 Idm Global, Inc. Systems and methods for detecting relations between unknown merchants and merchants with a known connection to fraud
US10176526B2 (en) 2015-11-30 2019-01-08 Hartford Fire Insurance Company Processing system for data elements received via source inputs
US20170163664A1 (en) 2015-12-04 2017-06-08 Bottomline Technologies (De) Inc. Method to secure protected content on a mobile device
US10467631B2 (en) 2016-04-08 2019-11-05 International Business Machines Corporation Ranking and tracking suspicious procurement entities
US10210518B2 (en) 2016-04-13 2019-02-19 Abdullah Abdulaziz I. Alnajem Risk-link authentication for optimizing decisions of multi-factor authentications
US10235356B2 (en) 2016-06-03 2019-03-19 Bottomline Technologies (De), Inc. Dual authentication method for identifying non-exactly matching text
US11163955B2 (en) 2016-06-03 2021-11-02 Bottomline Technologies, Inc. Identifying non-exactly matching text
US10607228B1 (en) 2016-08-24 2020-03-31 Jpmorgan Chase Bank, N.A. Dynamic rule strategy and fraud detection system and method
US11301765B2 (en) 2016-10-18 2022-04-12 Paypal, Inc. Processing machine learning attributes
WO2018087190A1 (en) 2016-11-11 2018-05-17 Octimine Technologies Gmbh Apparatus and method for semantic search
US10552841B1 (en) 2016-12-15 2020-02-04 Worldpay, Llc Systems and methods for partial authorization of electronic transactions
US10607008B2 (en) 2017-02-09 2020-03-31 International Business Machines Corporation Counter-fraud operation management
US10320800B2 (en) 2017-03-13 2019-06-11 International Business Machines Corporation Fraud detection mechanism
US10621587B2 (en) 2017-04-10 2020-04-14 Bank Of America Corporation Fraud remediation tool
US11301878B2 (en) 2017-06-01 2022-04-12 Databook Labs Inc. Peer-group based business information system
US10414197B2 (en) 2017-09-20 2019-09-17 Jesurum Scientific Enterprises, Inc. Check fraud prevention method
US10552837B2 (en) 2017-09-21 2020-02-04 Microsoft Technology Licensing, Llc Hierarchical profiling inputs and self-adaptive fraud detection system
US11250082B2 (en) 2017-12-21 2022-02-15 Paypal, Inc. Text processing of message data for item query submission
US20190228411A1 (en) 2018-01-23 2019-07-25 First Performance LLC Methods and systems for improving merchant data
US10965673B2 (en) 2018-05-11 2021-03-30 Civic Technologies, Inc. User ID codes for online verification
US20200019964A1 (en) 2018-07-11 2020-01-16 Mastercard International Incorporated Systems and methods for use in permitting restricted network transactions
US10402817B1 (en) 2018-10-12 2019-09-03 Capital One Services, Llc Relaxed fraud detection for transactions using virtual transaction cards
US10510083B1 (en) 2018-11-26 2019-12-17 Capital One Services, Llc Inactive blank checks
US10440015B1 (en) 2019-01-10 2019-10-08 Capital One Services, Llc Techniques for peer entity account management
US10523681B1 (en) 2019-05-28 2019-12-31 Capital One Services, Llc Techniques to automatically update payment information in a compute environment
US11042555B1 (en) 2019-06-28 2021-06-22 Bottomline Technologies, Inc. Two step algorithm for non-exact matching of large datasets

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050021650A1 (en) * 2003-07-24 2005-01-27 International Business Machines Corporation Method and system for multiple-party, electronic mail receipts
US8844059B1 (en) * 2011-02-15 2014-09-23 Symantec Corporation Method and apparatus for preventing data loss through screen capture
US8429745B1 (en) * 2011-09-23 2013-04-23 Symantec Corporation Systems and methods for data loss prevention on mobile computing systems
US20150264573A1 (en) * 2014-03-12 2015-09-17 Accenture Global Services Limited Secure distribution of electronic content

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11762989B2 (en) 2015-06-05 2023-09-19 Bottomline Technologies Inc. Securing electronic data by automatically destroying misdirected transmissions
US11496490B2 (en) 2015-12-04 2022-11-08 Bottomline Technologies, Inc. Notification of a security breach on a mobile device
US11163955B2 (en) 2016-06-03 2021-11-02 Bottomline Technologies, Inc. Identifying non-exactly matching text
US10601867B2 (en) * 2016-06-23 2020-03-24 Fujitsu Limited Attack content analysis program, attack content analysis method, and attack content analysis apparatus
US20210352105A1 (en) * 2016-12-15 2021-11-11 Interwise Ltd. Deception using screen capture
US11609971B2 (en) 2019-03-18 2023-03-21 Bottomline Technologies, Inc. Machine learning engine using a distributed predictive analytics data set
US11853400B2 (en) 2019-03-18 2023-12-26 Bottomline Technologies, Inc. Distributed machine learning engine
US11416713B1 (en) 2019-03-18 2022-08-16 Bottomline Technologies, Inc. Distributed predictive analytics data set
US11238053B2 (en) 2019-06-28 2022-02-01 Bottomline Technologies, Inc. Two step algorithm for non-exact matching of large datasets
US11269841B1 (en) 2019-10-17 2022-03-08 Bottomline Technologies, Inc. Method and apparatus for non-exact matching of addresses
US11449870B2 (en) 2020-08-05 2022-09-20 Bottomline Technologies Ltd. Fraud detection rule optimization
US11954688B2 (en) 2020-08-05 2024-04-09 Bottomline Technologies Ltd Apparatus for fraud detection rule optimization
US11544798B1 (en) 2021-08-27 2023-01-03 Bottomline Technologies, Inc. Interactive animated user interface of a step-wise visual path of circles across a line for invoice management
US11694276B1 (en) 2021-08-27 2023-07-04 Bottomline Technologies, Inc. Process for automatically matching datasets

Also Published As

Publication number Publication date
US20190373001A1 (en) 2019-12-05
US11496490B2 (en) 2022-11-08
US20230045087A1 (en) 2023-02-09
WO2017096206A9 (en) 2019-01-31
TWI787159B (en) 2022-12-21
TW201723907A (en) 2017-07-01
WO2017096206A1 (en) 2017-06-08

Similar Documents

Publication Publication Date Title
US20230045087A1 (en) Method for Remedying a Security Breach on a Mobile Device
US10375116B2 (en) System and method to provide server control for access to mobile client data
US10511605B2 (en) Method for securing electronic data by restricting access and transmission of the data
US9560026B1 (en) Secure computer operations
EP2761429B1 (en) Policy compliance-based secure data access
US11762989B2 (en) Securing electronic data by automatically destroying misdirected transmissions
US11200338B2 (en) Tagging and auditing sensitive information in a database environment
US11455424B2 (en) Tagging and auditing sensitive information in a database environment
US20170316196A1 (en) Controlling user access to electronic resources without password
CN109688145B (en) Method and device for protecting privacy information
US10298399B2 (en) Location-locked data
US11797706B2 (en) Mobile device network traffic modification and user based restrictions on data access
US20120311722A1 (en) Electronic systems with data protection functions
WO2015076790A1 (en) Context-aware proactive threat management system
US20150082445A1 (en) Information processing method and electronic device
US10235541B2 (en) System and method for confidential data management
CN107797731B (en) Information processing method, system and mobile terminal
US10810319B2 (en) Secure release of print jobs in printing devices
NO20190041A1 (en) System for responding to an alarm

Legal Events

Date Code Title Description
AS Assignment

Owner name: BOTTOMLINE TECHNOLOGIES (DE) INC., NEW HAMPSHIRE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NAGALLA, DURGA;DEEB, ALEXANDER;SIGNING DATES FROM 20151120 TO 20151202;REEL/FRAME:037872/0848

AS Assignment

Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, NO

Free format text: NOTICE OF GRANT OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BOTTOMLINE TECHNOLOGIES (DE), INC.;REEL/FRAME:040882/0908

Effective date: 20161209

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: BOTTOMLINE TECHNLOGIES, INC., NEW HAMPSHIRE

Free format text: CHANGE OF NAME;ASSIGNOR:BOTTOMLINE TECHNOLOGIES (DE), INC.;REEL/FRAME:055661/0461

Effective date: 20201104

AS Assignment

Owner name: BOTTOMLINE TECHNOLOGIES (DE), INC., NEW HAMPSHIRE

Free format text: RELEASE OF SECURITY INTEREST IN REEL/FRAME: 040882/0908;ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:060063/0701

Effective date: 20220513