Ingest Logs in SIEM
Prerequisites
Logpoint: v7.8.1 or later
AWS Access: Read access to the Amazon S3 bucket and its objects
AWS Credentials: Valid AWS Access Key ID and Secret Access Key
Network Access: Connectivity to AWS S3 endpoints (proxy support available)
Installation
Install S3Fetcher
Download the .pak file from the Marketplace.
Go to Settings >> System Settings from the navigation bar of Logpoint.
Click Applications.
Click Import.
Browse to the downloaded .pak file.
Click Upload.
After installation, verify the integration appears under Settings >> System Settings >> Plugins
Configuration
Before configuring S3Fetcher in Logpoint, obtain AWS access credentials (Access Key ID and Secret Access Key). Go to the AWS Documentation for instructions on retrieving them.
Configure S3Fetcher using two methods:
Log Source, recommended as it provides a centralized interface for all integrations
Method 1: Configure via Log Source
Go to Settings >> Log Sources and click + Add Log Source.
Click + Create New and select S3 Fetcher.
Source
Configure the log source settings:
Click Source.
Enter the Log Source's Name.
Select the Fetch Interval (min) to set how frequently the logs are retrieved.
Select the Charset and Time Zone.
Connector
Configure the connection to AWS:
Click Connector.
EndPoint URL:
For Amazon S3:
https://s3.amazonaws.com(default).For third-party services: Enter the service URL.
Enter your AWS Access Key ID and AWS Secret Access Key.
Enter the AWS Bucket Name. S3Fetcher fetches logs from this bucket.
In Filter by Prefix, enter a prefix name to fetch a specific file or folder from the bucket. Leave this field empty to fetch the entire bucket.
Select the AWS Region.
Select Initial Fetch Date. S3Fetcher fetches logs from the specified date. To change the Initial Fetch Date and re-fetch logs from the new date, enable Reset Last Fetch Date and select the new date.
If you are using a Distributed Logpoint, select Distributed Collectors from the drop-down.
Select a Parser to parse the logs.
Enable Proxy to use a proxy server.
Select either HTTP or HTTPS protocol.
Enter the proxy server IP address and the PORT number.
Routing
Set up log storage and routing:
Create Repository:
Click Routing and + Create Repo.
Enter a Repo name.
In Path, specify the location to store incoming logs.
In Retention (Days), set how long logs are kept before automatic deletion.
In Availability, select the Remote logpoint and Retention (Days).
Click Create Repo.
Select the created repo in Repo.
Create Routing Criteria
Click + Add row.
Enter a Key and Value for log filtering.
Select log handling options:
Store raw message: Store both incoming and normalized logs.
Discard raw message: Keep only normalized logs.
Discard entire event: Discard both incoming and normalized logs.
Select the target Repository.
Normalization
Set up log normalization:
Click Normalization.
Either:
Select a previously created normalization policy from the dropdown, or
Select a normalizer from the list and click the swap icon.
After the above configurations, click Create Log Source to save all configurations.
Method 2: Configure via Devices
Configuring the S3Fetcher via Devices
Go to Settings >> Configuration from the navigation bar and click Devices.
Click the Add collectors/fetchers icon for the localhost device.
Click S3 Fetcher.
Click Add and enter a Name.
Enter your AWS Access Key ID and Secret Access Key.
Enter the AWS Bucket Name. S3Fetcher fetches logs from this bucket.
In Filter by Prefix, enter a prefix name to fetch a specific file or folder from the bucket. Leave this field empty to fetch the entire bucket.
EndPoint URL:
For Amazon S3:
https://s3.amazonaws.com(default).For third-party services: Enter the service URL.
Select the AWS Region.
Select the frequency at which logs are retrieved in Fetch Interval (minutes).
Select the Logs From date. S3Fetcher fetches logs from the specified date.
Select a Processing Policy and Charset.
Select a Parser to parse the logs.
Enable Proxy to use a proxy server.
Select either HTTP or HTTPS protocol.
Enter the proxy server IP address and the PORT number.
Click Test to check if the configuration is working correctly.
Click Submit.
Last updated
Was this helpful?