Skip to content

[Test]Add Bitdefender GravityZone parsers & samples#13655

Open
v-sabiraj wants to merge 5 commits intomasterfrom
v-sabiraj-gravityzonetestpr
Open

[Test]Add Bitdefender GravityZone parsers & samples#13655
v-sabiraj wants to merge 5 commits intomasterfrom
v-sabiraj-gravityzonetestpr

Conversation

@v-sabiraj
Copy link
Contributor

Add ASIM and VIM filtering parsers for Bitdefender GravityZone and include sample ingested logs. New parser files: Parsers/ASimAlertEvent/Parsers/ASimAlertEventBitdefenderGravityZone.yaml and Parsers/ASimAlertEvent/Parsers/vimAlertEventBitdefenderGravityZone.yaml implement normalization to the ASIM AlertEvent schema (mapping core fields and packing additional fields) for multiple GravityZone modules (new-incident, new-extended-incident, ransomware-mitigation, network-sandboxing, exchange-malware). Also add sample data: Sample Data/ASIM/Bitdefender_GravityZone_AlertEvent_IngestedLogs.csv. Updated existing manifests Parsers/ASimAlertEvent/Parsers/ASimAlertEvent.yaml and Parsers/ASimAlertEvent/Parsers/imAlertEvent.yaml to register the new parsers and bump versions/lastUpdated metadata.

Required items, please complete

Change(s):

  • See guidance below

Reason for Change(s):

  • See guidance below

Version Updated:

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

Testing Completed:

  • See guidance below

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:


Add ASIM and VIM filtering parsers for Bitdefender GravityZone and include sample ingested logs. New parser files: Parsers/ASimAlertEvent/Parsers/ASimAlertEventBitdefenderGravityZone.yaml and Parsers/ASimAlertEvent/Parsers/vimAlertEventBitdefenderGravityZone.yaml implement normalization to the ASIM AlertEvent schema (mapping core fields and packing additional fields) for multiple GravityZone modules (new-incident, new-extended-incident, ransomware-mitigation, network-sandboxing, exchange-malware). Also add sample data: Sample Data/ASIM/Bitdefender_GravityZone_AlertEvent_IngestedLogs.csv. Updated existing manifests Parsers/ASimAlertEvent/Parsers/ASimAlertEvent.yaml and Parsers/ASimAlertEvent/Parsers/imAlertEvent.yaml to register the new parsers and bump versions/lastUpdated metadata.
@v-sabiraj v-sabiraj requested review from a team as code owners February 19, 2026 11:08
@v-sabiraj v-sabiraj changed the title Add Bitdefender GravityZone parsers & samples [Test]Add Bitdefender GravityZone parsers & samples Feb 19, 2026
@contentautomationbot
Copy link

ASIM parsers have been changed. ARM templates were regenerated from the updated KQL function YAML files.
To find the new ARM templates, pull your branch.

@v-atulyadav v-atulyadav self-assigned this Feb 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments