Restore SecDefaultAction inheritance for rules without explicit disruptive action

[Easton97-Jens]

Motivation

• A recent change gated SecDefaultAction disruptive execution on a containsBlock flag which caused matching rules that do not define their own disruptive action to become detection-only; this patch restores the expected behavior so default disruptive actions still apply unless the rule explicitly provides its own disruptive action.

Description

• Modify RuleWithActions::executeAction in src/rule_with_actions.cc to skip default disruptive actions only when the rule already has an explicit disruptive action (m_disruptiveAction != nullptr and its name is not "block"), and update the debug message to reflect this condition.

Testing

• Attempted to run the regression harness (test/regression_tests) but the test binary is not present in this environment, so no automated regression tests were executed here.

---

Codex Task

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud