P02 MR RFI 36C10B27Q0010 Attachment A PWS.pdf

PDF 913 KB Posted

Attached to
DA10--Enterprise Database Vulnerability Scanning Solution
Solicitation number
36C10B27Q0010
Issued by

About this file

Performance Work Statement Summary

This Performance Work Statement (PWS) describes the requirements for an enterprise database vulnerability scanning solution to support the Department of Veterans Affairs (VA) Office of Information and Technology, Cybersecurity Operations Center (CSOC). The VA currently operates LevelBlue Trustwave DbProtect across five environments and requires a replacement solution capable of scanning a minimum of 1,700 multi-vendor database targets within a three-week monthly period without adversely affecting active Authorization to Operate (ATO) scanning. The solution must support 11,000 database assets across on-premises, AWS, and Azure environments, including Microsoft SQL Server, Oracle, MySQL, PostgreSQL, MongoDB, MariaDB, Cassandra, and native cloud database services. The contractor must provide agentless, credentialed scanning with centralized on-premises management, distributed cloud scanning components, and storage of all scan data exclusively on VA on-premises repositories.

The contract includes a 15-day delivery requirement and 30-day installation and configuration window, with the base performance period consisting of 12 months of software licensing, maintenance, and technical support following Government acceptance, plus four 12-month option periods and one optional task, not to exceed 60 months total. Deliverables encompass project management planning, software requirements compliance, full implementation including integrations with Armis, ServiceNow, and Elastic platforms, comprehensive documentation, training for two administrators and six operators, and an OEM Technical Account Manager or equivalent. The solution must comply with extensive VA security, privacy, and enterprise architecture requirements, including FISMA compliance, VA Critical Security Controls, Federal Identity and Access Management (FICAM) standards requiring PIV credentials, encryption standards, and monitoring/reporting obligations. The contractor is responsible for all software licenses, assessments mapping to DISA STIGs, monthly content updates, one-year historical data retention, 99.9% system uptime, and service level agreements with specific response and resolution timeframes by severity level.

View the file

Other files

On GovTribe

Work with this file

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

Text version

DRAFT

PERFORMANCE WORK STATEMENT

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology Cybersecurity Operations Center for

Enterprise Database Vulnerability Scanning Solution

Date: November 04, 2026 Version 1.0

Request for Information 36C10B27Q0010

Contents

1.0 BACKGROUND

2.0 APPLICABLE DOCUMENTS

3.0 SCOPE OF WORK

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

4.2 PLACE OF PERFORMANCE

4.3 TRAVEL

5.0 SPECIFIC TASKS AND DELIVERABLES

5.1 PROJECT MANAGEMENT

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

5.1.2 REPORTING REQUIREMENTS

5.2 SOFTWARE REQUIREMENTS

5.2.1 RETENTION AND DATA ACCESS SUPPORT

5.3 IMPLEMENTATION

5.3.1 Implementation Plan

5.3.2 Architecture and Government Resources

5.3.3 Installation and Configuration

5.3.4 Integrations and Automation

5.3.5 Testing and Acceptance

5.3.6 Documentation Training and Operational Handoff

5.3.7 Completion

5.4 MAINTENANCE and TECHNICAL SUPPORT, AND TRAINING

5.5 REQUIREMENTS TRACEABILITY MATRIX

5.6 OEM TECHNICAL ACCOUNT MANAGER (TAM) OR EQUIVALENT

5.6.1 Services

5.6.2 Coordination and Use of Hours

5.7 SERVICE LEVEL AGREEMENT MONITORING PLAN AND REPORT

5.7.1 SLA QUALITY METRICS

5.7.2 SLA QUALITY LEVELS

6.0 GENERAL REQUIREMENTS

6.1 ENTERPRISE AND IT FRAMEWORK

6.1.1 VA TECHNICAL REFERENCE MODEL

6.1.2 ZERO TRUST – VA CRITICAL SECURITY CONTROLS

6.1.3 FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT

(FICAM)

6.1.4 INTERNET PROTOCOL VERSION 6 (IPv6)

6.1.5 TRUSTED INTERNET CONNECTION (TIC)

6.1.6 STANDARD COMPUTER CONFIGURATION

6.1.7 VETERAN FOCUSED INTEGRATION PROCESS (VIP) AND PRODUCT

LINE MANAGEMENT (PLM)

6.1.8 PROCESS ASSET LIBRARY (PAL)

6.1.9 AUTHORITATIVE DATA SOURCES

6.1.10 SOFTWARE AND LICENSING REQUIREMENTS

6.1.11 GENERATIVE ARTIFICIAL INTELLIGENCE REQUIREMENTS

6.1.11.1 AI SYSTEM/LLM DEVELOPMENT AND OPERATION

DOCUMENTATION REQUIREMENTS

6.1.11.2 MONITORING, REPORTING, AND CORRECTIVE ACTION

6.1.11.3 AI MODEL UPDATES AND CHANGE DISCLOSURES

6.1.12 SOURCE CODE HARMONIZATION AND REUSE IN INFORMATION

TECHNOLOGY (SHARE IT Act)

6.2 SECURITY AND PRIVACY REQUIREMENTS

6.2.1 POSITION/TASK RISK DESIGNATION LEVEL(S)

6.2.2 CONTRACTOR PERSONNEL SECURITY REQUIREMENTS

6.3 METHOD AND DISTRIBUTION OF DELIVERABLES

6.4 PERFORMANCE METRICS

6.5 FACILITY/RESOURCE PROVISIONS

6.6 GOVERNMENT FURNISHED PROPERTY

ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED

ADDENDUM B – VA CYBERSECURITY AND PRIVACY LANGUAGE FOR INCLUSION

IN ACQUISITIONS

1.0 BACKGROUND

The Department of Veterans Affairs (VA), Office of Information and Technology, Cybersecurity Operations Center (CSOC), requires an enterprise database vulnerability scanning solution to support recurring security assessments and Authorization to Operate (ATO) activities.

VA currently uses LevelBlue Trustwave DbProtect across four production environments and one development environment. The existing capability includes centralized management, distributed scanning, vulnerability assessment content, reporting and analytics, and supporting repository and data-processing functions.

Scanning components operate on premises and within VA Amazon Web Services (AWS) and Microsoft Azure environments. Management, reporting, and repository functions are hosted on premises. The current repository retains 12 months of scan information and uses approximately 3.17 terabytes (TB) of storage.

VA conducts monthly enterprise scanning and daily on-demand scans supporting Authorization to Operate (ATO) activities. The current solution assesses at least 1,700 multi-vendor enterprise database targets within a 3-week period each month without adversely affecting the performance or availability of active ATO scanning. Database owners establish authorized scan windows and operational restrictions.

The database inventory below reflects VA’s current environment and may change during the contract period. VA may add database types supported by the proposed solution, including those supported through standard product updates, during the base period or any exercised option period. The database inventory below reflects VA’s current environment. The inventory is expected to change during the contract period as VA adds new database platforms and as supported platforms are updated.

The table identifies the VA’s current database inventory by platform and hosting location.

Database Platform On-premises Azure AWS Total Microsoft SQL Server 2,056 340 135 2,531 Oracle 644 130 363 1,137 MySQL 177 4 49 230 PostgreSQL 754 178 58 990 MongoDB 12 14 23 49 MariaDB

6 6

Cassandra

2 2 Native MS Azure SQL

Current Inventory 3,643 869 636 5,148

2.0 APPLICABLE DOCUMENTS

In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:

1. “Federal Information Security Modernization Act of 2014.”

2. Federal Information Processing Standards (FIPS) Publication 140-3, “Security

Requirements for Cryptographic Modules”, March 22, 2019.

3. FIPS Pub 199. “Standards for Security Categorization of Federal Information and

Information Systems,” February 2004.

4. FIPS Pub 200, “Minimum Security Requirements for Federal Information and

Information Systems,” March 2006.

5. FIPS Pub 201-3, “Personal Identity Verification of Federal Employees and

Contractors,” January 2022.

6. 10 U.S.C. § 2224, "Defense Information Assurance Program", as amended.

7. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974.”

8. Public Law 109-461 (P.L. 109-461), Veterans Benefits, Health Care, and

Information Technology Act of 2006, as amended, Title IX, Information Security Matters.

9. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”, as amended.

10. VA Directive 0710, “Personnel Vetting Program,” September 8, 2025, https://www.va.gov/vapubs/index.cfm.

11. VA Handbook 0710, “Personnel Vetting Program,” September 8, 2025, https://www.va.gov/vapubs/index.cfm.

12. VA Directive 6102, “Internet/Intranet Services,” August 5, 2019.

13. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and

Guidelines,” as amended.

14. Office of Management and Budget (OMB) Circular A-130, “Managing Federal

Information as a Strategic Resource,” July 28, 2016.

15. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed

Services (CHAMPUS)”, as amended.

16. NIST SP 800-66 Rev. 2, “Implementing the Health Insurance Portability and

Accountability Act (HIPAA) Security Rule: A Cybersecurity Resource Guide,” February 2024.

17. 45 C.F.R Parts 160 and 164, Subparts A and E, the Standards for Privacy of Individually Identifiable Health Information (“Privacy Rule”); and 45 C.F.R. Parts 160 and 164, Subparts A and C, the Security Standard (“Security Rule”); as amended.

18. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended.

19. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004.

20. VA Directive 6500, “VA Cybersecurity Program,” September 22, 2026

21. VA Handbook 6500, “Risk Management Framework for VA Information Systems

VA Information Security Program,” February 24, 2021 (see VA Notice 25-01, dated October 15, 2024, “Update to VA Handbook 6500 Risk Management Framework for VA Information Systems VA Information Security Program”, VA Notice 25-16, dated September 15, 2025, “Amending VA Handbook 6500 to

Replace Enterprise Mission Assurance Support Services Tool With Office of Information Technology Governance Risk Compliance Tool, and VA Notice 25- 17, dated September 22, 2025, “Rescission Of Office Of Information Security (OIS) Deputy Assistant Secretary (DAS) Memorandum – Requirements of Proper Plan of Action and Milestones (POA&M) Completion).

22. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” June 30, 2023.

23. VA Handbook 6500.6, “Acquisition Cybersecurity,” October 2, 2026.

24. VA Handbook 6500.8, “Information System Contingency Planning,” March 25, 2025.

25. VA Handbook 6500.10, “Mobile Device Security Policy,” August 24, 2026.

26. VA Handbook 6500.11, “VA Firewall Configuration,” August 22, 2017.

27. OIT Process Asset Library (PAL), OIT Process Asset Library.

28. One-VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx).

29. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy

Impact Assessment,” October 15, 2014.

30. VA Directive 6510, “VA Identity, Credential and Access Management,”

September 3, 2024.

31. VA Handbook 6510, “VA Identity, Credential and Access Management,”

September 27, 2024.

32. VA Directive and Handbook 6513, “Secure External Connections,” October 12, 2017.

33. VA Directive 6300, “Records and Information Management,” September 21, 2018.

34. VA Handbook, 6300.1, “Records Management Procedures,“ March 24, 2010.

35. NIST SP 800-37 Rev 2, “Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy,” December 2018.

36. NIST SP 800-53 Rev. 5.2.0 “Security and Privacy Controls for Information Systems and Organizations,” August 27, 2025.

37. VA Directive 0735, “Homeland Security Presidential Directive 12 (HSPD-12), Personal Identity Verification, Credential Management Program,” September 19, 2025.

38. VA Handbook 0735, “Homeland Security Presidential Directive 12 (HSPD-12), Personal Identity Verification, Credential Management Program,” September 18, 2025.

39. OMB Memorandum 05-24, “Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors,” August 5, 2005.

40. OMB Memorandum M-19-17, “Enabling Mission Delivery Through Improved Identity, Credential, and Access Management,” May 21, 2019.

41. OMB Memorandum, “Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation,” May 23, 2008.

42. Federal Identity, Credential, and Access Management (FICAM) Architecture, June 30, 2023 (FICAM Architecture (idmanagement.gov)).

43. NIST SP 800-116 Rev 1, “Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access,“ June 2018.

44. NIST SP 800-63 Rev 4, 800-63A-4, 800-63B-4, 800-63C-4, “Digital Identity Guidelines,” August 1, 2025.

45. NIST SP 800-157, “Guidelines for Derived PIV Credentials,” December 2014.

46. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy

Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896.

47. Trusted Internet Connections (TIC) 3.0 Core Guidance Documents, https://www.cisa.gov/publication/tic-30-core-guidance-documents.

48. OMB Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative,” September 12, 2019.

49. OMB Memorandum M-08-23, “Securing the Federal Government’s Domain Name System Infrastructure,” August 22, 2008.

50. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (P.L. 110–140), December 19, 2007.

51. Section 104 of the Energy Policy Act of 2005, (P.L. 109–58), August 8, 2005.

52. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001.

53. Executive Order 14148, “Initial Rescissions of Harmful Executive Orders and

Actions,” dated January 20, 2025.

54. VA Directive 0057, “VA Environmental Management Program,” October 25, 2022.

55. OIS VAIQ #7424808 Memorandum, “Remote Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28.

56. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103.

57. “Veteran Focused Integration Process (VIP) Guide 4.0,” March 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371.

58. VA Memorandum “Proper Use of Email and Other Messaging Services,” January

2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28.

59. “Product Line Management Transformation Playbook” version 3.1, August 2023, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946.

60. NIST SP 500-267B Revision 1, “USGv6 Profile,” November 2020.

61. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol

Version 6 (IPv6),” November 19, 2020.

62. Social Security Number (SSN) Fraud Prevention Act of 2017.

63. Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23, 2018.

64. C.F.R Title 15 Part 7, “Securing the Information and Communications

Technology and Services (ICTS) Supply Chain”, as amended.

65. Executive Order 14028, “Executive Order on Improving the Nation's

Cybersecurity,” May 12, 2021, https://bidenwhitehouse.archives.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/.

66. OMB Memorandum M-22-09, “Moving the U.S. Government Toward Zero Trust Cybersecurity Principles”, January 26, 2022, https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf.

67. NIST SP 800-52 Revision 2, “Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations.

68. OMB M-26-05, “Adopting a Risk-based Approach to Software and Hardware Security,” January 23, 2026.

69. OMB M-21-31, “Improving the Federal Government’s Investigative and Remediation Capabilities Related to Cybersecurity Incidents,” August 27, 2021.

70. NIST SP 800-88 Revision 2 “Guidelines for Media Sanitization,” September 26, 2025.

71. CISA BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks. Cybersecurity & Infrastructure Security Agency (CISA), BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks

| CISA.

72. CISA BOD 26-04: Prioritizing Security Updates Based on Risk, June 10, 2026.

73. VA Directive 6550, Pre-Procurement Assessment and Implementation of Medical

Devices/Systems, June 03, 2019.

74. VA Memorandum, “VA Security Controls,” January 17, 2025, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010.

75. E.O. 13960, “Promoting the Use of Trustworthy Artificial Intelligence in the

Federal Government,” December 3, 2020.

76. E.O. 14319, “Preventing Woke AI in the Federal Government,” July 23, 2025.

77. OMB Memorandum M-25-21, “Accelerating Federal Use of AI through

Innovation, Governance, and Public Trust,” April 3, 2025.

78. OMB Memorandum M-25-22, “Driving Efficient Acquisition of Artificial Intelligence in Government,” April 3, 2025.

79. OMB Memorandum M-26-04, “Increasing Public Trust in Artificial Intelligence (AI)

Through Unbiased AI Principles,” December 11, 2025.

80. OMB Memorandum M-26-10, “Reinforcing Transparency, Accountability, and

Oversight of Federal Technology”, March 31, 2026.

3.0 SCOPE OF WORK

The Contractor shall provide all products and services necessary for an enterprise database vulnerability scanning solution, hereinafter referred to as ‘the solution,” to support VA’s recurring security assessments and Authorization to Operate (ATO) activities. The Contractor’s solution shall include project management, software requirements, implementation, maintenance and technical support, and training, and Original Equipment Manufacturer Technical Account Manager services.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

Delivery of items is 15 calendar days after receipt of Order. Installation and configuration, and testing shall commence no later than 30 days after receipt.

The Period of Performance (PoP) for the software solution licensing and maintenance and technical support is 12 months after the Government’s acceptance of installation, configuration, and testing of the Enterprise Database Vulnerability Scanning solution, with four 12-month option periods and one optional task. The optional task can be exercised anytime during the order and will end in the same period it was exercised in.

. The overall PoP shall not exceed 60 months.

Any work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO).

There are 11 Federal holidays set by law (USC Title 5 Section 6103) that VA follows:

Under current definitions, five are set by date:

New Year's Day January 1 Juneteenth June 19 Independence Day July 4 Veterans Day November 11 Christmas Day December 25

If any of the above falls on a Saturday, then Friday shall be observed as a holiday.

Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday.

The other six are set by a day of the week and month:

Martin Luther King's Birthday Third Monday in January Washington's Birthday Third Monday in February Memorial Day Last Monday in May Labor Day First Monday in September Columbus Day Second Monday in October Thanksgiving Fourth Thursday in November.

4.2 PLACE OF PERFORMANCE

Tasks under this PWS shall be performed at the Contractor facility.

4.3 TRAVEL

The Government does not anticipate travel under this effort.

5.0 SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following:

5.1 PROJECT MANAGEMENT

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

The Contractor shall deliver a Contractor Project Management Plan (CPMP) to the COR no later than 15 calendar days after award. The CPMP shall document the Contractor’s approach, timeline, and tools to be used in execution of the contract. The CPMP shall take the form of both a narrative and graphic format that displays the schedule, milestones, risks, and resource support. The CPMP shall also include how the Contractor coordinates and executes planned, routine, and ad hoc data collection reporting requests as identified within this PWS. The Contractor shall work with the COR to gain Government approval of the baseline CPMP. The CPMP shall be a living document, and the Contractor shall update and maintain the Government VA-approved CPMP throughout the PoP. During performance, the Contractor shall update the CPMP as necessary based on environmental changes. The Contractor shall work with the COR to obtain Government approval of the updated CPMP.

Deliverable:

Contractor Project Management Plan.

5.1.2 REPORTING REQUIREMENTS

The Contractor shall provide Monthly Progress Reports (MPR) drafted in Microsoft Word and/or Project formats to the COR. The MPR shall include detailed instructions/explanations for each required data element, to ensure that data is accurate and consistent. The MPR shall reflect status as of the last day of the preceding month.

The MPR shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall identify any concerns and/or issues that arose during the reporting period and a description of how they were resolved. If concerns/issues have not been completely resolved, the Contractor shall provide an explanation that includes the Contractor’s plan and timeframe for resolving. The MPR shall include an itemized list of all deliverables, including the Information and Communication Technology (ICT) deliverables and their current Section 508 conformance status. The Contractor shall monitor its performance against the CPMP and report any deviations. The Contractor shall keep in communication with VA such that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

The Contractor shall provide a Price and Utilization (P&U) Report using the M-26-10 Template, completing the appropriate tabs. The P&U shall provide information related to software, artificial intelligence, cloud, and hardware acquisitions in accordance with OMB M-26-10. This information shall be submitted on a quarterly basis throughout the period of performance, including any exercised options or contract extensions. OMB M- 26-10 is a requirement of this contract and requires IT vendors to disclose utilization and pricing information to the Government, without limiting the extent to which that information may be shared across agencies. Prior to reporting each quarter, the Contractor shall access the M-26-10 template at https://www.voa.va.gov/DocumentView.aspx?DocumentID=5122 to ensure latest template is used.

Deliverables:

A. Monthly Progress Report.

B. Price and Utilization Report.

5.2 SOFTWARE REQUIREMENTS

The Contractor shall be responsible for providing a Commercial-Off-the-Shelf software solution that meets the defined requirements within Table 1, Enterprise Database Vulnerability Scanning Solution Software Requirements.

TABLE 1 - Enterprise Database Vulnerability Scanning Solution Software Requirements

Category Req

Number Description Capacity 01 The solution shall support VA’s current inventory as provided in PWS section 1.0 Background and provide enterprise licensed capacity for up to 11,000 database assets throughout the performance of this contract.

The solution shall support additional database types as VA adds them during the base period or any exercised option period, including types supported through standard product updates, at no additional cost, provided the total number of database assets remains within the enterprise licensed capacity required by this PWS. The Contractor shall identify any database-specific licensing restrictions in its proposal.

02 The solution shall scan at least 1,700 multi-vendor enterprise database targets within a three-week period each month.

Monthly enterprise scanning shall not adversely affect the performance or availability of active ATO scanning for VA mission requirements.

03 The solution shall support vulnerability auditing of VA databases, such as, but not limited to Microsoft SQL Server, Oracle, MySQL, PostgreSQL, MongoDB, MariaDB, Cassandra, and native AWS and Azure database services across the applicable VA on-VA-premises and VA cloud environments.

Architecture 01 The solution’s process for Database scanning and assessment shall be agentless and credentialed. The VA will not install or maintain host-based scanning agents on its database servers.

Category Req

Number Description 02 The solution shall provide an on-VA-premises web management platform console controlling distributed cloud scanning components, including scanners deployed in VA AWS and Azure environments. The platform shall provide VA with a centralized, controlled discovery, inventory, scheduling, scanning, credential management, user administration, reporting, and scanner administration across on-premises and cloud environments.

03 The solution shall support scanning components located on VA premises and in VA AWS and Azure environments.

Communications among management, scanning, repository, integration, and target systems shall be encrypted using VA-approved methods.

04 All scanning data generated by cloud-based scanners shall be returned to and stored solely in VA on-premises repositories. All retained scan data, findings, metadata, logs, backups, and reports shall be stored on premises.

Scanning Operations

01 The solution shall support monthly scheduled enterprise scanning and on-demand ATO scanning within VA-authorized scan windows and operational restrictions.

02 The solution shall support real-time prioritization of scan jobs, including administrator control to pause or reorder jobs and yield scanning resources to higher-priority targets. When a running scan is interrupted for reprioritization, the solution shall preserve its state and permit the interrupted scan to resume from the preserved state.

03 The solution shall allocate and balance work across available scanning components to meet required scan windows, workload, and VA priorities.

04 The solution shall support individual database asset entry and automated bulk import. The solution shall provide a tiered parent/child organizational container hierarchy and permit an individual database asset to belong to multiple organizational containers.

05 The solution shall provide status, progress, completion, error, and operational-health information sufficient for VA administrators to manage enterprise scanning and troubleshoot unsuccessful assessments.

Number Description Assessment Content

01 The solution shall include vulnerability and security-configuration assessment content and policy templates for the required database platforms. Applicable templates shall map to current Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs) and Federal Information Security Modernization Act (FISMA) security controls. Updates shall not require VA administrators to manually modify individual assessment rules.

02 The solution shall receive product, vulnerability, and assessment-content updates available at least monthly or more frequently if critical updates are made available. The solution shall be capable of receiving critical content made available through the Contractor’s expedited release process.

Credentials 01 The solution shall provide a secure, encrypted repository for storing and managing database authentication credentials.

Saved credentials shall be assignable using least-privilege controls to organizational containers, subcontainers, individual targets, and individual scan jobs.

Reporting 01 The solution shall generate ATO compliance reports providing executive-level summaries in PDF format and database-administrator-actionable findings in CSV format.

CSV findings shall include vulnerability impact, affected-target metadata, and explicit remediation guidance.

02 The solution shall generate ATO compliance reports in both PDF and CSV formats. CSV finding output shall be formatted to support direct ingestion into ticketing systems.

03 Authorized personnel shall be able to dynamically search, filter, retrieve, and export granular scan findings and historical data by organizational unit, district, organizational container, environment, target, finding, and custom date range through the management interface.

04 The solution shall provide a reporting engine and flexible querying capable of processing enterprise scan datasets without manual reconstruction of results.

Retention and Data Access

01 The solution shall maintain a centralized consolidation repository on VA-provided, on-VA-premises storage containing at least one rolling year of complete historical scan data.

02 The solution’s historical scan data shall be extractable through the management interface or supported direct SQL access. Authorized personnel shall be able to filter and

Number Description export data by district, organizational container, and custom date range.

Integrations 01 The solution shall provide documented APIs for automated integration with Armis and ServiceNow, and other VA reporting solutions to exchange vulnerability findings and remediation-tracking information. The solution shall also provide supported integration capabilities for Elastic and other VA-authorized solutions identified in the accepted integration design.

02 The solution shall be capable of having the applicable records, fields, workflows, transmission frequency, direction, authentication, error handling, and system ownership for each integration defined by VA and the Contractor, but ultimately approved by VA.

03 The solution shall forward applicable security, audit, and operational logs to VA Elastic infrastructure using a VA-approved method.

Identity and Access Management

01 The web management Platform console shall support VA enterprise single sign-on using PIV credentials.

02 The solution shall provide for administrator and operator roles, least-privilege authorization, accountability for privileged actions, and support for at least eight concurrent users.

Security 01 The solution shall encrypt VA information at rest and in transit and support VA-approved secure tunneling between scanning, management, repository, integration, and database systems.

Recovery 01 The solution shall meet the SLA metrics.

02 The solution shall support monthly full repository backups retained for one year using VA-provided infrastructure.

The Contractor shall provide a transparent enterprise-license billing model that identifies the licensing unit, quantities, rates, billing frequency, usage measurement, adjustments, and any additional charges for the solution.

5.2.1 RETENTION AND DATA ACCESS SUPPORT

The Contractor shall document data models, export formats, retention settings, storage-sizing assumptions, and supported extraction methods in the Data Model and Retention Document.

Deliverables:

A. Enterprise License Billing Model.

B. Data Model and Retention Document.

5.3 IMPLEMENTATION

The Contractor shall implement and configure the solution for production use across the required VA environments. Implementation shall include all installation, configuration, integration, testing, documentation, training, and technical assistance necessary to deliver an operational solution that meets the PWS requirements.

5.3.1 Implementation Plan

Within 30 calendar days after award, the Contractor shall provide an Implementation Plan to the COR. The implementation plan shall identify all activities, milestones, completion dates, dependencies, risks, and Contractor and Government responsibilities.

The Contractor shall work with the COR to gain the Government’s approval of the plan.

The Contractor shall maintain the plan throughout implementation.

The plan shall identify prerequisites, including infrastructure, connectivity, accounts, certificates, security approvals, and access.

Deliverable:

Implementation Plan.

5.3.2 Architecture and Government Resources

At least 90 days before installation, the Contractor shall deliver to the COR the Architecture Documentation. At least 0- days before installation, the Contractor shall provide logical and physical architecture documentation identifying component locations, virtual-machine sizing, storage estimates, ports, protocols, firewall rules, certificates, service accounts, dependencies, and data flows. The Contractor shall work with the COR to obtain Government approval for the architecture.

The Government will provide Government-approved virtual machines, storage, network connectivity, VA cloud resources, certificates, service accounts, test environments, and Government technical support required for the Government-accepted architecture. The Architecture Documentation shall identify the quantities, specifications, and dates needed for these resources and any other resources necessary to ensure the Government is able to independently validate and verify, test, troubleshoot, and sustain the architecture.

Deliverable:

Architecture Documentation.

5.3.3 Installation and Configuration

The Contractor shall install and configure the management, scanning, reporting, and repository components of the Contractor’s solution; applicable software upgrades and security patches; encrypted communications; authentication; role-based access; and backup and recovery settings.

Implementation shall include database connectivity, target onboarding and grouping, scan scheduling, assessment content, reporting, and credential configuration. The Contractor shall provide and help VA tailor supported scripts or creating least-privilege scanning accounts.

5.3.4 Integrations and Automation

The Contractor shall configure, develop, test, and document the required interfaces with Armis, ServiceNow, Elastic, and other VA-authorized solutions identified for implementation.

For each interface, the Contractor shall work with VA to establish the records, fields, direction of exchange, frequency, authentication, error handling, and responsible system owners. The Contractor shall provide the supported scripts or automation necessary to operate the accepted configuration as part of the Integration Documentation.

Deliverable:

Integration Documentation.

5.3.5 Testing and Acceptance

The Contractor shall submit a Test Plan to the COR for VA approval. The Test Plan shall identify test activities, workloads, infrastructure assumptions, verification methods, and measurable acceptance criteria.

Testing shall demonstrate compliance with applicable PWS requirements, including database coverage, agentless credentialed scanning, scheduling and prioritization, reporting, historical-data access, integrations, access controls, logging, backup, and recovery.

The Contractor shall demonstrate completion of at least 1,700 database assessments within a three-week window without adversely affecting active ATO scanning. The test shall represent the required monthly enterprise workload.

Acceptance testing shall also verify:

AWS and Azure scanner operation under on-premises management control and on-premises storage of scan data.

Pausing or reordering a running scan, assigning resources to a higher-priority target, and resuming the interrupted scan from preserved state.

Agentless credentialed assessment across representative required database platforms and native cloud database services.

Current DISA STIG/FISMA-mapped assessment templates and the Contractor’s update mechanism.

Individual and bulk asset onboarding, parent/child containers, and membership of one asset in multiple containers.

Encrypted credential storage and assignment to containers, subcontainers, and scan jobs.

API-based findings and remediation exchange with Armis and ServiceNow.

Web-console single sign-on using PIV credentials.

PDF executive and CSV actionable ATO reports, including organizational, district, and date filtering.

One-year historical-data retention and extraction through the management interface or supported direct SQL access.

Enterprise licensing capacity for 11,000 database assets and the proposed billing model.

Required support capabilities and least-privilege scanning-account scripts.

The Contractor shall have documentation demonstrating VA’s approval of the Implementation Plan, Transition Plan, Architecture Documentation, and network/firewall specification before production migration.

The Contractor shall deliver the Test Report to the COR. The Contractor shall document results in the Test Report, correct deficiencies, and repeat affected tests. The Contractor shall not request Government acceptance prior to correction of all deficiencies.

Deliverable:

A. Test Plan.

B. Test Report.

5.3.6 Documentation Training and Operational Handoff

Documentation:

Before production acceptance, the Contractor shall deliver the Final Architecture and Configuration Documentation. The documentation shall include all interface specifications, account-creation procedures, operating instructions, backup and recovery procedures, troubleshooting guidance, and support escalation information.

Training:

The Contractor shall provide virtual, hands-on training for two administrators and six operators. Training and associated training content shall include configuration, operations, reporting, integrations, backup and recovery, account creation, and troubleshooting.

Operational Handoff:

The Contractor shall conduct an operational handoff demonstrating that VA personnel can perform routine administration, scanning, reporting, and recovery activities. The Contractor shall provide a link and access to a training site for VA authorized users.

Deliverables:

A. Final Architecture and Configuration Documentation.

B. Training link and access.

5.3.7 Completion

Installation alone does not constitute completion. Implementation shall be considered complete when the required components and interfaces are operational, acceptance criteria have been met, required documentation and training have been delivered, and the Government has accepted the implementation.

5.4 MAINTENANCE AND TECHNICAL SUPPORT, AND TRAINING

The Contractor shall provide Maintenance and Technical Support of the solution.

Maintenance and technical support shall cover, at a minimum, installation, configuration, updates, upgrades, security patches, assessment content and policy templates, reporting, integrations, least-privilege account scripts, troubleshooting, recovery, and product consultation.

The Contractor shall notify VA of applicable releases, updates, security issues, end-of-support dates, material changes, and required corrective actions.

Required Maintenance and technical support shall include virtual support with core software installation, configuration, version upgrades, security patch deployment, complex reporting configuration, integration support, custom script authoring, troubleshooting, recovery, and product consultation. These included support activities are separate from, and shall not be performed using or charged against, the Technical Account Manager (TAM) or equivalent hours under section 5.6.

Refresher training shall be provided after material product changes and otherwise twice each year. Maintenance and Technical Support and Refresher Training shall be separately priced.

Deliverables:

A. Software Maintenance and Technical Support.

B. Refresher Training.

5.5 REQUIREMENTS TRACEABILITY MATRIX

The Contractor shall deliver a Requirements Traceability Matrix. The matrix shall map each requirement identifier to the proposed product capability, response location, verification method, limitation or exception, and separately licensed dependency. The Contractor shall work with the COR throughout performance to maintain and improve the matrix structure or objective verification.

Deliverable:

Requirements Traceability Matrix.

5.6 OEM TECHNICAL ACCOUNT MANAGER (TAM) OR EQUIVALENT

The Contractor shall provide an OEM TAM or Equivalent. The Contractor shall provide a TAM or equivalent to support the Contractor’s Solution.

The TAM or equivalent shall possess expert knowledge of the Contractor’s solution and shall provide access to appropriate OEM technical, professional services, and product development resources. Services shall be performed by OEM personnel or personnel with current OEM certification and authorization appropriate to the awarded solution and assigned duties. No later than 15 calendar days after award, the Contractor shall provide the COR with the TAM or equivalent’s name, phone number, and email address, as well as identify the assigned TAM or equivalent’s qualifications, OEM relationship, availability, escalation contacts, and any service limitations.

5.6.1 Services

The TAM or equivalent shall perform additional professional services as identified by the Government’s COR. The CPMP shall be updated with any TAM or equivalent tasks.

TAM or equivalent services may include the following, but are not limited to:

Perform advanced upgrade and migration planning, architecture and design reviews, and performance optimization for the accepted solution across VA on-premises, AWS, and Azure environments.

Provide additional complex reporting, interface configuration, and integration engineering for Armis, ServiceNow, Elastic, and other VA-authorized solutions identified in the accepted integration design.

Provide additional custom scripting and automation for least-privilege scanning accounts, VA reporting, or data exchange.

Perform advanced troubleshooting, recovery planning, and coordination with OEM engineering or development resources for issues requiring services beyond included maintenance and technical support.

Provide additional technical workshops, knowledge transfer, and product consultation for VA staff in connection with approved TAM tasks.

5.6.2 Coordination and Use of Hours

Before performing a TAM task, the Contractor shall submit a task plan identifying the requested outcome, scope, deliverables, estimated hours, schedule, dependencies, and acceptance criteria. The plan shall explain how the work exceeds the requirements already included in Sections 5.3, 5.4, and 5.5. Work shall begin after the COR and PM concur with the plan. Changes affecting contract scope, price, or the period of performance require Contracting Officer authorization.

The TAM or equivalent’s hours shall be documented by task and report completed work, deliverables, hours used per task, and cumulative hours used as part of the MPR.

5.7 SERVICE LEVEL AGREEMENT MONITORING PLAN AND REPORT

The Contractor shall provide to the COR an initial Service Level Agreement (SLA) Monitoring Plan for review and approval within 15 calendar days of award. The SLA Monitoring Plan shall identify the Contractor’s monitoring methods, incident reporting channels, the VA business hours and time zone to measure business day response times, and outage attribution procedures.

The Contractor shall provide the SLA Monitoring Report. The SLA Monitoring Report shall be delivered to the COR monthly and shall align to the performance period covered in the MPR. The SLA Monitoring Report shall capture the three metrics in the SLA Quality Metrics section (response times, restoration and resolution times, and system uptime), with the initial report due 30 calendar days after award. Subsequent reports shall accompany the MPR. Before production acceptance, the report shall address support performance and identify operational metrics that are not yet applicable. Software uptime measurement shall begin upon Government acceptance of installation, configuration, and testing.

VA will not hold the Contractor responsible for outages caused solely by VA actions or VA-owned infrastructure, including VA-provided virtual machines, storage, networks, credentials, and VA cloud resources. Planned and emergency maintenance performed by VA personnel is excluded from downtime and Contractor software or configuration failures shall count as downtime.

Outage time that does not count as downtime under this paragraph is an ‘exclusion’. For each exclusion, the Contractor shall document the cause, start and end times, and duration, and submit them with the monthly SLA Monitoring Report for COR review. The COR may dispute any claimed exclusion.

Deliverables:

A. SLA Monitoring Plan.

B. SLA Monitoring Reports.

5.7.1 SLA QUALITY METRICS

This section establishes the Government’s expectations for the Contractor solution’s quality, service levels, performance management, and reporting.

The SLA Monitoring Reports shall contain response times, restoration and resolution status, and software uptime against metrics one (1) through three (3) below. This report constitutes the SLA Monitoring Report required by Section 5.7.

Severity levels apply to the Enterprise Database Vulnerability Scanning Solution:

Severity 1 (Critical): Required production scanning, on-demand ATO scanning, or access to required scan results is unavailable, with no acceptable workaround.

Severity 2 (Major): Scanning, reporting, repository, or required integration functions are materially degraded; operations continue at a reduced or inconsistent rate.

Severity 3 (Minor): The issue has limited operational impact, an acceptable workaround exists, or the case is a routine request for assistance or information.

The Government assigns the severity level of each case.

1. Response Times

Response time begins when the Contractor receives the support request through the designated support channel. An automated acknowledgment does not constitute an engineer-level response.

Quality Metrics:

Severity 1 (Critical): Initial qualified engineer-level remote response within 1 hour, 24 hours per day, seven days per week.

Severity 2 (Major): Initial qualified engineer-level remote response within 2 hours, 24 hours per day, seven days per week.

Severity 3 (Minor): Initial qualified engineer-level remote response by the end of the next business day.

Severity 1 and Severity 2 response times are elapsed hours, including weekends and Federal holidays.

Business days are Monday through Friday, excluding Federal holidays, during the VA business hours identified in the approved monitoring plan.

2. Restoration and Resolution Times

The following are performance targets. The Contractor shall document the solution’s issues. Contractor failure to meet a target shall be reported in the SLA Monitoring Report and identify the cause, corrective action taken, and response time, and solution time. A

Quality Metrics:

Severity 1 (Critical): Restoration of affected functions or implementation of a government-accepted workaround within 8 elapsed hours after receipt of the support request. The Contractor shall provide continuous 24/7 efforts until restoration or an acceptable workaround and provide status updates at least every 2 hours.

Severity 2 (Major): Restoration of affected functions or implementation of a government-accepted workaround within 24 elapsed hours after receipt of the support request. The Contractor shall provide status updates at least daily until restoration or an acceptable workaround.

Severity 3 (Minor): Resolution or provision of a documented action plan within 3 business days after receipt of the support request.

Restoration through a workaround does not constitute permanent correction. For unresolved defects, the Contractor shall document the corrective action, OEM escalation where applicable, and expected completion date, and report progress through closure.

3. System Uptime

Monthly uptime (%) = 100 × (eligible minutes minus Contractor-attributable downtime minutes) ÷ eligible minutes.

Eligible minutes are calendar minutes following production acceptance in the reporting month, less documented exclusions under Section 5.7.

Overlapping outages shall be counted once. Downtime begins at the earliest documented service loss and ends when restoration is verified. If there are no eligible minutes, uptime shall be reported as not applicable.

Quality Metrics At least 99.9% monthly uptime for the accepted production Enterprise Database

Vulnerability Scanning Solution.

Availability means the production software can perform authorized database scanning, support on-demand ATO scanning, and provide access to required scan results and reports. Contractor-attributable failure of a required function constitutes downtime. Individual component and integration failures and their operational effects shall be reported.

The SLA Monitoring Report shall identify each incident, affected functions, outage start and end times, cause, excluded minutes, eligible minutes, calculated uptime, and applicable invoice discounts.

Uptime compliance does not replace the PWS requirement to scan at least 1,700 database targets within a three-week period each month without adversely affecting active ATO scanning.

5.7.2 SLA QUALITY LEVELS

The Contractor shall apply the following discounts to the affected month’s price for software maintenance and technical support (Section 5.4). The contract pricing schedule shall separately identify this price. For annual billing, the monthly amount shall equal one-twelfth of the annual maintenance and technical support price. Separately priced implementation and training shall be excluded. For prepaid support, discounts shall be provided as equivalent credits or refunds through the contract payment process.

SEVERITY 1 SLA QUALITY LEVELS: Failure to provide the required engineer-level response within 1 hour shall constitute a qualifying instance. The monthly discount shall be determined by the number of qualifying instances during that calendar month, as shown below. The percentage is the total monthly response discount and is not applied separately for each instance.

Number of Qualifying Instances in the Calendar Month

Discount as a % of the Monthly Maintenance and Technical Support Price

One (1) instance 5% Two (2) instances 10% Three (3) or more instances 15%

An instance is one Severity 1 incident with an initial engineer-level response exceeding 1 hour after receipt of the support request. One incident affecting multiple components counts as one instance. Counts reset each calendar month.

UPTIME SLA QUALITY LEVEL: If cumulative monthly software uptime falls below 99.9%, the Contractor shall apply the following discount. Thresholds shall be evaluated using the unrounded uptime calculation.

Cumulative System Uptime

Discount as a % of the Monthly Maintenance and Technical

Support Price 99.9% to 100% 0% 99.0% to less than 99.9% 10% 95.0% to less than 99.0% 25% Less than 95.0% 100%

Response and uptime discounts shall be calculated separately and added, capped at 100% of the affected month’s maintenance and technical support price. The Contractor shall identify all applicable discounts and supporting calculations in the SLA Monitoring Reports.

6.0 GENERAL REQUIREMENTS

6.1 ENTERPRISE AND IT FRAMEWORK

6.1.1 VA TECHNICAL REFERENCE MODEL

The Contractor shall comply with the VA OIT Technical Reference Model (VA TRM).

Compliance with the VA TRM is achieved by using only technologies and standards that are listed as approved for use in the VA TRM. The Contractor shall provide all necessary information requested by VA to ensure TRM approval is obtained prior to use on VA’s network.

6.1.2 ZERO TRUST – VA CRITICAL SECURITY CONTROLS

VA has established minimum mandatory security requirements and requires that any network connected software system or service must meet the VA Critical Security Controls as outlined in the VA Memorandum, “VA Security Controls”, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010. VA Critical Security Controls identify the minimum mandatory requirements that must be implemented across all VA enterprise infrastructure, cloud computing environments, information systems, networks, and specialized devices (medical devices/systems, special-purpose systems, and research scientific computing devices) that process, store, and/or transmit VA data. Effective July 1, 2025, the Contractor shall implement these VA Critical Security Controls, within any network connected software system or service prior to being authorized for use in the VA. This functional requirement is not negotiable, and Plan of Action & Milestones (POAM) will not be accepted in the event these controls cannot be implemented for new systems. Critical Security Controls are intended to increase VA’s security posture and provide security and privacy risk visibility into the VA network and is not a new requirement. The Contractor’s failure to maintain these VA Critical Controls after implementation will result in VA discontinuing the use of the system.

6.1.3 FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT (FICAM)

The Contractor shall ensure Commercial Off-The-Shelf (COTS) product(s), software configuration and customization, and/or new software are Personal Identity Verification (PIV) card-enabled by accepting HSPD-12 PIV credentials using VA Enterprise Architecture (EA), and VA Identity and Access Management (IAM) approved Enterprise Technology Guidelines (ETG).

This is the start of the file's text. The full file is on GovTribe.

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