Earning the Microsoft 365 Threat Protection CCP Badge

I am super honored to say that I am now officially part of the Microsoft 365 Threat Protection Customer Connection Program as a Community Member!

You can view the official badge & details here -> https://www.credly.com/badges/b6a58efe-386f-43c6-a056-2e1defbf45a6/public_url

I have been extremely fortunate to be able to help drive many of Microsoft’s security tools and roadmaps. For those members that are part of the M365 Threat Protection CCP group. They get a chance to contribute heavily to provide feedback on Microsoft Security products. In the end, it helps enhance the security roadmap that Microsoft plans out. Some of the technologies we get to help drive forward and further enhance are listed below.

For example:

Autopsy– A Forensic Analysis Tool

Autopsy – Digital Forensics

For anyone looking to conduct some in depth forensics on any type of disk image. Autopsy is a great free tool that you can make use of for deep forensic analysis.

It has been a few years since I last used Autopsy. I recall back on one of the SANS tools (SANS SIFT). Back then I felt it was a great tool, but did lack speed in terms of searching through data. It appears with the most recent version of Autopsy that issue has been drastically improved. On top of that, machines have also become much faster using SSD’s and tons of more CPU and RAM power.

Azure – Security Best Practices

Azure Security Best Practices – Part 1

Hello and welcome again!

This time around, I’ve decided to make this blog post as a Part 1 of many several parts that will be released. There is just too much Azure security information to put up in a single post. So, my plan is to make multiple posts over time.

Azure has many great security features that not everyone may be aware of right from the start. This post will focus on some key areas of Azure, and how it can better enhance the security of the environment. Key focus will investigate security best practices for Azure.

Recover Keys – Part 2 – Scanning Devices on the Network

In this Part 2 review of Recover Keys, we will look at how we can scan machines via the network. For most users, I don’t believe this option will be used too often. The average home user that purchase a license for personal use could just uninstall and install the tool on each machine they want to grab license keys off of, or buy a license for multiple machines.

For larger organizations this tool is excellent as it can be installed in one location on a single machine. You also get the ability of being able to extract the license keys via the network, which makes this tool much more efficient and valuable. At the end of the day it is all about saving and making the best use of time.

If you haven’t read Part 1 of using Recover Keys (scanning a local machines) you can check it out here: https://www.stealthbay.com/recover-keys-part-1-scanning-a-local-machine/

Recover Keys – Part 1 – Scanning a Local Machine

Recovering License Keys

I ran into an issue when trying to upgrade a windows 7 PC back in 2019 before Windows 7 went EOL. A decision was made to start a complete fresh install of Windows 10 instead of upgrading from Windows 7 to 10.

However, it came with a caveat that I would have to reinstall many tools all over again. For some of them, I no longer had a stored copy of the license key(s) laying around, or stored digitally any longer. So it got me thinking, if there was a way to recover these license keys.

Now, I could poke around and find the answers combing through the Registry or disk. However, I thought I’d speed things up by using existing tools that get the job done for you.

Nirsoft (a well-known website for recovering all kinds of artifacts from your PC) used to have a free tool that would search the registry for license keys. The tool was called “ProduKey”, and can be found here:https://www.nirsoft.net/utils/product_cd_key_viewer.html

But, upon trying to download the file, it gets redirected to another website called “recover keys” https://recover-keys.com/en/aboutus.html