Monitoring with PowerShell: External port scanning part 2

So recurring readers will be reading this title and go “Wait a minute, he already blogged about this” and you’d be right. With the recent Github Sponsorship taking off, I’ve decided to release some more public tools so life can be made easier for other MSPs. In the previous blog I’ve told you to create and upload a port scan file yourself to a web host, some people found it challenging because a lot of hosts block unknown outbound ports.

This is why I’m introducing the Public CyberDrain Remote Port Scan API. I’ll be the first to admit the name could use some work ;). This tool allows you to initiate a remote port scan from anywhere. The tool will only scan the external IP from where the script is launched to prevent abuse.

If you’re worried about privacy, want more granular control, or just prefer to roll your own you can see the code for the port scan tool here and host it yourself instead. 🙂

To start a remote port scan, you can execute the following code.

$Results = invoke-restmethod -uri "https://azportscan.azurewebsites.net/api/PortScanner"
$OpenPorts = $Results | Where-Object { $_.status -eq "open"}
$ClosedPorts = $Results | Where-Object { $_.status -eq "closed"}

if(!$OpenPorts) {
$PortScanResult = "Healthy"
} else {
$PortScanResult = $OpenPorts
}

By default the port scan only scans a specific subset of ports namely 21,25,8080,33890,1234,1111,2222,3333,3389,3389,4444,5555,6666,7777,8888,9999,1234, you can add ports to this list by appending the request with your ports as such:

$Results = invoke-restmethod -uri "https://azportscan.azurewebsites.net/api/PortScanner?ports=1234,8080,3389,3333"
$OpenPorts = $Results | Where-Object { $_.status -eq "open"}
$ClosedPorts = $Results | Where-Object { $_.status -eq "closed"}

if(!$OpenPorts) {
$PortScanResult = "Healthy"
} else {
$PortScanResult = $OpenPorts
}

As I explained in the older blog; having a remote port scan tool that runs with your RMM is super useful to detect the current state of what you’ve exposed at your edge. It can also help you capture tiny mistakes your engineers have made, or detect places where you might need to reconsider how you access resources.

And that’s it! as always, Happy PowerShelling.

PS: I’ve started a new short youtube series about technologies you could use in your MSP. Check out the blog about that here.

Recent Articles

The return of CyberDrain CTF

CyberDrain CTF returns! (and so do I!)

It’s been since september that I actually picked up a digital pen equivalent and wrote anything down. This was due to me being busy with life but also my side projects like CIPP. I’m trying to get back into the game of scripting and blogging about these scripts. There’s still so much to automate and so little time, right? ;)

Monitoring with PowerShell: Monitoring Acronis Backups

Intro

This is a monitoring script requested via Reddit, One of the reddit r/msp users wondered how they can monitor Acronis a little bit easier. I jumped on this because it happened pretty much at the same time that I was asked to speak at the Acronis CyberSummit so it kinda made sense to script this so I have something to demonstrate at my session there.

Monitoring with PowerShell: Monitoring VSS Snapshots

Intro

Wow! It’s been a while since I’ve blogged. I’ve just been so swamped with CIPP that I’ve just let the blogging go entirely. It’s a shame because I think out of all my hobbies it’s one I enjoy the most. It’s always nice helping others achieve their scripting target. I even got a couple of LinkedIn questions asking if I was done with blogging but I’m not. Writing always gives me some more piece of mind so I’ll try to catch up again. I know I’ve said that before but this time I’ll follow through. I’m sitting down right now and scheduling the release of 5 blogs in one go. No more whining and no more waiting.