Laserfiche WebLink
6.D. - Page 31 of 33 <br />key vulnerabilities including zero -day attacks. The software communicates with the <br />manufacturer's cloud site which continuously updates the local software with the latest <br />protections. <br />• VLAN's, or virtual segmented networks, are used strategically throughout the organization to <br />limit end-point access to servers and networks in which access is needed. <br />• Password policies meet generally accepted industry recommendations that are considered very <br />strong and include required periodic changing which includes disallowing reuse of recent <br />passwords. <br />• All servers are patched as appropriate, generally after a short while once a patch has been <br />released and tested by others as bug free. <br />• Two Factor Authentication is being researched and expected to be implemented City-wide once <br />the best solution for the City is determined. <br />R1.2 Backup & Recovery (In the event of an attack, can you shut down your system quickly? What is <br />being backed up, how it is being backed up, when are backups run, and where are the backups being <br />stored? Have backups been tested? Can you fully restore a Server from a backup?) <br />City response: The recommendation has been implemented. Following is a summary of what has been <br />implemented. <br />More than 60 TB of user data is backed up in multiple ways. A shadow copy is created twice daily on the <br />server to allow for easy rollback of deleted or changed files. In addition, files are backed up to an on - <br />premise dedicated appliance. The appliance replicates itself to the manufacturers' cloud on a daily basis. <br />In the event the on -premise device becomes infected with mal -ware, including ransomware, the device <br />can be wiped clean and the data restored from the cloud's back up. If the backup device itself fails, <br />within three business days a new appliance will be shipped, which is pre -loaded with our backed up <br />data. Data can also be recovered directly from the manufacturer's cloud storage. Daily backups are <br />preserved for a week, weekly backups are preserved for four weeks, monthly backups are saved for <br />twelve months, and yearly revisions are kept for no less than two years. The process is continuously <br />being tested in normal operations via requests from users asking IT to restore data from one of the <br />previous day's backups. <br />All databases in the City's robust database infrastructure are included in all backup processes. As new <br />databases are brought online, the requesting department is involved in determining the acceptable <br />number of transactions they would be willing to re-enter from the previous full backup, usually nightly. <br />If the number of daily transactions is great and the department desires, database backups are scheduled <br />more often. <br />The City runs in a robust, industry best virtual environment. This not only allows the City to realized cost <br />savings by having many virtual servers running on fewer physical servers, it allows the City to maintain <br />hot -standby servers in the Police Department data center. <br />In addition to data backups, the City runs a sophisticated recovery tool which can shut one or more <br />critical servers down and switch their function to hot stand-by servers located at our second data <br />center, located in Police headquarters, from any recovery point within the last 24 hours. Communication <br />between the two data centers is via dedicated fiber, keeping access limited to just the two firewalls at <br />each end of the fiber. <br />The City's IT Manager recommends against the testing of a system wide recovery as it is not a practical <br />approach to Redwood City's mix of different technology functions, services, and protections. The <br />152 <br />