Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Infoblox BloxOne DDI] DNS Data Records Not Populating ECS Fields #9039

Closed
MakoWish opened this issue Feb 1, 2024 · 3 comments · Fixed by #9062
Closed

[Infoblox BloxOne DDI] DNS Data Records Not Populating ECS Fields #9039

MakoWish opened this issue Feb 1, 2024 · 3 comments · Fixed by #9062
Assignees
Labels
Crest Integration:infoblox_bloxone_ddi Infoblox BloxOne DDI (DNS, DHCP, IP management) Team:Security-Service Integrations Security Service Integrations Team

Comments

@MakoWish
Copy link
Contributor

MakoWish commented Feb 1, 2024

We recently started leveraging the Infoblox BloxOne DDI integration, and I am noticing on the DNS Data events, there is absolutely no population of the ECS DNS fields. Why is that?

@jamiehynds jamiehynds added the Team:Security-Service Integrations Security Service Integrations Team label Feb 2, 2024
@elasticmachine
Copy link

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@jamiehynds jamiehynds added Integration:infoblox_bloxone_ddi Infoblox BloxOne DDI (DNS, DHCP, IP management) Crest labels Feb 2, 2024
@jamiehynds
Copy link

Hey @MakoWish, based the fields within our sample data , you're absolutely right, there is no population of the ECS DNS fields (except for dns.answers.ttl). This is generally down to the absence of suitable ECS fields to map to. Based on the DNS Data you have, are there any fields currently mapped to infoblox. but could be mapped to an ECS DNS field?

@MakoWish
Copy link
Contributor Author

MakoWish commented Feb 2, 2024

Hi Jamie,

We just recently started using Infloblox (I absolutely hate it), but just a quick look without scouring all the logs, I can see at least these:

infoblox_bloxone_ddi.dns_data.type --> dns.question.type
infoblox_bloxone_ddi.dns_data.type --> dns.answers.type
infoblox_bloxone_ddi.dns_data.absolute.name.spec --> dns.question.name
infoblox_bloxone_ddi.dns_data.absolute.zone.name --> dns.question.registered_domain
infoblox_bloxone_ddi.dns_data.name_in.zone --> dns.question.subdomain
infoblox_bloxone_ddi.dns_data.rdata_value --> dns.answers

Also, not sure if it is just in our environment, but these appear to be duplicates in 100% of the cases I can see:

infoblox_bloxone_ddi.dns_data.absolute_name.spec == infoblox_bloxone_ddi.dns_data.absolute.name.spec
infoblox_bloxone_ddi.dns_data.absolute_zone.name == infoblox_bloxone_ddi.dns_data.absolute.zone.name

If the question or answer is a hostname, I think those should also be appended to related.hosts, but that is also not happening.

Eric

@efd6 efd6 self-assigned this Feb 6, 2024
@efd6 efd6 closed this as completed in #9062 Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Crest Integration:infoblox_bloxone_ddi Infoblox BloxOne DDI (DNS, DHCP, IP management) Team:Security-Service Integrations Security Service Integrations Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants