Laserfiche WebLink
brazos <br />RFP 209-028 <br />Hand Held Ticket Writer System <br />120 Securit Th <br />S <br />t <br /> y e <br />ys <br />em should enable real- Currently the system allows the user to operate with the Expected <br /> time user and group security role security settings that were defined when they log in. That <br /> updates while a user is logged means that any new settings will not take place until the user <br /> into the system. logs out or is logged out due to inactivity. We would be <br /> willing to change the system to apply those setting <br /> immediately if desired by the City, at no additional cost. <br />121 Security The System should allow the The Administrator can lock out any user at any time. As Expected <br /> Administrator to lock out a described above, we currently would not disconnect an <br /> particular user and to disconnect already connected user but are willing to make this change <br /> a user during an active session. to the system at no additional cost. <br />122 Security Administrators should be able to The Administrator can change both the number of login Expected <br /> define the number of login attempts as well as the 'lock out' period of time. For <br /> attempts allowed before a user example, after three login attempts - lock the user for 15 <br /> account is disabled. minutes. This is completely controlled by the City. <br />123 Security The System should log an event We are not currently sending failed login emails to the Expected <br /> and alert the Administrator when Administrator but would be willing to do so if desired by the <br /> a user exceeds login attempts. City. <br />124 Security Administrators should be able to The session timeout period is set via the web.config file on Expected <br /> define the duration of inactivity the server, <br /> before a session terminates. <br />125 Security Administrators should be able to Administrators can not only create an expiration date for Expected <br /> create user IDs with an expiration each user, but they can also create a beginning date for <br /> date and time. each user if they don't want access to be granted until <br /> sometime in the future. <br />126 Security Administrators should be able to The same discussion above related to the security of users Expected <br /> create security profiles to also applies to groups. Each group is also assigned a <br /> establish individual and group security level and users can be assigned multiple groups. <br /> privileges. <br />'Item # Cate o Re uirement'Description : Required, Resonse Priority <br />127 Security Administrators should have the Currently the system allows Administrators to see how many Desired <br /> ability to monitor (in real-time) and and who is logged into the system. We can provide <br /> report on file access activities for immediate audit reports as to what was changed but would <br /> a particular user, group, also be willing to identify what action was last taken by each <br /> application, device, and file. user. For example, Mike logged in at 9:20am and last <br /> accessed the Citation Entry Screen. <br />128 Security The System should display a We currently display the security level of each user at the top Desired <br /> configurable security banner upon of the screen when they login. If the City desires specific <br /> login. wording at the top of every screen, we can provide that <br /> capability at no additional cost. <br />129 Security To ensure the security and Based upon the security roles assigned to each user, they Desired <br /> i ntegrity of data, access should be access the DBMS based upon pre-built security roles that <br /> controlled through the user's f urther assure data control and integrity. <br /> security profile.