1

I have a very specific scenario in which maschines (IoT) are communicating with a central server over websockets.

I need to inspect the websockets traffic (wss/tls) for audit and monitoring reasons (especially troubleshooting). We can't do it on the IoT or server site, since we don't maintain software.

We are able to configure the url/ip of the central server. Therefore I thought to route the traffic over a proxy/load balancer and intercept/log the traffic there in tls bridging mode. Ideally the proxy would be free (optional) and scalable (>65k connections, mandatory). I am also aware of MITM websocket proxies, who can do that for pentest and testing purposes, but I am not aware one that is scalable and ready for a high load production enviroment.

I tried different open source/free proxies, and could proxy the connections, but could not log the traffic (besides the initial http upgrade request).

I read about Application Load Balancer and the possibility to do the routing by traffic interception, but most solutions seem to use an IP Hash or sticky cookie mechanism, which isn't usefull in my case. I read into Stingray Traffic Manager, which is in principle capable of doing it (i am a bit unsure about the logging), but a free/unlimited alternative would be great.

Kitano
  • 11
  • 1

0 Answers0