Quantifying Risk Based on Relationships and Applying Protections Based on Business Rules
First Claim
1. A method comprising:
- receiving a request to access a system from a user, the request including a user identification;
receiving metadata of the request to access the system;
querying a database with the user identification and the metadata to identify relationship data, the relationship data indicating a relationship between an individual assigned the user identification and the system;
inputting the relationship data into a rules engine; and
selecting at least one security measure with the rules engine based on the relationship data.
2 Assignments
0 Petitions
Accused Products
Abstract
An embodiment of the invention provides a method for controlling access to a system, wherein a request to access the system and metadata of the request are received from a user, the request including a user identification. The metadata includes: information obtained from a history of prior accesses to an application access system, information obtained from a history of prior accesses to a wireless authentication system, and/or confirmation of the user identification by an entity physically proximate to the user. A database is queried with the user identification and the metadata to identify relationship data. The relationship data indicates the relationship between the individual assigned the user identification and an entity owning the system, an entity leasing the system, and/or an entity operating the system. The relationship data is input into a rules engine; and, security measure(s) are selected with the rules engine based on the relationship data.
-
Citations
25 Claims
-
1. A method comprising:
-
receiving a request to access a system from a user, the request including a user identification; receiving metadata of the request to access the system; querying a database with the user identification and the metadata to identify relationship data, the relationship data indicating a relationship between an individual assigned the user identification and the system; inputting the relationship data into a rules engine; and selecting at least one security measure with the rules engine based on the relationship data. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A method for controlling access to a system, said method comprising:
-
receiving a request to access the system from a user, the request including a user identification; receiving metadata of the request to access the system, the metadata including at least one of; information obtained from a history of prior accesses to an application access system, information obtained from a history of prior accesses to a wireless authentication system, and confirmation of the user identification by an entity physically proximate the user; querying a database with the user identification and the metadata to identify relationship data, the relationship data indicating a relationship between an individual assigned the user identification and the system; inputting the relationship data into a rules engine; and selecting at least one security measure with the rules engine based on the relationship data. - View Dependent Claims (11, 12, 13, 14)
-
-
15. A method for controlling access to a system, said method comprising:
-
receiving a request to access the system from a user, the request including a user identification; receiving metadata of the request to access the system, the metadata including at least one of; information obtained from a history of prior accesses to an application access system, information obtained from a history of prior accesses to a wireless authentication system, and confirmation of the user identification by an entity physically proximate the user; querying a database with the user identification and the metadata to identify relationship data, the relationship data indicating a relationship between the individual assigned the user identification and at least one of an entity owning the system, an entity leasing the system, and an entity operating the system; inputting the relationship data into a rules engine; and selecting at least one security measure with the rules engine based on the relationship data. - View Dependent Claims (16, 17, 18, 19)
-
-
20. A method for controlling access to a system, said method comprising:
-
receiving a request to access the system from a user, the request including a user identification; receiving metadata of the request to access the system, the metadata including; information obtained from a history of prior accesses to an application access system, information obtained from a history of prior accesses to a wireless authentication system, and confirmation of the user identification by an entity physically proximate the user; querying a database with the user identification and the metadata to identify relationship data, the relationship data indicating a relationship between an individual assigned the user identification and the system; inputting the relationship data into a rules engine; and selecting at least one security measure with the rules engine based on the relationship data. - View Dependent Claims (21, 22, 23, 24, 25)
-
Specification