One of my favorite programs for the Mac is from a company called Objective Development -- Little Snitch -- and it's a host-based firewall that alerts you anytime something on your computer tries to reach the Internet for the first time (or you can set to always ask all the time, which I wouldn't recommend just because of the alert volume). I personally like to know what programs and apps are doing and with whom they are communicating, and this app is a useful if imperfect way of doing that.

The most jarring aspect of Little Snitch is how some programs suddenly phone home but you have no idea what's going on because the requested IP is some shared Amazon cloud server or something. Even after spending a few minutes digging on the IP, you probably still won't find a hostname and you're no closer to gauging whether you should allow the connection or not. But most of the time the program is silent, operating the background to block or allow various connections that you have specified previously.

Anyway, what I wanted to share that's neat about Little Snitch is when you install an app that you've had on your phone or iPad onto your Mac, suddenly you have a much better idea of where (if not who) your apps are communicating with, and maybe even a little more info about what these apps are actually doing in the background.

reshared this

in reply to BrianKrebs

I also watch every alert and decide whether to all until quit or until restart. I’m frustrated that there seems to be no index or guide to common types. When searching I want to accept the minimum that will allow me To read text and see images, nothing more and then only until quit. *.cdn.* seem safe and “tag” or “doubleclick” seem unnecessary. Any other guides?
in reply to BrianKrebs

Also a similar application exists for Windows: SimpleWall
github.com/henrypp/simplewallAnd Windows sure is noisy 🙂
in reply to BrianKrebs

It is such a great program. I've been using it for years as well.

I also tried out this for Linux inspired by Little Snitch. github.com/evilsocket/opensnit…

in reply to BrianKrebs

I became a convert after switching back to macOS a few years ago - it's really handy when you juggle open source and commercial product dev and need to make sure things work as advertised on the network side; if you write code using open source dependencies (aka everyone writing code) you absolutely need something like this as an additional layer of defense on the supply chain side