10-RFP2009 - Part G - Attachment L - City of Alexandria Cloud Vendor Assessment Tool (On Premise).xlsx

XLSX spreadsheet 22 KB Posted

Attached to
Computer-Aided Dispatch / Automatic Vehicle Location (CAD/AVL) System Replacement
Solicitation number
2009
Issued by
Alexandria City, Virginia

About this file

This document is a Cloud Vendor Assessment Tool utilized by the City of Alexandria as part of a Request for Proposal (RFP) for a Computer-Aided Dispatch/Automatic Vehicle Location (CAD/AVL) system replacement for DASH (Dash Bus Service). The assessment tool is designed to evaluate vendor capabilities across multiple security and operational dimensions to ensure the selected cloud-based solution meets the City's stringent requirements for managing transit operations, real-time bus tracking, wayside displays, schedule adherence monitoring, performance reporting, incident management, and customer communications. The evaluation framework does not specify explicit response dates, due dates, site visits, or bidder conferences within this document; however, it establishes comprehensive criteria that vendors must address to demonstrate compliance with the City's security posture and operational standards.

The assessment tool encompasses nine major evaluation categories: Development Environment, Software Compatibility, Authentication/Authorization/Accounting, Software Development Lifecycle (SDLC), Business Continuity Planning, Change Management, Data Security, Database Management, Disaster Recovery Planning, Physical Security, and Policies/Procedures/Processes. Vendors are required to provide detailed responses demonstrating compliance with industry standards such as NIST, CIS, and NSA guidelines; support for standards-based single sign-on and Active Directory integration; encryption of data in transit and at rest; documented business continuity and disaster recovery plans with annual reviews; formal incident response procedures; and secure coding practices with both internal and external security reviews. The document does not address pricing terms, set-asides, incumbent information, or specific funding amounts; rather, it serves as a technical and security evaluation mechanism to assess vendor qualifications prior to contract award.

View the file

Other files

File Type Posted
4-RFP2009 - Part G - Attachment E - Reference Sheet - Final.pdf PDF
20-RFP2009 - Part A - General Information - Final.pdf PDF
12-RFP2009 - Part H - Exhibits Title Page - Final.pdf PDF
16-RFP2009 - Part H - Exhibit I - MAPT Cooperative Rider Clause - Final.pdf PDF
9-RFP2009 - Part G - Attachment K - Current DASH Fixed-Route On-Board Vehicle Systems - Final.pdf PDF
18-RFP2009 - Part H - Exhibit K - ITS Data Classification Policy - Final.pdf PDF
1-RFP2009 - Part G - Attachment A - Authorized Signatory Statement - Final.pdf PDF
22-RFP2009 - Part C - Special Terms and Conditions - Final.pdf PDF
7-RFP2009 - Part G - Attachment I - System Requirements Matrix - Final (Updated).pdf PDF
25-RFP2009 - Part F - Evaluation and Method of Award - Final.pdf PDF
11-RFP2009 - Part G - Attachment M - City of Alexandria Cloud Vendor Assessment Tool (Cloud).xlsx XLSX spreadsheet
5-RFP2009 - Part G - Attachment F - Subcontractors List - Final.pdf PDF
19-RFP2009 - Part H - Exhibit L - Security Controls Contract Language - Final.pdf PDF
23-RFP2009 - Part D - General Terms and Conditions - Final.pdf PDF
17-RFP2009 - Part H - Exhibit J - COA - Confidentiality and Non-Disclosure Agreement - Final.pdf PDF
21-RFP2009 - Part B - Scope of Work - Final .pdf PDF
13-RFP2009 - Part H - Exhibit A - Definitions - Final.pdf PDF
8-RFP2009 - Part G - Attachment J - Current DASH Fixed-Route Vehicles - Final.pdf PDF
2-RFP2009 - Part G - Attachment C - Required Information Form - Final.pdf PDF
3-RFP2009 - Part G - Attachment D - Certifications - Final.pdf PDF
6-RFP2009 - Part G - Attachment H - Offeror Pricing Schedule - Final (Updated).pdf PDF
26-RFP2009 - Part G - Attachment G - No Response Form - Final.pdf PDF
24-RFP2009 - Part E - Instructions to Offerors - Final.pdf PDF
15-RFP2009 - Part H - Exhibit H - Information Technology Ts and Cs - Final.pdf PDF
14-RFP2009 - Part H - Exhibit D - Federal or Grant Funding Provisions - Final.pdf PDF
Show all 25

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Sheet1

Development EnvironmentVendor AnswersAdditional Information
DEVE-01Does your development environment comply with a configuration baseline based on expert sources (NIST, CIS, NSA, etc.)? If so, can you share which guidelines with which they are compliant?
DEVE-02What controls are in place to detect and prevent malicious code tampering?
DEVE-03Describe or provide a reference to your media handling process, that is documented and currently implemented, including end-of-life, repurposing, and data sanitization procedures.
Software CompatabilityVendor AnswersAdditional Informationplan on
COMP-01Is your product regularly tested for compatibility with current security patches for major software (e.g. Windows)? If so, how frequently? And with which software?
COMP-02Which third-party frameworks does your product require?
COMP-03Which third-party libraries does your product leverage internally? Should a security update become available for a library, how long does integration and distribution of the updated library take?
Authentication, Authorization, and AccountingVendor AnswersAdditional Information
HLAA-01Can you enforce password/passphrase complexity requirements provided by the City?
HLAA-02Describe or provide a reference to the types of authentication, including standards-based single-sign-on (SSO, InCommon), that are supported by the product.
HLAA-03Describe or provide a reference to the authentication and authorization systems such as Active Directory, Kerberos (what version) or a institution centralized authorization service that work with your application.
HLAA-04Does the system (servers/infrastructure) support external authentication services (e.g. Active Directory, LDAP) in place of local authentication?
HLAA-05Does your system have the capability to log security/authorization changes as well as user and administrator security events (e.g., login failures, access denied, changes accepted), and all requirements necessary to implement logging and monitoring on the system?
SDLCVendor AnswersAdditional Information
SDLC-01What processes are in place to ensure secure coding practices are integrated into the SDLC?
SDLC-02Are processes in place to ensure proper version control? If so, can you share what versioning software and/or service you use?
SDLC-03If a code repository is utilized, what processes are in place to prevent sensitive information from appearing in version control?
SDLC-04Will implementation involve code customization or modification? If so, can you provide a brief summary of the scope of the customization?
SDLC-05Does your application contain any web application components? If so, how do you address the OWASP Top 10 (or similar risk compilations) from a development perspective?
SDLC-06How often is your product reviewed internally for secure coding practices? If so, can the results be provided?
SDLC-07How often is your product reviewed by an external entity for secure coding practices? If so, can the results be provided?
SDLC-08What mechanisms are in place to facilitate reporting of vulnerabilities in your product?
SDLC-09What are the remediation process and customer expectations if a vulnerability is reported?
Business Continuity PlanVendor AnswersAdditional Information
HLBC-01Do you have a documented Business Continuity Plan (BCP)? If so, can it be shared?
HLBC-02Is there a documented communication plan in your BCP for impacted clients?
HLBC-03Are all components of the BCP reviewed at least annually and updated as needed to reflect change?
HLBC-04Does your organization conduct an annual test of relocating to this alternate site for business recovery purposes?
Change ManagementVendor AnswersAdditional Information
HLCH-01Do you have a Change Management Plan? If so, can it be shared?
HLCH-02How and when will the City be notified of major changes to your environment that could impact our security posture?
HLCH-03Do you have documented procedures on how security risks are mitigated until patches can be applied? If so, can it be shared?
HLCH-04Do procedures exist to provide that emergency changes are documented and authorized (including after the fact approval)? If so, can it be shared?
DataVendor AnswersAdditional Information
HLDA-01Is sensitive data encrypted in transport and at-rest?
HLDA-02What data backup, restoration, or fail-over mechanisms are provided with your software? What third-party tools or mechanisms are recommended?
DatabaseVendor AnswersAdditional Information
HLDB-01What types of databases does your product support?
HLDB-02Does the database support encryption of specified data elements in storage?
HLDB-03If built into the product, do you currently use encryption in your database?
HLDB-04Should database migration be necessary (e.g. the database host or OS becomes deprecated) do you provide a mechanism to facilitate the transition?
Disaster Recovery PlanVendor AnswersAdditional Information
HLDR-01Do you have a Disaster Recovery Plan (DRP)? If so, can it be shared?
HLDR-02Are any disaster recovery locations outside the United States? If so, please provide the locations.
HLDR-03Are all components of the DRP reviewed at least annually and updated as needed to reflect change?
Physical SecurityVendor AnswersAdditional Information
HLPH-01Does your organization have physical security controls and policies in place? If so, can it be shared?
HLPH-02Are employees allowed to take home customer data in any form?
Policies, Procedures, and ProcessesVendor AnswersAdditional Information
HLPP-01Can you share the org chart, mission statement and policies for your information security unit?
HLPP-02Are information security principles designed into the product and / or SDLC lifecycle?
HLPP-03Do you have a formal incident response plan? If so, can it be shared?
HLPP-04Do you have a documented information security policy? If so, can it be shared?

File details come from the government source that posted it. Updated .