[m365_defender] Fix event.category for the AdvancedHunting-AlertInfo events

[brijesh-elastic]

Proposed commit message

Remove the threat value from event.category for AdvancedHunting-AlertInfo events because we are not populating any threat.* ECS fields.
See schema documentation.

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

How to test this PR locally

• Clone integrations repo.
• Install elastic package locally.
• Start elastic stack using elastic-package.
• Move to integrations/packages/m365_defender directory.
• Run the following command to run tests.

elastic-package test

Related issues

• Closes [M365 Defender] Change event.type of AlertInfo #10109

[elasticmachine]

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

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 660d514

History

• 💚 Build #23614 succeeded 7d54571
• 💔 Build #23613 failed 59b359c

cc @brijesh-elastic

[elastic-vault-github-plugin-prod]

Package m365_defender - 3.0.1 containing this change is available at https://epr.elastic.co/package/m365_defender/3.0.1/