IDENTITY MAPPING SYSTEM AND METHOD

• US 20140207813A1
• Filed: 04/03/2014
• Published: 07/24/2014
• Est. Priority Date: 05/31/2005
• Status: Active Grant

• Current Assignee: Fairwarning IP LLC
• Original Assignee: Fairwarning IP LLC
• Inventors: LONG, Kurt James, Arnold, Christopher R., Lyons, Michael B., Keane, Michael P.
• Granted Patent: US 9,330,134 B2
• Time in Patent Office: Days
• US Class Current: 707/758
• CPC Class Codes: G06F 16/24 Querying
• CPC Class Codes: G06F 21/55 Detecting local intrusion or implementing counter-measures
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management
• CPC Class Codes: G06Q 10/0635 Risk analysis of enterprise or organisation activities
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/1408 by monitoring network traffic monitoring network traffic per se H04L43/00

Abstract

An identity mapping system includes an identity mapping database and a master user table (MUT) communicatively coupled with the identity mapping database. The MUT includes a record having at least one record data field, a unique user identification (ID) field and at least one user data field. The at least one user data field contains data from a software application.

Claims

1. An identity mapping system, comprising:

an identity mapping database; and

a master user table (MUT) communicatively coupled with the identity mapping database, wherein the MUT includes a record having at least one record data field, a unique user identification (ID) field and at least one user data field, the at least one user data field containing data from a software application.

2. The identity mapping system of claim 1, wherein the MUT is exported from one of a database table, a directory service and a spreadsheet.

3. The identity mapping system of claim 1, wherein the at least one record data field includes a unique record number associated with each record.

4. The identity mapping system of claim 3, wherein the unique record number associated with each record is a row number in the MUT.

5. The identity mapping system of claim 1, wherein the at least one record data field includes a master record start time field and a master record end time field.

6. The identity mapping system of claim 1, wherein the at least one user data field containing data from a software application includes a user hire date field and a user termination date field.

11. The identity mapping system of claim 1, wherein the at least one record data field includes a master record start time field and a master record end time field.

12. The identity mapping system of claim 1, wherein the at least one user data field containing data from a software application includes a user hire date field and a user termination date field.

7. An identity mapping system, comprising:

at least one a user identification (UID) associated with a software application;

at least one human resources (HR) directory having user data selected from a primary active HR directory, additional active HR directories or other HR directories;

an identity mapping database; and

a master user table (MUT) communicatively coupled with the identity mapping database, wherein the MUT includes a record having at least one record data field, a unique user identification (ID) field and at least one user data field, the at least one user data field comprising data selected by a highest priority assigned to one of the at least one software application and the at least one human resources (HR) directory.

8. The identity mapping system of claim 7, wherein the at least one user data field is populated with user data from the at least one HR directory having a higher priority than user data from the software application.

9. The identity mapping system of claim 7, wherein the at least one user data field is populated with user data from the at least one HR directory having a higher priority than user data from an at least one access log.

10. The identity mapping system of claim 7, wherein the at least one user data field is populated with user data from the at least one access log having a higher priority than user data from the at least one at least one HR directory.

13. A method of automatically generating a report with an identity mapping system, comprising:

reviewing one or more master user table (MUT) records with a identity mapping database to identify first records corresponding to a request for a report by comparing a first field in the MUT records;

identifying second records from the first records by comparing a second field in the first records; and

recording at least a portion of each of the second records in the report.

14. The method of claim 13 wherein the requested report is a hidden users report that identifies users having a username for at least one software application and not having a unique user identification (ID).

15. The method of claim 13 wherein the requested report is a dormant users report that identifies users having a username for at least one software application that have not had recent interaction with that software application as defined by a predetermined time or time period.

16. The method of claim 13 wherein the requested report is an application access report that identifies a most recent access date for each software application associated with a user.

17. The method of claim 13 wherein the requested report is an access right audit report that identifies software application access inconsistent with at least one organizational rule.

18. The method of claim 13 wherein the requested report is a departed user access report that identifies software application access after a user'"'"'s termination date.

19. The method of claim 13 wherein the requested report is a shared logins report that designates records as being shared among a plurality of users if at least one organizational rule indicates some fields are associated with a shared login.

20. The method of claim 13 wherein the requested report is a role definition report that groups users having similar highest to lowest frequency of software application use.

21. A method of identifying a user of a software application, comprising:

applying a rule for comparing at least one user field from the software application against a corresponding field in a record in a master user table (MUT), wherein the at least one user field is not associated with a known user of the software application; and

identifying a match by comparing the at least one field from the software application against the corresponding field in the record in the master user table (MUT), wherein a portion of the at least one user field from the software application is identical to a portion of the corresponding field in the record in the master user table (MUT), and the record in the master user table (MUT) is associated with a known individual.

22. The method of claim 21, wherein the rule is a matching rule selected from a plurality of matching rules.

23. The method of claim 21, wherein the rule is a suggested matching rule selected from a plurality of suggested matching rules.

24. The method of claim 21, wherein the rule is a matching rule that identifies more than one field from the software application and one field in the record in the master user table (MUT).

25. The method of claim 21, wherein the rule is a suggested matching rule that identifies more than one field from the software application and one field in the record in the master user table (MUT).

26. The method of claim 24, wherein the one field from the software application and one field in the record in the master user table (MUT) includes a social security number (SSN).

27. The method of claim 25 wherein the one field from the software application and one field in the record in the master user table (MUT) includes a social security number (SSN).

28. The method of claim 21, further comprising:

applying a secondary rule for comparing a secondary user field from the software application against a corresponding secondary field in a record in a master user table (MUT), wherein the secondary field is not associated with a known user of the software application;

29. The method of claim 28, wherein the secondary rule is a matching rule selected from a plurality of matching rules.

30. The method of claim 28, wherein the secondary rule is a suggested matching rule selected from a plurality of suggested matching rules.