Imperva Cyber Community

communities_1.jpg
 View Only

  • 1.  Imperva DAM Capturing Generic Account Instead of Staff Account for DB Query

    Posted 30 days ago

    A user logs in with their staff profile to execute a DB query (attached), but Imperva DAM captures a generic account instead of the staff account as the user performing the action. Has anyone encountered this issue, and how was it resolved?


    #DataRiskAnalytics(formerlyCounterBreach)
    #DatabaseActivityMonitoring

    ------------------------------
    Joy Ampitan
    Security Engineer
    Ethnos Cyber Limited
    Lagos
    ------------------------------


  • 2.  RE: Imperva DAM Capturing Generic Account Instead of Staff Account for DB Query

    Posted 30 days ago

    I think, the attachment is forgotten. Can you share audit details screenshot?



    ------------------------------
    Cezmi Cal
    Consultant
    Barikat Internet Guvenligi Bilisim Ticaret A.S.
    Ankara
    ------------------------------

    Original Message


  • 3.  RE: Imperva DAM Capturing Generic Account Instead of Staff Account for DB Query

    Posted 28 days ago

    Hi Joy,

    Could you please arrange to provide complete details (like both Source IP and Destination IP with middle octets in masked format, OS UserName, Source Application, Source of Activity, DB User)?

    Is there any filtered (in the form of Match Criteria) applied to the databases? Did you configure any Agent Monitoring Rule also?

    Long back, we observed similar behaviour but because of configurations given in the KB article (https://docs.imperva.com/bundle/z-kb-articles-knowledgebase-support/page/290722706.html) which impacted other operations as well apart from RMAN activity.

    Regards,



    ------------------------------
    SBISOC 4430
    Manager
    Mumbai
    ------------------------------

    Original Message