Closed fdalmaup closed 1 year ago
A test is considered valid if the following conditions are met:
analysisd
.{wazuh_path}/logs/ossec.log
file.The data available in our Wazuh-dev environment for each of these supported services will be used. Additional logs may be created if they are necessary or there is insufficient data for testing.
Bucket/Service type | Status | Issue ref. |
---|---|---|
Test using ossec.conf in a manager | :green_circle: | - |
Test using ossec.conf in an agent (Python 3.6) | :green_circle: | - |
The module worked as expected.
Deploy a CentOS 8 agent and install the required dependencies described in the official Wazuh documentation, then run the module adding the following configuration to the ossec.conf
using Python 3.6:
The module worked as expected.
No data must be modified or removed unless it was specified for the test.
The tests assume there is a valid authentication file located at /var/ossec/wodles/gcloud/credentials.json
.
A test is considered valid if the following conditions are met:
analysisd
.{wazuh_path}/logs/ossec.log
file.Bucket/Service type | Status | Issue ref. |
---|---|---|
Test using ossec.conf in a manager | :green_circle: | - |
Test using ossec.conf in a agent (Python 3.6) | :green_circle: | - |
To test Pub/Sub integration we developed a script able to publish any number of messages in the testing topic so we can ensure there always will be data available for the tests. This was required because of how Pub/Sub is designed as the messages are consumed once they are pulled.
Run the module using the following ossec.conf
configuration:
The module worked as expected, 50 events were sent to analysisd
.
Run the module using the following ossec.conf
configuration:
The module worked as expected, 50 events were sent to analysisd
.
The following tests must be performed in sequential order. No data must be modified or removed unless it was specified for the test.
The tests assume there is a valid authentication file located at {wazuh_path}/wodles/azure/credentials
.
A test is considered valid if the following conditions are met:
analysisd
.{wazuh_path}/logs/azure-logs.log
file.Bucket/Service type | Status | Issue ref. |
---|---|---|
Test using ossec.conf in a manager | :green_circle: | - |
Test using ossec.conf in a agent (Python 3.6) | :green_circle: | - |
Remove the database file and run the module using the following configuration. Check the output and the database status.
The module worked as expected. The events were sent to the analysis engine.
Remove the database file and run the module using the following configuration. Check the output and the database status.
The module worked as expected. The events were sent to the analysis engine.
The logall_json option must be enabled in the ossec.conf
file before starting the tests.
Apply the following configuration, restart Wazuh and check ossec.log to verify the module is running
<wodle name="docker-listener">
<interval>30s</interval>
<attempts>5</attempts>
<run_on_start>yes</run_on_start>
<disabled>no</disabled>
</wodle>
Run a container with no cache available
docker run ubuntu
Remove the image
The module worked as expected
The test assumes there is a functional Shuffle instance with an available webhook.
A test is considered valid if the following conditions are met:
{wazuh_path}/logs/integrations.log
and {wazuh_path}/logs/ossec.log
file.The following configuration has to be added to ossec.conf
<integration>
<name>shuffle</name>
<hook_url>http://<IP>:3001/api/v1/hooks/<HOOK_ID></hook_url>
<level>3</level>
<alert_format>json</alert_format>
</integration>
Also, the configuration integrator.debug=2
to local_internal_options.conf
.
Restart the Wazuh Manager.
The integration works as expected, sending the alerts to Shuffle.
The following issue aims to perform all the required testing for the current release candidate to ensure the modules (AWS, GCP, Azure, DockerListener and Shuffle) works as expected, report the results, and open new issues for any encountered errors.
Modules tests information
Test report procedure
Any failing test must be properly addressed with a new issue, detailing the error and the possible cause. It must be included in the
Fixes
section of the current release candidate main issue.The resulting logs for the tests must be included in the status report so it can be used by the auditors to dig deeper into any possible failures and details.
Conclusions
Auditors validation
The definition of done for this one is the validation of the conclusions and the test results from all auditors.
All checks from below must be accepted in order to close this issue.