Relationships are links between two or more entities. Relationships
are detected at the end of entity resolution process, when two entities share
several data attribute values.
Relationships can be based on links discovered by the system, disclosed
by an analyst, or both. However, not every relationship is interesting enough
to warrant generating an alert for further analysis or investigation. You
define relationships of interest by configuring role alert rules that specify
which combination of roles assigned to entities need to generate alerts.
Relationship examples
Examples of relationships
that might be detected during entity resolution:
- A customer is also a vendor. Based on the policies and procedures of your
organization, this might be considered a relationship of interest.
- An employee knows a customer. Unless the policies and procedures of your
organization forbid such an association, or perhaps depending on the data
that is shared by the employee and the customer, this might not be considered
a relationship of interest.
- A customer knows another customer. If one of the customers has a high
net worth to your company, knowing whom your customer knows might be a good
way to use your customer network to market within that network.