Elastic Fleet is pre-configured during Security Onion setup, however, centralized management of configuration is provided within its user interface inside of Kibana.
Configuration options for various components are detailed below.
This section displays registered Elastic agents (https://docs.securityonion.net/en/2.4/elastic-agent.html) and allows the user to add additional agents.
To view agent details, click the
To assign the agent to a new policy, unenroll, upgrade the agent, or perform other actions, click the
Actions menu on the right side of the agent listing and select the appropriate option.
By default, Elastic Agent is installed on every Security Onion grid node. As a result, all grid node agents will be enrolled in the
SO-Grid-Nodes agent policy. We do not recommend removing policy settings for Security Onion grid node agents.
To add a new agent to your deployment, see the following:
Agent policies dictate what data each agent will ingest and forward to Elasticsearch. This could be through the use of an HTTP, log file, or TCP-based input.
The individual components within each agent policy are called integrations (referred to as
package policies at the API level), and refer to a specific input and settings pertinent to a data source.
For example, the
SO-Grid-Nodes agent policy is comprised of the following integrations:
- elasticsearch-logs (
- import-evtx-logs (
- import-suricata-logs (
- import-zeek-logs (
- kratos-logs (
- osquery-grid-nodes (
- redis-logs (
- strelka-logs (
- suricata-logs (
- syslog-tcp-514 (
- syslog-udp-514 (
- system-grid-nodes (
- zeek-logs (
Agent Policies - endpoints-initial¶
Agent installers downloaded from SOC –> Downloads, are deployed using the
endpoints-initial Agent Policy. This policy includes the
Elastic Defend integration)¶
Elastic Defend integration has both free and paid features. By default, only the following free features are enabled:
Event Collection - Windows
- Credential Access
- DLL and Driver Load
Event Collection - macOS
Event Collection - Linux
Osquery Manager integration)¶
Osquery Manager integration runs osquery as a daemon on the endpoint, and makes the endpoint available for Live or Scheduled queries through the Osquery manager interface in Kibana.
System integration collects the following logs from the endpoint, where applicable:
System auth logs
Windows Event Log - Application channel
Windows Event Log - Security channel
Windows Event Log - System channel
Windows integration collects the following logs from the endpoint, where applicable:
Windows Event Log:
- ForwardedEvents channel
- Windows Powershell channel
- Microsoft-Windows-Powershell/Operational channel
- Microsoft-Windows-Sysmon/Operational channel
Security Onion 2.4.10 supports the following Elastic integrations:
Security Onion 2.4.20 supports these additional Elastic integrations:
Security Onion 2.4.30 supports these additional Elastic integrations:
You can read more about Elastic integrations at https://docs.elastic.co/integrations.
Adding an Integration¶
New integrations can be added to existing policies to provide increased visibility and more comprehensive monitoring.
To add an integration to an existing policy:
Agent policies ->
$Policy name, click
Add Integration and follow the steps for adding the integration.
Adding a Custom Integration¶
A custom integration can be added by adding an integration such as the
Custom Logs integration. We can specify various settings relative to the data source and define additional actions to be performed.
An enrollment token allows an agent to enroll in Fleet, subscribe to a particular agent policy, and send data.
Each agent policy typically uses its own enrollment token. It is recommended that these tokens are NOT to be changed, especially those generated by default Security Onion agent policies.
Data collected by Elastic Agent is sent to a data stream (https://www.elastic.co/guide/en/fleet/current/fleet-overview.html#data-streams-intro) by default. This allows data to be efficiently categorized and managed across a variety of datasets. This section within the Fleet UI allows for a quick review of data streams generated by data from Elastic Agent.
The section provides details such as:
- Fleet server hosts in your deployment
- Configured outputs
- specifies where data will be sent
- this should include Elasticseach for the Fleet server and Logstash for Elastic Agent
- Method in which agent binaries will be downloaded
- this will be a a local artifact repository if running an airgapped deployment)
We do NOT recommend changing these settings, as they are managed by Security Onion.
For more information about Fleet, please see https://www.elastic.co/guide/en/kibana/current/fleet.html.