feat/intezer-azure-sentinel-integration-playbooks

[matany90]

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):

• New schema used for XYZ.yaml
• Resolves ISSUE Add Logstash required version to Readme file #1234

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:

• Guidance for Detection checks
• General contribution guidance
• PR validation troubleshooting

---

[v-prasadboke]

Hello @matany90, Thank you for raising this PR. This PR will be investigated and will update you about the same by 31 August, 2023.

[v-prasadboke]

Hello @matany90, Metadata is missing from playbook. Can you please add playbook metadata in the azuredeploy.json.

You can refer this Playbook for more clarification:- https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/ThreatXCloud/Playbooks/ThreatXPlaybooks/ThreatX-BlockIP-URL/azuredeploy.json

Also can you please share LogicApp designer images.
Thank you.

[v-prasadboke]

Hello @matany90, Hope you are doing well. We just wanted to know if there are any updates on the above requested changes.

[v-prasadboke]

Hello @matany90, Please respond to the above forementioned comments.
Thanks.

[v-prasadboke]

Hello, @matany90. We haven't heard from you in a while. I hope everything is okay with you, and please answer to the comments above.

[v-prasadboke]

Hello @matany90, Please respond to the above forementioned comments.

[v-prasadboke]

Hello @matany90, Please respond to the above mentioned comments.

[v-prasadboke]

Hello @matany90, Please respond to the above requests.

[v-prasadboke]

Hello @matany90, Please respond to the above comments

[v-prasadboke]

Hello @matany90, We are waiting for your response.

[v-prasadboke]

Hello @matany90, Please respond to the above comments. Also please agree to the required license.

[v-prasadboke]

Hello @matany90, We are waiting for your response.

[v-prasadboke]

We wanted to check on the status of PR #8890. PR is pending for more than 30 days. Please let us know if you need any assistance to review this PR. Per our standard operating procedures if no response is received in the next 7 business days, we will close this PR. Thank you for your cooperation.

[v-prasadboke]

Since we have not received a response in the last 7 days, we are closing your PR #8890 per our standard operating procedures. If you still need support for this issue, you can re-open the PR at any time.

If you do re-open, we simply request that you ensure the PR has response to the last request. Thank you for your cooperation.