Bug/8954 action scope verify v2 - #3329
Open
lukashino wants to merge 2 commits into
Open
Conversation
added 2 commits
August 27, 2026 16:46
Ticket: 8954
There was a problem hiding this comment.
Pull request overview
Adds Suricata-verify firewall tests covering action-scope inheritance and pass secondary-action compatibility rules (ticket 8954 follow-up), ensuring invalid configurations are rejected and valid combinations continue to load.
Changes:
- Add a valid ruleset test ensuring inherited scopes remain acceptable where supported (including
passscope inheritance andalertinheritance). - Add invalid cases ensuring
passrejects unsupported inherited scopes (rule + default-policy variants). - Add valid/invalid cases ensuring
passis only permitted as a secondary action afteraccept(rule + policy variants).
Reviewed changes
Copilot reviewed 18 out of 18 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| tests/firewall/firewall-action-scope-inherited-valid/test.yaml | Verifies expected successful rule-load outcome for valid inherited scopes. |
| tests/firewall/firewall-action-scope-inherited-valid/suricata.yaml | Engine-analysis + logging config for the valid inherited-scope test. |
| tests/firewall/firewall-action-scope-inherited-valid/firewall.rules | Ruleset covering valid inherited-scope combinations (incl. pass + alert). |
| tests/firewall/firewall-action-scope-inherited-rule-invalid/test.yaml | Expects failure + specific log message for invalid inherited scope into pass (rule case). |
| tests/firewall/firewall-action-scope-inherited-rule-invalid/suricata.yaml | Engine-analysis + logging config for invalid inherited-scope rule test. |
| tests/firewall/firewall-action-scope-inherited-rule-invalid/firewall.rules | Single rule intended to trigger invalid inherited-scope validation. |
| tests/firewall/firewall-action-scope-inherited-policies-invalid/test.yaml | Expects failure + specific log message for invalid inherited scope into pass (policy case). |
| tests/firewall/firewall-action-scope-inherited-policies-invalid/suricata.yaml | Defines default-policy intended to trigger invalid inherited-scope validation. |
| tests/firewall/firewall-action-scope-inherited-policies-invalid/firewall.rules | Placeholder rules file (policy-only test). |
| tests/firewall/firewall-action-pass-requires-accept-valid/test.yaml | Verifies expected successful rule-load outcome for valid accept→pass usage. |
| tests/firewall/firewall-action-pass-requires-accept-valid/suricata.yaml | Engine-analysis + logging config for valid pass-requires-accept test. |
| tests/firewall/firewall-action-pass-requires-accept-valid/firewall.rules | Ruleset covering valid pass usage after accept and allowed alert usage. |
| tests/firewall/firewall-action-pass-requires-accept-rule-invalid/test.yaml | Expects failure + specific log message when pass follows a non-accept primary (rule case). |
| tests/firewall/firewall-action-pass-requires-accept-rule-invalid/suricata.yaml | Engine-analysis + logging config for invalid pass-requires-accept rule test. |
| tests/firewall/firewall-action-pass-requires-accept-rule-invalid/firewall.rules | Single rule intended to trigger invalid pass-requires-accept validation. |
| tests/firewall/firewall-action-pass-requires-accept-policies-invalid/test.yaml | Expects failure + specific log message when policy chain includes invalid pass placement. |
| tests/firewall/firewall-action-pass-requires-accept-policies-invalid/suricata.yaml | Defines policy chain intended to trigger invalid pass placement validation. |
| tests/firewall/firewall-action-pass-requires-accept-policies-invalid/firewall.rules | Minimal rules file for policy-only test. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This was referenced Aug 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up of #3323
Redmine ticket: https://redmine.openinfosecfoundation.org/issues/8954
Describe changes:
v2:
passkeyword (in)compatibility added