Show the whole picture
A destination on its own is a number. With the device, the application, the user and the owner beside it, it's an answer. Every page in ShadowLatch is built to keep those together.
Our approach
ShadowLatch started with a question every administrator has asked: what is this machine talking to, and should it be? We built the tool we wanted for answering it.
Windows already knows which programs open connections. The trouble is that the answer is scattered across a dozen machines, disappears the moment you look away, and comes as a bare IP address with no name attached. Finding out why a PC in accounting talks to a server in another country shouldn't take an afternoon.
ShadowLatch brings that activity from every device into one console, adds the owner and location of each address, keeps the history, and lets you block what shouldn't be there in a couple of clicks. It does that one job well, and it plays nicely with the antivirus and EDR you already have.
A destination on its own is a number. With the device, the application, the user and the owner beside it, it's an answer. Every page in ShadowLatch is built to keep those together.
When something is certain, we show it plainly. When it isn't, we say so instead of guessing. You'll never see a made-up name or a confidence score pretending to be a fact.
A policy should be quick to try on one device and just as quick to take back. Testing something shouldn't feel like a commitment.
ShadowLatch is built by 27 TOOLS LLC, an Indiana company. We're small on purpose: the people who answer support@shadowlatch.com are the people who write the code, and beta feedback lands directly in what we build next.
We're inviting a small group of IT teams and MSPs into the beta. Your feedback shapes the launch.