Closed amitschendel closed 7 months ago
PR Description updated to latest commit (https://github.com/kubescape/node-agent/commit/874ec0da5d11193a71316a338431a3748e510d36)
⏱️ Estimated effort to review [1-5] | 2, because the changes are localized to a specific part of the code and involve a straightforward addition of a new field to an existing data structure. The logic and flow of the code remain largely unchanged, making it easier to review. |
🧪 Relevant tests | No |
🔍 Possible issues | Possible Bug: The addition of `InfectedPID` assumes that `domainEvent.Pid` is always valid and non-null. If `domainEvent.Pid` can be null or invalid under certain conditions, this could lead to runtime errors or incorrect data being logged. |
🔒 Security concerns | No |
Category | Suggestions |
Best practice |
Add validation for the
___
**Consider checking if |
Summary:
Summary:
User description
Overview
Type
bug_fix
Description
InfectedPID
field to theBaseRuntimeAlert
struct within the rule failure logic to capture and display the process ID (Pid
) that triggered the rule. This helps in identifying the specific process involved in the unexpected domain request, enhancing debugging and monitoring capabilities.Changes walkthrough
r0005_unexpected_domain_request.go
Include Infected PID in Rule Failure Alert
pkg/ruleengine/v1/r0005_unexpected_domain_request.go
InfectedPID
field toBaseRuntimeAlert
struct in rule failure toinclude the process ID.