Next week will begin the campus wide release of Sophos Anti-virus for Windows. This will be delivered across our network using the same mechanism that manages our Windows workstations. To facilitate this deployment we need to ask that all Windows systems be turned off on Friday nights and powered back up on Monday mornings for the next several weekends. The install packages will be pushed across the network according to the following schedule:
- February 19th: Windows7 systems
- February 26th: Remaining Staff workstations
- March 4th: Remaining Faculty workstations and computers that have not been addressed in prior groups.
For information on Sophos please see the FAQ at http://go/sophos. This will answer many questions you may have and will address many issues you may encounter. Prior to the date your system is scheduled for the Sophos install please do the following:
- Complete any software installs you may have pending, including any Windows.
- Disable any additional firewalls you may have added beyond the Windows Firewall. Please note, this is not referring to Anti-virus such as Symantec but rather products such as SonicWall.
- Shut your system down the Friday before the install so that it powers up the Monday morning of the scheduled install. If you power your system up over the weekend the install will start at that time.
- Shut your system down the Monday night after the install.
For additional information please see http://go/sophos
Dear LIS Colleagues:
As posted in the blog earlier this week. We are asking LIS to help us with a test of the Sophos deployment. Endpoint Protection Product. If each Windows user in LIS would please run the executable at the following link it will install the Sophos client onto your Windows system. It will also remove the Symantec anti-virus client from your system. There are some things you should be aware of in this process:
- When Windows detects the uninstall of Symantec and that you have no anti-virus it will give you a warning. You should ignore this as you are in the process of installing a new package.
- During the install process Windows Defender, if you have it running, may be disabled. If this occurs Windows will give you a warning. Please ignore this warning.
- While you are at a state with no anti-virus Windows may offer you a link to install a new Anti-virus. These may also be ignored as you are in the process of installing Sophos.
- The removal process for Symantec has been seen to take a protracted amount of time on some computers. You need to be patient. It is unusual but 10 minutes is a reasonable amount of time to allow for an install of this package. During this process some systems may stop responding at times.
- When Sophos has been installed the Gold shield of Symantec will have been replaced with a blue and white shield of Sophos .
For additional information on Sophos check out the FAQ at http://go/itsecurity.
Please click here for the Sophos install package for LIS Windows Users: http://whitetail.middlebury.edu/SohopsUpdate/SophosLIS.exe
Dear LIS Colleagues,
This Thursday and Friday we will have representatives from Sophos here on site. They will be helping us to develop a deployment package for the client component of the Sophos Endpoint Protection product which we are using to replace Symantec Anti-Virus. As we complete the development of this deployment package and have tested it thoroughly, we will be initiating a test across the systems in LIS to ensure that the package works on a larger group of systems and also to start a larger test of the client here at Middlebury.
Later this week you will receive a second communication about this test effort and it will also include information about how you can help us to assess the impact of the client on your system and also the install process. For additional information about Sophos please see the FAQ at http://GO/ITSECURITY. Also, feel free to contact LIS Security at email@example.com or contact Ian Burke at ext. 5368. Thank you for your help and understanding with this process.
LIS Network Security Administrator
Dear Middlebury Colleagues:
To offer some additional information on the Sophos roll-out the following timeline has been proposed and will be followed by the LIS deployment team for this
- Email will be converted to the Sophos solution the weekend of January 22, 2012
- Testing will be conducted on individual systems through the month of January
- Sophos engineers will be on site to help with a larger test group across LIS and to build a deployment agent on January 25 and 26th
- Server deployment and will be conducted on test servers and production servers through the month of January and February
- A second desktop test group will be identified and targeted for the end of January and beginning of February
- Based on the conclusion of two successful tests deployment will continue to the remainder of the campus in February
If you are interested in being a part of one of the test groups, please contact LIS Information Security at firstname.lastname@example.org. If you would Iike more information about Sophos please check the Infosec web site at go\itsecurity or contact LIS Information Security.
LIS-IT Security Administrator
The Payment Card Industry Data Security Standard (PCI DSS v2.0) is a standard that has been accepted by all major credit card companies and most credit providers. It is a standard that we must abide by if we are to accept credit cards as a form of payment. PCI DSS is broken into 12 requirements; each focusing on a different domain of security.
While PCI DSS is not an actual law, it is a standard enforced by the credit card industry, and the banks have stated and upheld the policy that they will no longer accept business from non-PCI compliant merchants. The government has used the PCI DSS as a yardstick by which they have measured such regulations as Gram-Leach-Bliley, Sarbanes-Oxley, and most recently the drafting of the Data Accountability and Trust Act.
We employ a device called a Barracuda here at Middlebury which helps us prevent SPAM from flooding our email system. Just shy of a year ago this system was updated to enable it to filter on cardholder information. By default this feature was turned on. We have left this enabled and have begun reporting on these blocked messages and alerting the senders of outbound messages. The Barracuda is intended to serve both as a SPAM filter and a compliance tool.