Link to home
Start Free TrialLog in
Avatar of compdigit44
compdigit44

asked on

McAfee SIEM Event Collector 11.0 and Windows 2008 R2 Domain Controller

Has anyone found a way to use the Mcafee SIEM Collector work on a Domain Controller and tail the DNS.log file without making it a Domain Admin. I have been working on this for days trying to figure out what files, folders and registry keys it needs but not luck..

I keep getting the same message: "Failed to start impersonation: 1326" but with the same config works fine under my domain admin account.
Avatar of Busbar
Busbar
Flag of Egypt image

It didn't work with us and we created domain admin account
Avatar of compdigit44
compdigit44

ASKER

This seems SO WRONG TO ME from a security point of view
Avatar of Mohammed Khawaja
Same here when I tested.   It is kind of funny that a security software requirements goes against most security recommendations.
Here are my thoughts..

1) Create a domain admin account but only grant it the ability to log into one or two DC's running DNS. yes this account can still access AD from the servers both at least it is not as wide open.

2) From my testing the application does not linke UNC paths or network drives. I was trying to see if I could install the softwrae on anther server and map to the DC folder to read the log file...Even tried a linked directory..  and it did not work...

It has to be something with the registry but do not want to  change anything on a DC.

So the trick is to create a mount point that is really a \\unc path which I know you cannot do BUT wondering if you could trick windows to think the network drive is local

http://superuser.com/questions/812433/can-i-make-a-mapped-network-share-appear-as-a-local-drive
ASKER CERTIFIED SOLUTION
Avatar of compdigit44
compdigit44

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Found solution and posted finding for others.