WO2003046700A2 - Method and system for protecting data from unauthorized disclosure - Google Patents
Method and system for protecting data from unauthorized disclosure Download PDFInfo
- Publication number
- WO2003046700A2 WO2003046700A2 PCT/US2002/036931 US0236931W WO03046700A2 WO 2003046700 A2 WO2003046700 A2 WO 2003046700A2 US 0236931 W US0236931 W US 0236931W WO 03046700 A2 WO03046700 A2 WO 03046700A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- database
- data
- data protection
- protection rules
- state change
- Prior art date
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
Definitions
- the present invention relates generally to the field of data protection and, more particularly, to a method and system for protecting data from unauthorized disclosure.
- a compute ⁇ zed method for managing a plurality of data protection rules includes receiving and sto ⁇ ng the data protection rules in a database, receiving and storing a plurality of permissions generated by a data owner in the database, accepting a query from a data requester with respect to a particular set of data, accessing the database to validate that a permission exists for the data requester, accessing the database to validate that the particular set of data may be accessed by the data requester, and generating a response to the query
- a compute ⁇ zed method for managing a plurality of data protection rules includes receiving and sto ⁇ ng the data protection rules and a plurality of corporate policies in a database, querying a user about a user preference with respect to one or more data protection rules stored in the database, accepting the user preference, and stonng the user preference in the database
- a computenzed method for managing a plurality of data protection rules includes receiving and sto ⁇ ng a first set of data protection rules, receiving a second set of data protection rules, compa ⁇ ng the second set of data protection rules to the first set of data protection rules to determine an impact on existing information, notifying a data owner of the impact, and updating the database with the second set of data protection rules
- a compute ⁇ zed method for managing a plurality of data protection rules includes receiving and sto ⁇ ng the data protection rules in a database, receiving and sto ⁇ ng one or more states of an entity in the database, receiving a state change of the entity, compa ⁇ ng the state change to the data protection rules stored in the database, determining whether the state change complies with the data protection rules, and updating the database with the state change
- a compute ⁇ zed method for managing a plurality of data protection rules includes receiving and stonng a first set of data protection rules in a data protection database, receiving and sto ⁇ ng managed system information in a managed system database, extracting meta data from the managed system database and storing the meta data in the data protection database.
- the meta data is associated with the managed system information.
- the method further includes receiving a second set of data protection rules, comparing, by utilizing the meta data, the second set of data protection rules to the managed system information to determine if the managed system information complies with the second set of data protection rules, notifying a data owner of one or more results of the comparison, and updating the data protection database with the second set of data protection rules.
- Embodiments of the invention may include all, some, or none of these advantages. For example, some embodiments significantly decrease the risk of unauthorized disclosure of employee data. Having a Global Data Protection Repository that spans all layers of an enterprise architecture provides consistent application of data protection protocols across the enterprise. In addition, a Global Data Protection
- Repository centralizes the collection, maintenance, and administration of rules and regulations, and may reduce the number of system modifications to support a corporation. Auditing of managed systems may also be accomplished more easily and cost-effectively. Capturing employee acknowledgements of corporate policies and employee preferences with regard to opting in or opting out of a particular disclosure of his or her personal information is also much easier to accomplish and maintain.
- FIGURE 1 is a functional block diagram illustrating an enterp ⁇ se architecture having a global data protection repository according to one embodiment of the present invention
- FIGURE 2 is a block diagram illustrating the global data protection repository of FIGURE 1
- FIGURE 3 is a flowchart illustrating a data protection autho ⁇ zation method according to one embodiment of the present invention
- FIGURE 4 is a flowchart illustrating a method for capturing a users acknowledgement of corporate policies and preferences with respect to certain data protection laws according to one embodiment of the present invention
- FIGURE 5 is a flowchart illustrating a method for captu ⁇ ng data protection rules and determining impacts of those data protection rules according to one embodiment of the present invention
- FIGURE 6 is a flowchart illustrating a method of captu ⁇ ng and processing a state change according to one embodiment of the present invention
- FIGURE 7A is a flowchart illustrating a method of auditing the compliance of a managed system based on new data protection rules according to one embodiment of the present invention
- FIGURE 7B is a flowchart illustrating a method of auditing the compliance of a managed system based on new managed system information according to one embodiment of the present invention DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS OF THE INVENTION
- FIGURE 1 is a functional diagram illustrating an enterprise architecture 100 having an associated global data protection repository 200 according to one embodiment of the present invention.
- Enterprise architecture 100 is a functional diagram of a typical large, global corporation. However, enterprise architecture 100 may represent a corporation of any size. As illustrated in FIGURE 1, enterprise architecture 100 includes a business intelligence function 102, a corporate master data function 104, and three regions 106, each region 106 including a reporting function 108, a customer relationship management function 110, a business-to-business function 112, and a business applications function 114. Enterprise architecture 100 may have more, less, or different functions and/or elements than that shown in FIGURE 1.
- Business intelligence function 102 includes data warehouses and other corporate data consolidation systems that contain a myriad of information associated with an enterprise, such as employee information.
- Corporate master data function 104 provides a consistent definition of major business objects, such as client, chart of account, and organization structures.
- Regions 106 are separate geographical regions, such as the Americas, Europe, and Australia/Southeast Asia. Although three regions 106 are shown in FIGURE 1, there may be any number of regions 106 within enterprise architecture 100.
- Reporting function 108 contains operational information about an enterprise, such as manufacturing and construction information.
- Customer relationship management function 110 contains a myriad of information relating to customers and suppliers and the relationship between them and the enterprise.
- Business-to-business function 112 contains various information relating to buying and selling products and services between businesses and between businesses and customers, such as buying and selling over the Internet.
- Business applications function 114 contains information on back office systems, such as payroll information, accounting functions, human resources, and material management.
- Global data protection repository 200 manages a plurality of data protection rules, as described more fully below in conjunction with FIGURE 2.
- global data protection repository 200 manages a plurality of data protection rules, as described more fully below in conjunction with FIGURE 2.
- global data protection repository 200 manages a plurality of data protection rules, as described more fully below in conjunction with FIGURE 2.
- Global data protection repository 200 may function to, among other things, capture, maintain, manage, and enforce one or more data protection laws, regulations, and other rules, for an enterprise, such as an enterprise depicted by enterprise architecture 100.
- Global data protection repository 200 is communicatively coupled to all functions 102, 104, and 108 through 114 in enterprise architecture 100.
- any of functions 102, 104, and 108 through 114 may have a software application and/or other suitable computer system, whose data protection compliance is managed by global data protection repository 200.
- This application and/or system is known throughout this detailed description as a managed system.
- a managed system would be a human resources system, such as Peoplesoft ® .
- Functions 102, 104, and 108 through 114 and global data protection repository 200 as illustrated in FIGURE 1 may comprise a myriad of information in both hard copy and soft copy form. They may also include a myriad of human intelligence, as well as a myriad of computing intelligence, such as computer hardware and/or computer software that is interconnected with any suitable type of communications hardware and/or software.
- the functional diagram illustrated in FIGURE 1 may comprise one or more networks, such as the Internet, intranets, extranets, and any other suitable networks, or combination thereof, that allows one function to communicate with another function. These networks each may have any number of clients, servers, mainframes, or any other suitable types of computing equipment.
- the functionality of functions 102, 104, and 108 through 114 and global data protection repository 100 may all be stored on one large scale mainframe or one large scale server.
- FIGURE 2 is a block diagram illustrating global data protection repository 200 according to one embodiment of the present invention.
- Global data protection repository 200 includes an interface 202, an input device 204, an output device 206, and a server 207.
- Server 207 further includes a processor 208, a rules database 210, a managed systems database 212, and a memory 214.
- Memory 214 further includes a rule capture and impact analysis tool 216, an authorization management tool 218, a user acceptance and individual preferences tool 220, a state change tool 222, and an audit and compliance tool 224.
- Interface 202 couples global data protection repository 200 to a network 201 via a link 203.
- Interface 202 may be any suitable combination of hardware, software, firmware, and/or middleware, operable to facilitate communication between global data protection repository 200 and network 201.
- interface 202 may be a cable modem, digital subscriber line, 10/100 base-T Ethernet port, fiber optic connection, dial-up connection, or other suitable interface.
- Network 201 may be one or more networks, such as an Internet, intranet, extranet, or any other suitable networks or combination thereof.
- Network 201 represents the functions 102, 104, and 108 through 114 of enterprise architecture 100, as described above.
- Network 201 may also include employees of an enterprise and may also include information that is not contained in soft copy form.
- network 201 may comprise a global computing network, a virtual private network, a local area network, a wide area network, or any other suitable communication network that facilitates communication of data and information between global data protection repository 200 and enterprise architecture 100.
- Link 203 may be any suitable wireline connection, such as any conventional telephone line, cable, or fiber optic cable.
- Link 203 may also be any suitable wireless link.
- Input device 204 is coupled to server 207 for the purpose of inputting data and other suitable information.
- input device 204 is a client computer; however, input device 204 may be any other suitable device, such as a personal data assistant, a keyboard, a mouse, a stylus, or a scanner.
- Output device 206 may be any suitable visual display unit, such as a liquid crystal display (“LCD”) or cathode ray tube (“CRT”) display. Output device 206 may also be coupled to other devices, such as a printer (not shown) for the purpose of pnnting out any desired data or information.
- Server 207 is any suitable hardware and or software having processor 208 that is operable to execute computer programs, such as those tools that are stored in memory 214, which are described in more detail below.
- Processor 208 comprises any suitable type of processing unit that executes logic. One of the functions of processor 208 is to execute computer programs that are stored in memory 214. Processor 208 may also control the receiving, storing, and/or retrieving of data, such as data protection rules, from rules database 210 and/or managed systems database 212.
- Rules database 210 and managed systems database 212 may be any suitable type of database, such as a relational database, that store information. Rules database 210 and managed system database 212 may comprise files, stacks, or any other suitable organizations of volatile or non-volatile memory. Databases 210, 212 may be random access memory ("RAM"), read only memory (“ROM”), CD-ROM, removable memory devices, or any other suitable devices that allow storage and/or retrieval of data. For example, one function of rules database 210 is to receive and store data protection rules. One function of managed systems database 212 is to receive and store managed systems information, such as payroll information. Databases 210, 212 may be combined into one database or distributed among many databases. There may also be other types of databases in server 207 that perform other functions.
- Memory 214 may comprise files, stacks, or other suitable organizations of volatile or non- volatile memory.
- Memory 214 may be RAM, ROM, CD-ROM, removal of memory devices, or any other suitable devices that allows storage and/or retrieval of data.
- memory 214 may store tools 216 through 224.
- Rule capture and impact analysis tool 216 generally functions to receive existing data protection laws, regulations, and other suitable data protection rules and store them in rules database 210. Tool 216 further functions to receive new and/or updated data protection rules and compare those rules to the existing data protection rules to determine any impacts on existing information associated with enterprise architecture 100. Other functions of tool 216 are described in more detail below.
- Authorization management tool 218 generally functions to accept queries from data requesters related to information associated with enterprise architecture 100, access rules database 210 to validate that permissions exist for the data requesters, validate that the desired information may be accessed by the data requesters, and generate a response to the queries. Further details of the functions of tool 218 are described more fully below.
- User acceptance and individual preferences tool 220 generally functions to query a user about a user preference with respect to one or more data protection rules, accept one or more user preferences, and store these preferences in rules database 210 or managed systems database 212 or other suitable databases. Tool 220 further functions to query a user about one or more corporate policies and to accept an acknowledgement from the user indicating that the user has agreed to the corporate policies. Additional details on the functions of tool 220 are described in more detail below.
- State change tool 222 generally functions to receive a state change of an entity, such as an employee, compare the state change to data protection rules that are stored in rules database 210, determine whether the state change complies with the data protection rules, and update the managed system database 212 with the state change. Further details of tool 222 are described more fully below.
- Audit and compliance tool 224 generally functions to extract metadata from managed systems database 212 and store the metadata in rules database 210, receive a new and/or updated set of data protection rules, compare the new and/or updated data protection rules to existing managed systems information stored in managed systems database 212 to determine if the managed systems information complies with the new or updated set of data protection rules.
- Tool 224 may also function to notify a data owner of one or more results of the comparison and to update rules database 210 with the new and/or updated set of data protection rules. More details on the functions of tool 224 are described more fully below. Additional details of some of the functions of tools 216 through 224 according to some embodiments of the present invention are described below in conjunction with FIGURES 3 through 7B.
- global data protection repository 200 functions to capture, maintain, manage, and enforce one or more data protection rules, such as data protection laws, regulations, and other suitable rules for an ente ⁇ rise, such as the ente ⁇ rise depicted by ente ⁇ rise architecture 100 above in FIGURE 1.
- data protection rules are created and/or revised, one or more employees of an ente ⁇ rise, such as a business process owner, inputs these data protection rules into global data protection repository 200 so that they may be stored in one or more databases, such as rules database 210. This employee is sometimes referred to in this detailed description as a data owner.
- Co ⁇ orate policies with respect to data protection are also input into global data protection repository 200 and stored in either rules database 210 or other suitable database.
- managed systems information is stored in managed systems database 212.
- global data protection repository 200 includes information on entities, such as employees, buyers, and suppliers.
- the data owners keep the data protection rules, co ⁇ orate policies, and other data protection information constantly updated in rules database 210, managed systems database 212, or other suitable databases.
- global data protection repository 200 has a number of computer software tools that perform various functions related to the data protection rules. For example, if an employee of the ente ⁇ rise desires to find out certain information on another employee, then authorization management tool 218 receives a query from this user and checks the data protection rules stored in rules database 210 to see if this requesting employee is allowed to see this type of information.
- Authorization management tool 218 also validates that a permission exists for the requesting employee, which is typically input ahead of time by a data owner or other suitable employee of the ente ⁇ rise, before allowing a response to be generated to the requesting employee. Permissions are typically determined on an employee-by- employee basis or by the role of an employee and organizational position. Global protection repository 200 may also function to keep track of which employees are receiving which type of information and/or which employees are denied access to certain information.
- Global data protection repository 200 may also function to query employees regarding one or more co ⁇ orate policies relating to data protection. For example, an employee may be queried to read a co ⁇ orate policy related to some data protection rule and acknowledge that he or she has read and understood the co ⁇ orate policy by clicking a button to indicate that acknowledgment. Employees may also be prompted to opt in or opt out of specific data protection rules. For example, under certain data protection laws of a certain country, an employee may have the option to allow some of their personal information to be disclosed if that employee elects to opt in. Global data protection repository 200 functions to query this employee and receive the employee's preference with respect to opting in or opting out. If the employee opts- in, then his or her personal information would be stored in global data protection repository 200.
- global data protection repository 200 would first check to see what the data protection rule is for that information. If the rule stated that one cannot see that employee's information unless they opted in, then global data protection repository 200 checks to see whether or not that employee has opted in. If they have, global data protection repository 200 would generate a response to the employee who requested that information.
- Global data protection repository 200 may also function to adapt to changes in either data protection rules, co ⁇ orate policies, or other suitable changes, such as a state change of an employee. For example, if new data protection laws come in for the country of Germany, then global data protection repository 200 compares the new rules to the stored rules in rules database 210 and determines any impacts that those new rules may have. These impacts are then communicated to the appropriate entity in the ente ⁇ rise, such as the appropriate data owner, so that they may resolve any discrepancies.
- the global data protection repository 200 is able to prompt that employee that has moved to obtain his or her consent.
- Global data protection repository 200 may also function to audit managed systems. For example, based on stored data protection rules and stored managed systems information, an employee may generate reports to find out if the managed systems are complying with the existing data protection rules. Or if a change comes in to a managed system, then global data protection repository 200 may check to see if the new managed system information complies with the existing data protection rules. Other example functions of global data protection repository 200 are described below in conjunction with FIGURES 3 through 7B.
- FIGURE 3 is a flow chart illustrating a data protection authorization method according to one embodiment of the present invention. This flow chart illustrates example functions of authorization management tool 218.
- the method begins at step 300 where data protection rules are received and stored in rules database 210 of global data protection repository 200.
- a data owner which may be any suitable employee of an ente ⁇ rise, determines permissions for one or more data requesters and stores these permissions in rules database 210 or another suitable database at step 302.
- a data requester may also be an employee of an ente ⁇ rise that is trying to access certain information that may be protected by data protections rules.
- the data requester requests information.
- the data requester may be a vice president of an ente ⁇ rise that wishes to obtain information about an employee, such as an employee's home address, home phone number, or certain payroll information.
- the rules database 210 stores identifying information about the request. For example, rules database 210 may store such information as who is requesting the data (i.e., the data requester), what type of information they are requesting, what time the request was made, and from which location the request was made.
- a determination is made whether the data requester is permitted to access the requested information. If the data requester is not permitted to access that information, then the method proceeds to step 310 as described below.
- step 312 a determination is made whether the requested information is allowed to be released to the data requester. If the information is not allowed to be released to the data requester, such as when that information is protected by certain data protection rules, then the method proceeds to step 310 as outlined below. If the information is allowed to be released to the data requester, then the method proceeds to step 314 where the information is sent to the data requester.
- a request result is stored in rules database 210 or other suitable database in global data protection repository 200.
- a request result may be whether or not the information was sent to the data requester. This request result may also contain timestamp information or other suitable identifying information as to the request result.
- FIGURE 4 is a flow chart illustrating a method for capturing a user's acknowledgment of co ⁇ orate policies and a user's preferences with respect to certain data protection rules according to various embodiments of the present invention.
- This flow chart illustrates example functions of user acceptance and individual preferences tool 220.
- the method begins at step 400 where data protection rules are received and stored in rules database 210 in global data protection repository 200. Similarly, at step 402, co ⁇ orate policies are received and stored in rules database 210 or other suitable database in global data protection repository 200. Co ⁇ orate policies may supplement or add to existing data protection rules.
- one or more co ⁇ orate policies are sent to a user, such as an employee of an ente ⁇ rise.
- the user is queried, at step 406, to acknowledge receipt and acceptance of the co ⁇ orate policies that were sent at step 404.
- decisional step 408 a determination is made whether the user's acknowledgment was received. If the user's acknowledgment is not received, then a message is sent to the user at step 410. For example, the message sent to the user may alert the user that his non- acknowledgment has been received and it may explain possible implications of the user's non-acknowledgment.
- the non-acknowledgment is stored in rules database 210 or other suitable database, at step 412, and the method continues at step 422 as outlined below If the acknowledgment is received at step 408, the acknowledgment is stored in rules database 210 or other suitable database in global data protection repository 200 At step 416, a user is que ⁇ ed to opt-in or opt-out of specific data protection rules For example, if a data protection law m Germany states that certain personal information of an employee may not be disclosed unless an employee agrees to disclose it, then this is a situation where a user would be que ⁇ ed to give him or her a chance to opt-m and allow certain personal information to be disclosed, if so requested User preferences are received at step 418 regarding specific data protection rules and these user preferences are stored in rules database 210 or other suitable database in global data protection repository 200 User preferences are the decisions made by a user with respect to opting-in or opting-out of certain data protection rules At step 422, the user's acknowledgment or non-acknowledgment of certain co ⁇ orate
- FIGURE 5 is a flow chart illustrating a method for captu ⁇ ng data protection rules and determining impacts of those data protection rules according to one embodiment of the present invention
- This flow chart illustrates example functions of rule capture and impact analysis tool 216
- the method begins at step 500 where new and/or updated data protection rules are received For example, data protection laws in a specific country may be changed, certain government regulations may be promulgated, or data protection rules may be provided by labor agreements or work council agreements
- these new data protection rules are compared to existing data protection rules stored in rules database 210 of global data protection repository 200 Any differences and/or changes are identified at step 504
- decisional step 506 a determination is made whether any changes in data protection rules necessitate any co ⁇ orate policy changes of an ente ⁇ rise.
- step 516 If no changes to co ⁇ orate policies are necessary, then the method proceeds to step 516 as described below. If co ⁇ orate policy changes are necessitated, then a data owner of co ⁇ orate policy changes is notified at step 508. For example, a vice president or high-level manager of a co ⁇ oration may receive an e-mail stating that because of a new data protection law, this particular co ⁇ orate policy needs to be changed. At that time, there is a change in the co ⁇ orate policy, and that changed co ⁇ orate policy is input into global data protection repository 200 at step 510. At decisional step 512, a determination is made whether these new co ⁇ orate policy changes necessitate changes in user preferences.
- step 514 the global data protection repository 200 is updated with the new co ⁇ orate policy changes, which may be stored in rules database 210 or other suitable database. The method would then proceed to step 516 as described below. If changes in user preferences are necessitated by the new co ⁇ orate policy changes, then the method proceeds to step 528 as described in further detail below.
- step 518 a determination is made whether any data protection rules changes necessitate managed systems changes. If no managed systems changes are necessary, then the method proceeds to step 516 as described below. If managed systems changes are necessary, then the method proceeds to step 520 where a managed systems owner is notified via an e-mail or other suitable communication that manage systems changes are necessary. At this point, a particular managed system may be changed automatically or may be changed manually via employee intervention. For example, a simple change may be handled by rule capture and impact analysis tool 216 or updated managed system software may be received by a supplier to update managed systems database 212.
- the managed system changes are received and the global data protection repository 200 is updated with the managed systems changes at step 524.
- any suitable database in global data protection repository 200 such as managed systems database 212, may accept and store these managed systems changes. The method then proceeds to step 516 as described more fully below.
- step 526 a determination is made whether any data protection rules changes necessitate changes in user preferences. If no user preference changes are necessary, then the method then proceeds to step 516 as described more fully below. If, however, changes to user preferences are necessary, then the method proceeds to step 528 where a user is queried with respect to opting-in or opting-out of specific data protection rules that have been updated and/or added. In step 530, the new user preferences are received with respect to opting-in or opting-out and these user preferences are stored at step 532 in global data protection repository
- FIGURE 6 is a flowchart illustrating a method of capturing and processing a state change according to one embodiment of the present invention. This flow chart illustrates example functions of state change tool 222. The method begins at step 600 where a state change is received. For example, a state change may be where an employee's location changes from the United States to Germany. At step 602, the state change is compared to data protection rules stored in rules database 210 of global data protection repository 200.
- the appropriate entity may be a data owner, such as a business process owner, that has to resolve the problem by deleting certain protected personal information of the employee that has moved from, for example, United States to Germany. The database in this case would have to be updated to reflect and comply with current data protection rules. If the state change does comply with the data protection rules in rules database 210, then any managed systems are updated with the state change at step 610.
- step 612 a determination is made whether the state change necessitates any changes in user preferences with respect to opting-in or opting-out of specific data protection rules. If no changes in user preferences are required, then the method ends. However, if user preference changes are required because of the state change, then the method proceeds to step 614 where the user is queried with respect to opting-in or opting-out of the data protection rule that has been affected by the state change.
- step 616 the user preferences with regard to the state change and associated data protection rule is received at step 616. The user preferences are replicated to security systems at step 618.
- global data protection repository 200 is updated with the user preferences, such as by updating rules database 210 or other suitable database.
- FIGURE 7 is a flowchart illustrating a method of auditing one or more data protection rules or managed systems according to one embodiment of the present invention.
- This flow chart illustrates example functions of audit and compliance tool 224.
- the method begins at step 700 where data protection rules are received and stored in rules database 210 of global data protection repository 200.
- managed system information is received at step 702 and stored in, for example, managed systems database 212.
- Metadata is extracted from the managed system information stored in managed system database 212 and stored in rules database 210 at step 704. Metadata is information used to define the managed system information stored in managed systems database 212.
- new or updated data protection rules are received and stored in rules database 210.
- the metadata is utilized in step 708 to read one or more data fields of managed systems information contained in managed systems database 212.
- the new or updated data protection rules are compared to the managed system information in the data field(s) at step 710.
- decisional step 712 a determination is made whether the data in the data field(s) complies with the new or updated data protection rules. If the managed system data does not comply with the new or updated data protection rules, then a managed systems owner is notified at step 714 via e-mail or other suitable communication, and the method continues at step 716 as described below.
- step 712 If the managed system data complies with the new or updated data protection rules at step 712, then the method proceeds to decisional step 718 where a determination is made whether the new or updated data protection rules necessitate a change in user preferences. If no changes in user preferences are required, then the method continues at step 716 as described below. However, if user preferences changes are required, then the method proceeds to step 720 where a user is que ⁇ ed to opt-in or opt-out with respect to the new or updated data protection rules. The revised or new user preferences are received at step 722 and replicated to security systems at step 724. Global data protection repository 200 is updated with user preferences at step 726, such as by storing the user preferences in rules database 210 or other suitable database. The method then proceeds to step 716.
- reports of one or more data protection rules are generated. For example, if an officer of the co ⁇ oration needs or wants to take a look at certain data protection rules for certain regions 106, employees, or certain subsidiaries of the co ⁇ oration then step 716 generates the report and typically uses output device 206 to present a hard copy of that report. Other suitable reports may be generated, such as information regarding managed systems changes.
- FIGURE 7B is a flowchart illustrating a method of auditing the compliance of a managed system based on new managed system information according to one embodiment of the present invention.
- This flow chart illustrates example functions of audit and compliance tool 224.
- the method begins at step 728 where data protection rules are received and stored in rules database 210.
- Managed system information is also received at step 730.
- metadata from managed system information is extracted at step 732 and stored in rules database 210 or other suitable database.
- New and/or updated managed system information is received at step 734.
- Metadata is utilized at step 736 to read one or more data fields in managed system information stored in managed systems database 212.
- Data protection rules are compared to managed systems information in the particular data field(s).
- decisional step 740 a determination is made whether managed system information in the data field(s) complies with the data protection rules. If the managed systems information stored in managed systems database 212 does not comply with the data protection rules, then a managed systems owner is notified at step 742 via e-mail or other suitable communication, so that the managed systems owner may address the non-compliance The method then proceeds to step 744 as desc ⁇ bed below
- step 746 a determination is made whether the new and/or updated managed system information necessitates a change in user preferences If no change in user preferences are required, then the method proceeds to step 744 as desc ⁇ bed below However, if a change in user preferences are necessitated by the new and/or updated managed system information, then the method proceeds to step 748 where a user is que ⁇ ed to opt-in or opt-out with respect to the new and/or updated managed system information User preferences are received at step 750 and replicated to secu ⁇ ty systems at step 752 Global data protection repository 200 is updated with the new and/or revised user preferences at step 754 before the method continues at step 744 At step 744, reports of one or more data protection rules are generated For example, if an officer of the co ⁇ oration needs or wants to take a look at certain data protection rules for certain regions 106, employees, or certain subsidia ⁇ es of the co ⁇ oration then step 744 generates the report and typically uses output device 206 to present a hard copy of that
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
MXPA04004822A MXPA04004822A (en) | 2001-11-26 | 2002-11-18 | Method and system for protecting data from unauthorized disclosure. |
CA002467641A CA2467641A1 (en) | 2001-11-26 | 2002-11-18 | Method and system for protecting data from unauthorized disclosure |
AU2002352764A AU2002352764A1 (en) | 2001-11-26 | 2002-11-18 | Method and system for protecting data from unauthorized disclosure |
EP02789717A EP1449047A2 (en) | 2001-11-26 | 2002-11-18 | Method and system for protecting data from unauthorized disclosure |
JP2003548067A JP2006503344A (en) | 2001-11-26 | 2002-11-18 | Method and system for protecting data from unauthorized disclosure |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/996,099 US20030101341A1 (en) | 2001-11-26 | 2001-11-26 | Method and system for protecting data from unauthorized disclosure |
US09/996,099 | 2001-11-26 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2003046700A2 true WO2003046700A2 (en) | 2003-06-05 |
WO2003046700A8 WO2003046700A8 (en) | 2003-08-28 |
Family
ID=25542503
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2002/036931 WO2003046700A2 (en) | 2001-11-26 | 2002-11-18 | Method and system for protecting data from unauthorized disclosure |
Country Status (7)
Country | Link |
---|---|
US (1) | US20030101341A1 (en) |
EP (1) | EP1449047A2 (en) |
JP (1) | JP2006503344A (en) |
AU (1) | AU2002352764A1 (en) |
CA (1) | CA2467641A1 (en) |
MX (1) | MXPA04004822A (en) |
WO (1) | WO2003046700A2 (en) |
Families Citing this family (91)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10361802B1 (en) | 1999-02-01 | 2019-07-23 | Blanding Hovenweep, Llc | Adaptive pattern recognition based control system and method |
US8352400B2 (en) | 1991-12-23 | 2013-01-08 | Hoffberg Steven M | Adaptive pattern recognition based controller apparatus and method and human-factored interface therefore |
US7966078B2 (en) | 1999-02-01 | 2011-06-21 | Steven Hoffberg | Network media appliance system and method |
US8364136B2 (en) | 1999-02-01 | 2013-01-29 | Steven M Hoffberg | Mobile system, a method of operating mobile system and a non-transitory computer readable medium for a programmable control of a mobile system |
US8126889B2 (en) | 2002-03-28 | 2012-02-28 | Telecommunication Systems, Inc. | Location fidelity adjustment based on mobile subscriber privacy profile |
US7426380B2 (en) | 2002-03-28 | 2008-09-16 | Telecommunication Systems, Inc. | Location derived presence information |
US8290505B2 (en) | 2006-08-29 | 2012-10-16 | Telecommunications Systems, Inc. | Consequential location derived information |
US8918073B2 (en) | 2002-03-28 | 2014-12-23 | Telecommunication Systems, Inc. | Wireless telecommunications location based services scheme selection |
US20030190045A1 (en) * | 2002-04-03 | 2003-10-09 | Huberman Bernardo A. | Apparatus and method for protecting privacy while revealing data |
US8140635B2 (en) | 2005-03-31 | 2012-03-20 | Tripwire, Inc. | Data processing environment change management methods and apparatuses |
US7822724B2 (en) * | 2002-07-03 | 2010-10-26 | Tripwire, Inc. | Change audit method, apparatus and system |
US7207067B2 (en) * | 2002-11-12 | 2007-04-17 | Aol Llc | Enforcing data protection legislation in Web data services |
US8666397B2 (en) | 2002-12-13 | 2014-03-04 | Telecommunication Systems, Inc. | Area event handling when current network does not cover target area |
US7444668B2 (en) * | 2003-05-29 | 2008-10-28 | Freescale Semiconductor, Inc. | Method and apparatus for determining access permission |
US7260186B2 (en) | 2004-03-23 | 2007-08-21 | Telecommunication Systems, Inc. | Solutions for voice over internet protocol (VoIP) 911 location services |
US20080126535A1 (en) | 2006-11-28 | 2008-05-29 | Yinjun Zhu | User plane location services over session initiation protocol (SIP) |
US20080090546A1 (en) | 2006-10-17 | 2008-04-17 | Richard Dickinson | Enhanced E911 network access for a call center using session initiation protocol (SIP) messaging |
US7739303B2 (en) | 2004-07-22 | 2010-06-15 | International Business Machines Corporation | Method, system and program product for verifying access to a data object |
US7629926B2 (en) | 2004-10-15 | 2009-12-08 | Telecommunication Systems, Inc. | Culled satellite ephemeris information for quick, accurate assisted locating satellite location determination for cell site antennas |
US7411546B2 (en) * | 2004-10-15 | 2008-08-12 | Telecommunication Systems, Inc. | Other cell sites used as reference point to cull satellite ephemeris information for quick, accurate assisted locating satellite location determination |
US6985105B1 (en) | 2004-10-15 | 2006-01-10 | Telecommunication Systems, Inc. | Culled satellite ephemeris information based on limiting a span of an inverted cone for locating satellite in-range determinations |
US7827608B2 (en) * | 2005-02-08 | 2010-11-02 | International Business Machines Corporation | Data leak protection system, method and apparatus |
JP2006277579A (en) * | 2005-03-30 | 2006-10-12 | Fujitsu Ltd | Data managing device, data managing method and data management program |
US20060242277A1 (en) | 2005-03-31 | 2006-10-26 | Tripwire, Inc. | Automated change approval |
US7353034B2 (en) | 2005-04-04 | 2008-04-01 | X One, Inc. | Location sharing and tracking using mobile phones or other wireless devices |
US8660573B2 (en) | 2005-07-19 | 2014-02-25 | Telecommunications Systems, Inc. | Location service requests throttling |
WO2007021823A2 (en) | 2005-08-09 | 2007-02-22 | Tripwire, Inc. | Information technology governance and controls methods and apparatuses |
US10318894B2 (en) * | 2005-08-16 | 2019-06-11 | Tripwire, Inc. | Conformance authority reconciliation |
US7825780B2 (en) | 2005-10-05 | 2010-11-02 | Telecommunication Systems, Inc. | Cellular augmented vehicle alarm notification together with location services for position of an alarming vehicle |
US8467320B2 (en) | 2005-10-06 | 2013-06-18 | Telecommunication Systems, Inc. | Voice over internet protocol (VoIP) multi-user conferencing |
US7907551B2 (en) | 2005-10-06 | 2011-03-15 | Telecommunication Systems, Inc. | Voice over internet protocol (VoIP) location based 911 conferencing |
EP1955235A4 (en) * | 2005-11-25 | 2010-11-10 | Continuity Software Ltd | System and method of managing data protection resources |
US20070124255A1 (en) * | 2005-11-28 | 2007-05-31 | Tripwire, Inc. | Pluggable heterogeneous reconciliation |
US8150363B2 (en) | 2006-02-16 | 2012-04-03 | Telecommunication Systems, Inc. | Enhanced E911 network access for call centers |
US8059789B2 (en) | 2006-02-24 | 2011-11-15 | Telecommunication Systems, Inc. | Automatic location identification (ALI) emergency services pseudo key (ESPK) |
US7899450B2 (en) | 2006-03-01 | 2011-03-01 | Telecommunication Systems, Inc. | Cellular augmented radar/laser detection using local mobile network within cellular network |
US7471236B1 (en) | 2006-03-01 | 2008-12-30 | Telecommunication Systems, Inc. | Cellular augmented radar/laser detector |
US9167553B2 (en) | 2006-03-01 | 2015-10-20 | Telecommunication Systems, Inc. | GeoNexus proximity detector network |
US8208605B2 (en) | 2006-05-04 | 2012-06-26 | Telecommunication Systems, Inc. | Extended efficient usage of emergency services keys |
EP2026239A4 (en) * | 2006-05-22 | 2011-05-11 | Nec Corp | Information providing system, method of providing information and program for providing information |
CN101123644A (en) * | 2006-08-11 | 2008-02-13 | 华为技术有限公司 | An authorized management system and authorized management server |
US7966013B2 (en) | 2006-11-03 | 2011-06-21 | Telecommunication Systems, Inc. | Roaming gateway enabling location based services (LBS) roaming for user plane in CDMA networks without requiring use of a mobile positioning center (MPC) |
US7505973B2 (en) * | 2007-01-16 | 2009-03-17 | Microsoft Corporation | Efficient paging of search query results |
US8050386B2 (en) | 2007-02-12 | 2011-11-01 | Telecommunication Systems, Inc. | Mobile automatic location identification (ALI) for first responders |
US7929530B2 (en) | 2007-11-30 | 2011-04-19 | Telecommunication Systems, Inc. | Ancillary data support in session initiation protocol (SIP) messaging |
US9130963B2 (en) | 2011-04-06 | 2015-09-08 | Telecommunication Systems, Inc. | Ancillary data support in session initiation protocol (SIP) messaging |
US8914341B2 (en) | 2008-07-03 | 2014-12-16 | Tripwire, Inc. | Method and apparatus for continuous compliance assessment |
US8068587B2 (en) | 2008-08-22 | 2011-11-29 | Telecommunication Systems, Inc. | Nationwide table routing of voice over internet protocol (VOIP) emergency calls |
US9202221B2 (en) * | 2008-09-05 | 2015-12-01 | Microsoft Technology Licensing, Llc | Content recommendations based on browsing information |
JP5267027B2 (en) | 2008-10-03 | 2013-08-21 | 富士通株式会社 | Personal information system |
US8892128B2 (en) | 2008-10-14 | 2014-11-18 | Telecommunication Systems, Inc. | Location based geo-reminders |
US8525681B2 (en) | 2008-10-14 | 2013-09-03 | Telecommunication Systems, Inc. | Location based proximity alert |
US9301191B2 (en) | 2013-09-20 | 2016-03-29 | Telecommunication Systems, Inc. | Quality of service to over the top applications used with VPN |
WO2012005769A1 (en) | 2010-07-09 | 2012-01-12 | Telecommunication Systems, Inc. | Location privacy selector |
US20120006610A1 (en) | 2010-07-09 | 2012-01-12 | Erik Wallace | Telematics enhanced mobile device safety interlock |
CN103348373A (en) * | 2010-10-05 | 2013-10-09 | 日本电气株式会社 | Personal-information transmission/reception system, personal-information transmission/reception method, personal-information provision device, preference management device, and computer program |
US8688087B2 (en) | 2010-12-17 | 2014-04-01 | Telecommunication Systems, Inc. | N-dimensional affinity confluencer |
US8942743B2 (en) | 2010-12-17 | 2015-01-27 | Telecommunication Systems, Inc. | iALERT enhanced alert manager |
US8682321B2 (en) | 2011-02-25 | 2014-03-25 | Telecommunication Systems, Inc. | Mobile internet protocol (IP) location |
US8649806B2 (en) | 2011-09-02 | 2014-02-11 | Telecommunication Systems, Inc. | Aggregate location dynometer (ALD) |
US9479344B2 (en) | 2011-09-16 | 2016-10-25 | Telecommunication Systems, Inc. | Anonymous voice conversation |
WO2013048551A1 (en) | 2011-09-30 | 2013-04-04 | Telecommunication Systems, Inc. | Unique global identifier for minimizing prank 911 calls |
WO2013065161A1 (en) * | 2011-11-02 | 2013-05-10 | 株式会社日立製作所 | Safety evaluation method and safety evaluation computer |
US20130111545A1 (en) * | 2011-11-02 | 2013-05-02 | Alcatel-Lucent Usa Inc. | Privacy Management for Subscriber Data |
US9313637B2 (en) | 2011-12-05 | 2016-04-12 | Telecommunication Systems, Inc. | Wireless emergency caller profile data delivery over a legacy interface |
US9792451B2 (en) * | 2011-12-09 | 2017-10-17 | Echarge2 Corporation | System and methods for using cipher objects to protect data |
US8984591B2 (en) | 2011-12-16 | 2015-03-17 | Telecommunications Systems, Inc. | Authentication via motion of wireless device movement |
US9384339B2 (en) | 2012-01-13 | 2016-07-05 | Telecommunication Systems, Inc. | Authenticating cloud computing enabling secure services |
US8688174B2 (en) | 2012-03-13 | 2014-04-01 | Telecommunication Systems, Inc. | Integrated, detachable ear bud device for a wireless phone |
US9544260B2 (en) | 2012-03-26 | 2017-01-10 | Telecommunication Systems, Inc. | Rapid assignment dynamic ownership queue |
US9307372B2 (en) | 2012-03-26 | 2016-04-05 | Telecommunication Systems, Inc. | No responders online |
US20130268503A1 (en) * | 2012-04-06 | 2013-10-10 | Damodara R. Budithi | Database navigation of changes at commit time |
US9338153B2 (en) | 2012-04-11 | 2016-05-10 | Telecommunication Systems, Inc. | Secure distribution of non-privileged authentication credentials |
WO2014028712A1 (en) | 2012-08-15 | 2014-02-20 | Telecommunication Systems, Inc. | Device independent caller data access for emergency calls |
US9208346B2 (en) | 2012-09-05 | 2015-12-08 | Telecommunication Systems, Inc. | Persona-notitia intellection codifier |
GB2505644A (en) * | 2012-09-05 | 2014-03-12 | Ibm | Managing network configurations |
US9456301B2 (en) | 2012-12-11 | 2016-09-27 | Telecommunication Systems, Inc. | Efficient prisoner tracking |
US9336256B2 (en) | 2013-03-15 | 2016-05-10 | Informatica Llc | Method, apparatus, and computer-readable medium for data tokenization |
US8983047B2 (en) | 2013-03-20 | 2015-03-17 | Telecommunication Systems, Inc. | Index of suspicion determination for communications request |
US9408034B2 (en) | 2013-09-09 | 2016-08-02 | Telecommunication Systems, Inc. | Extended area event for network based proximity discovery |
US9516104B2 (en) | 2013-09-11 | 2016-12-06 | Telecommunication Systems, Inc. | Intelligent load balancer enhanced routing |
US9479897B2 (en) | 2013-10-03 | 2016-10-25 | Telecommunication Systems, Inc. | SUPL-WiFi access point controller location based services for WiFi enabled mobile devices |
US9542570B2 (en) * | 2014-11-10 | 2017-01-10 | Successfactors, Inc. | Permission control |
WO2016081856A1 (en) * | 2014-11-21 | 2016-05-26 | Whip Networks, Inc. | Media management and sharing system |
US20160315927A1 (en) * | 2015-04-21 | 2016-10-27 | Zte (Usa) Inc. | Method and system for establishing and managing personal black box (pbb) in virtually-networked big-data (vnbd) environment |
GB2572389A (en) * | 2018-03-28 | 2019-10-02 | Sony Corp | A device, requesting device, method and computer program |
US11222132B2 (en) * | 2018-10-05 | 2022-01-11 | Optum, Inc. | Methods, apparatuses, and systems for data rights tracking |
US10831917B2 (en) * | 2018-10-29 | 2020-11-10 | At&T Intellectual Property I, L.P. | Database system consensus-based access control |
US11062043B2 (en) | 2019-05-01 | 2021-07-13 | Optum, Inc. | Database entity sensitivity classification |
WO2021188725A1 (en) | 2020-03-17 | 2021-09-23 | Optum, Inc. | Predicted data use obligation match using data differentiators |
AU2022205946A1 (en) * | 2021-01-06 | 2023-08-17 | ARETE SECURITY INC. dba DRUVSTAR | Systems, devices, and methods for observing and/or securing data access to a computer network |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5903882A (en) * | 1996-12-13 | 1999-05-11 | Certco, Llc | Reliance server for electronic transaction system |
US6125447A (en) * | 1997-12-11 | 2000-09-26 | Sun Microsystems, Inc. | Protection domains to provide security in a computer system |
US6697948B1 (en) * | 1999-05-05 | 2004-02-24 | Michael O. Rabin | Methods and apparatus for protecting information |
US7424543B2 (en) * | 1999-09-08 | 2008-09-09 | Rice Iii James L | System and method of permissive data flow and application transfer |
US7426750B2 (en) * | 2000-02-18 | 2008-09-16 | Verimatrix, Inc. | Network-based content distribution system |
-
2001
- 2001-11-26 US US09/996,099 patent/US20030101341A1/en not_active Abandoned
-
2002
- 2002-11-18 EP EP02789717A patent/EP1449047A2/en not_active Withdrawn
- 2002-11-18 CA CA002467641A patent/CA2467641A1/en not_active Abandoned
- 2002-11-18 MX MXPA04004822A patent/MXPA04004822A/en unknown
- 2002-11-18 JP JP2003548067A patent/JP2006503344A/en active Pending
- 2002-11-18 AU AU2002352764A patent/AU2002352764A1/en not_active Abandoned
- 2002-11-18 WO PCT/US2002/036931 patent/WO2003046700A2/en not_active Application Discontinuation
Non-Patent Citations (1)
Title |
---|
No Search * |
Also Published As
Publication number | Publication date |
---|---|
EP1449047A2 (en) | 2004-08-25 |
CA2467641A1 (en) | 2003-06-05 |
US20030101341A1 (en) | 2003-05-29 |
AU2002352764A1 (en) | 2003-06-10 |
WO2003046700A8 (en) | 2003-08-28 |
JP2006503344A (en) | 2006-01-26 |
MXPA04004822A (en) | 2004-08-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20030101341A1 (en) | Method and system for protecting data from unauthorized disclosure | |
US9727744B2 (en) | Automatic folder access management | |
US6928439B2 (en) | Computer system with access control mechanism | |
US8370388B2 (en) | Mandatory access control list for managed content | |
US8086615B2 (en) | Security data redaction | |
US7467414B2 (en) | Entitlement security and control for information system entitlement | |
US7065515B2 (en) | System and method for electronically managing composite documents | |
US7890530B2 (en) | Method and system for controlling access to data via a data-centric security model | |
US7716242B2 (en) | Method and apparatus for controlling access to personally identifiable information | |
US7673323B1 (en) | System and method for maintaining security in a distributed computer network | |
US7350226B2 (en) | System and method for analyzing security policies in a distributed computer network | |
US7950049B2 (en) | Hybrid meta-directory | |
US7707623B2 (en) | Self-service resource provisioning having collaborative compliance enforcement | |
EP2405607B1 (en) | Privilege management system and method based on object | |
US20090094193A1 (en) | Secure normal forms | |
US8141129B2 (en) | Centrally accessible policy repository | |
US20080022370A1 (en) | System and method for role based access control in a content management system | |
US11386224B2 (en) | Method and system for managing personal digital identifiers of a user in a plurality of data elements | |
US8719903B1 (en) | Dynamic access control list for managed content | |
Mont et al. | Privacy policy enforcement in enterprises with identity management solutions | |
US9202069B2 (en) | Role based search | |
US20190066123A1 (en) | Method for storing, delivering, and displaying documentation and credentials related to intrastate and interstate commerce | |
US11886608B2 (en) | Subject logging | |
US20230297702A1 (en) | Token generation and management | |
CN111917739A (en) | RESTful specification-based ACBC (Access control Block) authority management model |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG UZ VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LU MC NL PT SE SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
D17 | Declaration under article 17(2)a | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2467641 Country of ref document: CA Ref document number: 2003548067 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2002352764 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: PA/a/2004/004822 Country of ref document: MX |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2002789717 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2002789717 Country of ref document: EP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 2002789717 Country of ref document: EP |