You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SCA allows creating rules without compliance field (see SCA checks). So, while I was creating a custom SCA file, I can't expand those rules without this field in the SCA section of the agent.
If you want to reproduce it, add this rule to any SCA file:
- id: 7101title: "Ensure ufw is installed"description: "ufw the default firewall manager in Ubuntu and can be installed in your Raspberry Pi to help you to set up the firewall rules"rationale: "A firewall is a network security system that monitors and controls incoming and outgoing network traffic based on predetermined security rules. ufw uses iptables to set up the firewall but with less complicated rules. This will filter your network traffic and block non-desired or malicious traffic."remediation: "Install ufw using the following command. # apt install ufw"references:
- 'https://www.raspberrypi.org/documentation/configuration/security.md'condition: nonerules:
- 'c:dpkg -s ufw -> r:install ok installed'
Steps to reproduce
Go to Security configuration assessment.
Select the agent with the rule from above.
Select the policy with the rule from above.
Try to expand the rule to get more info:
Screenshots
Rule without compliance:
Rule with compliance:
Additional context
Wazuh Manager: Ubuntu 16.04
Environment: The Wazuh Manager and ELK run in Docker containers.
Agent: Raspbian GNU/Linux 10 (buster)
Browser: Mozilla Firefox 77.0.1
The text was updated successfully, but these errors were encountered:
Description
Hi team,
SCA allows creating rules without
compliance
field (see SCA checks). So, while I was creating a custom SCA file, I can't expand those rules without this field in the SCA section of the agent.If you want to reproduce it, add this rule to any SCA file:
Steps to reproduce
Security configuration assessment
.Screenshots
compliance
:compliance
:Additional context
The text was updated successfully, but these errors were encountered: