DOCUMENT
99 -- Disaster recovery - Attachment
- Notice Date
- 7/30/2013
- Notice Type
- Attachment
- NAICS
- 541519
— Other Computer Related Services
- Contracting Office
- Philadelphia VAROIC;Department of Veterans Affairs Regional;Bonnie Robinson;5000 Wissahickon Avenue;Philadelphia PA 19144
- ZIP Code
- 19144
- Solicitation Number
- VA31013I0007
- Response Due
- 8/31/2013
- Archive Date
- 9/30/2013
- Point of Contact
- Bonnie Robinson
- Small Business Set-Aside
- N/A
- Description
- Request for Information/ Source Sought VA310-13-I-0007 Disaster Recovery The Department of Veterans Affairs, Philadelphia Regional Office This Sources Sought / Request for information is released pursuant to FAR Part 15.201(e), Exchanges with Industry. The Veterans Benefits Administration Eastern Area Contracting Team is issuing this combination Sources Sought Notice / Request for Information. The objective is to gain information on industries ability to provide Disaster Recovery service in accordance with the statement of work below. This request is to facilitate the Contracting Officer's review of the market base, for acquisition planning, size determination, and procurement strategy. This Sources Sought/RFI notice provides an opportunity for respondents to submit their notice of ability, ask any questions, or submit comments in response to the below statement of work. Vendors are being requested to submit their availability and potential to fulfill the requirement, in the form of a capability response. Information is sought on industry best practices, vendor capabilities, and company profile information. ? STATEMENT OF WORK Disaster Recovery Services Insurance Collections A. TITLE OF PROJECT: Off-Site Disaster Recovery Services for VBA Insurance Service Collections Operations The VBA Insurance Service requires a disaster recover site that has hardware compatible with the BancTec X350 Remittance Processing System. This system allows VBA personnel to process Insurance payments and transmit the transactions to a remote VA Information Technology site. These services would only be used in the event of a disaster that would render the Insurance Service location in Philadelphia PA unusable. Scope of Work: The contractor will provide all resources necessary to continue the deliverables as described in this Statement of Work (SOW), except as may be otherwise specified. The Department of Veterans Affairs, Veterans Benefits Administration, Insurance Service requires the vendor to supply all the hardware support at their Remittance Processing Disaster Recovery site that will allow VBA personnel to process bills and checks received form veterans paying their Insurance premiums and loan payments. The hardware must be compatible with BancTec X350 hardware and software and VBA customized collections software. This will enable VBA personnel to operate the hardware, process the checks and transmit the data to the VA remote IT site. As the data involves veteran PII the site must be secure and only VBA personnel will have access to the data while at the site and during processing. VBA personnel must also have the ability to delete all of the data immediately after the data has been transmitted to the VA host site. Only VBA personnel will have access to the source documentation and the data files and the vendor supplied hardware during the processing cycle. VBA personnel will delete all data after successful transmission of the data. VBA personnel will be responsible for processing and managing the documentation and the data file. ? Background: The Department of Veterans Affairs (VA), Veterans Benefits Administration (VBA), Insurance Service is responsible for the administration of six government life insurance programs for Veterans and service members. This responsibility includes the billing and collection of all premiums, all loans payments for Veterans who pay monthly, quarterly, semi-annually and annually. Veterans remit these instruments with a scannable billing document and a check. The BANCTEC System reads the scannable document, compares the check amount, accepts the payment and builds an updating transaction batched and sent to the mainframe or rejects the transaction and routes it to a VBA employee for clarification. This is done using a high-speed transport for processing, endorsing, micro-encoding and batching the documents in Federal Reserve banking System standards. The BANCTEC System also controls all individual checks and billing documents and prepares 12 specialty reports suitable for the Remittance Processing and Finance activities at the Philadelphia VAROIC as well as daily deposit media for the Federal Reserve Bank. This process is accomplished on a high-speed specialty system, built and programmed by BANCTEC, capable of processing checks and a similar number of documents per hour. The BANCTEC equipment is capable of processing 350 transactions per hour and on an average day VAROIC processes over 5,000 transactions. In FY 2009 a total of 1,231,231 transactions were processed, in the amount of $159,843,835. This system is located in the Philadelphia Insurance Service Office with only local backup. In the event of a disaster, the Insurance Service personnel responsible for processing this work will need to remove to a remote location in order to process this most important insurance work that is vital to our operations. These daily remittances are vital to our mission in that the premiums are used to offset claims and must be processed on the date of receipt. Therefore VBA requires a remote site where the vendor supplied compatible hardware can be activated and used by VBA personnel to process the work until such time as the Insurance site is returned to working order. ? Performance Period: The period of performance shall be for one (1) 12-month base year at time of award with three optional years. Type of Contract: Firm Fixed Price Place of Performance: Primary place of performance will be at the contractor's facility staffed by VBA personnel. BPA Number & Title: Not applicable. CONTRACT AWARD MEETING: After award the time and place to be determined by the Contracting Officer's Technical representative (COTR) GENERAL REQUIREMENTS 1.For every task, the contractor shall identify in writing all necessary subtasks (if any), associated costs by task, together with associated sub milestone dates. 2.All written deliverables will be phased in layperson language. Statistical and other technical terminology will not be used without providing a glossary of terms. 3.Ideal learning opportunities from the contractor should be flexible to meet Insurance Service's needs and convenient for employees. 4.The contractor, their personnel, and their subcontractors shall be subject to the Federal laws, regulations, standards, and VA Directives and Handbooks regarding information and information system security as delineated in this contract. VA HANDBOOK 6500.6 APPENDIX B 1.SUBPART 839.2 - INFORMATION AND INFORMATION TECHNOLOGY SECURITY REQUIREMENTS 839.201 Contract clause for Information and Information Technology Security: a.Due to the threat of data breach, compromise or loss of information that resides on either VA-owned or contractor-owned systems, and to comply with Federal laws and regulations, VA has developed an Information and Information Technology Security clause to be used when VA sensitive information is accessed, used, stored, generated, transmitted, or exchanged by and between VA and a contractor, subcontractor or a third party in any format (e.g., paper, microfiche, electronic or magnetic portable media). b.In solicitations and contracts where VA Sensitive Information or Information Technology will be accessed or utilized, the CO shall insert the clause found at 852.273-75, Security Requirements for Unclassified Information Technology Resources. 2,852.273-75 ? SECURITY REQUIREMENTS FOR UNCLASSIFIED INFORMATION TECHNOLOGY RESOURCES (INTERIM- OCTOBER 2008) The contractor, their personnel, and their subcontractors shall be subject to the Federal laws, regulations, standards, and VA Directives and Handbooks regarding information and information system security as delineated in this contract. VA HANDBOOK 6500.6 APPENDIX C 1. GENERAL Contractors, contractor personnel, subcontractors, and subcontractor personnel shall be subject to the same Federal laws, regulations, standards, and VA Directives and Handbooks as VA and VA personnel regarding information and information system security. 2. ACCESS TO VA INFORMATION AND VA INFORMATION SYSTEMS a. A contractor/subcontrator shall request logical (technical) or physical access to VA information and VA information systems for their employees, subcontractors, and affiliates only to the extent necessary to perform the services specified in the contract, agreement, or task order. b. All contractors, subcontractors, and third-party servicers and associates working with VA information are subject to the same investigative requirements as those of VA appointees or employees who have access to the same types of information. The level and process of background security investigations for contractors must be in accordance with VA Directive and Handbook 0710, Personnel Suitability and Security Program. The Office for Operations, Security, and Preparedness is responsible for these policies and procedures. c. Contract personnel who require access to national security programs must have a valid security clearance. National Industrial Security Program (NISP) was established by Executive Order 12829 to ensure that cleared U.S. defense industry contract personnel safeguard the classified information in their possession while performing work on contracts, programs, bids, or research and development efforts. The Department of Veterans Affairs does not have a Memorandum of Agreement with Defense Security Service (DSS). Verification of a Security Clearance must be processed through the Special Security Officer located in the Planning and National Security Service within the Office of Operations, Security, and Preparedness. d. Custom software development and outsourced operations must be located in the U.S. to the maximum extent practical. If such services are proposed to be performed abroad and are not disallowed by other VA policy or mandates, the contractor/subcontractor must state where all non-U.S. services are provided and detail a security plan, deemed to be acceptable by VA, specifically to address mitigation of the resulting problems of communication, control, data protection, and so forth. Location within the U.S. may be an evaluation factor. e. The contractor or subcontractor must notify the Contracting Officer immediately when an employee working on a VA system or with access to VA information is reassigned or leaves the contractor or subcontractor's employ. The Contracting Officer must also be notified immediately by the contractor or subcontractor prior to an unfriendly termination. 3. VA INFORMATION CUSTODIAL LANGUAGE a. Information made available to the contractor or subcontractor by VA for the performance or administration of this contract or information developed by the contractor/subcontractor in performance or administration of the contract shall be used only for those purposes and shall not be used in any other way without the prior written agreement of the VA. This clause expressly limits the contractor/subcontractor's rights to use data as described in Rights in Data - General, FAR 52.227-14(d) (1). b. VA information should not be co-mingled, if possible, with any other data on the contractors/subcontractor's information systems or media storage systems in order to ensure VA requirements related to data protection and media sanitization can be met. If co-mingling must be allowed to meet the requirements of the business need, the contractor must ensure that VA's information is returned to the VA or destroyed in accordance with VA's sanitization requirements. VA reserves the right to conduct on site inspections of contractor and subcontractor IT resources to ensure data security controls, separation of data and job duties, and destruction/media sanitization procedures are in compliance with VA directive requirements. c. Prior to termination or completion of this contract, contractor/subcontractor must not destroy information received from VA, or gathered/created by the contractor in the course of performing this contract without prior written approval by the VA. Any data destruction done on behalf of VA by a contractor/subcontractor must be done in accordance with National Archives and Records Administration (NARA) requirements as outlined in VA Directive 6300, Records and Information Management and its Handbook 6300.1 Records Management Procedures, applicable VA Records Control Schedules, and VA Handbook 6500.1, Electronic Media Sanitization. Self-certification by the contractor that the data destruction requirements above have been met must be sent to the VA Contracting Officer within 30 days of termination of the contract. d. The contractor/subcontractor must receive, gather, store, back up, maintain, use, disclose and dispose of VA information only in compliance with the terms of the contract and applicable Federal and VA information confidentiality and security laws, regulations and policies. If Federal or VA information confidentiality and security laws, regulations and policies become applicable to the VA information or information systems after execution of the contract, or if NIST issues or updates applicable FIPS or Special Publications (SP) after execution of this contract, the parties agree to negotiate in good faith to implement the information confidentiality and security laws, regulations and policies in this contract. e. The contractor/subcontractor shall not make copies of VA information except as authorized and necessary to perform the terms of the agreement or to preserve electronic information stored on contractor/subcontractor electronic storage media for restoration in case any electronic equipment or data used by the contractor/subcontractor needs to be restored to an operating state. If copies are made for restoration purposes, after the restoration is complete, the copies must be appropriately destroyed. f. If VA determines that the contractor has violated any of the information confidentiality, privacy, and security provisions of the contract, it shall be sufficient grounds for VA to withhold payment to the contractor or third party or terminate the contract for default or terminate for cause under Federal Acquisition Regulation (FAR) part 12. g. If a VHA contract is terminated for cause, the associated BAA must also be terminated and appropriate actions taken in accordance with VHA Handbook 1600.01, Business Associate Agreements. Absent an agreement to use or disclose protected health information, there is no business associate relationship. h. The contractor/subcontractor must store, transport, or transmit VA sensitive information in an encrypted form, using VA-approved encryption tools that are, at a minimum, FIPS 140-2 validated. i. The contractor/subcontractor's firewall and Web services security controls, if applicable, shall meet or exceed VA's minimum requirements. VA Configuration Guidelines are available upon request. j. Except for uses and disclosures of VA information authorized by this contract for performance of the contract, the contractor/subcontractor may use and disclose VA information only in two other situations: (i) in response to a qualifying order of a court of competent jurisdiction, or (ii) with VA's prior written approval. The contractor/subcontractor must refer all requests for, demands for production of, or inquiries about, VA information and information systems to the VA contracting officer for response. k. Notwithstanding the provision above, the contractor/subcontractor shall not release VA records protected by Title 38 U.S.C. 5705, confidentiality of medical quality assurance records and/or Title 38 U.S.C. 7332, confidentiality of certain health records pertaining to drug addiction, sickle cell anemia, alcoholism or alcohol abuse, or infection with human immunodeficiency virus. If the contractor/subcontractor is in receipt of a court order or other requests for the above mentioned information, that contractor/subcontractor shall immediately refer such court orders or other requests to the VA contracting officer for response. l. For service that involves the storage, generating, transmitting, or exchanging of VA sensitive information but does not require C&A or an MOU-ISA for system interconnection, the contractor/subcontractor must complete a Contractor Security Control Assessment (CSCA) on a yearly basis and provide it to the COTR. 4. INFORMATION SYSTEM DESIGN AND DEVELOPMENT a. Information systems that are designed or developed for or on behalf of VA at non-VA facilities shall comply with all VA directives developed in accordance with FISMA, HIPAA, NIST, and related VA security and privacy control requirements for Federal information systems. This includes standards for the protection of electronic PHI, outlined in 45 C.F.R. Part 164, Subpart C, information and system security categorization level designations in accordance with FIPS 199 and FIPS 200 with implementation of all baseline security controls commensurate with the FIPS 199 system security categorization (reference Appendix D of VA Handbook 6500, VA Information Security Program). During the development cycle a Privacy Impact Assessment (PIA) must be completed, provided to the COTR, and approved by the VA Privacy Service in accordance with Directive 6507, VA Privacy Impact Assessment. b. The contractor/subcontractor shall certify to the COTR that applications are fully functional and operate correctly as intended on systems using the VA Federal Desktop Core Configuration (FDCC), and the common security configuration guidelines provided by NIST or the VA. This includes Internet Explorer 7 configured to operate on Windows XP and Vista (in Protected Mode on Vista) and future versions, as required. c. The standard installation, operation, maintenance, updating, and patching of software shall not alter the configuration settings from the VA approved and FDCC configuration. Information technology staff must also use the Windows Installer Service for installation to the default "program files" directory and silently install and uninstall. d. Applications designed for normal end users shall run in the standard user context without elevated system administration privileges. e. The security controls must be designed, developed, approved by VA, and implemented in accordance with the provisions of VA security system development life cycle as outlined in NIST Special Publication 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems, VA Handbook 6500, Information Security Program and VA Handbook 6500.5, Incorporating Security and Privacy in System Development Lifecycle. f. The contractor/subcontractor is required to design, develop, or operate a System of Records Notice (SOR) on individuals to accomplish an agency function subject to the Privacy Act of 1974, (as amended), Public Law 93-579, December 31, 1974 (5 U.S.C. 552a) and applicable agency regulations. Violation of the Privacy Act may involve the imposition of criminal and civil penalties. g. The contractor/subcontractor agrees to: (1) Comply with the Privacy Act of 1974 (the Act) and the agency rules and regulations issued under the Act in the design, development, or operation of any system of records on individuals to accomplish an agency function when the contract specifically identifies: (a) The Systems of Records (SOR); and (b) The design, development, or operation work that the contractor/subcontractor is to perform; (1) Include the Privacy Act notification contained in this contract in every solicitation and resulting subcontract and in every subcontract awarded without a solicitation, when the work statement in the proposed subcontract requires the redesign, development, or operation of a SOR on individuals that is subject to the Privacy Act; and (2) Include this Privacy Act clause, including this subparagraph (3), in all subcontracts awarded under this contract which requires the design, development, or operation of such a SOR. h. In the event of violations of the Act, a civil action may be brought against the agency involved when the violation concerns the design, development, or operation of a SOR on individuals to accomplish an agency function, and criminal penalties may be imposed upon the officers or employees of the agency when the violation concerns the operation of a SOR on individuals to accomplish an agency function. For purposes of the Act, when the contract is for the operation of a SOR on individuals to accomplish an agency function, the contractor/subcontractor is considered to be an employee of the agency. (1) "Operation of a System of Records" means performance of any of the activities associated with maintaining the SOR, including the collection, use, maintenance, and dissemination of records. (2) "Record" means any item, collection, or grouping of information about an individual that is maintained by an agency, including, but not limited to, education, financial transactions, medical history, and criminal or employment history and contains the person's name, or identifying number, symbol, or any other identifying particular assigned to the individual, such as a fingerprint or voiceprint, or a photograph. (3) "System of Records" means a group of any records under the control of any agency from which information is retrieved by the name of the individual or by some identifying number, symbol, or other identifying particular assigned to the individual. i. The vendor shall ensure the security of all procured or developed systems and technologies, including their subcomponents (hereinafter referred to as "Systems"), throughout the life of this contract and any extension, warranty, or maintenance periods. This includes, but is not limited to workarounds, patches, hotfixes, upgrades, and any physical components (hereafter referred to as Security Fixes) which may be necessary to fix all security vulnerabilities published or known to the vendor anywhere in the Systems, including Operating Systems and firmware. The vendor shall ensure that Security Fixes shall not negatively impact the Systems. j. The vendor shall notify VA within 24 hours of the discovery or disclosure of successful exploits of the vulnerability which can compromise the security of the Systems (including the confidentiality or integrity of its data and operations, or the availability of the system). Such issues shall be remediated as quickly as is practical, but in no event longer than 3 Days. k. When the Security Fixes involve installing third party patches (such as Microsoft OS patches or Adobe Acrobat), the vendor will provide written notice to the VA that the patch has been validated as not affecting the Systems within 10 working days. When the vendor is responsible for operations or maintenance of the Systems, they shall apply the Security Fixes within 3 days. l. All other vulnerabilities shall be remediated as specified in this paragraph in a timely manner based on risk, but within 60 days of discovery or disclosure. Exceptions to this paragraph (e.g. for the convenience of VA) shall only be granted with approval of the contracting officer and the VA Assistant Secretary for Office of Information and Technology. 5. INFORMATION SYSTEM HOSTING, OPERATION, MAINTENANCE, OR USE a. For information systems that are hosted, operated, maintained, or used on behalf of VA at non-VA facilities, contractors/subcontractors are fully responsible and accountable for ensuring compliance with all HIPAA, Privacy Act, FISMA, NIST, FIPS, and VA security and privacy directives and handbooks. This includes conducting compliant risk assessments, routine vulnerability scanning, system patching and change management procedures, and the completion of an acceptable contingency plan for each system. The contractor's security control procedures must be equivalent, to those procedures used to secure VA systems. A Privacy Impact Assessment (PIA) must also be provided to the COTR and approved by VA Privacy Service prior to operational approval. All external Internet connections to VA's network involving VA information must be reviewed and approved by VA prior to implementation. b. Adequate security controls for collecting, processing, transmitting, and storing of Personally Identifiable Information (PII), as determined by the VA Privacy Service, must be in place, tested, and approved by VA prior to hosting, operation, maintenance, or use of the information system, or systems by or on behalf of VA. These security controls are to be assessed and stated within the PIA and if these controls are determined not to be in place, or inadequate, a Plan of Action and Milestones (POA&M) must be submitted and approved prior to the collection of PII. c. Outsourcing (contractor facility, contractor equipment or contractor staff) of systems or network operations, telecommunications services, or other managed services requires certification and accreditation (authorization) (C&A) of the contractor's systems in accordance with VA Handbook 6500.3, Certification and Accreditation and/or the VA OCS Certification Program Office. Government-owned (government facility or government equipment) contractor-operated systems, third party or business partner networks require memorandums of understanding and interconnection agreements (MOU-ISA) which detail what data types are shared, who has access, and the appropriate level of security controls for all systems connected to VA networks. d. The contractor/subcontractor's system must adhere to all FISMA, FIPS, and NIST standards related to the annual FISMA security controls assessment and review and update the PIA. Any deficiencies noted during this assessment must be provided to the VA contracting officer and the ISO for entry into VA's POA&M management process. The contractor/subcontractor must use VA's POA&M process to document planned remedial actions to address any deficiencies in information security policies, procedures, and practices, and the completion of those activities. Security deficiencies must be corrected within the timeframes approved by the government. Contractor/subcontractor procedures are subject to periodic, unannounced assessments by VA officials, including the VA Office of Inspector General. The physical security aspects associated with contractor/subcontractor activities must also be subject to such assessments. If major changes to the system occur that may affect the privacy or security of the data or the system, the C&A of the system may need to be reviewed, retested and re-authorized per VA Handbook 6500.3. This may require reviewing and updating all of the documentation (PIA, System Security Plan, Contingency Plan). The Certification Program Office can provide guidance on whether a new C&A would be necessary. e. The contractor/subcontractor must conduct an annual self-assessment on all systems and outsourced services as required. Both hard copy and electronic copies of the assessment must be provided to the COTR. The government reserves the right to conduct such an assessment using government personnel or another contractor/subcontractor. The contractor/subcontractor must take appropriate and timely action (this can be specified in the contract) to correct or mitigate any weaknesses discovered during such testing, generally at no additional cost. f. VA prohibits the installation and use of personally-owned or contractor/subcontractor-owned equipment or software on VA's network. If non-VA owned equipment must be used to fulfill the requirements of a contract, it must be stated in the service agreement, SOW or contract. All of the security controls required for government furnished equipment (GFE) must be utilized in approved other equipment (OE) and must be funded by the owner of the equipment. All remote systems must be equipped with, and use, a VA-approved antivirus (AV) software and a personal (host-based or enclave based) firewall that is configured with a VA-approved configuration. Software must be kept current, including all critical updates and patches. Owners of approved OE are responsible for providing and maintaining the anti-viral software and the firewall on the non-VA owned OE. g. All electronic storage media used on non-VA leased or non-VA owned IT equipment that is used to store, process, or access VA information must be handled in adherence with VA Handbook 6500.1, Electronic Media Sanitization upon: (i) completion or termination of the contract or (ii) disposal or return of the IT equipment by the contractor/subcontractor or any person acting on behalf of the contractor/subcontractor, whichever is earlier. Media (hard drives, optical disks, CDs, back-up tapes, etc.) used by the contractors/subcontractors that contain VA information must be returned to the VA for sanitization or destruction or the contractor/subcontractor must self-certify that the media has been disposed of per 6500.1 requirements. This must be completed within 30 days of termination of the contract. h. Bio-Medical devices and other equipment or systems containing media (hard drives, optical disks, etc.) with VA sensitive information must not be returned to the vendor at the end of lease, for trade-in, or other purposes. The options are: (1) Vendor must accept the system without the drive; (2) VA's initial medical device purchase includes a spare drive which must be installed in place of the original drive at time of turn-in; or (3) VA must reimburse the company for media at a reasonable open market replacement cost at time of purchase. (4) Due to the highly specialized and sometimes proprietary hardware and software associated with medical equipment/systems, if it is not possible for the VA to retain the hard drive, then; (a) The equipment vendor must have an existing BAA if the device being traded in has sensitive information stored on it and hard drive(s) from the system are being returned physically intact; and (b) Any fixed hard drive on the device must be non-destructively sanitized to the greatest extent possible without negatively impacting system operation. Selective clearing down to patient data folder level is recommended using VA approved and validated overwriting technologies/methods/tools. Applicable media sanitization specifications need to be pre-approved and described in the purchase order or contract. (c) A statement needs to be signed by the Director (System Owner) that states that the drive could not be removed and that (a) and (b) controls above are in place and completed. The ISO needs to maintain the documentation. 6. SECURITY INCIDENT INVESTIGATION a. The term "security incident" means an event that has, or could have, resulted in unauthorized access to, loss or damage to VA assets, or sensitive information, or an action that breaches VA security procedures. The contractor/subcontractor shall immediately notify the COTR and simultaneously, the designated ISO and Privacy Officer for the contract of any known or suspected security/privacy incidents, or any unauthorized disclosure of sensitive information, including that contained in system(s) to which the contractor/subcontractor has access. b. To the extent known by the contractor/subcontractor, the contractor/subcontractor's notice to VA shall identify the information involved, the circumstances surrounding the incident (including to whom, how, when, and where the VA information or assets were placed at risk or compromised), and any other information that the contractor/subcontractor considers relevant. c. With respect to unsecured protected health information, the business associate is deemed to have discovered a data breach when the business associate knew or should have known of a breach of such information. Upon discovery, the business associate must notify the covered entity of the breach. Notifications need to be made in accordance with the executed business associate agreement. d. In instances of theft or break-in or other criminal activity, the contractor/subcontractor must concurrently report the incident to the appropriate law enforcement entity (or entities) of jurisdiction, including the VA OIG and Security and Law Enforcement. The contractor, its employees, and its subcontractors and their employees shall cooperate with VA and any law enforcement authority responsible for the investigation and prosecution of any possible criminal law violation(s) associated with any incident. The contractor/subcontractor shall cooperate with VA in any civil litigation to recover VA information, obtain monetary or other compensation from a third party for damages arising from any incident, or obtain injunctive relief against any third party arising from, or related to, the incident. 7. LIQUIDATED DAMAGES FOR DATA BREACH a. Consistent with the requirements of 38 U.S.C. §5725, a contract may require access to sensitive personal information. If so, the contractor is liable to VA for liquidated damages in the event of a data breach or privacy incident involving any SPI the contractor/subcontractor processes or maintains under this contract. b. The contractor/subcontractor shall provide notice to VA of a "security incident" as set forth in the Security Incident Investigation section above. Upon such notification, VA must secure from a non-Department entity or the VA Office of Inspector General an independent risk analysis of the data breach to determine the level of risk associated with the data breach for the potential misuse of any sensitive personal information involved in the data breach. The term 'data breach' means the loss, theft, or other unauthorized access, or any access other than that incidental to the scope of employment, to data containing sensitive personal information, in electronic or printed form, that results in the potential compromise of the confidentiality or integrity of the data. Contractor shall fully cooperate with the entity performing the risk analysis. Failure to cooperate may be deemed a material breach and grounds for contract termination. c. Each risk analysis shall address all relevant information concerning the data breach, including the following: (1) Nature of the event (loss, theft, unauthorized access); (2) Description of the event, including: (a) date of occurrence; (b) data elements involved, including any PII, such as full name, social security number, date of birth, home address, account number, disability code; (3) Number of individuals affected or potentially affected; (4) Names of individuals or groups affected or potentially affected; (5) Ease of logical data access to the lost, stolen or improperly accessed data in light of the degree of protection for the data, e.g., unencrypted, plain text; (6) Amount of time the data has been out of VA control; (7) The likelihood that the sensitive personal information will or has been compromised (made accessible to and usable by unauthorized persons); (8) Known misuses of data containing sensitive personal information, if any; (9) Assessment of the potential harm to the affected individuals; (10) Data breach analysis as outlined in 6500.2 Handbook, Management of Security and Privacy Incidents, as appropriate; and (11) Whether credit protection services may assist record subjects in avoiding or mitigating the results of identity theft based on the sensitive personal information that may have been compromised. d. Based on the determinations of the independent risk analysis, the contractor shall be responsible for paying to the VA liquidated damages in the amount of $______ per affected individual to cover the cost of providing credit protection services to affected individuals consisting of the following: (1) Notification; (2) One year of credit monitoring services consisting of automatic daily monitoring of at least 3 relevant credit bureau reports; (3) Data breach analysis; (4) Fraud resolution services, including writing dispute letters, initiating fraud alerts and credit freezes, to assist affected individuals to bring matters to resolution; (5) One year of identity theft insurance with $20,000.00 coverage at $0 deductible; and (6) Necessary legal expenses the subjects may incur to repair falsified or damaged credit records, histories, or financial affairs. ? 8. SECURITY CONTROLS COMPLIANCE TESTING On a periodic basis, VA, including the Office of Inspector General, reserves the right to evaluate any or all of the security controls and privacy practices implemented by the contractor under the clauses contained within the contract. With 10 working-days' notice, at the request of the government, the contractor must fully cooperate and assist in a government-sponsored security controls assessment at each location wherein VA information is processed or stored, or information systems are developed, operated, maintained, or used on behalf of VA, including those initiated by the Office of Inspector General. The government may conduct a security control assessment on shorter notice (to include unannounced assessments) as determined by VA in the event of a security incident or at any other time. D.SPECIFIC MANDATORY TASKS AND ASSOCIATED DELIVERABLES: Description of Tasks and Associated Deliverables: The contractor shall provide the specific deliverables described below within the performance period stated in Section A.3 of this SOW. Task One: Provide all the hardware, software and telecommunications equipment required by VBA personnel to process Insurance Remittances on BancTec X350 hardware and software using customized VBA RPS software. Deliverable One: Access to the vendors site for VBA testing to assure that the vendor's equipment is compatible with BancTec X350 hardware and software. Provide VBA personnel with access to the site equipment so that they can process VBA remittances successfully and build acceptable transactions that process successfully against VBA mainframe records. Task Two: Access at the vendor's site and telecommunications hardware in order to determine that VBA personnel will be able to successfully transmit data to a remote VBA site Deliverable Two: VBA personnel will be able to remotely transfer data created at the vendor's site, using vendor supplied telecommunications hardware, to a remote VBA host. VBA personnel must be able to successfully transmit a data file to a remote VBA host and receive reports form the host. Task Three: The vendor must supply sufficient access to the vendor site and vendor supplied hardware in order for VBA personnel to conduct testing as well as VBA in the event that VBA personnel will need to conduct any actual recovery efforts. Deliverable Three: The contractor shall provide a schedule for VBA access to their site and hardware. A schedule for both VBA testing and scheduled times that VBA will have access to the site and equipment during any 24 hour period in the event a disaster. What prescheduled time that VBA personnel will be permitted on site in order to process their remittances on each and every workday. Task Four: For security reasons, the vendor must be able to demonstrate that all work created by VBA personnel during the course of testing and actual disaster recovery can be fully deleted and removed form any vendor hardware, software and telecommunications systems. Only VBA personnel can manage VBA data and a=only under the direct supervision of VBA employees and must be fully deleted when the operation is complete. Deliverable Four: The vendor must demonstrate to VBA personnel satisfaction that all data is only available to VBA personnel during processing operations and is fully deleted from all hardware, and telecommunications equipment once VBA personnel have completed their daily processing and transmission. E.EVALUATED OPTIONAL TASKS AND ASSOCIATED DELIVERABLES: N/A F.SCHEDULE FOR DELIVERABLES 1. Upon request throughout the term of the contract. 2. Unless otherwise specified, the number of draft copies and the number of final copies shall be the same. 3. If for any reason the scheduled time for a deliverable cannot be met, the contractor is required to explain why (include the original deliverable due date) in writing to the CO, including a firm commitment of when the work shall be completed. This notice to the CO shall cite the reasons for the delay, and the impact on the overall project. The CO will then review the facts and issue a response in accordance with applicable regulations. G.CHANGES TO STATEMENT OF WORK: Any changes to this SOW shall be authorized and approved only through written correspondence from the CO. A copy of each change will be kept in a project folder along with all other products of the project. Costs incurred by the contractor through the actions of parties other than the CO shall be borne by the contractor. H. REPORTING REQUIREMENTS: 1. The contractor shall demonstrate to the Contracting Officers Technical Representative (COTR) that all VBA reports can be retrieved form the remote VBA IT site. I. TRAVEL: Contractor travel is not anticipated at this time. If any travel is required it shall be reimbursed in accordance with VA/Federal Travel Regulations. I.NOTES: A.All questions, comments or concerns should be directed to Michael.Sherick@va.gov B.Submittals furnished will not be returned to the sender. No debriefs will be conducted. Eligibility in participating in a future acquisition does not depend upon a response to this notice. C.Proprietary information is neither requested nor desired. If such information is submitted, it must clearly be marked "proprietary" on every sheet containing such information, and the proprietary information must be segregated to the maximum extent practicable from other portions of the response (e.g., use an attachment or exhibit). II.TIMELINE : This request will close 5:00 p.m. 08/30/ 2013 eastern standard time. FAR Clause 52.215-3 Request for Information or Solicitation for Planning Purposes applies. Request for Information or Solicitation for Planning Purposes (Oct 1997) (a) The Government does not intend to award a contract on the basis of this solicitation or to otherwise pay for the information solicited except as an allowable cost under other contracts as provided in subsection 31.205-18, Bid and proposal costs, of the Federal Acquisition Regulation. (b) Although "proposal" and "offeror" are used in this Request for Information, your response will be treated as information only. It shall not be used as a proposal. (c) This solicitation is issued for the purpose of: Acquisition Planning. ? III.Requested information: Interested parties shall provide information to the Government as follows: A.Format: 1.MS Word or pdf format 2.Page limit -15 pages 3.Company name and Sources Sought/RFI number listed on each page 4.Proprietary information MUST be marked as such, on a page-by-page basis. B.Introduction: 1.Provide name of company, company address, a contact person's name, telephone number, fax number and email address. 2.CAGE code, and indicate if actively registered on System for award management (SAM) 3.Contractual vehicles the company holds, such as GSA schedules. 4.STATUS -NAICS Code. State the size of your company [e.g., 8(a) (including graduation date), HUBZone-certified small business, Service-Disabled Veteran-Owned small business, small business, large business, etc.]. ? Notes: 1. This Sources Sought/RFI is for planning purposes, and does not constitute a commitment, implied or otherwise, that a procurement action will follow. The Department of Veterans Affairs will use the information submitted in response to this notice at its discretion and will not provide comments to any submission; however, The Department of Veterans reserves the right to contact any respondent to this notice for the sole purpose of enhancing The Department of Veteran Affairs understanding of the notice submission. 2. The content of any responses to this notice may be reflected in any subsequent solicitation, except for content marked or designated as business confidential or proprietary which will be fully protected from release outside the government The Department of Veteran Affairs Contracting Office POC: Bonnie Robinson, Contracting Officer Eastern Area Contracting Team Email: Bonnnie.Robinson@va.gov DISCLAIMER This RFI is issued solely for information and planning purposes only and does not constitute a solicitation. All information received in response to this RFI that is marked as proprietary will be handled accordingly. In accordance with FAR 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Responders are solely responsible for all expenses associated with responding to this RFI.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/73259f0a508df0602ff278c60f3c16f6)
- Document(s)
- Attachment
- File Name: VA310-13-I-0007 VA310-13-I-0007_1.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=904036&FileName=VA310-13-I-0007-003.docx)
- Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=904036&FileName=VA310-13-I-0007-003.docx
- Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
- File Name: VA310-13-I-0007 VA310-13-I-0007_1.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=904036&FileName=VA310-13-I-0007-003.docx)
- Record
- SN03131717-W 20130801/130730235916-73259f0a508df0602ff278c60f3c16f6 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |