{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":44554,"path":"security-management/security-incident-response/install-and-config-logrhythm.md","title":"Install the plugin and configure LogRhythm","bundle":null,"doc_type":null,"release":"australia","body":"\n# Install the plugin and configure LogRhythm\n\nBefore you run the integration on your instance, complete the installation and configuration steps so the application properly integrates with Security Operations on the ServiceNow AI Platform®.\n\n## Before you begin\n\nRole required: admin\n\nComplete the following setup checklist prior to installation. These setup tasks are required for a smooth installation and configuration. The latest LogRhythm version is 7.8 or later.\n\n**Note:** Your existing alarm profiles will no longer be supported on the latest LogRhythm version, so you need to create new alarm profiles and perform the required configurations.\n\n<table id=\"table_xxz_jyj_4cb\"><thead><tr><th>\n\nSetup task\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nVerify that you have assigned the required ServiceNow AI Platform® and Security Incident Response \\(SIR\\) roles.\n\n</td><td>\n\nThe following roles are required for installation, configuration, and verification of expected results:-   The system administrator \\(admin\\) installs the application plugin and assigns the security incident administrator \\(sn\\_si.admin\\) role.\n-   The \\(sn\\_si.admin\\) oversees the following tasks:\n    -   Names, creates, and edits alarm profiles.\n    -   Maps and filters alarms – identifies specific LogRhythm alarms that create security incidents and configures how these alarm fields map to a ServiceNow AI Platform® security incident.\n    -   Previews security incident details for accuracy prior to finalizing the configuration.\n    -   Ingests historical alarms and schedules pulled alarms.\n    -   Assigns the security incident analyst \\(sn\\_si.analyst\\) role.\n    -   This role also has access to the Security Operations module.\n-   The security incident analyst \\(sn\\_si.analyst\\) responds to security incidents that are created based on the alarm profile settings.\n\n</td></tr><tr><td>\n\nObtain a LogRhythm API user name and password and verify that you are using version LogRhythm 7.8 or later.\n\n</td><td>\n\nVisit the product website for information on API keys and to create an account: [LogRhythm Enterprise website](https://logrhythm.com/). The user accounts, credentials, and certificates must be configured properly prior to installing the application. The integration requires LogRhythm version 7.8 or later and the LogRhythm REST APIs.\n\n See [Set up the REST API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/drilldown-api-lr.md).\n\n</td></tr><tr><td>\n\nVerify that you have installed and configured a MID Server.\n\n</td><td>\n\nA MID Server is required in your ServiceNow AI Platform environment. See the [ServiceNow Product Documentation website](https://www.servicenow.com/docs) for information about how to set up and configure MID Servers.\n\n</td></tr><tr><td>\n\nVerify that the ServiceNow core applications that are required to support the integration are installed and activated before you install the application for the integration.\n\n</td><td>\n\nFor the Rome release and later family releases, the Security Incident Response Dependency plugin \\(com.snc.si\\_dep\\) is required. This plugin automatically installs all the dependencies that are required to support the Security Incident Response product. Install and activate this plugin before you install and activate the other Security Operations applications required by the integration.\n\n Verify that the following Security Operations applications are installed and activated from the ServiceNow Store. If not installed, install and activate one application at a time in the following order to ensure a smooth installation.\n\n 1.  Security Incident Response\n2.  Security Integration Framework\n3.  Security Support Common\n4.  Security Support Orchestration\n\n For more information on setting up your ServiceNow AI Platform instance for the integration, see [Get entitlement for a Security Operations product or application](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/entitle-secops-product.md) and [Activate a ServiceNow Store application](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/activate-entitled-store-app.md).\n\n</td></tr></tbody>\n</table>**Important:** If you have any connectivity issues to the LogRhythm client console, refer to the [Verify connectivity for LogRhythm](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/verify-connectivity.md).\n\n## Procedure\n\n1.  If you have not installed the application for the integration, see [Install a Security Operations integration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/install-non-core-apps.md) and follow the steps to install it.\n\n2.  Once the installation completes, navigate to **Integrations** &gt; **Integrations Configurations** and locate the LogRhythm tile.\n\n3.  Click **Configure**.\n\n    \\[Omitted image \"lr-config-tile-4-2.png\"\\] Alt text: Task: Click Configure button for LogRhythm.\n\n4.  Click the **New Configuration** link.\n\n    \\[Omitted image \"lr-config-2-4-2.png\"\\] Alt text: Task: Click New Configuration link.\n\n5.  On the form, fill in the fields:\n\n<table id=\"table_r5j_x2j_3tb\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nName\n\n</td><td>\n\nLogRhythm server name, for example, `logrhythm-server-a`.\n\n</td></tr><tr><td>\n\nBase URL\n\n</td><td>\n\nBase URL hosting the LogRhythm REST API.The MID Server permits access to the network where the LogRhythm Client Console is hosted. This URL is where the LogRhythm server is hosted within that network. Click the lock icon on the right-end to edit the field and enter text for a URL, for example, `https://logrhythm.secops-eng.com:8501/`.\n\n</td></tr><tr><td>\n\nAPI Token\n\n</td><td>\n\nEnter the token that is associated with your REST API that you created on the LogRhythm Client Console.\n\n</td></tr><tr><td>\n\nOn-Premise Deployment\n\n</td><td>\n\nOption to select if it's a LogRhythm on-premise deployment.\n\n</td></tr><tr><td>\n\nMID Server\n\n</td><td>\n\nSpecific MID Server that is set up in your environment. Only the MID Servers that are active and have been validated are available from this choice list.\n\n</td></tr></tbody>\n</table>    The following figure is an example of a completed form.\n\n    \\[Omitted image \"logrhythm-configuration.png\"\\] Alt text: A completed LogRhythm Configuration form.\n\n6.  Click **Validate and save**.\n\n    After validation is successfully completed, a message is displayed and the LogRhythm Configurations page is reloaded. The next step is to create an alarm profile.\n\n\n## What to do next\n\nAfter you successfully complete the validation, the next step is to [Creating an alarm profile for LogRhythm](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/create-alarm-profile-logrhythm.md).\n\n**Parent Topic:**[LogRhythm Overview](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/ovrview-logrhythm.md)\n\n**Previous topic:**[Set up the REST API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/drilldown-api-lr.md)\n\n**Next topic:**[Creating an alarm profile for LogRhythm](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/create-alarm-profile-logrhythm.md)\n\n"}}