New answers tagged

2

Looks like someone is probably trying to brute force usernames/passwords or other malicious connections to your host. Either way you should never have telnet open because it is very insecure. You need to disable port 23 immediately on your host.


0

There is no way to do it with "external" tools. Because the information about the circuits is kept within Tor. However you can utilise Tor's control protocol. This means you can connect to your Tor client and extract information out of your client. So sending GETINFO circuit-status prints out information to your current circuit(s). Usually Tor opens several ...


2

The approaches you mention are a bit confusing, and I will explain why. In a properly designed infrastructure many of the bulletpoints you listed would be addressed: Hourly host discovery scans - If you implement strong port security on your switches, and used NAC - PacketFence (since you mentioned open source, I did also) you wouldn't need to worry about ...


1

Assuming you have control of the network equipment then yes you can log and monitor their actions. Full packet capture: Ideally you want full-packet capture of all traffic at key ingress/egress points for each segment. You asked for the best way to do this and this would give you the most data about traffic on your network. Even if you can only capture the ...


1

The quickest and easiest way would be to verify whether there are processes keeping a socket open for listening. You need a utility such as netstat (Unix, Mac and Windows). There are also GUI utilities - I seem to remember tcpstat and wintcp for Windows. Also Process Explorer by SysInternals and TCPView. These utilities will provide you with the open ports ...



Top 50 recent answers are included