Laserfiche WebLink
Chapter 3 - System Components <br />20.3.1 PLATFORM SPECIFIC RECOMMENDATIONS <br />1. For all Windows OS -based equipment in your system, please follow the Microsoft guidelines which can be <br />found at http://support.m'icrosoft.com/l(b/822158. <br />2. For all servers twining Microsoft SQL Server, please follow the recommendations in the Microsoft article <br />"Guidelines for choosing antivirus software to nrn on the computers that are running SQL Server" at <br />http://support.microsoft.com/kb/309422. <br />3. For customers using Areserve RHA (an CA software application), CA recommends that the <br />"%winddir%\CASpool" (folder and all of the folders or files that are being synchronized by Areserve must <br />be excluded from active and scheduled virus scans. This includes the TriTech file structure on the server. <br />4. If your system uses Microsoft Cluster Server, please consult with your Virus Protection software vendor to <br />determine its compatibility with Cluster services. Because Virus Protection software drivers reside above <br />the file system, they may not properly address the nuances related to a clustered environment. For more <br />information on this topic, please refer to: http://support.microsoft.com/Icb/250355. <br />5. If you use Microsoft Access for reporting, do not scan these database files while in use as they too can be <br />corrupted by active virus scanning. For more information see Symantec Document ID: 2002091913503748 <br />on their website. <br />6. Customers utilizing VMWare products should consult the VMWare best practices for additional Antivirus <br />and Security. For more information see VMWare websites: <br />http://kb.mit.edu/confluence/dis lalay/istcontrib/VMware+Security+Recommendations+and+Best+Practices <br />http://www,vmware.com/files/pdf/VMware-View-AntiV irusPractices-TN-EN.pdf <br />20.3.2 GENERAL VIRUS PROTECTION RECOMMENDATIONS <br />1. The frequency for Virus Definition file updates should be configured to run daily. Virus Definition files are <br />essentially databases that hold information pertaining to viruses. The updating of both the Virus' Definition <br />files and the Virus Scan engine should be permitted. This is considered a best practice. <br />2. Machines should scan only their local drives (not network drives); therefore, do not set active or scheduled <br />scanning of the Inform CAD Q: drive other than the server hosting the file share. <br />3. Virus Protection software needs to be disabled when software updates occur, whether the updates are from <br />Microsoft, TriTech, or any other software vendor. This will prevent file locking problems from occurring <br />and is considered a best practice. <br />4. Port activities within the Virus Protection software have to be managed, for example, you would want to <br />allow VNC packets to be sent and received without each packet being scanned. Disrupting VNC packets <br />could impede the VNC application and slow the network. <br />5. The implementation and management of Virus Protection software requires regular monitoring of security <br />related websites for the purpose of staying informed on virus threat's, technical tips, and security related <br />advisories. Please monitor your Virus Protection software provider's site. Other reference sites include the <br />following: <br />a, http://us.mcafee.com/virusInfo/default.asp <br />b. http://www.sare.com <br />c. http://www.cert.org <br />6. Other management activities include the regular review of Virus Scan log files for each computer, which <br />contain statistical information about the scanning activities on that machine. <br />7. Another important consideration is the implementation and management of Firewall and IP Ports. Many <br />security breaches can be prevented through effective IP Port management, for example, IP Ports should be <br />closed except for the ones being used, Often this is not the case, as many systems are vulnerable because <br />most IP Ports are open. Please refer to the firewall port recommendations earlier in this document for <br />configuration settings needed for this product. <br />The contents of this material are confidential and proprietary to TriTech Software Systems, Inc. and may not be reproduced, <br />published or disclosed to others without the prior written consent of TriTech Software Systems, Inc. <br />©2015 TriTech Software Systems <br />