Getting Data In

How to monitor Microsoft CA logs on Server 2008 R2?

jodros
Builder

Has anyone been successful in monitoring Microsoft CA logs on Server 2008 R2? It looks as if they are being written to C:\Windows\System32\CertLog in EDB log format, which is not human readable. I want to say the EDB log format might also be used by Microsoft Exchange, so I don't know if any TA or SA for exchange could be leveraged.

Any assistance with this issue would be appreciated.

Thanks

Tags (2)
0 Karma
1 Solution

jodros
Builder

Figured out the issue. There was an additional auditing setting that needed to be tweaked in the GPO before the CA events started showing up in the WinEventLog:Security. No need to try and figure out a way to monitor the edb files.

View solution in original post

0 Karma

jodros
Builder

Figured out the issue. There was an additional auditing setting that needed to be tweaked in the GPO before the CA events started showing up in the WinEventLog:Security. No need to try and figure out a way to monitor the edb files.

0 Karma

thambisetty
SplunkTrust
SplunkTrust

would be helpful, if you could provide how did you fix this.

————————————
If this helps, give a like below.

nabeel652
Builder

Do you remember what change did you make in GPO in order to collect CerLog like EventCode=64 etc?

jlemoine
Path Finder

What was the solution?

0 Karma

jodros
Builder

early morning bump. No one is monitoring any Microsoft CA servers running on 2008 R2 with Splunk?

0 Karma
Get Updates on the Splunk Community!

Splunk at Cisco Live 2025: Learning, Innovation, and a Little Bit of Mr. Brightside

Pack your bags (and maybe your dancing shoes)—Cisco Live is heading to San Diego, June 8–12, 2025, and Splunk ...

Splunk App Dev Community Updates – What’s New and What’s Next

Welcome to your go-to roundup of everything happening in the Splunk App Dev Community! Whether you're building ...

The Latest Cisco Integrations With Splunk Platform!

Join us for an exciting tech talk where we’ll explore the latest integrations in Cisco + Splunk! We’ve ...