Hi Avinash,
Can you possibly share an obfuscated screenshot and additional details to help clarify the problem and what you're expecting to see?
Also, are you stating that the username specified in an Alert differs from the username specified in the Audit data? If so, are you looking at the console, or are you reviewing data in a SIEM or other central logging solution? If not the MX console, you may want to review your Followed Action and Action Interface or Action Set regarding the event placeholders.
For what it's worth, I've always really liked the simplicity of Joel Spolsky's* 3 tenets of problem reporting (*of Stack Overflow and Trello fame at Glitch/Fog Creek Software)
Every good bug report needs exactly three things:
- Screenshot and/or Steps to reproduce,
- What you expected to see, and
- What you saw instead.
.
When you refer to "local access user" instead of username, the first thing that pops to mind for me is OS User Chaining or possibly SQL User Tracking.
Whatever the case, can you clarify a little bit further? Separately, you may want to open a support case, if you haven't already done so.
Looking forward to hearing back from you!
- JT
------------------------------
John Thompson
Director, Channel Presales
Imperva
San Diego CA
------------------------------
Original Message:
Sent: 03-14-2024 03:36
From: Avinash Krishna ADDALA
Subject: How do I Avoid Local User Access in profile with MSSQL
Hi All,
Greetings for the day!!
We have observed that in the alerts, we are only able to see the local access user instead of username. Can anyone guide us on how to avoid the local access user and capture the username form MS SQL DB.
#DatabaseActivityMonitoring
------------------------------
Avinash Krishna ADDALA
Security Expert
Societe Generale
PARIS
------------------------------