[AccessD] AV on a server

Locking ports  and disabling services is a totally different issue to AV on a server. A server 
should NEVER, EVER, EVER be connected to the internet other than through at least a 
router, to say nothing of harware firewalls, DMZ s etc.


On 13 Dec 2012 at 12:08, Jim Lawrence wrote:

> Yes, of course.
> 
> There are, without a setup router over 65K opens ports on any computer
> connected to the internet.
> 
> All servers have at least a couple hundred ports open by default each
> potentially attached to various applications. Here is just a few of the
> ports used by major applications:
> http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers
> 
> For example; that is why most servers have their FTP program turned off,
> have changed the port setting or moved the FTP process to a stand-alone
> server or virtual drive.
> 
> Additionally, if any network station get compromised it is then relatively
> easy to gain control of the servers and then everything is compromised.
> 
> Jim    
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
> Sent: Thursday, December 13, 2012 11:19 AM
> To: 'Access Developers discussion and problem solving'; List
> Subject: [AccessD] AV on a server
> 
> Question arose at customer site that I hadn't thought about before.  Any
> reason to put AV on the server?  Most virii are coming from email or web
> sites and if you're not doing email or browsing on the server, should you AV
> anyway?
>  
> TIA
>  
> Rocky
>  
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>