Closed MikeBakerSAV closed 10 months ago
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.
Hi @MikeBakerSAV, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 12-12-2023. Thanks!
Hi @MikeBakerSAV, we are working on modification, meanwhile could you please follow the below steps and check is modified function is working for you.
go to LAW and search for CrowdstrikeFalconEventStream
in functions -
Click on Load function code-
then click on save as a function and save the function with name - CrowdStrikeFalconEventStream
Once function is saved, check your sentinel connection for which you are facing issue. Thanks!
Hi @MikeBakerSAV, We are waiting for your response on above comment. Thanks!
Hi @MikeBakerSAV, Gentle Reminder: We are waiting for your response on this issue. If you still need to keep this issue active, please respond to it in the next 2 days. If we don't receive a response by 20-12-2023 date, we will be closing this issue.
Thanks!
this seems to have resolved the problems for the workbook - we will check the other advanced modules for CS enrichment and see if there are other issues.
Hi @MikeBakerSAV, sure. Please check and let us know. Thanks!
Hi @MikeBakerSAV, I hope you are doing well. just want to check have you check on your advance environment? Thanks!
this appears to be working through our smoketests. i think you can close issue
Hi @MikeBakerSAV, thank you for your confirmation. Closing this issue. If you still need support for this issue, feel free to re-open it any time. Thank you for your co-operation.
Describe the bug Sentinel connections and workbooks for crowdstrike do not work due to incoherent use of Case when referencing "CrowdstrikeFalconEventStream" or "CrowdStrikeFalconEventStream" - note issue with "strike v Strike"
previously reported in #8028
To Reproduce Steps to reproduce the behavior: Function (lower case s)- https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/CrowdStrike%20Falcon%20Endpoint%20Protection/Parsers/CrowdstrikeFalconEventStream.yaml
https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/CrowdStrike%20Falcon%20Endpoint%20Protection/Workbooks/CrowdStrikeFalconEndpointProtection.json line 120
Expected behavior use of correct and consistent CASE