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

CiscoSEG solution's analytics rules refer to a column that does not exist in the function (parser) #11400

Closed
pixel559 opened this issue Nov 8, 2024 · 2 comments · Fixed by #11513
Assignees
Labels
Parser Parser specialty review needed Solution Solution specialty review needed

Comments

@pixel559
Copy link

pixel559 commented Nov 8, 2024

Hello Team,
There is a problem with the Cisco SEG solution's analytic rules (all of those).
https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/CiscoSEG

The analytics rules are referencing a function. Picking 'CiscoSEGDLPViolation.yaml' for example. Missing column 'AdditionalFields'.
https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/CiscoSEG/Analytic%20Rules/CiscoSEGDLPViolation.yaml

CiscoSEGEvent
| where NetworkDirection =~ 'Outgoing'
| where tostring(AdditionalFields) has 'ESADLPVerdict' //<-------- there is no 'AdditionalFields' defined in the function_
| extend dlp_verdict = extract(@'ESADLPVerdict":"(NOT_EVALUATED|NO TRIGGER|VIOLATION|NO VIOLATION)"', 1, tostring(AdditionalFields))
| where dlp_verdict =~ 'VIOLATION'
| extend AccountCustomEntity = SrcUserName

Looks like the function (parser) needs to be updated or the analytics rules need an update.
Function:
https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/CiscoSEG/Parsers/CiscoSEGEvent.yaml

Please update the function/analytics rules.

Thank you!

@v-rusraut v-rusraut added the Parser Parser specialty review needed label Nov 11, 2024
@v-rusraut
Copy link
Contributor

Hi @pixel559 , Thanks for flagging this issue, we will investigate this issue and get back to you with some updates. Thanks!

@v-sudkharat v-sudkharat added Solution Solution specialty review needed and removed Parser Parser specialty review needed labels Nov 11, 2024
@v-visodadasi v-visodadasi self-assigned this Dec 2, 2024
@v-visodadasi v-visodadasi linked a pull request Dec 2, 2024 that will close this issue
@v-visodadasi v-visodadasi added the Parser Parser specialty review needed label Dec 2, 2024
@v-visodadasi
Copy link
Contributor

@pixel559, We have made the changes in Parser, so could you please custom deploy the below shared Main Temple into your workspace and let us know if your issue resolves :

The custom deployment steps are mentioned into below file :
Custom Deployment - CustomDeploymentSteps.docx

Main Template file - mainTemplate.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Parser Parser specialty review needed Solution Solution specialty review needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants