Wiz Explains How to Create Agentless Host Configuration Rules

Summary
Wiz describes custom agentless rules for auditing host and application settings, detecting configuration drift, and generating remediation findings. Its example checks Nginx configuration for the merge_slashes directive.
Key points
- Custom rules run during agentless workload scans to assess host and application configurations without deploying an agent or sidecar.
- The rules can check file contents, package information, and operating-system settings across selected applications and platforms.
- Wiz says the rules can identify configuration drift over time, generate findings, and alert teams to misconfigurations for remediation.
- The example checks /etc/nginx/nginx.conf for a merge_slashes setting; the article says leaving this setting off can lead to directory traversal.
Article Details
- Defense Focus
- Agentless auditing of host and application configurations to identify misconfigurations and configuration drift across cloud workloads.
- Detection Methods
- Run custom host configuration rules during agentless workload scans to assess new workloads and detect configuration changes.
- Use file-content parsing, package-information probing, and OS configuration tests.
- Define checks with Direct OVAL, including regex pattern matching against specified files; the example checks /etc/nginx/nginx.conf for the Nginx merge_slashes directive.
- Generate findings for hosts that fail a rule and review host configuration details in the Configuration tab.
- Data Sources
- Host and application configuration data
- Virtual machine files and file contents
- DPKG package information
- Operating system configuration
- Detected applications and operating systems on workloads
- Rule Types
- Direct OVAL rules
- File-content and regex-matching rules
- File permission tests
- Package-information tests
- Operating-system configuration tests
- Platforms
- Wiz
- Defensive Actions
- Create custom rules for the applications and operating systems in scope, and configure appropriate severity and compliance-framework associations.
- Use agentless scans to assess workloads without deploying an agent or sidecar.
- Review generated findings and remediate identified host or application misconfigurations.
- Monitor configuration changes over time for drift.
