The following explains how to add a collector agent to Starling Identity Analytics & Risk Intelligence in order to begin collecting entitlement data.
|
NOTE: You cannot install multiple collector agents on the same machine. |
|
NOTE: The data collected by the data source module(s) associated with the collector agent will remain within Starling Identity Analytics & Risk Intelligence until it has been purged. For more information, see Purging data. |
|
IMPORTANT: Read the Additional hardware and software requirements before installing a collector agent. |
To add a collector agent
Once installation has been successfully completed, close the Add Collector Agent dialog to return to the Collector Agents page.
The page will automatically refresh once the collector agent has been installed. The new collector agent appears listed on the Collector Agents page with a green check mark to indicate the collector agent has been installed correctly and is able to communicate with Starling Identity Analytics & Risk Intelligence. You are now able to add modules to the collector agent (see Adding data source modules to Starling Identity Analytics & Risk Intelligence).
The Collector Agent page is displayed when the Collector Agents link is selected from the Configuration drop-down menu located in the navigation bar. The Collector Agent page is used for adding and managing the collector agents and data source modules that are configured for your account.
The following information appears once at least one collector agent has been installed.
Use this field to filter the list of collector agents appearing at the bottom of this page.
This button is used for adding a new collector agent. For more information, see Adding collector agents to Starling Identity Analytics & Risk Intelligence.
The following information appears in the table at the bottom of the page once at least one collector agent has been configured.
This is the host name for the collector agent.
This is the number of data source modules currently configured for the collector agent.
This displays the time of the last communication between the collector agent and the Starling Identity Analytics & Risk Intelligence cloud service. This communication is done through an HTTPS call on port 443 and cannot be configured. This check is in order to ensure communication between the two components is active and secure.
This indicates the current status of the connection. Mousing over the displayed icon provides a brief explanation of the current status.
Clicking this button displays information regarding the currently installed versions of both the collector agent and the installer.
This drop-down menu displays the following configuration options:
Once you have finished Adding collector agents to Starling Identity Analytics & Risk Intelligence you need to configure modules for that source.
|
IMPORTANT: Read the Additional hardware and software requirements before adding a data source module. |
|
NOTE: Only one module of each type can be added to each collector agent. |
|
NOTE: The amount of time needed to collect data will increase if the network is slow between the machine where the collector agent is installed and the machine it is collecting data from. |
(Optional) Enter a Host Name or IP Address. If you have more than one Active Directory data source available in the environment then you need to specify which one to connect with, otherwise Starling Identity Analytics & Risk Intelligence will randomly select one.
|
IMPORTANT: A global catalog must be resolvable via its DNS name regardless of whether you are connecting directly to it or to a domain controller connected with a global catalog. |
In the Data Collection Frequency (hours) field, enter how often Starling Identity Analytics & Risk Intelligence should initiate a collection. By default, collections will occur every 24 hours. This process will be indicated by an alert bar in Starling Identity Analytics & Risk Intelligence followed by the impacted pages automatically updating once the evaluation has completed.
|
NOTE: The Data Collection Frequency (hours) value must be between 1-576. |
Click Save to save the module and close the dialog.
Once you have completed adding the data source, the following information may appear indicating the state of the connection:
The next step in this process is the actual collection of the data, which is indicated by a icon. During this step, the data source will begin the process of connecting with and sending data to Starling Identity Analytics & Risk Intelligence. This process may take a while depending on a number of factors (for example, the amount of data that needs to be collected).
The data being collected includes information regarding disabled accounts since, although inactive, they still exist, and therefore can provide important information about both the account and the data source overall. However, this account information will not include data related to actions an account cannot perform. For example, expired entitlements within Safeguard are not considered when calculating the risk level of an account since an expired entitlement is the same as the entitlement not existing.
(Optional) Enter a Host Name or IP Address. If you have more than one Active Roles data source available in the environment then you need to specify which one to connect with, otherwise Starling Identity Analytics & Risk Intelligence will randomly select one.
|
IMPORTANT: The collector agent must also be able to resolve the DNS names of all computers hosting Active Roles Administration Services in the Active Roles installation. |
In the Data Collection Frequency (hours) field, enter how often Starling Identity Analytics & Risk Intelligence should initiate a collection. By default, collections will occur every 24 hours. This process will be indicated by an alert bar in Starling Identity Analytics & Risk Intelligence followed by the impacted pages automatically updating once the evaluation has completed.
|
NOTE: The Data Collection Frequency (hours) value must be between 1-576. |
Click Save to save the module and close the dialog.
Once you have completed adding the data source, the following information may appear indicating the state of the connection:
The next step in this process is the actual collection of the data, which is indicated by a icon. During this step, the data source will begin the process of connecting with and sending data to Starling Identity Analytics & Risk Intelligence. This process may take a while depending on a number of factors (for example, the amount of data that needs to be collected).
The data being collected includes information regarding disabled accounts since, although inactive, they still exist, and therefore can provide important information about both the account and the data source overall. However, this account information will not include data related to actions an account cannot perform. For example, expired entitlements within Safeguard are not considered when calculating the risk level of an account since an expired entitlement is the same as the entitlement not existing.
In the Data Collection Frequency (hours) field, enter how often Starling Identity Analytics & Risk Intelligence should initiate a collection. By default, collections will occur every 24 hours. This process will be indicated by an alert bar in Starling Identity Analytics & Risk Intelligence followed by the impacted pages automatically updating once the evaluation has completed.
|
NOTE: The Data Collection Frequency (hours) value must be between 1-576. |
Based on your Authentication Type, enter the following information:
Click Save to save the module and close the dialog.
Once you have completed adding the data source, the following information may appear indicating the state of the connection:
The next step in this process is the actual collection of the data, which is indicated by a icon. During this step, the data source will begin the process of connecting with and sending data to Starling Identity Analytics & Risk Intelligence. This process may take a while depending on a number of factors (for example, the amount of data that needs to be collected).
The data being collected includes information regarding disabled accounts since, although inactive, they still exist, and therefore can provide important information about both the account and the data source overall. However, this account information will not include data related to actions an account cannot perform. For example, expired entitlements within Safeguard are not considered when calculating the risk level of an account since an expired entitlement is the same as the entitlement not existing.
|
IMPORTANT: In order to use Azure Active Directory as a data source, additional configuration must be done BEFORE it will be able to connect with Starling Identity Analytics & Risk Intelligence. For instructions on configuring Azure Active Directory, see Configuring Azure Active Directory. |
In the Data Collection Frequency (hours) field, enter how often Starling Identity Analytics & Risk Intelligence should initiate a collection. By default, collections will occur every 24 hours. This process will be indicated by an alert bar in Starling Identity Analytics & Risk Intelligence followed by the impacted pages automatically updating once the evaluation has completed.
|
NOTE: The Data Collection Frequency (hours) value must be between 1-576. |
Click Save to save the module and close the dialog.
Once you have completed adding the data source, the following information may appear indicating the state of the connection:
The next step in this process is the actual collection of the data, which is indicated by a icon. During this step, the data source will begin the process of connecting with and sending data to Starling Identity Analytics & Risk Intelligence. This process may take a while depending on a number of factors (for example, the amount of data that needs to be collected).
The data being collected includes information regarding disabled accounts since, although inactive, they still exist, and therefore can provide important information about both the account and the data source overall. However, this account information will not include data related to actions an account cannot perform. For example, expired entitlements within Safeguard are not considered when calculating the risk level of an account since an expired entitlement is the same as the entitlement not existing.
The Data Source Modules page is displayed by editing a configured collector agent (see Adding data source modules to Starling Identity Analytics & Risk Intelligence). The Data Source Modules page is used for adding and managing the data source modules for a collector agent.
Once a collector agent has been installed, the following information appears on this page:
Use this field to filter the list of data source modules appearing at the bottom of this page.
This button is used for adding a new data source module. For more information, see Adding data source modules to Starling Identity Analytics & Risk Intelligence.
The following information appears in the table at the bottom of the page once at least one data source module has been configured for the collector agent.
This is the type of data source module.
This is the host name for the collector agent.
This is the last update from the data source module to Starling Identity Analytics & Risk Intelligence. These updates can occur manually and are also configurable for each data source module (for information on configuring those settings, see Editing a data source module).
This indicates the current status of the connection. Mousing over the displayed icon provides a brief explanation of the current status.
Clicking this button displays information regarding the currently installed versions of both the collector agent and the installer.
This drop-down menu displays the following configuration options:
© ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center