Laserfiche WebLink
brazos <br />116 (Security IAII Systems (i.e. client, web (The entire Brazos S( <br /> servers, application industry best standal <br /> servers, database servers) security architecture, <br /> should meet industry-best issues. We are not c <br /> standards (InfoSec). broad scope of this r <br /> answer any question <br /> runs in a hosted envi <br /> at the heart of our en <br /> Department of Home <br /> vetting process to en <br /> their security and bus <br />117 Security Systems should be able to We do not have any ; <br /> be monitored using SNMP. believe that another s <br /> capability. We currer <br /> Rackspace (our hosti <br /> capability. <br />118 Security The System should The Brazos system al <br /> minimize the number of are used for all data ti <br /> different IP ports used by servers as well as fror <br /> servers, clients, and other the City can define all <br /> related sub-systems. should be straightforw <br /> built as a hosted mode <br /> (such as the Universit, <br /> data are contained in 1 <br /> sectioned off via custc <br /> t o operation completel <br /> i nformation with each <br />119 Security To maintain network All defined ports (desc <br /> security, the System must file and in each custon <br /> include re-assignable ports define and/or change t <br /> for the System. <br />120 Security The System should enable Currently the system a <br /> real-time user and group security settings that w <br /> security role updates while means that any new SE <br /> a user is logged into the logs out or is logged oL <br /> system. willing to change the sy <br /> immediately if desired t <br />121 Security The System should allow The Administrator can I <br /> the Administrator to lock described above, we CL <br /> out a particular user and to already connected user <br /> disconnect a user during an to the system at no add <br /> active session. <br />122 Security Administrators should be The Administrator can c <br /> able to define the number attempts as well as the <br /> of login attempts allowed example, after three log <br /> before a user account is minutes. This is complE <br /> disabled. <br />123 Security The System should log an We are not currently sel <br /> event and alert the Administrator but would <br /> Administrator when a user City. <br />e xceeds login attempts. <br />RFP 209-028 <br />Hand Held Ticket Writer System <br />iutlon has been built utilizing the Expected <br />ds for policy and risk management, <br />user security, authentication, and DRA <br />ompletely sure how to address the very <br />Iquirement, but would be willing to <br />desired by the City. Since our system <br />'onment, security and DRA issues are <br />lire system. One of our customers, the <br />and Security, put us through a rigorous <br />'ure our system was compliant with <br />iness continuity requirements. <br />'NMP traps built into our system and Expected <br />erver should have this monitoring <br />tly use a service provided by <br />ig company) to provide this monitoring <br />ows the City to configure which ports Expected <br />ansmission from the devices to the <br />n the web server to the DBMS. Since <br />of these ports, security on these ports <br />and. In addition, since our system is <br />?I, setting up additional customers <br />1) is built into the system. While all <br />he same database schema, it is all <br />mer number which allows the entities <br />it autonomously and/or share <br />rther. <br />-ibed above) are set via the web.config Expected <br />er profile. This allows the City to <br />iem at anytime. <br />lows the user to operate with the Expected <br />are defined when they log in. That <br />ttings will not take place until the user <br />t due to inactivity. We would be <br />stem to apply those setting <br />iy the City, at no additional cost. <br />Eck out any user at any time. As Expected <br />rrently would not disconnect an <br />but are willing to make this change <br />tional cost. <br />hange both the number of login Expected <br />lock out' period of time. For <br />n attempts - lock the user for 15 <br />tely controlled by the City. Expected <br />(ding failed login emails to the Expected <br />be willing to do so if desired by the