draft RX Framework PWS.docx

Performance Work Statement Veterans Integrated Service Network (VISN) 19 Document Storage Solution (DSS) RxFramework Omnicell Intravenous X (IVX)/ Inpatient Pharmacy Interface

1. BACKGROUND

1.1 The purpose of this requirement is to provide interface development, maintaining the interface, and a service level agreement (SLA) for the DSS RxFramework license at Salt Lake City (SLC) and Eastern Colorado (ECH) Veteran’s Affairs (VA) Health Care Systems. The DSS RxFramework license interfaces between Veterans Health Information System Technology Architecture (VistA)/ Computerized Patient Record System (CPRS) and Omnicenter, Omnicell Central Pharmacy Manager (CPM), and Omnicell IVX systems to allow for the automation of data flow using Health Level Seven (HL7) Messaging Standard. VISN 19 requires the DSS RxFramework Omnicell CPM/IVX/Inpatient interface license, subscription maintenance and support to include 24 hours per day - 7 days a week support coverage for bug fixes, minor release upgrades and telephone support.

1.2 The selected Contractor shall provide services, which include the installation of the DSS VistA integration software and license, RX Framework. The SLA shall include upgrades as needed from manufacturer, remote network support, unlimited 24x7 telephone support, and all licenses necessary for the software/interface to perform as intended by the manufacturer.

1.3 No physical equipment is required for usage of these interfaces between VistA and respective system: Omnicell IVX, Omnicell CPM, and Omnicenter.

1.4 Locations:

2. WORK HOURS

2.1 Hours of Operation: Normal business hours are Monday through Friday, 8:00 a.m. to 5:00 MST p.m., excluding holidays. Should the Contractor require work afterhours, the Contractor shall arrange in advance with the On-site Point of Contact (POC) and Contracting Officer’s Representative (COR).

3. PERIOD OF PERFORMANCE (POP):

3.1 The Base Year Period of Performance (POP) of this contract will be co-termed to pick up service on DSS RxFramework Omnicell IVX/Inpatient interfaces as VISN 19 facilities fall off existing contracts and/or warranty periods.

3.2 The period of performance shall be one (1) 12-month base period and four (4) 12-month option periods per the below:

POP

Optional (Omnicell Inpatient VistA Interface Software Subscription) 8/1/26-2/14/27

Optional 2/15/27-2/14/28

Optional 2/15/28-2/14/29

Optional 2/15/29-2/14/30

Optional 2/15/30-2/14/31

Optional

4. SPECIFICATIONS

4.1 Corrective Maintenance

4.1.1 The contract shall include all corrective (unplanned) maintenance/repair of the interfaces in accordance with the manufacturer’s specifications.

4.2 Updates/Patching

4.2.1 Contractor shall complete available updates to the software at the discretion of Healthcare Technology Management (HTM/biomed).

4.2.2 Contractor shall complete all patching according to manufacturer’s specifications.

4.2.3 Contractor shall ensure DSS RxFramework Omnicell IVX/Inpatient interfaces are installed and maintained per vendor specifications.

4.2.4 The Contractor will assist the Veteran’s Health `Affairs (VHA) Office of Information and Technology (OI&T) and HTM staff with keeping licensed products updated.

4.2.5 The Contractor shall track issues or complications with a software system that records and stores repair tickets/requests for the life of the contract including experienced issue, involved individuals, and resolutions. Tickets will be available to Veteran Affairs Medical Center (VAMC) upon request. Tickets created will be made available to VHA OI&T and/or HTM staff using live reporting with summaries of previous 30 or seven days as well as summaries of tickets open, closed, current status, and expected resolution date. Upon ticket creation, the Contractor shall assist VHA OI&T/biomed staff configure the necessary licensed products to meet end-users needs. The Contractor will also keep site VAMC end users aware of issues that may impact their usage of licensed products through a Self-Service Portal.

4.3 Response Time

4.3.1 Contractor shall respond to trouble calls in a priority order submitted via a secure support portal or via telephone.

4.3.2 Tickets shall be assessed and rated as Urgent, High Priority, Normal, and Low.

4.3.2.1 Urgent-A catastrophic incident of an operating environment where production systems are severely impacted, down, or not functioning. Or an issue exists that may affect patient safety. A critical case requires continuous 24/7 attention until resolved.

4.3.2.2 High-a problem where a system is functioning but in a severely reduced capacity. Causing significant impact to portions of the business operations and productivity.

4.3.2.3 Normal-involves partial non-critical functionality loss. Impairs some operations but allows the user or an application to continue to function.

4.3.2.4 Low-no impact on the quality, performance or functionality of the system. Minimal organizational or business impact.

4.3.2.5 The response times for each priority are below:

4.3.3 Contractor shall work with biomedical engineering and respective OI&T and clinical stakeholders to address issues with the DSS RxFramework Omnicell IVX/Inpatient VistA interfaces.

4.4 Reporting

4.4.1 Contractor shall provide a copy of the service report to the site POC within five working days after completion of any services.

4.4.2 Contractor shall provide, upon request, summaries of tickets, incidents, service requests, known bugs/errors and remediation plans, etc. on the DSS RxFramework Omnicell IVX/Inpatient VistA interfaces.

4.4.3 Service reports shall include identifying information about all services provided, any issues found, the technician/engineer names of the personnel performing work, and the date service was provided.

4.5 Remote Support

4.5.1 The Contractor shall provide a telephone line and/or service support portal available 24/7 for technical support.

4.5.2 If remote support via site-to-site virtual private network (VPN) is required, Contractor shall work with the COR and the facility Information Security Officer (ISO) to meet the requirements prior to connection. A National Site to Site Memorandum of Understanding/Interconnection Security Agreement (MOU/ISA) is the preferred way to complete this connection. If one already exists, then the vendor shall maintain it for the life of this contract.

4.6 Patient Health Information

4.6.1 The Contractor shall safeguard patient health information.

4.6.2 The Contractor shall report to the onsite HTM and COR any issues with disclosed or unsecure patient health information.

4.7 Contractor Requirements

4.7.1 All Contractor personnel performing interface implementation services shall have DSS training and experience in the deployment and sustainment of DSS RxFramework Omnicell IVX/Inpatient VistA interfaces.

4.7.2 The contractor must work with VA OIT or HTM staff for any system updates, upgrades, or maintenance.

5. CLIN STRUCTURE

CLIN 0006: Optional Qty 12 Months: DSS-INST-R Qty 12 Months: DSSRX-Omni-P Eastern Colorado

6. PERFORMANCE/QUALITY STANDARDS

The contractor performance shall be evaluated in accordance with the Performance Standards outlined in the table below.

6.1.1 End-users, Onsite POC and Onsite HTM, and/or the COR shall perform system verification tests to ensure the system is fully functional following service/repairs.

6.1.2 Issues with the quality of the Contractor’s work will be communicated through the Contracting Officer to the Contractor point of contact for resolution.

6.1.3 Documentation with be completed in the Government systems.

6.1.4 The Contractor performance shall be evaluated based on the below performance standard and acceptable levels of performance associated with this effort:

· Efficient and effective in meeting requirements

· Meets technical needs and mission requirements.

· Provides quality services/products.

· Performs service needs and repairs timely.

· Notifies customer in advance of potential problems and upcoming maintenance actions

90% of response times are within the time period specified in section 4.3.

90% of reports are submitted on time as outlined in section 4.4.

· Personnel possess necessary knowledge, tools, skills, and abilities to perform tasks.

· Issues resolved

· Integration and coordination of all activities to execute effort.

Satisfactory or higher

Acceptable Performance: The Government shall document positive or negative performance. Any report may become a part of the supporting documentation for any contractual action.

Unacceptable Performance: When unacceptable performance occurs, the COR shall work with the Contracting Officer (CO) inform the contractor. This will normally be in writing unless circumstances necessitate verbal communication. In any case, the COR shall document the discussion and place it in the COR file.

To assure that the contractor receives impartial, fair, and equitable treatment under this contract, the COR will work with the contractor to increase performance to an acceptable level. When the COR and CO determines formal written communication is required, the COR and CO shall prepare a Notification (Letter or Concern (LOC), Cure Notice, Show Cause Notice) and present it to the Contractor.

1. The contractor shall acknowledge receipt of the LOC Notice in writing.

2. The LOC will specify if the contractor is required to prepare a corrective action plan (CAP) to document how the contractor shall correct the unacceptable performance and avoid a recurrence. The Notice will also state how long after receipt the contractor shall present this corrective action plan to the CO.

3. The Government shall review the contractor's corrective action plan to determine acceptability.

Any Notice may become a part of the supporting documentation for any contractual action deemed necessary by the CO.

7. APPENDIX C — VA INFORMATION AND INFORMATION SYSTEM SECURITY AND GENERALVA INFORMATION CUSTODIAL LANGUAGE.

7.1 The Government shall receive unlimited rights to data/intellectual property first produced and delivered in the performance of this contract or order (hereinafter “contract”) unless expressly stated otherwise in this contract. This includes all rights to source code and all documentation created in support thereof. The primary clause used to define Government and Contractor data rights is FAR 52.227-14 Rights in Data – General. The primary clause used to define computer software license (not data/intellectual property first produced under this contractor or order) is FAR 52.227-19, Commercial Computer Software License.

7.2 Information made available to the contractor by VA for the performance or administration of this contract will be used only for the purposes specified in the service agreement, SOW, PWS, PD, and/or contract. The contractor shall not use VA information in any other manner without prior written approval from a VA Contracting Officer (CO). The primary clause used to define Government and Contractor data rights is FAR 52.227-14 Rights in Data – General.

7.3 VA information will not be co-mingled with any other data on the contractor’s information systems or media storage systems. The contractor shall ensure compliance with Federal and VA requirements related to data protection, data encryption, physical data segregation, logical data segregation, classification requirements and media sanitization.

7.4 VA reserves the right to conduct scheduled or unscheduled audits, assessments, or investigations of contractor Information Technology (IT) resources to ensure information security is compliant with Federal and VA requirements. The contractor shall provide all necessary access to records (including electronic and documentary materials related to the contracts and subcontracts) and support (including access to contractor and subcontractor staff associated with the contract) to VA, VA’s Office Inspector General (OIG),and/or Government Accountability Office (GAO) staff during periodic control assessments, audits, or investigations.

7.5 The contractor may only use VA information within the terms of the contract and applicable Federal law, regulations, and VA policies. If new Federal information security laws, regulations or VA policies become applicable after execution of the contract, the parties agree to negotiate contract modification and adjustment necessary to implement the new laws, regulations, and/or policies.

7.6 The contractor shall not make copies of VA information except as specifically authorized and necessary to perform the terms of the contract. If copies are made for restoration purposes, after the restoration is complete, the copies shall be destroyed in accordance with VA Directive 6500, VA Cybersecurity Program and VA Information Security Knowledge Service.

7.7 If a Veterans Health Administration (VHA) contract is terminated for default or cause with a business associate, the related local Business Associate Agreement (BAA) shall also be terminated and actions taken in accordance with VHA Directive 1605.05, Business Associate Agreements. If there is an executed national BAA associated with the contract, VA will determine what actions are appropriate and notify the contactor.

7.8 The contractor shall store and transmit VA sensitive information in an encrypted form, using VA-approved encryption tools which are, at a minimum, Federal Information Processing Standards (FIPS) 140-2, Security Requirements for Cryptographic Modules (or its successor) validated and in conformance with VA Information Security Knowledge Service requirements. The contractor shall transmit VA sensitive information using VA approved Transport Layer Security (TLS) configured with FIPS based cipher suites in conformance with National Institute of Standards and Technology (NIST) 800-52, Guidelines for the Selection, Configuration and Use of Transport Layer Security (TLS) Implementations.

7.9 The contractor’s firewall and web services security controls, as applicable, shall meet or exceed VA’s minimum requirements.

7.10 Except for uses and disclosures of VA information authorized by this contract for performance of the contract, the contractor may use and disclose VA information only in two situations: (i) in response to a qualifying order of a court of competent jurisdiction after notification to VA CO (ii) with written approval from the VA CO. The contractor shall refer all requests for, demands for production of or inquiries about, VA information and information systems to the VA CO for response.

7.11 Notwithstanding the provision above, the contractor 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 medical records pertaining to drug addiction, sickle cell anemia, alcoholism or alcohol abuse or infection with Human Immunodeficiency Virus (HIV). If the contractor is in receipt of a court order or other requests for the abovementioned information, the contractor shall immediately refer such court order or other requests to the VA CO for response.

7.12 Information made available to the contractor by VA for the performance or administration of this contract or information developed by the contractor in performance or administration of the contract will be protected and secured in accordance with VA Directive 6500 and Identity and Access Management (IAM) Security processes specified in the VA Information Security Knowledge Service.

7.13 Any data destruction done on behalf of VA by a contractor shall be done in accordance with National Archives and Records Administration (NARA) requirements as outlined in VA Directive 6300, Records and Information Management, VA Handbook 6300.1, Records Management Procedures, and applicable VA Records Control Schedules.

7.14 The contractor shall provide its plan for destruction of all VA data in its possession according to VA Directive 6500 and NIST 800-88, Guidelines for Media Sanitization prior to termination or completion of this contract. If directed by the COR/CO, the contractor shall return all Federal Records to VA for disposition.

7.15 Any media, such as paper, magnetic tape, magnetic disks, solid state devices or optical discs that is used to store, process, or access VA information that cannot be destroyed shall be returned to VA.The contractor shall hold the appropriate material until otherwise directed by the Contracting Officer’s Representative (COR) or CO. Items shall be returned securely via VA-approved methods. VA sensitive information must be transmitted utilizing VA-approved encryption tools which are validated under FIPS 140-2 (or its successor) and NIST 800-52. If mailed, the contractor shall send via a trackable method (USPS, UPS, FedEx, etc.) and immediately provide the COR/CO with the tracking information. Self-certification by the contractor that the data destruction requirements above have been met shall be sent to the COR/CO within 30 business days of termination of the contract.

7.16 All electronic storage media (hard drives, optical disks, CDs, back-up tapes, etc.) used to store, process or access VA information will not be returned to the contractor at the end of lease, loan, or trade-in. Exceptions to this paragraph will only be granted with the written approval of the VA CO.

8. ACCESS TO VA INFORMATION AND VA INFORMATION SYSTEMS.

8.1 A contractor/subcontractor shall request logical (technical) or physical access to VA information and VA information systems for their employees and subcontractors only to the extent necessary to perform the services specified in the solicitation or contract. This includes indirect entities, both affiliate of contractor/subcontractor and agent of contractor/subcontractor.

8.2 Contractors and subcontractors shall sign the VA Information Security Rule of Behavior (ROB) before access is provided to VA information and information systems (see Section 4, Training, below). The ROB contains the minimum user compliance requirements and does not supersede any policies of VA facilities or other agency components which provide higher levels of protection to VA’s information or information systems. Users who require privileged access shall complete the VA elevated privilege access request processes before privileged access is granted.

8.3 All contractors and subcontractors working with VA information are subject to the same security investigative and clearance 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 shall be in accordance with VA Directive and Handbook 0710, Personnel Suitability and Security Program. The Office of Human Resources and Administration/Operations, Security and Preparedness (HRA/OSP) is responsible for these policies and procedures. Contract personnel who require access to classified information or information systems shall have an appropriate security clearance. Verification of a Security Clearance shall be processed through the Special Security Officer located in HRA/OSP. Contractors shall conform to all requirements stated in the National Industrial Security Program Operating Manual (NISPOM).

8.4 All contractors and subcontractors shall comply with conditions specified in VAAR 852.204-71(d); Contractor operations required to be in United States. All contractors and subcontractors working with VA information must be permanently located within a jurisdiction subject to the law of the United States or its Territories to the maximum extent feasible. If services are proposed to be performed abroad the contractor must state where all non-U.S. services are provided. The contractor shall deliver to VA a detailed plan specifically addressing communications, personnel control, data protection and potential legal issues. The plan shall be approved by the COR/CO in writing prior to access being granted.

8.5 The contractor shall notify the COR/CO in writing immediately (no later than 24 hours) after personnel separation or occurrence of other causes. Causes may include the following:

8.5.1 Contractor/subcontractor personnel no longer has a need for access to VA

8.5.2 Contractor/subcontractor personnel are terminated, suspended, or otherwise has their work on a VA project discontinued for any reason.

8.5.3 Contractor believes their own personnel or subcontractor personnel may pose a threat to their company’s working environment or to any companyowned property. This includes contractor-owned assets, buildings, confidential data, customers, employees, networks, systems, trade secrets and/or VA data.

8.5.4 Any previously undisclosed changes to contractor/subcontractor background history are brought to light, including but not limited to changes to background investigation or employee record.

8.5.5 Contractor/subcontractor personnel have their authorization to work in the United States revoked.

8.5.6 Agreement by which contractor provides products and services to VA has either been fulfilled or terminated, such that VA can cut off electronic and/or physical access for contractor personnel.

8.6 In such cases of contract fulfillment, termination, or other causes; the contractor shall take the necessary measures to immediately revoke access to VA network, property, information, and information systems (logical and physical) by contractor/subcontractor personnel. These measures include (but are not limited to): removing and then securing Personal Identity Verification (PIV) badges and PIV – Interoperable (PIV-I) access badges, VA-issued photo badges, credentials for VA facilities and devices, VA-issued laptops, and authentication tokens. Contractors shall notify the appropriate VA COR/CO immediately to initiate access removal.

8.7 Contractors/subcontractors who no longer require VA accesses will return VAissued property to VA. This property includes (but is not limited to): documents, electronic equipment, keys, and parking passes. PIV and PIV-I access badges shall be returned to the nearest VA PIV Badge Issuance Office. Once they have had access to VA information, information systems, networks and VA property in their possessions removed, contractors shall notify the appropriate VA COR/CO.

9. TRAINING.

9.1 All contractors and subcontractors requiring access to VA information and VA information systems shall successfully complete the following before being granted access to VA information and its systems:

9.1.1 VA Privacy and Information Security Awareness and Rules of Behavior course (Talent Management System (TMS) #10176) initially and annually

9.1.2 Sign and acknowledge (electronically through TMS #10176) understanding of and responsibilities for compliance with the Organizational Rules of Behavior, relating to access to VA information and information systems initially and annually thereafter; and

9.1.3 Successfully complete any additional cyber security or privacy training, as required for VA personnel with equivalent information system or information access [to be defined by the VA program official and provided to the VA CO for inclusion in the solicitation document – i.e., any rolebased information security training].

9.2 The contractor shall provide to the COR/CO a copy of the training certificates and certification of signing the Organizational Rules of Behavior for each applicable employee within five days of the initiation of the contract and annually thereafter, as required.

9.3 Failure to complete the mandatory annual training is grounds for suspension or termination of all physical or electronic access privileges and removal from work on the contract until such time as the required training is complete.

10. SECURITY INCIDENT INVESTIGATION.

10.1 The contractor, subcontractor, their employees, or business associates shall immediately (within one hour) report suspected security / privacy incidents to the VA OIT’s Enterprise Service Desk (ESD) by calling (855) 673-4357 (TTY: 711). The ESD is OIT’s 24/7/365 single point of contact for IT-related issues.

10.2 After reporting to the ESD, the contractor, subcontractor, their employees, or business associates shall, within one hour, provide the COR/CO the incident number received from the ESD.

10.3 To the extent known by the contractor/subcontractor, the contractor/ subcontractor’s notice to VA shall identify the information involved and the circumstances surrounding the incident, including the following:

10.3.1 The date and time (or approximation of) the Security Incident occurred.

10.3.2 The names of individuals involved (when applicable).

10.3.3 The physical and logical (if applicable) location of the incident.

10.3.4 Why the Security Incident took place (i.e., catalyst for the failure).

10.3.5 The amount of data belonging to VA believed to have been compromised.

10.3.6 The remediation measures the contractor is taking to ensure no future

10.4 After the contractor has provided the initial detailed incident summary to VA, they will continue to provide written updates on any new and relevant circumstances or facts they discover. The contractor, subcontractor, and their employes shall fully cooperate with VA or third-party entity performing an independent risk analysis on behalf of VA. Failure to cooperate may be deemed a material breach and grounds for contract termination.

10.5 VA IT contractors shall follow VA Handbook 6500, Risk Management Framework for VA Information Systems VA Information Security Program, and VA Information Security Knowledge Service guidance for implementing an Incident Response Plan or integrating with an existing VA implementation.

10.6 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 the VA Office of 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.

10.7 The contractor shall comply with VA Handbook 6500.2, Management of Breaches Involving Sensitive Personal Information, which establishes the breach management policies and assigns responsibilities for the oversight, management and reporting procedures associated with managing of breaches.

10.8 With respect to unsecured Protected Health Information (PHI), the contractor is deemed to have discovered a data breach when the contractor knew or should have known of breach of such information. When a business associate is part of VHA contract, notification to the covered entity (VHA) shall be made in accordance with the executed BAA.

10.9 If the contractor or any of its agents fails to protect VA sensitive personal information or otherwise engages in conduct which results in a data breach involving any VA sensitive personal information the contractor/subcontractor processes or maintains under the contract; the contractor shall pay liquidated damages to the VA as set forth in clause 852.211-76, Liquidated Damages—Reimbursement for Data Breach Costs.

11. INFORMATION SYSTEM HOSTING, OPERATION, MAINTENANCE OR USE.

11.1 This entire section applies to information systems, systems, major applications, minor applications, enclaves, and platform information technologies (cloud and noncloud)hosted, operated, maintained, or used on behalf of VA at non-VA facilities.

11.2 The contractor shall comply with all Federal laws, regulations, and VA policies for Information systems (cloud and non-cloud) that are hosted, operated, maintained, or used on behalf of VA at non-VA facilities. Security controls for collecting, processing, transmitting, and storing of VA sensitive information, must be in place. The controls will be tested by VA or a VA sanctioned 3PAO and approved by VA prior to hosting, operation, maintenance or use of the information system or systems by or on behalf of VA. This includes conducting compliance risk assessments, security architecture analysis, routine vulnerability scanning, system patching, change management procedures and the completion of an acceptable contingency plan for each system. The contractor’s security control procedures shall be the same as procedures used to secure VA-operated information systems.

11.3 Outsourcing (contractor facility, equipment, or staff) of systems or network operations, telecommunications services or other managed services require Assessment and Authorization (A&A) of the contractor’s systems in accordance with VA Handbook 6500 as specified in VA Information Security Knowledge Service. Major changes to the A&A package may require reviewing and updating all the documentation associated with the change. The contractor’s cloud computing systems shall comply with FedRAMP and VA Directive 6517 requirements.

11.4 The contractor shall return all electronic storage media (hard drives, optical disks, CDs, back-up tapes, etc.) on non-VA leased or non-VA owned IT equipment used to store, process or access VA information to VA in accordance with A&A package requirements. This applies when the contract is terminated or completed and prior to disposal of media. The contractor shall provide its plan for destruction of all VA data in its possession according to VA Information Security Knowledge Service requirements and NIST 800-88. The contractor shall send a self-certification that the data destruction requirements above have been met to the COR/CO within 30 business days of termination of the contract.

11.5 All external internet connections to VA network involving VA information must be in accordance with VA Trusted Internet Connection (TIC) Reference Architecture and VA Directive and Handbook 6513, Secure External Connections and reviewed and approved by VA prior to implementation. Government-owned contractor-operated systems, third party or business partner networks require a Memorandum of understanding (MOU) and Interconnection Security Agreements (ISA).

11.6 Contractor procedures shall be subject to periodic, announced, or unannounced assessments by VA officials, the OIG or a 3PAO. The physical security aspects associated with contractor activities are also subject to such assessments. The contractor shall report, in writing, any deficiencies noted during the above assessment to the VA COR/CO. The contractor shall use VA’s defined processes to document planned remedial actions that address identified deficiencies in information security policies, procedures, and practices. The contractor shall correct security deficiencies within the timeframes specified in the VA Information Security Knowledge Service.

11.7 All major information system changes which occur in the production environment shall be reviewed by the VA to determine the impact on privacy and security of the system. Based on the review results, updates to the Authority to Operate (ATO) documentation and parameters may be required to remain in compliance with VA Handbook 6500 and VA Information Security Knowledge Service requirements.

11.8 The contractor shall conduct an annual privacy and security self-assessment on all information systems and outsourced services as required. Copies of the assessment shall be provided to the COR/CO. The VA/Government reserves the right to conduct assessment using government personnel or a third-party if deemed necessary. The contractor shall correct or mitigate any weaknesses

11.9 VA prohibits the installation and use of personally owned or contractor-owned equipment or software on VA information systems. If non-VA owned equipment must be used to fulfill the requirements of a contract, it must be stated in the service agreement, SOW, PWS, PD or contract. All security controls required for government furnished equipment must be utilized in VA approved Other Equipment (OE). Configuration changes to the contractor OE, must be funded by the owner of the equipment. All remote systems must use a VA-approved antivirus software and a personal (host-based or enclave based) firewall with a VA-approved configuration. The contractor shall ensure software on OE is kept current with all critical updates and patches. Owners of approved OE are responsible for providing and maintaining the anti-virus software and the firewall on the non-VA owned OE. Approved contractor OE will be subject to technical inspection at any time.

11.10 The contractor shall notify the COR/CO within one hour of disclosure or successful exploits of any vulnerability which can compromise the confidentiality, integrity, or availability of the information systems. The system or effected component(s) need(s) to be isolated from the network. A forensic analysis needs to be conducted jointly with VA. Such issues will be remediated as quickly as practicable, but in no event longer than the timeframe specified by VA Information Security Knowledge Service. If sensitive personal information is compromised reference VA Handbook 6500.2 and Section 5, Security Incident Investigation.

11.11 For cases wherein the contractor discovers material defects or vulnerabilities impacting products and services they provide to VA, the contractor shall develop and implement policies and procedures for disclosure to VA, as well as remediation. The contractor shall, within 30 business days of discovery, document a summary of these vulnerabilities or defects. The documentation will include a description of the potential impact of each vulnerability and material defect, compensating security controls, mitigations, recommended corrective actions, root cause analysis and/or workarounds (i.e., monitoring). Should there exist any backdoors in the products or services they provide to VA (referring to methods for bypassing computer authentication), the contractor shall provide the VA CO/CO written assurance they have permanently remediated these backdoors.

11.12 All other vulnerabilities, including those discovered through routine scans or other assessments, will be remediated based on risk, in accordance with the remediation timelines specified by the VA Information Security Knowledge Service and/or the applicable timeframe mandated by Cybersecurity & Infrastructure Security Agency (CISA) Binding Operational Directive (BOD) 22-01 and BOD 19-02 for Internet-accessible systems. Exceptions to this paragraph will only be granted with the approval of the COR/CO.

12. SECURITY AND PRIVACY CONTROLS COMPLIANCE TESTING, ASSESSMENT AND AUDITING.

12.1 Should VA request it, the contractor shall provide a copy of their (corporation’s, sole proprietorship’s, partnership’s, limited liability company (LLC), or other business structure entity’s) policies, procedures, evidence and independent report summaries related to specified cybersecurity frameworks (International Organization for Standardization (ISO), NIST Cybersecurity Framework (CSF), etc.). VA or its third-party/partner designee (if applicable) are further entitled to perform their own audits and security/penetration tests of the contractor’s IT or systems and controls, to ascertain whether the contractor is complying with the information security, network or system requirements mandated in the agreement between VA and the contractor.

12.2 Any audits or tests of the contractor or third-party designees/partner VA elects to carry out will commence within 30 business days of VA notification. Such audits, tests and assessments may include the following: (a): security/penetration tests which both sides agree will not unduly impact contractor operations; (b): interviews with pertinent stakeholders and practitioners; ©: document review; and (d): technical inspections of networks and systems the contractor uses to destroy, maintain, receive, retain, or use VA information.

12.3 As part of these audits, tests and assessments, the contractor shall provide all information requested by VA. This information includes, but is not limited to, the following: equipment lists, network or infrastructure diagrams, relevant policy documents, system logs or details on information systems accessing, transporting, or processing VA data.

12.4 The contractor and at its own expense, shall comply with any recommendations resulting from VA audits, inspections and tests. VA further retains the right to view any related security reports the contractor has generated as part of its own security assessment. The contractor shall also notify VA of the existence of any such security reports or other related assessments, upon completion and validation.

12.5 VA appointed auditors or other government agency partners may be granted access to such documentation on a need-to-know basis and coordinated through the COR/CO. The contractor shall comply with recommendations which result from these regulatory assessments on the part of VA regulators and associated government agency partners.

13. PRODUCT INTEGRITY, AUTHENTICITY, PROVENANCE, ANTI-COUNTERFEIT AND ANTI-TAMPERING.

13.1 The contractor shall comply with Code of Federal Regulations (CFR) Title 15 Part 7, “Securing the Information and Communications Technology and Services (ICTS) Supply Chain”, which prohibits ICTS Transactions from foreign adversaries. ICTS Transactions are defined as any acquisition, importation, transfer, installation, dealing in or use of any information and communications technology or service, including ongoing activities, such as managed services, data transmission, software updates, repairs or the platforming or data hosting of applications for consumer download.

13.2 When contracting terms require the contractor to procure equipment, the contractor shall purchase or acquire the equipment from an Original Equipment Manufacturer (OEM) or an authorized reseller of the OEM. The contractor shall attest that equipment procured from an OEM or authorized reseller or distributor are authentic. If procurement is unavailable from an OEM or authorized reseller, the contractor shall submit in writing, details of the circumstances prohibiting this from happening and procure a product waiver from the VA COR/CO.

13.3 All contractors shall establish, implement, and provide documentation for risk management practices for supply chain delivery of hardware, software (to include patches) and firmware provided under this agreement. Documentation will include chain of custody practices, inventory management program, information protection practices, integrity management program for sub-supplier provided components, and replacement parts requests. The contractor shall make spare parts available. All contractor(s) shall specify how digital delivery for procured products, including patches, will be validated and monitored to ensure consistent delivery. The contractor shall apply encryption technology to protect procured products throughout the delivery process.

13.4 If a contractor provides software or patches to VA, the contractor shall publish or provide a hash conforming to the FIPS Security Requirements for Cryptographic Modules (FIPS 140-2 or successor).

13.5 The contractor shall provide a software bill of materials (SBOM) for procured (to include licensed products) and consist of a list of components and associated metadata which make up the product. SBOMs must be generated in one of the data formats defined in the National Telecommunications and Information Administration (NTIA) report “The Minimum Elements for a Software Bill of Materials (SBOM).”

13.6 Contractors shall use or arrange for the use of trusted channels to ship procured products, such as U.S. registered mail and/or tamper-evident packaging for physical deliveries.

13.7 Throughout the delivery process, the contractor shall demonstrate a capability for detecting unauthorized access (tampering).

13.8 The contractor shall demonstrate chain-of-custody documentation for procured products and require tamper-evident packaging for the delivery of this.

14. VIRUSES, FIRMWARE AND MALWARE.

14.1 The contractor shall execute due diligence to ensure all provided software and patches, including third-party patches, are free of viruses and/or malware before releasing them to or installing them on VA information systems.

14.2 The contractor warrants it has no knowledge of and did not insert, any malicious virus and/or malware code into any software or patches provided to VA which could potentially harm or disrupt VA information systems. The contractor shall use due diligence, if supplying third-party software or patches, to ensure the third-party has not inserted any malicious code and/or virus which could damage or disrupt VA information systems.

14.3 The contractor shall provide or arrange for the provision of technical justification as to why any “false positive” hit has taken place to ensure their code’s supply chain has not been compromised. Justification may be required, but is not limited to, when install files, scripts, firmware, or other contractor-delivered software solutions (including third-party install files, scripts, firmware, or other software) are flagged as malicious, infected, or suspicious by an anti-virus vendor.

14.4 The contractor shall not upload (intentionally or negligently) any virus, worm, malware or any harmful or malicious content, component and/or corrupted data/source code (hereinafter “virus or other malware”) onto VA computer and information systems and/or networks. If introduced (and this clause is violated), upon written request from the VA CO, the contractor shall:

14.4.1 Take all necessary action to correct the incident, to include any and all assistance to VA to eliminate the virus or other malware throughout VA’s information networks, computer systems and information systems; and

14.4.2 Use commercially reasonable efforts to restore operational efficiency and remediate damages due to data loss or data integrity damage, if the virus or other malware causes a loss of operational efficiency, data loss, or damage to data integrity.

15. PATCHING GOVERNANCE.

15.1 The contractor shall provide documentation detailing the patch management, vulnerability management, mitigation and update processes (to include thirdparty) prior to the connection of electronic devices, assets or equipment to VA’s assets. This documentation will include information regarding the follow:

15.2 The resources and technical capabilities to sustain the program or process (e.g., how the integrity of a patch is validated by VA); and The approach and capability to remediate newly reported zero-day vulnerabilities for contractor products.

15.3 The contractor shall verify and provide documentation all procured products (including third-party applications, hardware, software, operating systems, and firmware) have appropriate updates and patches installed prior to delivery to VA.

15.4 The contractor shall provide or arrange the provision of appropriate software and firmware updates to remediate newly discovered vulnerabilities or weaknesses for their products and services within 30 days of discovery. Updates to remediate critical or emergent vulnerabilities will be provided within seven business days of discovery. If updates cannot be made available by contractor within these time periods, the contractor shall submit mitigations, methods of exploit detection and/or workarounds to the COR/CO prior to the above deadlines.

15.5 The contractor shall provide or arrange for the provision of appropriate hardware, software and/or firmware updates, when those products, including open-source software, are provided to the VA, to remediate newly discovered vulnerabilities or weaknesses. Remediations of products or services provided to the VA’s system environment must be provided within 30 business days of availability from the original supplier and/or patching source. Updates to remediate critical vulnerabilities applicable to the Contractor’s use of the third party product in its system environment will be provided within seven business days of availability from the original supplier and/or patching source. If applicable third-party updates cannot be integrated, tested and made available by Contractor within these time periods, mitigations and/or workarounds will be provided to the COR/CO before the above deadlines.

16. SPECIALIZED DEVICES/SYSTEMS (MEDICAL DEVICES, SPECIAL PURPOSE

16.1 Contractor supplies/delivered Medical Devices, Special Purpose Systems-Operational Technology (SPS-OT) and Research Scientific Computing Devices shall comply with all applicable Federal law, regulations, and VA policies. New developments require creation, testing, evaluation, and authorization in compliance with processes specified on the Specialized Device Cybersecurity Department Enterprise Risk Management (SDCD-ERM) Portal, VA Directive 6550, Pre-Procurement Assessment and Implementation of Medical

16.2 Devices/Systems, VA Handbook 6500, and the VA Information Security Knowledge Service. Deviations from Federal law, regulations, and VA Policy are identified and documented as part of VA Directive 6550 and/or the VA Enterprise Risk Analysis (ERA) processes for Specialized Devices/Systems processes.

16.3 All contractors and third-party service providers shall address and/or integrate applicable VA Handbook 6500 and Information Security Knowledge Service specifications in delivered IT systems/solutions, products and/or services. If systems/solutions, products and/or services do not directly match VA security requirements, the contractor shall work though the COR/CO for governance or resolution.

16.4 The contractor shall certify to the COR/CO that devices/systems that have completed the VA Enterprise Risk Analysis (ERA) process for Specialized Devices/Systems are fully functional and operate correctly as intended. Devices/systems must follow the VA ERA authorized configuration prior to acquisition and connection to the VA computing environment. If VA determines a new VA ERA needs to be created, the contractor shall provide required technical support to develop the configuration settings. Major changes to a previously approved device/system will require a new ERA.

16.5 The contractor shall comply with all practices documented by the Food Drug and Administration (FDA) Premarket Submission for Management of Cybersecurity in Medical Devices and Post market Management of Cybersecurity in Medical Devices.

16.6 The contractor shall design devices capable of accepting all applicable security patches with or without the support of the contractor personnel. If patching can only be completed by the contractor, the contractor shall commit the resources needed to patch all applicable devices at all VA locations. If unique patching instructions or packaging is needed, the contractor shall provide the necessary information in conjunction with the validation/testing of the patch. The contractor shall apply security patches within 30 business days of the patch release and have a formal tracking process for any security patches not implemented to include explanation when a device cannot be patched.

16.7 The contractor shall provide devices able to install and maintain VA-approved antivirus capabilities with the capability to quarantine files and be updated as needed in response to incidents. Alternatively, a VA-approved whitelisting application may be used when the contractor cannot install an anti-virus / antimalware application.

16.8 The contractor shall verify and document all software embedded within the device does not contain any known viruses or malware before delivery to or installation at a VA location.

16.9 Devices and other equipment or systems containing media (hard drives, optical disks, solid state, and storage via chips/firmware) with VA sensitive information will be returned to the contractor with media removed. When the contract requires return of equipment, the options available to the contractor are the following:

16.9.1.1 The contractor shall accept the system without the drive, firmware and solid state.

16.9.1.2 VA’s initial device purchase includes a spare drive or other replacement media which must be installed in place of the original drive at time of turn in; or

16.9.1.3 Due to the highly specialized and sometimes proprietary hardware and software associated with the device, if it is not possible for VA to retain the hard drive, firmware, and solid state, then:

16.9.1.4 The equipment contractor shall have an…