|
You are here |
thinkdfir.com | ||
| | | | |
www.binaryspiral.com
|
|
| | | | | This evening I got an urgent email from a colleague that just got the rug pulled out from under him. His customer decided that the two web servers on the front end of a SharePoint farm he was build... | |
| | | | |
www.khyrenz.com
|
|
| | | | | Let me start by saying that, yes: many tools already exist to parse information out of the Windows Registry and/or the Event Log. However, while I was conducting my own tool validation processes (see https://github.com/khyrenz/tool_validation), I realised that very few tools parse this information out and automatically populate the kind of table that I would be adding into my forensic report.So... I did a bit of R&D, and I present to you a Python script that does just that; creatively named pars | |
| | | | |
pentestlab.blog
|
|
| | | | | 1 post published by Administrator on November 13, 2019 | |
| | | | |
www.morling.dev
|
|
| | | Recently I ran into a situation where it was necessary to capture the output of a Java process on the stdout stream, and at the same time a filtered subset of the output in a log file. The former, so that the output gets picked up by the Kubernetes logging infrastructure. The letter for further processing on our end: we were looking to detect when the JVM stops due to an OutOfMemoryError, passing on that information to some error classifier. | ||