This depends on the application and the OS. Make sure you have the OS
security patches up to date. Older unpatched OS's allow attacks at the
TCP/IP layers. Aside form that there can be bugs on the application level
(ex. MS IIS, older snedmail, etc ). Keep up with the vendor's patches and
subscribe
This depends on the application and the OS. Make sure you have the OS
security patches up to date. Older unpatched OS's allow attacks at the
TCP/IP layers. Aside form that there can be bugs on the application level
(ex. MS IIS, older snedmail, etc ). Keep up with the vendor's patches and
subscribe
This depends on the application and the OS. Make sure you have the OS
security patches up to date. Older unpatched OS's allow attacks at the
TCP/IP layers. Aside form that there can be bugs on the application level
(ex. MS IIS, older snedmail, etc ). Keep up with the vendor's patches and
subscribe
This depends on the application and the OS. Make sure you have the OS
security patches up to date. Older unpatched OS's allow attacks at the
TCP/IP layers. Aside form that there can be bugs on the application level
(ex. MS IIS, older snedmail, etc ). Keep up with the vendor's patches and
subscribe
I agree with Sam. You can (and should) limit access as much as possible; if
server A needs TCP port 100 open, then TCP port 100 should *only* be open to
server A's ip address. That way, the only packets that get it will be
dropped into the waiting arms of your vendors program. And if there's a
5 matches
Mail list logo
