OSSEC Variants (OSSEC/WAZUH/ATOMIC)
Overview
Apica Ascent supports ingesting security events logs directly from OSSEC compatible agents. OSSEC (Open Source Security) is a powerful, open-source host-based intrusion detection system (HIDS) developed to detect and prevent malicious activities on systems. It has the ability to monitor all types of environments, including Windows, Mac OS X, Linux and Solaris systems. OSSEC works by monitoring the system.
The OSSEC architecture consists of three main components: the manager, the agent, and the local OSSEC server.
The manager is responsible for managing the agents, which monitor system activity and report back to the manager. The manager then compiles the agent reports, combines them with its own rules and tests, and alerts if there are any security issues.
The agents watch files, directories and network connections for changes or anomalies in data flow that could signify a malicious attack. Agents can detect attacks from worms, viruses, hacking tools, and more. The agent also looks for any unauthorized changes to critical system files or configurations that could indicate an attempted breach of security.
The local OSSEC server is responsible for analyzing the data from the agents and taking appropriate action depending on the type of attack detected. This can involve sending out alerts, blocking traffic, performing forensic analysis, and more.
OSSEC is an incredibly powerful tool that can be used to detect and prevent malicious activities on systems. It is an invaluable asset for any organization looking to secure their networks from threats both outside and within the company.
Apica Ascent takes over the functions of the manager and the local OSSEC server and makes it easy to bring together security related events into your data fabric for instant consumption.
Starting the manager, ossec server
Launching the Apica Ascent OSSEC components is accomplished by launching the OSSEC Input "App Extension" which can be found under "Explore"
![](https://docs.apica.io/~gitbook/image?url=https%3A%2F%2F2948796384-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-LmzGprckLqwd5v6bs6m%252Fuploads%252FgZycoONvAOIGPK3ahGaz%252FScreen%2520Shot%25202023-01-02%2520at%252010.19.49%2520PM.png%3Falt%3Dmedia%26token%3Ddb4b002a-1de6-4812-a1a4-8b9551d938c9&width=768&dpr=4&quality=100&sign=d6349895&sv=1)
You can now provide the credentials that the agents can use to connect to Apica Ascent instance
![](https://docs.apica.io/~gitbook/image?url=https%3A%2F%2F2948796384-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-LmzGprckLqwd5v6bs6m%252Fuploads%252FWot3c5WwO0CK6tApNE56%252FScreen%2520Shot%25202023-01-02%2520at%252010.24.04%2520PM.png%3Falt%3Dmedia%26token%3Df4032f97-6c71-4ded-bc4f-87b1635f4cbb&width=768&dpr=4&quality=100&sign=9d26e08f&sv=1)
HostName - Enter a name for the app extension.
AuthToken - The user chooses a 32-digit hex number, for example '2DAEF3165265A....FB793126B780BA4'.
Resources - The user enters CPU and MEM usage limit, format adopted from Kubernetes resource notation - see explanation here, https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ Example setting,
cpu/cpu_limit = 1000m
,mem/mem_limit=4Gi
.Version - Enters the image here. The latest Apica Ascent OSSEC component image can be browsed here, https://hub.docker.com/r/logiqai/hauler-ossec/tags Example image is 'logiqai/hauler-ossec:v1'.
Shortly after the user configures all of the above, he will see the assigned manager IP address appears in the display below. This IP is needed for setting up the agent next.
![](https://docs.apica.io/~gitbook/image?url=https%3A%2F%2F2948796384-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-LmzGprckLqwd5v6bs6m%252Fuploads%252FKAhK7YOqhplYvq1Ziy5d%252Fossec-display-2023-01-03_12-11-18.jpg%3Falt%3Dmedia%26token%3D8f95343d-6ba0-4b65-a62f-0251136521a2&width=768&dpr=4&quality=100&sign=ddbb255&sv=1)
Wazuh agent installation
OSS (open source software) OSSEC/Automic agent variation Wazuh agent is used for capturing host observability data. Wazuh agent is better than the OSSEC agent in terms of performance, functionality and scalability. Wazuh agent has a better rules engine that is more efficient for large-scale deployments. It also offers enhanced logging capabilities with the ability to tag events and generate alerts in real-time. Furthermore, Wazuh can collect data from multiple sensors, such as Windows hosts, Linux systems, cloud platforms, and network devices.
Wazuh agent can easily be installed on both Linux and Windows platforms. Please follow the simple installation steps below,
Configuring the agents
OSSEC/Automic OSS agent variation Wazuh agents can connect to the Apica Ascent instance using the agent-auth tool once after successfully installed. For Debian-style Linux distribution, the command below is used to link the agent to the manager.
Windows system runs similarly from cmd or power shell window with Administrator privileges.
For Windows system we have a powershell script which can directly setup OSSEC agent. Please follow this link for Windows OSSEC agent setup.
Enable automatic vulnerability scan at the endpoint
Wazuh agent supports automatic vulnerability scans, file integrity monitoring, and policy compliance features. With the Apica Ascent server manager activated, the platform will provide comprehensive visibility across the entire environment with centralized management of security policies and events.
Last updated