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

Update EventsToTableMapping.json #11293

Merged
merged 2 commits into from
Oct 22, 2024
Merged

Conversation

v-sabiraj
Copy link
Contributor

@v-sabiraj v-sabiraj commented Oct 17, 2024

Required items, please complete

Change(s):

  • See guidance below

Reason for Change(s):

  • mapping was incorrect and events were ingested in Additional_events_Logs_CL

Version Updated:

  • Required only for Detections/Analytic Rule templates
  • See guidance below

Testing Completed:

  • yes

Checked that the validations are passing and have addressed any issues that are present:

  • See guidance below

Guidance <- remove section before submitting


Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:

Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR. Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process. Providing associated Issues that this resolves also easily connects the reason.

Change(s):

  • Updated syntax for XYZ.yaml

Reason for Change(s):

Version updated:

  • Yes
  • Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly. If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

  • Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

  • Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:


@v-sabiraj v-sabiraj requested review from a team as code owners October 17, 2024 13:15
@v-atulyadav v-atulyadav added Connector Connector specialty review needed Solution Solution specialty review needed labels Oct 17, 2024
anki-narravula
anki-narravula previously approved these changes Oct 18, 2024
@anki-narravula anki-narravula dismissed their stale review October 18, 2024 03:42

Please check if are referring this file every time we run the function and also I think this should go inside zip file for the customers who do offline deployment

Copy link
Contributor

@anki-narravula anki-narravula left a comment

Choose a reason for hiding this comment

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

Please check if are referring this file every time we run the function and also, I think this should go inside zip file for the customers who do offline deployment

@v-sabiraj
Copy link
Contributor Author

Please check if are referring this file every time we run the function and also, I think this should go inside zip file for the customers who do offline deployment

Hi @anki-narravula , I have update the file from zip.
I think yes, this check is defined in customize_event and we are checking this while processing after the file is downloaded and unzipped.

image

@v-atulyadav v-atulyadav merged commit ca6f45b into master Oct 22, 2024
32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Connector Connector specialty review needed Content-Package Solution Solution specialty review needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants