Skip to content

[AWS] Add mappings for runtimeDetails field in GuardDuty events #11392

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

Merged

Conversation

chemamartinez
Copy link
Contributor

@chemamartinez chemamartinez commented Oct 10, 2024

Proposed commit message

As reported in an SDH, the content of the field service.runtimeDetails was not being parsed and mapped for GuardDuty events. That field contains critical information about the event so it is important to process it properly.

The schema of the runtimeDetails field can be found here.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

@chemamartinez chemamartinez added enhancement New feature or request Integration:aws AWS Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] labels Oct 10, 2024
@chemamartinez chemamartinez self-assigned this Oct 10, 2024
@elastic-vault-github-plugin-prod
Copy link

elastic-vault-github-plugin-prod bot commented Oct 10, 2024

🚀 Benchmarks report

Package aws 👍(7) 💚(10) 💔(2)

Expand to view
Data stream Previous EPS New EPS Diff (%) Result
route53_resolver_logs 6493.51 4672.9 -1820.61 (-28.04%) 💔
cloudtrail 1650.17 1283.7 -366.47 (-22.21%) 💔

To see the full report comment with /test benchmark fullreport

@chemamartinez chemamartinez force-pushed the aws-guardduty-runtimeDetails-mapping branch from fb55d15 to f5f66c7 Compare October 15, 2024 15:08
@chemamartinez chemamartinez marked this pull request as ready for review October 15, 2024 15:09
@chemamartinez chemamartinez requested review from a team as code owners October 15, 2024 15:09
@elasticmachine
Copy link

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

@chemamartinez chemamartinez force-pushed the aws-guardduty-runtimeDetails-mapping branch from f5f66c7 to 915c1df Compare October 16, 2024 16:42
@chemamartinez chemamartinez requested a review from efd6 October 17, 2024 08:40
@elasticmachine
Copy link

💚 Build Succeeded

History

cc @chemamartinez

Copy link

Copy link
Contributor

@muthu-mps muthu-mps left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

code owner approval.

@chemamartinez chemamartinez merged commit 32127b8 into elastic:main Oct 18, 2024
5 checks passed
@elastic-vault-github-plugin-prod

Package aws - 2.29.0 containing this change is available at https://epr.elastic.co/search?package=aws

harnish-crest-data pushed a commit to chavdaharnish/integrations that referenced this pull request Feb 4, 2025
…tic#11392)

Add mappings for runtimeDetails field in GuardDuty events
harnish-crest-data pushed a commit to chavdaharnish/integrations that referenced this pull request Feb 5, 2025
…tic#11392)

Add mappings for runtimeDetails field in GuardDuty events
@chemamartinez chemamartinez deleted the aws-guardduty-runtimeDetails-mapping branch February 6, 2025 10:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Integration:aws AWS Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants