-   Notifications  
You must be signed in to change notification settings  - Fork 509
 
[M365 Defender][Microsoft Defender Endpoint] Add support of vulnerability data-stream #13595
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
[M365 Defender][Microsoft Defender Endpoint] Add support of vulnerability data-stream #13595
Conversation
|   Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)  |  
|   /test  |  
| The [Microsoft 365 Defender](https://learn.microsoft.com/en-us/microsoft-365/security/defender) integration allows you to monitor Alert, Incident (Microsoft Graph Security API), Event (Streaming API) Logs, and Vulnerability (Microsoft Defender for Endpoint API) Logs. Microsoft 365 Defender is a unified pre and post-breach enterprise defense suite that natively coordinates detection, prevention, investigation, and response across endpoints, identities, email, and applications to provide integrated protection against sophisticated attacks. | ||
|   |  ||
| Use the Microsoft 365 Defender integration to collect and parse data from the Microsoft Azure Event Hub, and the Microsoft Graph Security v1.0 REST API. Then visualise that data in Kibana. | ||
| Use the Microsoft 365 Defender integration to collect and parse data from the Microsoft Azure Event Hub, Microsoft Graph Security v1.0 REST API, and the Micrsoft Defender Endpoint API. Then visualise that data in Kibana. | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is already a Microsoft Defender for Endpoint integration. I think this data_stream should be added there since we are using Micrsoft Defender Endpoint API to retrieve the vulnerabilities.
@jamiehynds / @cpascale43 please kindly clarify which integration does this datastream need to go into?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That makes logical sense to me @kcreddy, we can go ahead and add this to Defender for Endpoint
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sharadcrest, can you please change the integration?
 cc: @piyush-elastic
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be possible to have the vuln data added to both the M365D and Defender for Endpoint integration? Reason being, the vulnerability data is exposed in both the M365D UI, as well as Defender for Endpoint customers running standalone, i.e. without M365D. If we add it to both integrations, we at least cover all bases, although I'd expect the M365D integration to be the more popular route.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, will replicate same in Defender for Endpoint integration  also.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sharadcrest can you please fix the CI error?
|   It looks like something has gone terribly wrong with this PR. Why are so many files involved? This has happened due to the back merge of main into this branch, but something went wrong.  |  
|   /test  |  
   packages/microsoft_defender_endpoint/data_stream/vulnerability/manifest.yml  Outdated   Show resolved Hide resolved  
    packages/microsoft_defender_endpoint/data_stream/vulnerability/manifest.yml  Outdated   Show resolved Hide resolved  
    packages/microsoft_defender_endpoint/data_stream/vulnerability/manifest.yml  Outdated   Show resolved Hide resolved  
    ...5_defender/data_stream/vulnerability/_dev/test/pipeline/test-vulnerability.log-expected.json  Show resolved Hide resolved  
    ...5_defender/data_stream/vulnerability/_dev/test/pipeline/test-vulnerability.log-expected.json  Outdated   Show resolved Hide resolved  
 |   /test  |  
|   /test  |  
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only pending comment: #13595 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sharadcrest can you update this PR by removing vulnerability.package fields, but populating package fields at root instead?
 Please refer to latest Tenable IO PR: #13636
 CDR guide is/will be updated accordingly.
cc: @maxcold
|   /test  |  
   |  
 💚 Build Succeeded
 History
  |  
|   Package m365_defender - 3.8.0 containing this change is available at https://epr.elastic.co/package/m365_defender/3.8.0/  |  
|   Package microsoft_defender_endpoint - 2.38.0 containing this change is available at https://epr.elastic.co/package/microsoft_defender_endpoint/2.38.0/  |  
…lity data-stream (elastic#13595) This release introduces the vulnerability data stream, along with its associated dashboard and visualizations. Vulnerability fields are mapped to their corresponding ECS fields where possible. Test samples were derived from live data samples, which were subsequently sanitized.




Proposed commit message
This release introduces the vulnerability data stream,
along with its associated dashboard and visualizations.
Vulnerability fields are mapped to their corresponding ECS fields where possible.
Test samples were derived from live data samples, which were subsequently
sanitized.
Checklist
changelog.ymlfile.How to test this PR locally
To test the m365_defender package:
To test the microsoft_defender_endpoint package:
Related Issues
Screenshots