CA2471604A1 - Multiple trust modes for handling data - Google Patents
Multiple trust modes for handling data Download PDFInfo
- Publication number
- CA2471604A1 CA2471604A1 CA002471604A CA2471604A CA2471604A1 CA 2471604 A1 CA2471604 A1 CA 2471604A1 CA 002471604 A CA002471604 A CA 002471604A CA 2471604 A CA2471604 A CA 2471604A CA 2471604 A1 CA2471604 A1 CA 2471604A1
- Authority
- CA
- Canada
- Prior art keywords
- user
- sensitive data
- trust
- mode
- modes
- 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.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting 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/6245—Protecting personal data, e.g. for financial or medical purposes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
Abstract
A user is presented with multiple modes of operation, such that the multiple modes of operation define different trust options for handling data (such as login credentials or other sensitive data) associated with the user (306). A
selection of one of the multiple modes of operation is received from the user (308). Data associated with the user is handled in accordance with the selected mode of operation (310).
selection of one of the multiple modes of operation is received from the user (308). Data associated with the user is handled in accordance with the selected mode of operation (310).
Description
MULTIPLE TRUST MODES FOR HANDLING DATA
TECHNICAL FIELD
a The present invention relates to the handling data and, more particularly, to 3 the use of multiple trust modes that define the manner in which certain data is ø handled.
BACKGROUND
7 Users that interact with online services that involve, for example, financial data or financial transactions (e.g., accessing financial accounts, or buying or selling goods or services) are often required to provide data to the online service.
~o This data may include bank account numbers, credit card numbers, passwords, and n the like. Many existing online services store the data provided by the users of the iz online services. Some users may not be comfortable with their data being stored n by a third party and, as a result, are reluctant to use the online services offered by ia. these third parties. Thus, users are often faced with the decision to allow their is data to be stored by a third party or to forego the services offered by the third 16 party.
m Similar problems occur with other types of online accounts and online is relationships where credentials are issued to a user. With these types of accounts, 19 when the user's credentials are stored, for example, on a server associated with the zo online account ox other online service, those credentials are at risk of being ai accessed by an unauthorized person, thereby compromising the security of the za user's account.
as The systems and methods described herein address these and other 24 problems by providing multiple trust modes that allow a user to determine how the as user's data is handled.
a SUMMARY
The system and methods described herein provide users of online services with multiple options regarding how the user's data is handled. A particular s option is selected by each user based on that user's level of trust in the system or organization that is handling the user's data. Certain options allow the system or 7 organization to store the data while other options require the system or organization to avoid persistently storing the data when finished processing the user's request or transaction.
to A particular embodiment presents a user with multiple modes of operation.
n The multiple modes of operation define different trust options for handling ~z sensitive data associated with the user. A selection is received from the user, 13 where the selection is one of the multiple modes of operation. The sensitive data 14 associated with the user is handled in accordance with the selected mode of is operation.
In one embodiment, the multiple modes include a low trust option that 17 retrieves sensitive data from the user each time the user requests a service 18 requiring the sensitive data.
i9 In another embodiment, the multiple modes include a moderate trust option ao that retrieves sensitive data from the user and stores the sensitive data in an zi encrypted format using a password known only to the user.
as In a particular embodiment, the multiple modes include a high trust option z3 that retrieves sensitive data from the user and stores the sensitive data in an 24 encrypted format for future use.
zs z Fig. 1 illustrates an exemplary network environment in which various 3 servers, computing devices, and a financial analysis system exchange data across a network, such as the Internet.
s Fig. 2 is a block diagram showing exemplary components and modules of a 6 financial analysis system.
7 Fig. 3 is a flow diagram illustrating a procedure in which a user registers an s account with the financial analysis system.
9 Fig. 4 is a flow diagram illustrating a procedure for automatically updating to user accounts having a High Trust Mode of operation.
11 Fig. 5 is a flow diagram illustrating a procedure for updating one or more lz user accounts.
is ~~ Fig. 6 is a flow diagram illustrating a procedure for allowing financial la.~~ institutions to select among multiple trust modes that are made available to is I I customers of the financial institutions.
16 ~ ~ Fig. 7 is a block diagram showing pertinent components of a computer in 17 II accordance with the invention.
zo DETAILED DESCRIPTION
zl The systems and methods described herein provide various modes of zz operation that determine how user data is handled. A particular mode of operation z3 is selected by each user based on the user's level of trust in the system or za. organization that is handling the data. A high level of trust allows the system or zs organization to store data, such as user credentials and other sensitive data, for 1 later use. A moderate level of trust allows the system or organization to store a sensitive data in an encrypted format using a key derived frorri the user's password 3 (l.e., the user associated with the sensitive data). A low level of trust does not a. allow the system or organization to store any sensitive data persistently.
A user s can change the level of trust associated with a particular account to reflect changes 6 in their attitude toward the system or organization.
7 As used herein, the terms "account holder", "customer", "user", and 8 "client" are interchangeable. "Account holder" refers to any person having access 9 to an account. A particular account may have multiple account holders (e.g., a to joint checking account having husband and wife as account holders or a corporate l account identifying multiple corporate employees as account holders).
Various la financial account and financial institution examples are provided herein for is purposes of explanation. However, it will be appreciated that the system and la. procedures described herein can be used with any type of asset account, any type is of debt account, and any type of financial institution. Example asset accounts 16 include savings accounts, money market accounts, checking accounts (both 17 interest-bearing and non-interest-bearing), certificates of deposit (CDs), mutual la funds, bonds, and equities. Example debt accounts include credit card accounts, m mortgage accounts, home equity loans, overdraft protection, margin accounts, ao personal loans, and other types of loans. Exemplary financial institutions include zi banks, savings and loans, credit unions, mortgage companies, mutual fund as companies, lending companies, and stock brokers.
zs Various financial account and financial institution examples are provided 24 herein for purposes of explanation. However, the methods and procedures as described herein can be applied to any type of transaction involving any type of account. For example, a data aggregation system may aggregate data from 2 multiple sources, such as multiple financial accounts, multiple email accounts, 3 multiple online award (or reward) accounts, multiple news headlines, and the like.
a Similarly, the data retrieval and data processing systems and methods discussed s herein may be applied to collect data from any type of account containing any type 6 of data. Thus, the methods and systems described herein can be applied to a data 7 aggregation system or any other account management system instead of the s financial analysis system discussed in the examples provided herein.
Although particular examples discussed herein refer to the handling of a to user's "sensitive data", the methods and systems described herein may be applied 11 to any type of data associated with a user, an organization or other entity.
lz Fig. 1 illustrates an exemplary network environment 100 in which various i3 servers, computing devices, and a financial analysis system exchange data across a la data communication network. The network environment of Fig. 1 includes is multiple financial institution servers 102, 104, and 106 coupled to a data 16 communication network 108, such as the Internet. Each of the financial institution i7 servers 102, 104, and 106 are typically associated with a particular financial ~s institution and store data for that financial institution, such as customer account data. As shown in Fig. 1, a client computer 110 and a financial analysis system zo 112 are also coupled to network 108. A database 114 is coupled to financial analysis system 112 for storing various data used by the financial analysis system.
z2 Network 108 may be any type of data communication network using any 23 communication protocol. Further, network 108 may include one or more sub-aa networks (not shown) which are interconnected with one another. Although only a few devices are shown coupled to network 108 in Fig. 1, a particular network may 2 include any number of devices coupled to one another.
The communication links shown between the network 108 and the various a. devices (102-106 and 110-112) shown in Fig. 1 can use any type of s communication medium and any communication protocol. For example, one or 6 more of the communication links shown in Fig. 1 may be a wireless link (e.g., a 7 radio frequency (RF) link or a microwave link) or a wired link accessed via a $ public telephone system or another communication network. Certain devices, 9 such as servers, may be coupled to a local area network (LAN), which is coupled ~o to network 108. Client computer 110 may access network 108 in different ways.
11 First, client computer 110 may directly access network 108, for example, by using a modem to access a public telephone network (e.g., a public switched telephone is network (PSTN)) that is coupled to network 108.
ia. Financial analysis system 112 performs various analysis and data is integration functions with respect to user accounts. These analysis functions are discussed in greater detail below. Client computer 110 allows a user to access 17 information via the network 108. Client computer may be any type of computing is device, such as a laptop computer, desktop computer, personal digital assistant (PDA), cellular phone, or set top box. For example, the user can access account ao information from one of the financial institution servers 102, 104, or 106, or send zl a request for an analysis or summary of the user's financial accounts to financial 22 analysis system 112.
zs In a particular embodiment, the methods and systems described herein 24 provide an Internet-based server solution where the sensitive data of one or more zs users is stored on a server, not a client.
Fig. 2 is a block diagram showing exemplary components and modules of z financial analysis system 112. A communication interface 202 allows the financial 3 analysis system 112 to communicate with other devices, such as one or more a. financial institution servers and client computers. In one embodiment, s communication interface 202 is a network interface to a local area network (LAl~, 6 which is coupled to another data communication network, such as the Internet.
7 A database access module 204 allows financial analysis system 112 to store s data to database 114 and retrieve data from the database. Financial analysis system 112 also stores various financial institution data 206, which may be used to io locate and communicate with various financial institution servers.
Financial a institution data 206 includes, for example, Uniform Resource Locators (URLs) 12 and login parameters.
A data extraction module 208 retrieves (or extracts) data from web pages or la. other data sources. The data extraction module 208 may use one or more data ~s harvesting scripts 212 (also referred to as screen scraping scripts) to retrieve data ~6 from a web page or other data source. Data harvesting (or screen scraping) is a i7 process that allows a script to retrieve data from one or more web pages associated is with a web site. The retrieved data may be stored in a database, such as database 1~ 114 (Fig. 1). The data harvesting scripts are capable of navigating web sites and ao capturing individual HTML pages. Typically, JavaScript and images are removed 21 from the HTML pages or converted into HTML text if it contains account zz information. A parser then converts the HTML data into a field-delimited XML
z3 format. Data is then extracted from the XML format and stored in a database or z~ other storage mechanism.
2s Financial analysis system 112 also includes user account data 210 and a 2 data handling module 214. User account data 210 typically includes information 3 regarding the types of accounts are maintained by particular users as well as the 4 locations of the accounts (i.e., the financial institution that handles the account) s and account balances. The user account data 210 may also indicate the level of 6 trust associated with each user account. User account data 210 may be stored in 7 database 114 coupled to financial analysis system 112. Data handling module s determines how account data is handled based on the level of trust associated with 9 the account data and other factors.
to Fig. 3 is a flow diagram illustrating a procedure 300 in which a user l registers an account with the financial analysis system. Initially, a user generates a ~2 request to have the financial analysis system monitor one or more of the user's is accounts (block 302). The financial analysis system there collects information la. from the user regarding the user accounts to be monitored (block 304).
This ~s information may include, for example, an account number, password to access the ~6 account online, the financial institution associated with the account, and the name i7 or names listed on each account. The financial analysis system then presents the ~s user with three different trust options for handling sensitive data associated with 19 the user (block 306). This sensitive data may include, for example, the account 2o number and password used to access the account online. In a particular 2i embodiment, the sensitive data is the user login data (e.g., the username and 22 password used to access an account). Although various examples discussed herein 2s offer three different trust options for handling sensitive data, alternate 2a. embodiments may include fewer trust options or a greater number of trust options depending on the preferences of the users andlor the administrators of the financial z analysis system.
In a particular embodiment, the three different trust options for handling a. sensitive data are referred to as "High Trust Option", "Moderate Trust Option", s and "Low Trust Option".
High Trust Option A user selects the High Trust Option if the user is comfortable with having the financial analysis system store the user's sensitive data. When this option is io selected, the financial analysis system stores the user's sensitive data for future m use, such as automatically updating the user's account balances. The user's iz sensitive data is stored using a two-way data encryption technique, which allows a 13 user key (derived from the user's password) or a key maintained by the financial ia. analysis system to decrypt the sensitive data. In one embodiment, the user's is sensitive data is encrypted using a Triple DES (Data Encryption Standard) 16 algorithm. The Triple DES algorithm is a variation of the DES standard and has i7 been endorsed by the National Institute of Standards and Technology (NIST).
is Triple DES uses three 64-bit keys, for an overall key length of 192 bits.
The ~9 encryption procedure is similar to DES, but it is repeated three times. The data is zo encrypted with the first key, decrypted with the second key, and encrypted again z~ with the third key.
zz Since the financial analysis system stores the user's account number and 23 password, the system is then able to automatically retrieve the user's account 24 balances using, for example; the data harvesting procedure discussed above.
3 Moderate Trust Option a. A user selects the Moderate Trust Option if they are not comfortable with s the High Trust Option, but don't want to have to enter their sensitive information 6 each time they access the financial analysis system. When this option is selected, 7 the financial analysis system stores the user's sensitive information, but the s sensitive information is encrypted such that the information can only be decrypted when the user is online (i.e., logged into the financial analysis system). For to example, the data can be encrypted using a key derived from the user's password.
n This encryption technique is referred to as one-way encryption because only one 12 ,key (associated with the user's password) can decrypt the sensitive data.
A
~3 particular embodiment of the one-way encryption uses HMAC-MDS. HMAC
i4 (Keyed-Hashing Message Authentication) is a mechanism for message is authentication using cryptographic hash functions. HMAC can be used with any m iterative cryptographic hash function, such as MDS. This combination is referred 17 to as HMAC-MDS. MD5 is a message digest function, which is a function that is takes a variable-length message and produces a fixed-length hash. MD5 is an ~~ example of a public one-way hash function.
2o When the user logs into the financial analysis system, the system 2~ automatically decrypts the user's sensitive information, which can then be used to 22 retrieve updated information regarding the user's financial accounts.
2a. Low Trust Option 2s A user selects the Low Trust Option if they are not comfortable with the a financial analysis system storing any of the user's sensitive data. When this option 3 is selected, the user's sensitive data is not persistently stored by the financial 4 analysis system. Thus, the user must re-enter the sensitive data each time the user s logs into the financial analysis system.
Refernng again to Fig. 3, at block 308 the user selects one of the three trust 7 options for each user account. The user may select a different trust option for a different accounts or different financial institutions. For example, the user may assign a High Trust Option to a savings account and assign a Moderate Trust to Option to a brokerage account. The financial analysis system then stores the m selected trust option for each account (block 310). This information is stored, for i2 example, in database 114. The trust option associated with each of the user's is institutions can be retrieved from the database each time the user logs into the i4 financial analysis system.
~s Fig. 4 is a flow diagram illustrating a procedure 400 for automatically i6 updating user accounts having a High Trust Mode of operation. Initially, the procedure 400 determines whether it is time to perform automatic account updates ~a (block 402). For example, High Trust Mode accounts may be updated automatically each business day. Other accounts may be updated hourly, weekly, ao monthly, or at other time intervals. In one embodiment, the account updates are zi performed as batch processes at predetermined times. If one or more automatic as account updates are due to be performed, the financial analysis system identifies as account information associated with High Trust Mode accounts (block 404).
The aa. system then retrieves current account information from all High Trust Mode as accounts (block 406), e.g., using the data harvesting procedure discussed above.
i The system then updates the various account information in the database with the a retrieved information (block 408). The procedure then returns to block 402 to 3 await the next automatic account update time. Thus, all user accounts that are a. designated High Trust Mode are automatically accessed to retrieve current account s balances and other information. This retrieved data may be aggregated with data 6 retrieved from other accounts using any data retrieval process.
7 Fig. 5 is a flow diagram illustrating a procedure 500 for updating one or s more user accounts. Initially, a user logs on to the financial analysis system (block 502). The user then requests to refresh account information (block 504). The to financial analysis system identifies the user's account information, which includes l decrypting the user's sensitive data (block 506). The procedure 500 then ~2 determines whether any of the user's accounts are Low Trust Mode accounts 13 (block 508). If at least one of the user's accounts is a Low Trust Mode account, m the financial analysis system asks the user for the missing credential (block 510), is such as the user's password. As discussed above, the financial analysis system i6 does not store any of the user's sensitive data related to Low Trust Mode accounts.
17 Therefore, the user must provide the user ID and password, and explicitly request ~a that the financial analysis system retrieve the current account information from the Low Trust Mode accounts. In alternate embodiments, the financial analysis ao system stores the user ID associated with Low Trust Mode accounts, but requires zi the user to enter the appropriate password each time the account is accessed.
22 The procedure then retrieves the current account information from all of the z3 user's accounts, including Low Trust Mode accounts, Moderate Trust Mode aa. accounts, and High Trust Mode accounts (block 512). The financial analysis as system then updates the account information contained in the database with the 1 retrieved information (block 514). In one embodiment, only Moderate Trust Mode 2 accounts are updated when the user logs on to the financial analysis system.
In s other embodiments, the financial analysis system may also update the user's High Trust Mode accounts and/or the user's Low Trust Mode accounts.
s Fig. 6 is a flow diagram illustrating a procedure 600 for allowing partners 6 to select among multiple trust modes that are made available to customers of the 7 partners. A partner may be any organization that implements, for example, the s systems described herein. Alternatively, a partner may be an organization that has 9 the various services described herein implemented by another on behalf of the ~o organization. Further, a partner may be an organization that provides a portal to another web site, such as a web site that implements the systems described herein.
12 An organization that hosts a web site having an online registration requirement i3 may also be a partner.
la In certain situations, the financial analysis system provides data aggregation ~s functions for one or more partners. These partners may want to limit the number of trust modes that are offered to their customers. Initially, the financial analysis 17 system notifies one or more partners of the multiple trust modes available to users is (block 602). Each partner then determines which trust modes should be made m available to its customers (block 604). For example, a particular partner might not zo want to be responsible for storing the user's sensitive data in a two-way encrypted 21 format (High Trust Mode) and doesn't want to offer that option to its customers.
22 Each partner communicates the selected trust modes to the financial analysis z3 system (block 606). The financial analysis system maintains a listing of all 24 partners and their associated trust modes (block 608). This listing may be stored, zs for example, in database 114 (Fig. 1). Before allowing a user to set up a new 1 account with the financial analysis system, the system first checks to see if the z partner associated with the new account (if any) has any restrictions on the types 3 of trust modes available to its customers. If there are restrictions, the customer's a. choices are limited to those trust modes authorized by the partner.
Fig. 7 is a block diagram showing pertinent components of a computer 700 6 in accordance with the invention. A computer such as that shown in Fig. 7 can be 7 used, for example, to perform various procedures such as those discussed herein.
$ Computer 700 can also be used to access a web site or other computing facility to 9 access various financial information. The computer shown in Fig. 7 can function io as a server, a client computer, or a financial analysis system, of the types discussed 11 herein.
lz Computer 700 includes at least one processor 702 coupled to a bus 704 that ~s couples together various system components. Bus 704 represents one or more of la. any of several types of bus structures, such as a memory bus or memory controller, ~s a peripheral bus, and a processor or local bus using any of a variety of bus 16 architectures. A random access memory (RAM) 706 and a read only memory i7 (ROM) 708 are coupled to bus 704. Additionally, a network interface 710 and a 18 removable storage device 712, such as a floppy disk or a CD-ROM, are coupled to ~~ bus 704. Network interface 710 provides an interface to a data communication ao network such as a local area network (LAN) or a wide area network (WAN) for zi exchanging data with other computers and devices. A disk storage 714, such as a 22 hard disk, is coupled to bus 704 and provides for the non-volatile storage of data 23 (e.g., computer-readable instructions, data structures, program modules and other za. data used by computer 700). Although computer 700 illustrates a removable as storage 712 ~ and a disk storage 714, it will be appreciated that other types of 1 computer-readable media which can store data that is accessible by a computer, z such as magnetic cassettes, flash memory cards, digital video disks, and the like, may also be used in the exemplary computer.
Various peripheral interfaces 716 are coupled to bus 704 and provide an s interface between the computer 700 and the individual peripheral devices.
6 Exemplary peripheral devices include a display device 718, a keyboard 720, a 7 mouse 722, a modem 724, and a printer 726. Modem 724 can be used to access s other computer systems and devices directly or by connecting to a data 9 communication network such as the Internet.
to A variety of program modules can be stored on the disk storage 714, 11 removable storage 712, RAM 706, or ROM 708, including an operating system, lz one or more application programs, and other program modules and program data.
i3 A user can enter commands and other information into computer 700 using the la. keyboard 720, mouse 722, or other input devices (not shown). Other input devices is may include a microphone, joystick, game pad, scanner, satellite dish, or the like.
Computer 700 may operate in a network environment using logical a connections to other remote computers. The remote computers may be personal ~s computers, servers, routers, or peer devices. In a networked environment, some or all of the program modules executed by computer 700 may be retrieved from zo another computing device coupled to the network.
zi Typically, the computer 700 is programmed using instructions stored at 22 different times in the various computer-readable media of the computer.
Programs 23 and operating systems are often distributed, for example, on floppy disks or CD-z~ ROMs. The programs are installed from the distribution media into a storage zs device within the computer 700. When a program is executed, the program is at least partially loaded into the computer's primary electronic memory. As 2 described herein, the invention includes these and other types of computer-3 readable media when the media contains instructions or programs for a. implementing the steps described below in conjunction with a processor. The s invention also includes the computer itself when programmed according to the 6 procedures and techniques described herein.
7 For purposes of illustration, programs and other executable program s components are illustrated herein as discrete blocks, although it is understood that 9 such programs and components reside at vaxious times in different storage to components of the computer, and are executed by the computer's processor.
m Alternatively, the systems and procedures described herein can be implemented in 12 hardware or a combination of hardware, software, and/or firmware. For example, ~3 one or more application specific integrated circuits (ASICs) can be programmed to la. carry out the systems and procedures described herein.
~s Although the description above uses language that is specific to structural i6 features and/or methodological acts, it is to be understood that the invention 17 defined in the appended claims is not limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms i9 of implementing the invention.
zo zi 2s
TECHNICAL FIELD
a The present invention relates to the handling data and, more particularly, to 3 the use of multiple trust modes that define the manner in which certain data is ø handled.
BACKGROUND
7 Users that interact with online services that involve, for example, financial data or financial transactions (e.g., accessing financial accounts, or buying or selling goods or services) are often required to provide data to the online service.
~o This data may include bank account numbers, credit card numbers, passwords, and n the like. Many existing online services store the data provided by the users of the iz online services. Some users may not be comfortable with their data being stored n by a third party and, as a result, are reluctant to use the online services offered by ia. these third parties. Thus, users are often faced with the decision to allow their is data to be stored by a third party or to forego the services offered by the third 16 party.
m Similar problems occur with other types of online accounts and online is relationships where credentials are issued to a user. With these types of accounts, 19 when the user's credentials are stored, for example, on a server associated with the zo online account ox other online service, those credentials are at risk of being ai accessed by an unauthorized person, thereby compromising the security of the za user's account.
as The systems and methods described herein address these and other 24 problems by providing multiple trust modes that allow a user to determine how the as user's data is handled.
a SUMMARY
The system and methods described herein provide users of online services with multiple options regarding how the user's data is handled. A particular s option is selected by each user based on that user's level of trust in the system or organization that is handling the user's data. Certain options allow the system or 7 organization to store the data while other options require the system or organization to avoid persistently storing the data when finished processing the user's request or transaction.
to A particular embodiment presents a user with multiple modes of operation.
n The multiple modes of operation define different trust options for handling ~z sensitive data associated with the user. A selection is received from the user, 13 where the selection is one of the multiple modes of operation. The sensitive data 14 associated with the user is handled in accordance with the selected mode of is operation.
In one embodiment, the multiple modes include a low trust option that 17 retrieves sensitive data from the user each time the user requests a service 18 requiring the sensitive data.
i9 In another embodiment, the multiple modes include a moderate trust option ao that retrieves sensitive data from the user and stores the sensitive data in an zi encrypted format using a password known only to the user.
as In a particular embodiment, the multiple modes include a high trust option z3 that retrieves sensitive data from the user and stores the sensitive data in an 24 encrypted format for future use.
zs z Fig. 1 illustrates an exemplary network environment in which various 3 servers, computing devices, and a financial analysis system exchange data across a network, such as the Internet.
s Fig. 2 is a block diagram showing exemplary components and modules of a 6 financial analysis system.
7 Fig. 3 is a flow diagram illustrating a procedure in which a user registers an s account with the financial analysis system.
9 Fig. 4 is a flow diagram illustrating a procedure for automatically updating to user accounts having a High Trust Mode of operation.
11 Fig. 5 is a flow diagram illustrating a procedure for updating one or more lz user accounts.
is ~~ Fig. 6 is a flow diagram illustrating a procedure for allowing financial la.~~ institutions to select among multiple trust modes that are made available to is I I customers of the financial institutions.
16 ~ ~ Fig. 7 is a block diagram showing pertinent components of a computer in 17 II accordance with the invention.
zo DETAILED DESCRIPTION
zl The systems and methods described herein provide various modes of zz operation that determine how user data is handled. A particular mode of operation z3 is selected by each user based on the user's level of trust in the system or za. organization that is handling the data. A high level of trust allows the system or zs organization to store data, such as user credentials and other sensitive data, for 1 later use. A moderate level of trust allows the system or organization to store a sensitive data in an encrypted format using a key derived frorri the user's password 3 (l.e., the user associated with the sensitive data). A low level of trust does not a. allow the system or organization to store any sensitive data persistently.
A user s can change the level of trust associated with a particular account to reflect changes 6 in their attitude toward the system or organization.
7 As used herein, the terms "account holder", "customer", "user", and 8 "client" are interchangeable. "Account holder" refers to any person having access 9 to an account. A particular account may have multiple account holders (e.g., a to joint checking account having husband and wife as account holders or a corporate l account identifying multiple corporate employees as account holders).
Various la financial account and financial institution examples are provided herein for is purposes of explanation. However, it will be appreciated that the system and la. procedures described herein can be used with any type of asset account, any type is of debt account, and any type of financial institution. Example asset accounts 16 include savings accounts, money market accounts, checking accounts (both 17 interest-bearing and non-interest-bearing), certificates of deposit (CDs), mutual la funds, bonds, and equities. Example debt accounts include credit card accounts, m mortgage accounts, home equity loans, overdraft protection, margin accounts, ao personal loans, and other types of loans. Exemplary financial institutions include zi banks, savings and loans, credit unions, mortgage companies, mutual fund as companies, lending companies, and stock brokers.
zs Various financial account and financial institution examples are provided 24 herein for purposes of explanation. However, the methods and procedures as described herein can be applied to any type of transaction involving any type of account. For example, a data aggregation system may aggregate data from 2 multiple sources, such as multiple financial accounts, multiple email accounts, 3 multiple online award (or reward) accounts, multiple news headlines, and the like.
a Similarly, the data retrieval and data processing systems and methods discussed s herein may be applied to collect data from any type of account containing any type 6 of data. Thus, the methods and systems described herein can be applied to a data 7 aggregation system or any other account management system instead of the s financial analysis system discussed in the examples provided herein.
Although particular examples discussed herein refer to the handling of a to user's "sensitive data", the methods and systems described herein may be applied 11 to any type of data associated with a user, an organization or other entity.
lz Fig. 1 illustrates an exemplary network environment 100 in which various i3 servers, computing devices, and a financial analysis system exchange data across a la data communication network. The network environment of Fig. 1 includes is multiple financial institution servers 102, 104, and 106 coupled to a data 16 communication network 108, such as the Internet. Each of the financial institution i7 servers 102, 104, and 106 are typically associated with a particular financial ~s institution and store data for that financial institution, such as customer account data. As shown in Fig. 1, a client computer 110 and a financial analysis system zo 112 are also coupled to network 108. A database 114 is coupled to financial analysis system 112 for storing various data used by the financial analysis system.
z2 Network 108 may be any type of data communication network using any 23 communication protocol. Further, network 108 may include one or more sub-aa networks (not shown) which are interconnected with one another. Although only a few devices are shown coupled to network 108 in Fig. 1, a particular network may 2 include any number of devices coupled to one another.
The communication links shown between the network 108 and the various a. devices (102-106 and 110-112) shown in Fig. 1 can use any type of s communication medium and any communication protocol. For example, one or 6 more of the communication links shown in Fig. 1 may be a wireless link (e.g., a 7 radio frequency (RF) link or a microwave link) or a wired link accessed via a $ public telephone system or another communication network. Certain devices, 9 such as servers, may be coupled to a local area network (LAN), which is coupled ~o to network 108. Client computer 110 may access network 108 in different ways.
11 First, client computer 110 may directly access network 108, for example, by using a modem to access a public telephone network (e.g., a public switched telephone is network (PSTN)) that is coupled to network 108.
ia. Financial analysis system 112 performs various analysis and data is integration functions with respect to user accounts. These analysis functions are discussed in greater detail below. Client computer 110 allows a user to access 17 information via the network 108. Client computer may be any type of computing is device, such as a laptop computer, desktop computer, personal digital assistant (PDA), cellular phone, or set top box. For example, the user can access account ao information from one of the financial institution servers 102, 104, or 106, or send zl a request for an analysis or summary of the user's financial accounts to financial 22 analysis system 112.
zs In a particular embodiment, the methods and systems described herein 24 provide an Internet-based server solution where the sensitive data of one or more zs users is stored on a server, not a client.
Fig. 2 is a block diagram showing exemplary components and modules of z financial analysis system 112. A communication interface 202 allows the financial 3 analysis system 112 to communicate with other devices, such as one or more a. financial institution servers and client computers. In one embodiment, s communication interface 202 is a network interface to a local area network (LAl~, 6 which is coupled to another data communication network, such as the Internet.
7 A database access module 204 allows financial analysis system 112 to store s data to database 114 and retrieve data from the database. Financial analysis system 112 also stores various financial institution data 206, which may be used to io locate and communicate with various financial institution servers.
Financial a institution data 206 includes, for example, Uniform Resource Locators (URLs) 12 and login parameters.
A data extraction module 208 retrieves (or extracts) data from web pages or la. other data sources. The data extraction module 208 may use one or more data ~s harvesting scripts 212 (also referred to as screen scraping scripts) to retrieve data ~6 from a web page or other data source. Data harvesting (or screen scraping) is a i7 process that allows a script to retrieve data from one or more web pages associated is with a web site. The retrieved data may be stored in a database, such as database 1~ 114 (Fig. 1). The data harvesting scripts are capable of navigating web sites and ao capturing individual HTML pages. Typically, JavaScript and images are removed 21 from the HTML pages or converted into HTML text if it contains account zz information. A parser then converts the HTML data into a field-delimited XML
z3 format. Data is then extracted from the XML format and stored in a database or z~ other storage mechanism.
2s Financial analysis system 112 also includes user account data 210 and a 2 data handling module 214. User account data 210 typically includes information 3 regarding the types of accounts are maintained by particular users as well as the 4 locations of the accounts (i.e., the financial institution that handles the account) s and account balances. The user account data 210 may also indicate the level of 6 trust associated with each user account. User account data 210 may be stored in 7 database 114 coupled to financial analysis system 112. Data handling module s determines how account data is handled based on the level of trust associated with 9 the account data and other factors.
to Fig. 3 is a flow diagram illustrating a procedure 300 in which a user l registers an account with the financial analysis system. Initially, a user generates a ~2 request to have the financial analysis system monitor one or more of the user's is accounts (block 302). The financial analysis system there collects information la. from the user regarding the user accounts to be monitored (block 304).
This ~s information may include, for example, an account number, password to access the ~6 account online, the financial institution associated with the account, and the name i7 or names listed on each account. The financial analysis system then presents the ~s user with three different trust options for handling sensitive data associated with 19 the user (block 306). This sensitive data may include, for example, the account 2o number and password used to access the account online. In a particular 2i embodiment, the sensitive data is the user login data (e.g., the username and 22 password used to access an account). Although various examples discussed herein 2s offer three different trust options for handling sensitive data, alternate 2a. embodiments may include fewer trust options or a greater number of trust options depending on the preferences of the users andlor the administrators of the financial z analysis system.
In a particular embodiment, the three different trust options for handling a. sensitive data are referred to as "High Trust Option", "Moderate Trust Option", s and "Low Trust Option".
High Trust Option A user selects the High Trust Option if the user is comfortable with having the financial analysis system store the user's sensitive data. When this option is io selected, the financial analysis system stores the user's sensitive data for future m use, such as automatically updating the user's account balances. The user's iz sensitive data is stored using a two-way data encryption technique, which allows a 13 user key (derived from the user's password) or a key maintained by the financial ia. analysis system to decrypt the sensitive data. In one embodiment, the user's is sensitive data is encrypted using a Triple DES (Data Encryption Standard) 16 algorithm. The Triple DES algorithm is a variation of the DES standard and has i7 been endorsed by the National Institute of Standards and Technology (NIST).
is Triple DES uses three 64-bit keys, for an overall key length of 192 bits.
The ~9 encryption procedure is similar to DES, but it is repeated three times. The data is zo encrypted with the first key, decrypted with the second key, and encrypted again z~ with the third key.
zz Since the financial analysis system stores the user's account number and 23 password, the system is then able to automatically retrieve the user's account 24 balances using, for example; the data harvesting procedure discussed above.
3 Moderate Trust Option a. A user selects the Moderate Trust Option if they are not comfortable with s the High Trust Option, but don't want to have to enter their sensitive information 6 each time they access the financial analysis system. When this option is selected, 7 the financial analysis system stores the user's sensitive information, but the s sensitive information is encrypted such that the information can only be decrypted when the user is online (i.e., logged into the financial analysis system). For to example, the data can be encrypted using a key derived from the user's password.
n This encryption technique is referred to as one-way encryption because only one 12 ,key (associated with the user's password) can decrypt the sensitive data.
A
~3 particular embodiment of the one-way encryption uses HMAC-MDS. HMAC
i4 (Keyed-Hashing Message Authentication) is a mechanism for message is authentication using cryptographic hash functions. HMAC can be used with any m iterative cryptographic hash function, such as MDS. This combination is referred 17 to as HMAC-MDS. MD5 is a message digest function, which is a function that is takes a variable-length message and produces a fixed-length hash. MD5 is an ~~ example of a public one-way hash function.
2o When the user logs into the financial analysis system, the system 2~ automatically decrypts the user's sensitive information, which can then be used to 22 retrieve updated information regarding the user's financial accounts.
2a. Low Trust Option 2s A user selects the Low Trust Option if they are not comfortable with the a financial analysis system storing any of the user's sensitive data. When this option 3 is selected, the user's sensitive data is not persistently stored by the financial 4 analysis system. Thus, the user must re-enter the sensitive data each time the user s logs into the financial analysis system.
Refernng again to Fig. 3, at block 308 the user selects one of the three trust 7 options for each user account. The user may select a different trust option for a different accounts or different financial institutions. For example, the user may assign a High Trust Option to a savings account and assign a Moderate Trust to Option to a brokerage account. The financial analysis system then stores the m selected trust option for each account (block 310). This information is stored, for i2 example, in database 114. The trust option associated with each of the user's is institutions can be retrieved from the database each time the user logs into the i4 financial analysis system.
~s Fig. 4 is a flow diagram illustrating a procedure 400 for automatically i6 updating user accounts having a High Trust Mode of operation. Initially, the procedure 400 determines whether it is time to perform automatic account updates ~a (block 402). For example, High Trust Mode accounts may be updated automatically each business day. Other accounts may be updated hourly, weekly, ao monthly, or at other time intervals. In one embodiment, the account updates are zi performed as batch processes at predetermined times. If one or more automatic as account updates are due to be performed, the financial analysis system identifies as account information associated with High Trust Mode accounts (block 404).
The aa. system then retrieves current account information from all High Trust Mode as accounts (block 406), e.g., using the data harvesting procedure discussed above.
i The system then updates the various account information in the database with the a retrieved information (block 408). The procedure then returns to block 402 to 3 await the next automatic account update time. Thus, all user accounts that are a. designated High Trust Mode are automatically accessed to retrieve current account s balances and other information. This retrieved data may be aggregated with data 6 retrieved from other accounts using any data retrieval process.
7 Fig. 5 is a flow diagram illustrating a procedure 500 for updating one or s more user accounts. Initially, a user logs on to the financial analysis system (block 502). The user then requests to refresh account information (block 504). The to financial analysis system identifies the user's account information, which includes l decrypting the user's sensitive data (block 506). The procedure 500 then ~2 determines whether any of the user's accounts are Low Trust Mode accounts 13 (block 508). If at least one of the user's accounts is a Low Trust Mode account, m the financial analysis system asks the user for the missing credential (block 510), is such as the user's password. As discussed above, the financial analysis system i6 does not store any of the user's sensitive data related to Low Trust Mode accounts.
17 Therefore, the user must provide the user ID and password, and explicitly request ~a that the financial analysis system retrieve the current account information from the Low Trust Mode accounts. In alternate embodiments, the financial analysis ao system stores the user ID associated with Low Trust Mode accounts, but requires zi the user to enter the appropriate password each time the account is accessed.
22 The procedure then retrieves the current account information from all of the z3 user's accounts, including Low Trust Mode accounts, Moderate Trust Mode aa. accounts, and High Trust Mode accounts (block 512). The financial analysis as system then updates the account information contained in the database with the 1 retrieved information (block 514). In one embodiment, only Moderate Trust Mode 2 accounts are updated when the user logs on to the financial analysis system.
In s other embodiments, the financial analysis system may also update the user's High Trust Mode accounts and/or the user's Low Trust Mode accounts.
s Fig. 6 is a flow diagram illustrating a procedure 600 for allowing partners 6 to select among multiple trust modes that are made available to customers of the 7 partners. A partner may be any organization that implements, for example, the s systems described herein. Alternatively, a partner may be an organization that has 9 the various services described herein implemented by another on behalf of the ~o organization. Further, a partner may be an organization that provides a portal to another web site, such as a web site that implements the systems described herein.
12 An organization that hosts a web site having an online registration requirement i3 may also be a partner.
la In certain situations, the financial analysis system provides data aggregation ~s functions for one or more partners. These partners may want to limit the number of trust modes that are offered to their customers. Initially, the financial analysis 17 system notifies one or more partners of the multiple trust modes available to users is (block 602). Each partner then determines which trust modes should be made m available to its customers (block 604). For example, a particular partner might not zo want to be responsible for storing the user's sensitive data in a two-way encrypted 21 format (High Trust Mode) and doesn't want to offer that option to its customers.
22 Each partner communicates the selected trust modes to the financial analysis z3 system (block 606). The financial analysis system maintains a listing of all 24 partners and their associated trust modes (block 608). This listing may be stored, zs for example, in database 114 (Fig. 1). Before allowing a user to set up a new 1 account with the financial analysis system, the system first checks to see if the z partner associated with the new account (if any) has any restrictions on the types 3 of trust modes available to its customers. If there are restrictions, the customer's a. choices are limited to those trust modes authorized by the partner.
Fig. 7 is a block diagram showing pertinent components of a computer 700 6 in accordance with the invention. A computer such as that shown in Fig. 7 can be 7 used, for example, to perform various procedures such as those discussed herein.
$ Computer 700 can also be used to access a web site or other computing facility to 9 access various financial information. The computer shown in Fig. 7 can function io as a server, a client computer, or a financial analysis system, of the types discussed 11 herein.
lz Computer 700 includes at least one processor 702 coupled to a bus 704 that ~s couples together various system components. Bus 704 represents one or more of la. any of several types of bus structures, such as a memory bus or memory controller, ~s a peripheral bus, and a processor or local bus using any of a variety of bus 16 architectures. A random access memory (RAM) 706 and a read only memory i7 (ROM) 708 are coupled to bus 704. Additionally, a network interface 710 and a 18 removable storage device 712, such as a floppy disk or a CD-ROM, are coupled to ~~ bus 704. Network interface 710 provides an interface to a data communication ao network such as a local area network (LAN) or a wide area network (WAN) for zi exchanging data with other computers and devices. A disk storage 714, such as a 22 hard disk, is coupled to bus 704 and provides for the non-volatile storage of data 23 (e.g., computer-readable instructions, data structures, program modules and other za. data used by computer 700). Although computer 700 illustrates a removable as storage 712 ~ and a disk storage 714, it will be appreciated that other types of 1 computer-readable media which can store data that is accessible by a computer, z such as magnetic cassettes, flash memory cards, digital video disks, and the like, may also be used in the exemplary computer.
Various peripheral interfaces 716 are coupled to bus 704 and provide an s interface between the computer 700 and the individual peripheral devices.
6 Exemplary peripheral devices include a display device 718, a keyboard 720, a 7 mouse 722, a modem 724, and a printer 726. Modem 724 can be used to access s other computer systems and devices directly or by connecting to a data 9 communication network such as the Internet.
to A variety of program modules can be stored on the disk storage 714, 11 removable storage 712, RAM 706, or ROM 708, including an operating system, lz one or more application programs, and other program modules and program data.
i3 A user can enter commands and other information into computer 700 using the la. keyboard 720, mouse 722, or other input devices (not shown). Other input devices is may include a microphone, joystick, game pad, scanner, satellite dish, or the like.
Computer 700 may operate in a network environment using logical a connections to other remote computers. The remote computers may be personal ~s computers, servers, routers, or peer devices. In a networked environment, some or all of the program modules executed by computer 700 may be retrieved from zo another computing device coupled to the network.
zi Typically, the computer 700 is programmed using instructions stored at 22 different times in the various computer-readable media of the computer.
Programs 23 and operating systems are often distributed, for example, on floppy disks or CD-z~ ROMs. The programs are installed from the distribution media into a storage zs device within the computer 700. When a program is executed, the program is at least partially loaded into the computer's primary electronic memory. As 2 described herein, the invention includes these and other types of computer-3 readable media when the media contains instructions or programs for a. implementing the steps described below in conjunction with a processor. The s invention also includes the computer itself when programmed according to the 6 procedures and techniques described herein.
7 For purposes of illustration, programs and other executable program s components are illustrated herein as discrete blocks, although it is understood that 9 such programs and components reside at vaxious times in different storage to components of the computer, and are executed by the computer's processor.
m Alternatively, the systems and procedures described herein can be implemented in 12 hardware or a combination of hardware, software, and/or firmware. For example, ~3 one or more application specific integrated circuits (ASICs) can be programmed to la. carry out the systems and procedures described herein.
~s Although the description above uses language that is specific to structural i6 features and/or methodological acts, it is to be understood that the invention 17 defined in the appended claims is not limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms i9 of implementing the invention.
zo zi 2s
Claims (23)
1. A method comprising:
presenting a user with a plurality of modes of operation, wherein the plurality of modes of operation define different trust options for handling sensitive data associated with the user;
receiving a selection from the user, wherein the selection is one of the plurality of modes of operation; and handling sensitive data associated with the user in accordance with the selected mode of operation.
presenting a user with a plurality of modes of operation, wherein the plurality of modes of operation define different trust options for handling sensitive data associated with the user;
receiving a selection from the user, wherein the selection is one of the plurality of modes of operation; and handling sensitive data associated with the user in accordance with the selected mode of operation.
2. A method as recited in claim 1 wherein the plurality of modes include a low trust option for handling sensitive data associated with the user, the low trust option configured to retrieve sensitive data from the user each time the user requests a service requiring the sensitive data.
3. A method as recited in claim 2 wherein the low trust option does not persistently store sensitive data after the requested service requiring the sensitive data has been completed.
4. A method as recited in claim 1 wherein the plurality of modes include a high trust option for handling sensitive data associated with the user, the high trust option configured to retrieve sensitive data from the user and store the sensitive data in an encrypted format for future use.
5. A method as recited in claim 1 wherein the plurality of modes include a high trust option for handling sensitive data associated with the user, the high trust option configured to retrieve sensitive data from the user, encode the sensitive data using a two-way encryption technique, and store the encrypted sensitive data.
6. A method as recited in claim 1 wherein the plurality of modes include a moderate trust option for handling sensitive data associated with the user, the moderate trust option configured to retrieve sensitive data from the user and store the sensitive data in an encrypted format using a password known only to the user.
7. A method as recited in claim 1 wherein the plurality of modes include a moderate trust option for handling sensitive data associated with the user, the moderate trust option configured to retrieve sensitive data from the user, encode the sensitive data using a one-way encryption technique, and store the encrypted sensitive data.
8. A method as recited in claim 1 further comprising assigning a default mode of operation if the user does not select a valid mode of operation.
9. A method as recited in claim 1 further comprising associating a user account with the selected mode of operation.
10. A method comprising:
presenting a user with a low trust mode of operation, wherein the low trust mode of operation retrieves sensitive data from the user each time the user requests a service requiring the sensitive data;
presenting the user with a high trust mode of operation, wherein the high trust mode of operation stores sensitive data received from the user in an encrypted format;
receiving a selection from the user indicating one of the two modes of operation; and handling sensitive data associated with the user in accordance with the selected mode of operation.
presenting a user with a low trust mode of operation, wherein the low trust mode of operation retrieves sensitive data from the user each time the user requests a service requiring the sensitive data;
presenting the user with a high trust mode of operation, wherein the high trust mode of operation stores sensitive data received from the user in an encrypted format;
receiving a selection from the user indicating one of the two modes of operation; and handling sensitive data associated with the user in accordance with the selected mode of operation.
11. A method as recited in claim 10 further comprising presenting the user with a moderate trust mode of operation, wherein the moderate trust mode of operation stores sensitive data from the user in an encrypted format using a password known to the user; and wherein receiving a selection from the user includes receiving a selection indicating one of the three modes of operation.
12. A method as recited in claim 10 further comprising associating a user account with the selected mode of operation.
13. A method as recited in claim 10 further comprising assigning a default trust mode if the user does not select a valid mode of operation.
14. One or more computer-readable memories containing a computer program that is executable by a processor to perform the method recited in claim 10.
15. A method comprising:
presenting a user with a moderate trust mode of operation, wherein the moderate trust mode of operation stores sensitive data from the user in an encrypted format using a password known to the user;
presenting the user with a high trust mode of operation, wherein the high trust mode of operation stores sensitive data received from the user;
receiving a selection from the user indicating one of the two modes of operation; and handling sensitive data associated with the user in accordance with the selected mode of operation.
presenting a user with a moderate trust mode of operation, wherein the moderate trust mode of operation stores sensitive data from the user in an encrypted format using a password known to the user;
presenting the user with a high trust mode of operation, wherein the high trust mode of operation stores sensitive data received from the user;
receiving a selection from the user indicating one of the two modes of operation; and handling sensitive data associated with the user in accordance with the selected mode of operation.
16. One or more computer-readable memories containing a computer program that is executable by a processor to perform the method recited in claim 15.
17. A method comprising:
presenting a user with a moderate trust mode of operation, wherein the moderate trust mode of operation stores sensitive data from the user in an encrypted format using a password known to the user;
presenting the user with a low trust mode of operation, wherein the low trust mode of operation retrieves sensitive data from the user each time the user requests a service requiring the sensitive data;
receiving a selection from the user indicating one of the two modes of operation; and handling sensitive data associated with the user in accordance with the selected mode of operation.
presenting a user with a moderate trust mode of operation, wherein the moderate trust mode of operation stores sensitive data from the user in an encrypted format using a password known to the user;
presenting the user with a low trust mode of operation, wherein the low trust mode of operation retrieves sensitive data from the user each time the user requests a service requiring the sensitive data;
receiving a selection from the user indicating one of the two modes of operation; and handling sensitive data associated with the user in accordance with the selected mode of operation.
18. One or more computer-readable memories containing a computer program that is executable by a processor to perform the method recited in claim 17.
19. One or more computer-readable media having stored thereon a computer program that, when executed by one or more processors, causes the one or more processors to:
present a user with a plurality of modes of operation, wherein the plurality of modes of operation define different trust options for handling sensitive data associated with the user;
receive a selection from the user, wherein the selection is one of the plurality of modes of operation; and process sensitive data associated with the user in accordance with the selected mode of operation.
present a user with a plurality of modes of operation, wherein the plurality of modes of operation define different trust options for handling sensitive data associated with the user;
receive a selection from the user, wherein the selection is one of the plurality of modes of operation; and process sensitive data associated with the user in accordance with the selected mode of operation.
20. One or more computer-readable media as recited in claim 19 wherein the plurality of modes of operation include a low trust option for handling sensitive data associated with the user, the low trust option configured to retrieve sensitive data from the user each time the user requests a service requiring the sensitive data.
21. One or more computer-readable media as recited in claim 20 wherein the low trust option does not persistently store sensitive data after the requested service requiring the sensitive data is complete.
22 22. One or more computer-readable media as recited in claim 19 wherein the plurality of modes of operation include a high trust option for handling sensitive data associated with the user, the high trust option configured to retrieve sensitive data from the user and store the sensitive data in an encrypted format.
23. One or more computer-readable media as recited in claim 19 wherein the plurality of modes of operation include a moderate trust option for handling sensitive data associated with the user, the moderate trust option configured to retrieve sensitive data from the user and store the sensitive data in an encrypted format using a password known only to the user.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US10/044,289 US7203845B2 (en) | 2002-01-11 | 2002-01-11 | Multiple trust modes for handling data |
| US10/044,289 | 2002-01-11 | ||
| PCT/US2003/000664 WO2003061187A1 (en) | 2002-01-11 | 2003-01-08 | Multiple trust modes for handling data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2471604A1 true CA2471604A1 (en) | 2003-07-24 |
| CA2471604C CA2471604C (en) | 2013-09-03 |
Family
ID=21931535
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2471604A Expired - Fee Related CA2471604C (en) | 2002-01-11 | 2003-01-08 | Multiple trust modes for handling data |
Country Status (5)
| Country | Link |
|---|---|
| US (2) | US7203845B2 (en) |
| AU (1) | AU2003235662A1 (en) |
| CA (1) | CA2471604C (en) |
| GB (1) | GB2399437B (en) |
| WO (1) | WO2003061187A1 (en) |
Families Citing this family (48)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9038193B2 (en) * | 1998-08-14 | 2015-05-19 | Azos Al, Llc | System and method of data cognition incorporating autonomous security protection |
| US7668772B1 (en) | 1998-10-21 | 2010-02-23 | Island Intellectual Property Llc | Systems and methods for money fund banking with flexible interest allocation |
| US7536350B1 (en) | 1998-10-21 | 2009-05-19 | Island Intellectual Property Llc | Systems and methods for providing enhanced account management services for multiple banks |
| US7752129B2 (en) | 1998-10-21 | 2010-07-06 | Island Intellectual Property Llc | Systems and methods for managing client accounts |
| US8719562B2 (en) * | 2002-10-25 | 2014-05-06 | William M. Randle | Secure service network and user gateway |
| US7640200B2 (en) | 2000-07-10 | 2009-12-29 | Byallaccounts, Inc. | Financial portfolio management system and method |
| US7797207B1 (en) * | 2000-07-24 | 2010-09-14 | Cashedge, Inc. | Method and apparatus for analyzing financial data |
| US7383223B1 (en) * | 2000-09-20 | 2008-06-03 | Cashedge, Inc. | Method and apparatus for managing multiple accounts |
| US7203845B2 (en) * | 2002-01-11 | 2007-04-10 | Cashedge, Inc. | Multiple trust modes for handling data |
| US7979348B2 (en) | 2002-04-23 | 2011-07-12 | Clearing House Payments Co Llc | Payment identification code and payment system using the same |
| US8150766B1 (en) | 2003-01-27 | 2012-04-03 | Island Intellectual Property Llc | System and method for investing public deposits |
| DE602004024407D1 (en) * | 2003-08-12 | 2010-01-14 | Research In Motion Ltd | SYSTEM AND METHOD FOR DISPLAYING THE ENCRYPTION STRENGTH |
| US20050055296A1 (en) * | 2003-09-08 | 2005-03-10 | Michael Hattersley | Method and system for underwriting and servicing financial accounts |
| US8725607B2 (en) | 2004-01-30 | 2014-05-13 | The Clearing House Payments Company LLC | Electronic payment clearing and check image exchange systems and methods |
| GB2410113A (en) * | 2004-11-29 | 2005-07-20 | Morse Group Ltd | A system and method of accessing banking services via a mobile telephone |
| WO2006125027A1 (en) * | 2005-05-16 | 2006-11-23 | West Services Inc. | User interface for search and document production |
| US11200302B2 (en) * | 2005-11-16 | 2021-12-14 | Azos Ai, Llc | System and method of data cognition incorporating autonomous security protection |
| US8775214B2 (en) | 2006-07-19 | 2014-07-08 | Thompson Reuters (Market) LLC | Management method and system for a user |
| US7752107B1 (en) | 2007-02-28 | 2010-07-06 | Island Intellectual Property Llc | System and method for managing aggregated accounts |
| US8260705B1 (en) | 2007-02-28 | 2012-09-04 | Island Intellectual Property Llc | Systems, methods and program products for deposit and withdrawal processing |
| US8380621B1 (en) | 2007-02-28 | 2013-02-19 | Island Intellectual Property Llc | Systems, methods and program products for swap processing for uninsured accounts |
| US20080301022A1 (en) * | 2007-04-30 | 2008-12-04 | Cashedge, Inc. | Real-Time Core Integration Method and System |
| DE102007025262A1 (en) * | 2007-05-30 | 2007-10-25 | Meiko Maschinenbau Gmbh & Co. Kg | Cleaning device e.g. cycle dishwasher, for e.g. plate, has microwave drying device for partial drying of cleaning goods, where cooling blower of drying device guides air into source of microwave and air is warmed up and applied to goods |
| US8295486B2 (en) * | 2007-09-28 | 2012-10-23 | Research In Motion Limited | Systems, devices, and methods for outputting alerts to indicate the use of a weak hash function |
| US20090202081A1 (en) * | 2008-02-08 | 2009-08-13 | Ayman Hammad | Key delivery system and method |
| US8225106B2 (en) * | 2008-04-02 | 2012-07-17 | Protegrity Corporation | Differential encryption utilizing trust modes |
| US20090320089A1 (en) * | 2008-06-20 | 2009-12-24 | Microsoft Corporation | Policy-based user brokered authorization |
| US10108432B1 (en) * | 2009-04-16 | 2018-10-23 | Intuit Inc. | Generating a script based on user actions |
| US8781931B1 (en) | 2009-05-26 | 2014-07-15 | Island Intellectual Property Llc | Method and system for allocating deposits over a plurality of depository institutions |
| US8352342B1 (en) | 2009-06-19 | 2013-01-08 | Island Intellectual Property Llc | Method and system for determining fees for deposits allocated over a plurality of deposit institutions |
| US8756705B2 (en) * | 2009-07-01 | 2014-06-17 | Fiserv, Inc. | Personalized security management |
| US8370236B1 (en) | 2009-11-24 | 2013-02-05 | Island Intellectual Property Llc | Method and system for allocating funds over a plurality of time deposit instruments in depository institutions |
| US9026803B2 (en) * | 2009-11-30 | 2015-05-05 | Hewlett-Packard Development Company, L.P. | Computing entities, platforms and methods operable to perform operations selectively using different cryptographic algorithms |
| US9275360B2 (en) | 2010-05-21 | 2016-03-01 | Hsbc Technology & Services (Usa) Inc. | Account opening flow configuration computer system and process for implementing same |
| EP2572338A4 (en) | 2010-05-21 | 2016-04-27 | Hsbc Technology & Services Usa Inc | Account opening computer system architecture and process for implementing same |
| US8458089B1 (en) | 2010-06-14 | 2013-06-04 | Island Intellectual Property Llc | System, method and program product for administering fund movements using depository institution groups |
| US8583545B1 (en) | 2010-09-20 | 2013-11-12 | Island Intellectual Property Llc | Systems and methods for money fund banking with flexible interest allocation |
| WO2012051180A1 (en) | 2010-10-11 | 2012-04-19 | Hsbc Technologies Inc. | Computer architecture and process for application processing engine |
| WO2012054572A2 (en) | 2010-10-21 | 2012-04-26 | Hsbc Technologies Inc. | Computer metrics system and process for implementing same |
| WO2012058385A2 (en) | 2010-10-27 | 2012-05-03 | Hsbc Technlologies Inc. | Integrated customer communications computer system and process for implementing same |
| US8452702B1 (en) | 2011-09-08 | 2013-05-28 | Island Intellectual Property Llc | System, method and program product for minimizing fund movements |
| US8655689B1 (en) | 2011-10-13 | 2014-02-18 | Island Intellectual Property Llc | System, method and program product for modeling fund movements |
| US11295308B1 (en) | 2014-10-29 | 2022-04-05 | The Clearing House Payments Company, L.L.C. | Secure payment processing |
| US9805344B1 (en) | 2015-01-23 | 2017-10-31 | Island Intellectual Property, Llc | Notification system and method |
| US11694168B2 (en) | 2015-07-01 | 2023-07-04 | The Clearing House Payments Company L.L.C. | Real-time payment system, method, apparatus, and computer program |
| US11042882B2 (en) | 2015-07-01 | 2021-06-22 | The Clearing House Payments Company, L.L.C. | Real-time payment system, method, apparatus, and computer program |
| US20190132323A1 (en) * | 2017-10-27 | 2019-05-02 | Mastercard International Incorporated | Systems and methods for dynamically adjusting a password attempt threshold |
| US11436577B2 (en) | 2018-05-03 | 2022-09-06 | The Clearing House Payments Company L.L.C. | Bill pay service with federated directory model support |
Family Cites Families (52)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4346442A (en) | 1980-07-29 | 1982-08-24 | Merrill Lynch, Pierce, Fenner & Smith Incorporated | Securities brokerage-cash management system |
| US4694397A (en) * | 1984-12-27 | 1987-09-15 | The Advest Group, Inc. | Banking/brokerage computer interface system |
| US5644727A (en) | 1987-04-15 | 1997-07-01 | Proprietary Financial Products, Inc. | System for the operation and management of one or more financial accounts through the use of a digital communication and computation system for exchange, investment and borrowing |
| US4953085A (en) | 1987-04-15 | 1990-08-28 | Proprietary Financial Products, Inc. | System for the operation of a financial account |
| DE69029759T2 (en) | 1989-05-15 | 1997-07-17 | Ibm | Flexible interface for authentication services in a distributed data processing system |
| US5826243A (en) | 1994-01-03 | 1998-10-20 | Merrill Lynch & Co., Inc. | Integrated system for controlling master account and nested subaccount(s) |
| US6108641A (en) | 1994-01-03 | 2000-08-22 | Merrill Lynch, Pierce, Fenner & Smith | Integrated nested account financial system with medical savings subaccount |
| US6018722A (en) | 1994-04-18 | 2000-01-25 | Aexpert Advisory, Inc. | S.E.C. registered individual account investment advisor expert system |
| US5805719A (en) | 1994-11-28 | 1998-09-08 | Smarttouch | Tokenless identification of individuals |
| US5745706A (en) | 1994-12-30 | 1998-04-28 | Wolfberg; Larry | Computer system and related equipment for spending and investment account management |
| US5890140A (en) | 1995-02-22 | 1999-03-30 | Citibank, N.A. | System for communicating with an electronic delivery system that integrates global financial services |
| FI101864B1 (en) | 1995-07-07 | 1998-09-15 | Biohit Oy | Method for correcting fluid dosing errors, and liquid dosing device |
| US5812883A (en) | 1995-11-22 | 1998-09-22 | Mitsubishi Chemical America, Inc. | System for reading and storing formatting information after formatting a first storage medium and using the stored formatting information to format a second storage medium |
| US5787427A (en) | 1996-01-03 | 1998-07-28 | International Business Machines Corporation | Information handling system, method, and article of manufacture for efficient object security processing by grouping objects sharing common control access policies |
| US5855020A (en) | 1996-02-21 | 1998-12-29 | Infoseek Corporation | Web scan process |
| AU713316B2 (en) | 1996-05-23 | 1999-11-25 | Citibank, N.A. | Global financial services integration system and process |
| US5940809A (en) | 1996-08-19 | 1999-08-17 | Merrill Lynch & Co. | Securities brokerage-asset management system |
| JPH10149404A (en) | 1996-11-15 | 1998-06-02 | D & B Technol Asia Kk | Fixed assets management device and open type accounting processing network system |
| US6038603A (en) | 1997-03-25 | 2000-03-14 | Oracle Corporation | Processing customized uniform resource locators |
| US5893078A (en) | 1997-03-26 | 1999-04-06 | Carreker-Antinori, Inc. | System and method for determining optimal sweep threshold parameters for demand deposit accounts |
| US6012048A (en) | 1997-05-30 | 2000-01-04 | Capital Security Systems, Inc. | Automated banking system for dispensing money orders, wire transfer and bill payment |
| US6324523B1 (en) | 1997-09-30 | 2001-11-27 | Merrill Lynch & Co., Inc. | Integrated client relationship management processor |
| US6381592B1 (en) | 1997-12-03 | 2002-04-30 | Stephen Michael Reuning | Candidate chaser |
| US6108788A (en) | 1997-12-08 | 2000-08-22 | Entrust Technologies Limited | Certificate management system and method for a communication security system |
| US6473800B1 (en) * | 1998-07-15 | 2002-10-29 | Microsoft Corporation | Declarative permission requests in a computer system |
| US6321334B1 (en) | 1998-07-15 | 2001-11-20 | Microsoft Corporation | Administering permissions associated with a security zone in a computer system security model |
| US6792082B1 (en) | 1998-09-11 | 2004-09-14 | Comverse Ltd. | Voice mail system with personal assistant provisioning |
| US6374231B1 (en) | 1998-10-21 | 2002-04-16 | Bruce Bent | Money fund banking system |
| ATE273538T1 (en) | 1998-10-28 | 2004-08-15 | Verticalone Corp | APPARATUS AND METHOD FOR AUTOMATIC AGGREGATION AND SUPPLY OF ELECTRONIC PERSONAL INFORMATION OR DATA |
| WO2000028462A1 (en) * | 1998-11-09 | 2000-05-18 | Onecore Financial Network, Inc. | Systems and methods for performing integrated financial transactions |
| US6199077B1 (en) | 1998-12-08 | 2001-03-06 | Yodlee.Com, Inc. | Server-side web summary generation and presentation |
| US6412073B1 (en) | 1998-12-08 | 2002-06-25 | Yodiee.Com, Inc | Method and apparatus for providing and maintaining a user-interactive portal system accessible via internet or other switched-packet-network |
| US6802042B2 (en) | 1999-06-01 | 2004-10-05 | Yodlee.Com, Inc. | Method and apparatus for providing calculated and solution-oriented personalized summary-reports to a user through a single user-interface |
| US20020010768A1 (en) | 1998-12-17 | 2002-01-24 | Joshua K. Marks | An entity model that enables privilege tracking across multiple treminals |
| US6240399B1 (en) | 1998-12-24 | 2001-05-29 | Glenn Frank | System and method for optimizing investment location |
| US6513019B2 (en) | 1999-02-16 | 2003-01-28 | Financial Technologies International, Inc. | Financial consolidation and communication platform |
| US6477565B1 (en) | 1999-06-01 | 2002-11-05 | Yodlee.Com, Inc. | Method and apparatus for restructuring of personalized data for transmission from a data network to connected and portable network appliances |
| AU5742200A (en) | 1999-06-17 | 2001-01-09 | Mobius Management Systems, Inc. | Electronic statement, bill presentment and payment system and method |
| US6609128B1 (en) | 1999-07-30 | 2003-08-19 | Accenture Llp | Codes table framework design in an E-commerce architecture |
| US6598028B1 (en) | 1999-09-03 | 2003-07-22 | Lynn Sullivan | Computer-implemented universal financial management/translation system and method |
| US6510451B2 (en) | 1999-10-14 | 2003-01-21 | Yodlee.Com, Inc. | System for completing a multi-component task initiated by a client involving Web sites without requiring interaction from the client |
| US6799167B1 (en) * | 1999-10-22 | 2004-09-28 | Decision Analytics, Inc. | Dynamic portfolio benchmarking |
| US6986046B1 (en) | 2000-05-12 | 2006-01-10 | Groove Networks, Incorporated | Method and apparatus for managing secure collaborative transactions |
| US6639910B1 (en) * | 2000-05-20 | 2003-10-28 | Equipe Communications Corporation | Functional separation of internal and external controls in network devices |
| US7013310B2 (en) | 2002-01-03 | 2006-03-14 | Cashedge, Inc. | Method and apparatus for retrieving and processing data |
| US20020019753A1 (en) | 2000-08-07 | 2002-02-14 | Boden John B. | System, method, and computer program product for assisting caregivers |
| US7031939B1 (en) | 2000-08-15 | 2006-04-18 | Yahoo! Inc. | Systems and methods for implementing person-to-person money exchange |
| US6697860B1 (en) | 2000-08-28 | 2004-02-24 | Viagold Direct Network Limited | System and method for linking web sites |
| US7203845B2 (en) * | 2002-01-11 | 2007-04-10 | Cashedge, Inc. | Multiple trust modes for handling data |
| GB2392262A (en) | 2002-08-23 | 2004-02-25 | Hewlett Packard Co | A method of controlling the processing of data |
| US20060015450A1 (en) | 2004-07-13 | 2006-01-19 | Wells Fargo Bank, N.A. | Financial services network and associated processes |
| JP4471761B2 (en) * | 2004-07-26 | 2010-06-02 | 任天堂株式会社 | GAME PROGRAM, GAME DEVICE, AND INPUT DEVICE |
-
2002
- 2002-01-11 US US10/044,289 patent/US7203845B2/en not_active Expired - Lifetime
-
2003
- 2003-01-08 GB GB0414223A patent/GB2399437B/en not_active Expired - Fee Related
- 2003-01-08 AU AU2003235662A patent/AU2003235662A1/en not_active Abandoned
- 2003-01-08 WO PCT/US2003/000664 patent/WO2003061187A1/en not_active Application Discontinuation
- 2003-01-08 CA CA2471604A patent/CA2471604C/en not_active Expired - Fee Related
-
2007
- 2007-03-05 US US11/714,627 patent/US7657761B2/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| US7657761B2 (en) | 2010-02-02 |
| US20070162769A1 (en) | 2007-07-12 |
| AU2003235662A1 (en) | 2003-07-30 |
| GB2399437A (en) | 2004-09-15 |
| US20030135752A1 (en) | 2003-07-17 |
| WO2003061187A1 (en) | 2003-07-24 |
| GB2399437B (en) | 2006-05-03 |
| CA2471604C (en) | 2013-09-03 |
| GB0414223D0 (en) | 2004-07-28 |
| US7203845B2 (en) | 2007-04-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2471604C (en) | Multiple trust modes for handling data | |
| CA3026291C (en) | Information processing device, information processing method, and computer program | |
| US8086508B2 (en) | Method and apparatus for delegating authority | |
| US8521627B2 (en) | Systems and methods for facilitating electronic securities transactions | |
| US7565326B2 (en) | Dialect independent multi-dimensional integrator using a normalized language platform and secure controlled access | |
| US20140046820A1 (en) | Method and apparatus for managing a financial transaction system | |
| KR20180113084A (en) | Method for managing Digital Identity based on Blockchain | |
| CA3028628A1 (en) | Distributed electronic record and transaction history | |
| US20140041006A1 (en) | Secure messaging center | |
| US20050262025A1 (en) | Systems and methods for brokering data in a transactional gateway | |
| KR20080094000A (en) | Method and apparatus for establishing peer-to-peer karma and trust | |
| US8554872B2 (en) | Integration of different mobile device types with a business infrastructure | |
| US20020138447A1 (en) | System and method for updating personal financial information | |
| US20230135685A1 (en) | Access controller for secure transactions | |
| US20080265014A1 (en) | Credit Relationship Management | |
| JP2002163234A (en) | User authentication system and processing method therefor, and recording medium recorded with the program therefor | |
| KR20220031190A (en) | Method for intermediation of personal information data | |
| US20040236941A1 (en) | Method for secure transfer of information | |
| JP7113883B2 (en) | Identity verification system, method and computer program | |
| KR20230154665A (en) | Finacial service system and finacial service method thereof | |
| KR20020033891A (en) | unified web-page access system and its method | |
| KR20240021510A (en) | Logistics Service Support System | |
| JP2006048709A (en) | E-mail system, system processing method of e-mail system and recording medium which records program therefor | |
| WO2008065620A2 (en) | A method and system for obtaining data from a plurality of data sources | |
| JP2001319059A (en) | Financial processing system, system processing method of financial processing system, and recording medium with recorded program for the same |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |
Effective date: 20180108 |