Explore >> Select a destination
|
You are here 
|
www.geekrant.org | ||
| | | | |
thinkdfir.com
|
|
| | | | | In preparation for an upcoming FOR500 class I thought I would test out one of the recent additions to the class. This post by my colleague Zach shows that Win10 1903 and later has a registry key that will store the full path of any executable that utilises the computers camera or microphone. Zach shows... | |
| | | | |
www.micah.soy
|
|
| | | | | After today's encounter with Mobsync and COM+, I am left scratching my head and looking about in disarray. This doesn't happen often, but I am sure glad when it does because it beats sitting in a lecture hall 'attempting' to learn about the intricacies of Windows communication subsystems. | |
| | | | |
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 | |
| | | | |
www.iseatz.com
|
|
| | | How initiatives like the Open Web Application Security Project empower developers with tools to mitigate risks and fortify defenses. | ||
