LogRhythm
- 09 Jul 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
LogRhythm
- Updated on 09 Jul 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
LogRhythm combines SIEM, user and entity behavior analytics, network traffic and behavior analytics, and security automation and orchestration.
Types of Assets Fetched
This adapter fetches the following types of assets:
- Devices
Parameters
- LogRhythm Domain (required) - The hostname of the LogRhythm server. The LogRhythm Domain format is https://[instance]:8501.
- API Token (required) - API Token generated to use the LogRhythm API. For more details, see Generating API Token.
- Verify SSL - Select whether to verify the SSL certificate offered by the value supplied in LogRhythm Domain. For more details, see SSL Trust & CA Settings.
- HTTPS Proxy (optional) - A proxy to use when connecting to the value supplied in LogRhythm Domain.
To learn more about common adapter connection parameters and buttons, see Adding a New Adapter Connection.
Advanced Settings
Note:
Advanced settings can either apply for all connections for this adapter, or you can set different advanced settings and/or different scheduling for a specific connection, refer to Advanced Configuration for Adapters.
- Fetch Assets (optional) - Select this option to fetch data from the 'agent' endpoint.
- Fetch log sources behind collectors - Select this option to fetch configured syslog log sources.
- Fetch recent device logs for determining Last Seen - Select this option to only fetch the most recent device logs to determine the 'Last Seen' value.
- Ignore devices with record status (default: Retired) - Enter a record status with which to ignore devices.
Note:
To learn more about Adapter Configuration tab advanced settings, see Adapter Advanced Settings.
Required Ports
Port 8501 must be accessible for Axonius to communicate with the API in LogRhythm Domain.
Generating API Token for LogRhythm API
- Launch the LogRhythm client console.
- Select Deployment Manager > Third Party Applications.
- Create a new third-party application. To do this:
- Click the green Plus sign in the Client Console toolbar. The Third Party Application Properties window is displayed.
- Specify the name and description for your application in the appropriate fields.
- Click Apply to generate the token. This will force a quick restart of the authentication server to set up and validate the token. After a few moments, the client ID and client secret will appear.
- Adjust the expiry date as desired to make the token last longer or expire faster. By default, the token expires after 365 days (one year).
- Click Generate Token to create an API token.
- Enter the user name and password of the LogRhythm account that the token should connect with.
- Copy and paste the token into a text file that can be referenced from the PowerShell script.
Was this article helpful?