[INTS-676] DDS: BlueCat Integrity v1.0.0#22980
[INTS-676] DDS: BlueCat Integrity v1.0.0#22980jaypatel7-crest wants to merge 8 commits intoDataDog:masterfrom
Conversation
| preserveSource: true | ||
| overrideOnConflict: true | ||
| type: schema-remapper | ||
| - name: ocsf.activity_id |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5885a54e15
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| query: "@message_direction_value:BOOTREQUEST" | ||
| name: Outbound | ||
| id: 2 |
There was a problem hiding this comment.
Map DHCP BOOTREQUEST as inbound direction
data.dhcpv4Message.op=1 means a BOOTREQUEST (client → server), but this category currently assigns ocsf.connection_info.direction=Outbound. In this same pipeline, serverId is mapped to ocsf.dst_endpoint.name, so this inversion makes request packets look like server-originated traffic and reply packets look inbound, which will skew DHCP flow analysis and any direction-based detections.
Useful? React with 👍 / 👎.
|
This PR does not modify any files shipped with the agent. To help streamline the release process, please consider adding the |
|
hey @jaypatel7-crest thanks for the PR! is this ready for the docs team to review? just double-checking because |
|
Created an Editorial Review card: DOCS-13839 |
What does this PR do?
This is a initial release PR of BlueCat Integrity integration including all the required assets i.e. Pipeline, Dashboards
Motivation
ddsourcequery parameter set tobluecat-integrity.Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged