Originally posted by Faian Wosar - LINK 2
To give a quick update: I tried to replicate their results but was unable to. Online Armor behaved the way I expected it to which is:
1. Block access to all file sharing ports unless it the access originates from a trusted network/computer.
2. Block ping requests unless the requests originates from a trusted network/computer.
3. Allow access to the RDP port, no matter which network, as the RDP port is not a restricted port by default.
I contacted AVC. Unfortunately they no longer had the original test systems, but they kindly agreed to replicate the test and collect some additional logs for us. The problem we are facing at the moment is that at least according to the logs Online Armor performed exactly as it should be, blocking all the access attempts from the untrusted network:
Code:
[02/04/14 10:17:34] 2068/814 UDP <- 192.168.20.100:137, 192.168.20.133:137, System(4/0)
[02/04/14 10:17:34] 2068/814 Blocked by restricted port list
[02/04/14 10:17:37] 2068/814 TCP <- 192.168.20.100:139, 192.168.20.133:49822, System(4/0)
[02/04/14 10:17:37] 2068/814 Blocked by restricted port list
However, even though the network connection attempts were blocked according to the logs, AVC was still able to create/edit files remotely. At this point it is clear that somehow Online Armor messes up on their test system, but we don't know why yet. AVC offered remote access to their test setup and we will surely take advantage of that offer, but it will take a bit longer until we know exactly what is causing it.