Postpwned Ramblings

I just renewed this domain and I realized something - it's been a year since I first started this blog and we are already closing up the first month of 2018 and I don't have much to show for. I haven't put much out here honestly, I have plenty of code snippets and ideas for content, but life has gotten in the way. My original idea was to make this a security centric blog where I would document my studies and write about what I was learning to not only help me better understand the content, but to help anyone else who is interested. I think I would like to continue with the original idea, but also write about my non-security related wins and code snippets. I've recently taken on the role of a Citrix engineer in addition to my other tasks. I'm still pretty new, but I have spotted a few areas for automation and scripting that I would like to explore. So here's to 2018, may I finally get around to writing more often!

I created a PowerShell script to vaccinate systems from Bad Rabbit based on the findings of Amit Serper. I will be turning this into a Compliance Item in SCCM in order to get this to the systems in the company. Using Compliance Items will help us keep track of this and will attempt to rerun this script in the event that permissions ever get changed. It'll also allow for nice reporting for management. Edit: There's a much better way to do this: Using this method, it's much easier just to add a filename and it's relative path to the $files variable. This change makes the script much more scalable and dynamic. Edit 2: It looks like someone much better than me already beat me to this. Anders Rodland has created a Configuration Item and Remediation script nearly identical to mine and a few days before me. Jay Rosenberg from Intezer Labs has written more about Bad Rabbit and its relationship with NotPetya - the article can be read here.

In preparation for migrating our workstations over to Microsoft BitLocker Administration Management (MBAM), I wanted to backup the recovery keys for my team's systems since we're testing and implementing it. In order to do this, I needed to write something that would pull in every computer in an OU in AD, then grab the msFVE-RecoveryInformation class for each object. I know, I know... there's better ways to create the PSObject. I've been mired in writing in PowerShell 2.0 to support the Windows XP systems here at the company. I know, I know... yes, we still have Windows XP. Yes, there are plans on moving to a supported OS. No, I don't know when that will be.

Hello and welcome to my blog. My name is Alex and I will attempt an introduction. I am happily married with three kids. I enjoy the outdoors during the warmer months, either camping in my hammock or out Jeeping with the top off (the Jeep's, not mine... usually). The cooler months mean beer league hockey with the boys. I have been involved with IT since the late 90's. I started my career like most people, doing the occasional odd job fixing a neighbor's computer while learning as much as I could. If I wasn't breaking something, I wasn't learning. Throughout my professional career, I've moved from technician, to supervisor, back to technician before finally becoming an engineer at a larger privately owned company in the United States. During my tenure with my company, I have been given some great opportunities to travel the world. I've spent time across North America, South America, and Europe - I am very grateful for those experiences. I've been ...