Closed juliamagan closed 2 years ago
I've followed the Quickstart guide and set up an all-in-one environment. For the agent, we have followed this guide. We have installed a Windows agent, too.
Install type | OS | CPU | RAM |
---|---|---|---|
All-in-one | CentOS 8 | 2 | 4096 |
Agent | CentOS 8 | 2 | 1024 |
Agent | Windows | 2 | 4096 |
Linux agent:
We have created /home/vagrant/test
directory and added the following configuration in /var/ossec/etc/ossec.conf
:
<directories check_all="yes" whodata="yes">/home/vagrant/test</directories>
Windows agent:
We have created C:\Test
directory and added the following configuration in C:\Program Files (x86)\ossec-agent\ossec.conf
:
<directories check_all="yes" report_changes="yes" whodata="yes">C:\\Test</directories>
Finally, we restarted the agents to apply the configuration.
touch test/test.txt
echo "Testing" > test/test.txt
rm test/test.txt
Linux agent:
alerts.json
Windows agent:
alerts.json
Description
In this issue, we will study the FIM test case described here. All the info obtained will be used in the future for the design and implementation of E2E tests.
Tasks
Conclusion
We needed one manager and two agents (Linux and Windows). However, it could be done with one manager and one agent.