My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Res 2009-171
San-Marcos
>
City Clerk
>
03 Resolutions
>
2000 s
>
2009
>
Res 2009-171
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/15/2010 9:35:16 AM
Creation date
12/23/2009 8:30:54 AM
Metadata
Fields
Template:
City Clerk
City Clerk - Document
Resolutions
City Clerk - Type
Agreement
Number
2009-171
Date
12/16/2009
Volume Book
184
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
71
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
Brazos <br />RFP 209-028 <br />Hand Held Ticket Writer System <br />112 Security Patch updates should be Once a new version (or patch) is created and tested, we Expected <br /> identified for implementation identify several customers to pilot the patch prior to general <br /> within 5 days of a new patch release. Those customers are notified and given the <br /> release (i.e. server, OS, opportunity to accept or refuse the new patch. Once that <br /> application, browser, and patch has been tested and verified in a customer <br /> database). environment, all customers are notified of the patch and <br /> given the opportunity to refuse and/or schedule the release <br /> within their environment. The City will identify the person <br /> who will be charged with determining both the willingness to <br /> accept a pilot patch as well as scheduling the release of <br /> those patches. <br />113 Security The System should allow single Each user is assigned a user ID and a security profile Expected <br /> sign on authentication to the (defined by the City). Each user is required to sign into the <br /> application. handheld device and the website. Once they successfully <br /> log in, all applications and functions that they have access to <br /> are available without additional sign-ons. <br />114 Security The System should provide LDAP Brazos Technology can integrate with Active Directory for Expected <br /> or MS Active Directory BuiidlT and eCitation servers, but we do not recommend <br /> authentication. integration for the devices. This is because if the City <br /> chooses to have TCIC/NCIC returns, we must comply with <br /> those requirements for passwords. <br />115 Security All Windows systems should be We have installed our eCitation server with Symantec, Expected <br /> compatible with Symantec Anti- McAfee, and Sophos anti-virus software packages. If the <br /> Virus application. City desires another system, we will verify operation and <br /> work with the City to set the appropriate security levels to <br /> ensure system operation. <br />116 Security All Systems (i.e. client, web The entire Brazos Solution has been built utilizing the Expected <br /> servers, application servers, industry best standards for policy and risk management, <br /> database servers) should meet security architecture, user security, authentication, and DRA <br /> industry-best standards (InfoSec). issues. We are not completely sure how to address the very <br /> broad scope of this requirement, but would be willing to <br /> answer any question desired by the City. Since our system <br /> runs in a hosted environment, security and DRA issues are <br /> at the heart of our entire system. One of our customers, the <br /> Department of Homeland Security, put us through a rigorous <br /> vetting process to ensure our system was compliant with <br /> their security and business continuity requirements. <br />117 Security Systems should be able to be We do not have any SNMP traps built into our system and Expected <br /> monitored using SNMP. believe that another server should have this monitoring <br /> capability. We currently use a service provided by <br /> Rackspace (our hosting company) to provide this monitoring <br /> capability. <br />118 Security The System should minimize the The Brazos system allows the City to configure which ports Expected <br /> number of different IP ports used are used for all data transmission from the devices to the <br /> by servers, clients, and other servers as well as from the web server to the DBMS. Since <br /> related sub-systems. the City can define all of these ports, security on these ports <br /> should be straightforward. In addition, since our system is <br /> built as a hosted model, setting up additional customers <br /> (such as the University) is built into the system. While all <br /> data are contained in the same database schema, it is all <br /> sectioned off via customer number which allows the entities <br /> to operation completely autonomously and/or share <br /> information with each other. <br />Item # Cate o Requirement Description Required Response Priorit <br />119 Security To maintain network security, the All defined ports (described above) are set via the Expected <br /> System must include re- web.config file and in each customer profile. This allows the <br /> assignable ports for the System. City to define and/or change them at any time. <br />
The URL can be used to link to this page
Your browser does not support the video tag.