Draft VDI SOO - (Attachment 2).docx

DOCX document 348 KB Posted

Attached to
Virtual Desktop Infrastructure (VDI) Cloud Implementation
Solicitation number
25-29
Issued by

About this file

This document is a Draft Statement of Objective (SOO) for the Internal Revenue Service's (IRS) Virtual Desktop Infrastructure (VDI) Cloud Solution implementation. The project aims to modernize the IRS's desktop infrastructure by deploying a cloud-based VDI solution that will initially support 4,000 users in Calendar Year 2025, expanding to 8,000 users in Calendar Year 2026. The solution will be hosted by a FedRAMP High authorized Cloud Service Provider, providing centralized, secure desktop environments that enhance operational efficiency, improve cybersecurity, and reduce hardware maintenance costs.

Key objectives include implementing a flexible, scalable virtual desktop infrastructure that supports IRS personnel and contractors, ensures robust security compliance, provides consistent user experiences across devices, and integrates with existing IRS identity and security systems. The VDI solution must meet stringent performance requirements, including 99.9% weekday availability, rapid incident response times, multi-factor authentication, and comprehensive monitoring and reporting capabilities. The implementation will follow a phased approach, with careful evaluation of system performance and operational readiness at each stage, aligning with the IRS's modernization strategy and federal cloud computing guidelines.

View the file

Other files

File Type Posted
25-29 VDI Cloud RFI Response (Attachment 3).xlsx XLSX spreadsheet
25-29 RFI V2 3.21.25 (Attachment 1).docx DOCX document

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 Statement of Objective (SOO) Virtual Desktop Infrastructure (VDI) Cloud Solution User and Network Services

Version 1 March 28, 2025

SOO for VDI Cloud Solution | ii Table of Contents

1.0Project Title1
2.0Background1
3.0Purpose1
4.0Agency Mission1
5.0Scope2
6.0Outcomes3
7.0Current IT Network Environment3
8.0Objectives4
8.1Business Objectives4
8.2Program Management Objectives5
8.3Operational Objectives6
8.4Technical Objectives7
8.5Security Objectives8
9.0Deliverables9
10.0Constraints11
11.0Performance Requirements Summary11
12.0Performance12
13.0Travel12

Appendix A - Selected Unique Requirements 13

SOO for VDI Cloud Solution |

Project Title Internal Revenue Service (IRS) Virtual Desktop Infrastructure (VDI) Cloud Solution.

Background The IRS is implementing cloud-based VDI as a key component of its modernization strategy to enhance technology, digital services, data security, customer service, and process efficiency. VDI enables centralized management, scalability, and consistent user experience across devices. By enforcing controlled access and robust security measures, VDI strengthens data security and enhances customer service by enabling Information Technology (IT) teams to resolve issues from anywhere, at any time, using various devices to maximize resource utilization. Additionally, VDI supports process improvements by reducing hardware dependencies, promoting automation and standardization, and contributing to cost savings and adherence to federal laws and regulations for data protection, privacy, cybersecurity, and information management. Finally, VDI lowers capital expenditure by minimizing the need for physical hardware and associated maintenance costs as the desktop interface and applications are hosted on a remote server rather than on a local physical computer.

The VDI implementation will follow a phased approach. In Calendar Year 2025 (CY25) 4,000 users consisting of IRS personnel and cleared contractors will migrate to the VDI Cloud Solution, increasing to 8,000 users in Calendar Year 2026 (CY26). This approach allows the IRS to thoroughly evaluate system performance and operational readiness, address any potential challenges in a controlled environment, and provide an opportunity to plan for future expansion to additional personnel and contractors. This approach aligns with the Federal Cloud Computing Strategy (“Cloud Smart”), enabling the IRS to create a scalable platform that accounts for future growth. By adopting VDI, the IRS is positioning itself to better meet evolving operational demands while ensuring secure and reliable IT services for its users.

Purpose The purpose of the VDI Cloud Solution project is to provide a flexible, secure, and cost-effective solution for delivering desktop environments to users and enhance operational efficiency. This cloud-based solution enables the IRS to elastically scale infrastructure, increasing resiliency, promoting workload portability, and reducing operational overhead costs and lead times traditionally associated with provisioning and maintaining physical laptops.

Agency Mission The IRS' mission is to provide top-quality service to taxpayers by helping them understand and meet their tax responsibilities and enforce the law with integrity and fairness. The VDI Cloud Solution project aligns with IRS' strategic focus to modernize taxpayer services, streamline operations, and strengthen cybersecurity. The VDI Cloud Solution will improve information IT service delivery of secure and reliable employee and contractor access to IRS systems.

Scope The scope of this SOO includes the following:

· VDI Desktop-as-a-Service (DaaS) Managed Services: The scope includes VDI as a fully managed, cloud-hosted service tailored to the specific number of users and user types specified in Table 1. The managed services include DaaS vendor options to meet the objectives and performance requirements outlined in this SOO, such as monitoring, maintenance, user support, configuration management, and security management. The VDI services must be hosted by a Federal Risk and Authorization Management Program (FedRAMP) High authorized Cloud Service Provider (CSP). The cloud services include compute and storage resources that meet stringent federal security standards, ensuring taxpayer information is protected with advanced security measures and that the solution adheres to federal regulations for data handling and privacy.

· VDI Configuration, Integration, and Test: The scope includes configuration of the VDI Cloud Solution to deliver the required functionality and technical capabilities identified in this SOO and integration with existing IRS IT infrastructure to ensure secure connectivity. The scope also includes testing support in accordance with IRS processes prior to the VDI Cloud Solution being transitioned to production. These processes may require support for setting up test environments, providing access to necessary tools and resources, and troubleshooting and resolving any issues that arise during testing to ensure smooth and efficient operations.

· Commercial Product Licensing: The scope includes all necessary commercial product licenses required to implement and maintain the VDI Cloud Solution. This includes identifying and managing license compliance and ensuring that all licensing agreements are adhered to, thereby avoiding any legal or operational issues related to software usage.

· Documentation: Section 9 (Deliverables) outlines required deliverables and defines the quality standards for measuring acceptability.

Table 1. User Types Per Year

User Personas
CY2025
CY2026
Total Users
4,000
8,000
Dedicated Standard User
4%
4%
Dedicated Power User
1%
1%
Session Host (Shared)
95%
95%

Outcomes The IRS’ desired outcomes for the phased implementation of the VDI Cloud Solution are:

· CY25: Deploy a cloud-based virtual desktop solution to implement virtual workstation capacity and reliability for up to 4,000 users simultaneously.

· CY26: Deploy a cloud-based virtual desktop environment to expand virtual workstation capacity and reliability for up to 8,000 users simultaneously.

These desired outcomes of the VDI Cloud Solution align with IRS’ efforts to improve technology operations, specifically:

· Improve Efficiency of IT Operations and Customer Service: Reduce operational overhead costs and timeline associated with provisioning and maintaining physical laptops by transitioning to a cloud-based solution.

· Support IRS Modernization Goals: Align with the IRS' broader modernization strategy to enhance technology, digital services, and process efficiency.

· Ensure Compliance and Security: Adhere to IRS and federal security mandates to protect sensitive tax data and ensure cybersecurity compliance.

· Facilitate Scalability and Future Growth: Create a scalable platform that can accommodate future growth and evolving mission requirements, supporting additional users as needed.

Current IT Network Environment Currently, the User and Network Services (UNS) team supports IRS personnel and contractor access by provisioning physical laptops. During the first phase of the VDI project, the capability was added to provision virtual desktops from the IRS' Martinsburg data center using Citrix Virtual Desktops for up to 1,800 users. The VDI Cloud Solution will extend this capability to serve a larger number of users, eliminating the need to manage the associated hardware, and securely support user access from outside of IRS facilities and other remote work needs.

The VDI Cloud Solution will integrate with existing IRS infrastructure and services in the following ways:

· Identity Services: The IRS' existing identity service (Microsoft Entra ID) will be used to authenticate and authorize VDI users.

· Cloud Applications[footnoteRef:2]: VDI users will connect to Software-as-a-Service (SaaS) applications such as SharePoint to work with IRS documents and data. [2: Cloud applications are internet-based programs where processing and storage occur on the internet ("the cloud"), accessible through web browsers or apps, offering features like data storage, email, and collaboration tools. ]

· On-Premises Applications: The VDI Cloud Solution will need a secure, reliable connection between the CSP and the IRS Martinsburg data center to connect to services and applications running on-premises, such as the Domain Name System (DNS).

· Security Services: The VDI Cloud Solution will integrate with the IRS' Secure Access Service Edge (SASE) tool to provide an additional layer of security and consistent end user experience. In addition, logs from the VDI Cloud Solution will be sent to IRS' Security Information and Event Management tool for auditing and responding to security incidents.

· Endpoint Management: The VDI Cloud Solution must support IRS' endpoint management solution to protect against unauthorized usage and prevent data leakage from client devices.

Objectives The VDI Cloud Solution must meet the objectives outlined in the subsections below. Selected unique requirements are specified in Appendix A. Additionally, the IRS has standard requirements for Section 508 compliance, Internet Protocol version 6, operations, privacy, and security.

Business Objectives The VDI Cloud Solution must satisfy the following business objectives:

· Virtual Desktops: Deploy and manage fully configurable virtual desktops hosted in a secure cloud environment to provide users with reliable, highly available access to their applications and data from anywhere with an internet connection, at any time, using various devices such as laptops, tablets, or smartphones via various network configurations. Devices may include IRS-issued thin clients or user-furnished devices that comply with IRS Bring Your Own Device policy.

· User Experience Consistency: Provide a virtual desktop user experience that replicates the experience of using a physical workstation, including familiar interfaces and settings and Section 508 accessibility compliance. All necessary applications must be available and function seamlessly within the virtual desktop environment, just as they would on a physical workstation including comparable fast boot times, quick application launch, and smooth operation. This includes support for peripherals such as printers, audio/video conferencing, video playback, and high-resolution graphics as well as seamless integration with enterprise storage, databases, services, and applications. Robust network connectivity is essential to minimize latency and increase response times and ensure that users can access their virtual desktops without interruption, regardless of their location.

· Resource Allocation and Scalability: Provide the capability to efficiently allocate adequate computing resources (i.e., central processing unit (CPU), memory, storage) for each virtual desktop based on demand to maintain efficiency and performance and reduce over-provisioning. Provide the capability to quickly scale desktop resources up or down to accommodate varying numbers of users and workloads based on business needs, supporting growth and seasonal fluctuations without significant infrastructure changes and without performance degradation.

· Centralized Management: Provide a centralized platform for managing and configuring virtual desktops that enhances control over desktop environments while simplifying provisioning, Common Operating Environment (COE) image management and deployment, software updates, patches, security settings, and troubleshooting. The centralized platform should enable faster deployment of applications and services and enhance overall productivity to improve operational efficiency.

· Secure Access and Data Protection: Ensure that data and applications are secure, by fully integrating with IRS security controls, tools, and existing systems that support the IRS desktop infrastructure using measures such as encryption, access controls, use of key and certificate management, and network security that comply with industry standards, regulations, and IRS security policy. Support secure user authentication methods, including single sign-on and multi-factor authentication, and integrate with existing IRS identity management systems. The virtual workstations will access the IRS network access through existing firewalls, proxies, ports, and protocols.

· Disaster Recovery and Business Continuity: Minimize downtime caused by component failure or other unforeseen events. Implement reliable disaster recovery measures such as automated back-up/recovery and redundancy/failover to ensure data and applications remain accessible during disruptions.

· VDI Monitoring, Alerting, and Reporting: Provide tools for monitoring the performance of virtual desktops and applications to analyze resource usage and address bottlenecks, as well as the ability to provide alerting methods in the event that monitoring thresholds are exceeded. Generate reports, dashboards, and analytics on usage, performance, and security metrics in specified formats. Provide tools for auditing and compliance reporting that are compatible with existing IT management and monitoring tools.

Program Management Objectives Successful project execution will require consistent and well-organized program management that leverages existing IRS processes and tools, to deliver the successful integration and operation of the VDI Cloud Solution.

The contractor shall follow established IRS and Treasury program management processes, including:

· Contractor Performance Monitoring and Analysis: Provide meaningful reporting and analytics that provide UNS with up-to-date and comprehensive information regarding technical and management performance.

· Schedule: Develop and manage schedules for implementation along with planned maintenance and upgrades

· Cost and Resource Management: Implement effective cost management practices for implementation and operation of the VDI Cloud Solution including rightsizing of environments and staffing, following IRS IT standards for resource tagging and cloud cost management tools.

· Risk Management: Provide and maintain a Risk Management Plan that documents mitigation strategies, likelihood, impact, severity and an overall risk rating for project risks.

· Communication Plan: Develop a Communication Plan that establishes communication goals, identifies stakeholders, and identifies communication methods and frequency to ensure awareness across impacted organizations.

· Configuration Management Plan: Develop a Configuration Management Plan that identifies and baselines Configuration Items and controls modifications to these items for completeness and consistency.

· Training and Technical/User Documentation: Develop a Train-the-Trainer program tailored to the VDI Cloud Solution, encompassing the various types of training needed to ensure IRS IT staff, end users, and administrators can effectively use and support the system. Provide training materials, technical documentation, and resources to support the program and conduct the initial trainer training.

· Status Reports: Provide weekly and monthly status reports that provide visibility into program cost, schedule, technical performance, risks, and other key aspects of contractor progress and concerns.

· Implementation Plan: Develop an implementation plan detailing milestones, activities, and timelines for the VDI Cloud Solution and report status via the weekly status reports.

Operational Objectives The VDI Cloud Solution will support the following operational and maintenance objectives:

· Ensure the efficient, effective, and timely development and integration of all services.

· Maintain high availability, scalability, and performance to handle peak processing times and a growing user base.

· Ensure the solution can initially support up to 4,000 users in CY2025, and it is scalable to meet VDI deployment goals of up to 8,000 users in CY 2026.

· In the event of an outage, meet the applicable IRS service level agreements (SLA) for system recovery and end-use notification. Provide integration with established IRS Incident Response procedures to ensure awareness of system status per contract SLAs to assist in triaging and resolving outages (per IRS Master Service Level Agreement and IRS Incident Management Process).

· Plan and effectively execute timely updates and adjustments in response to evolving IRS needs along with updates to regulations and mandates.

· Provide plans and timelines for any required updates, whether vendor-led or in collaboration with the IRS.

· Provide expert integration services, ensuring the VDI Cloud Solution is successfully integrated with IRS operations and is fully compatible with existing IRS technologies.

· Provide support to assist IRS IT with technical issues related to the VDI environment and ensure rapid response times to IRS IT inquiries and technical problems.

In addition to the general Operations Objectives stated in this section, the VDI Cloud Solution must support IRS operational standards. This includes service objectives for availability and key IT Services Management processes such as Change Management, Configuration Management, Incident Management, Release Management, and Problem Management.

Technical Objectives The VDI Cloud Solution must provide a secure, scalable, and flexible cloud-based virtual desktop and application environment, enabling users to access applications and data from authorized devices. The landing zone[footnoteRef:3] design must be planned to initially support 4,000 concurrent users, with the capability to expand and accommodate up to 8,000 users. Designing and supporting the landing zone involves planning, implementing, and maintaining an infrastructure that encompasses network hardware, software, protocols, and services to ensure efficient communication and data transfer. When considering VDI performance, particularly in the context of network design, cloud services, or application development, two key factors need to be considered. [3: “Landing zone” is a term used by various cloud providers to refer to the basic cloud infrastructure and supporting components that enables efficient and secure deployment of applications based on an organization’s IT policies.]

· Bandwidth Considerations:

· Basic User Activity: For typical office productivity tasks, a minimum of 10 Mbps per user is generally considered adequate.

· Graphics Intensive Applications: Users of graphics-heavy applications will require higher bandwidth, potentially impacting shared circuits that connect to IRS data centers. Bandwidth usage must be monitored, and the IRS notified if additional circuits are required to maintain service levels.

· Scaling Considerations:

· Number of Users: As the number of concurrent users increases, so does the required network bandwidth.

· Application Type: Applications with high graphical demands require more bandwidth and computer resources than text-based applications.

· Region Selection: Choose a region with low network latency to users' locations.

· User Scalability: Virtual desktops can be adjusted to meet changing resource needs by increasing or decreasing CPU and random-access memory allocations.

Security Objectives Provide support and services in compliance and alignment with the FedRAMP High security requirements and standardized controls, assessment, authorization, and continuous monitoring policies. In addition to FedRAMP, comply with IRS-specific security requirements required to achieve an IRS Authority to Operate (ATO). The VDI CSP must maintain FedRAMP High authorization and the VDI Cloud Solution provider must support ATO reauthorization cycles.

· Assessment and Authorization activities will be included as part of the VDI Cloud Solution, as well as supplementary IRS-specific requirements described in IRS Policy Alert Update PA 24-03 – “Federal Information Security Modernization Act (FISMA) Cybersecurity Requirements Language”.

· Provide cloud-based VDI services regarding security and privacy that are consistent with the National Institute of Standards and Technology (NIST) Special Publication 800-144 – “Guidelines on Security and Privacy in Public Cloud Computing” and other applicable standards and guidelines.

· Provide support personnel who have Minimum Background Investigation clearance at the vendor’s expense.

· Provide support to the IRS to obtain an ATO and establish a Risk Management Framework (RMF) process prior to implementation.

Deliverables

#
Deliverable
Performance Standards
Acceptable Quality Levels
Surveillance Approach
1
Monthly Report
Quality: A detailed report providing updates on project progress per the Project Plan.

Timeline: Monthly

The Government review of the document only identifies minor updates or changes necessary for compliance.
Surveillance: 100% Inspection Surveillance Performed by: Contracting Officer Representative (COR), PM (PM), Contracting Officer (CO), or other Government personnel as directed.

Incentive/Disincentive: Any quality deficiencies or missing deadlines may adversely impact Contractor Performance Assessment Report (CPAR) ratings.

2
VDI Implementation Plan
Quality: The plan shall outline the project's scope, goals, objectives, tasks, timeline, key deliverables, and risks.

Timeline: initial phases

The Government review of the document only identifies minor updates or changes necessary for compliance.
Surveillance: 100% Inspection Surveillance Performed by: COR, PM, CO, or other Government personnel as directed.

Incentive/Disincentive: Any quality deficiencies or missing deadlines may adversely impact CPARs ratings.

3
Weekly Status Report
Quality: A concise report detailing weekly progress, challenges, and planned activities for the next period.

Timeline: Weekly

The report is accurate and timely, with no more than one late submission per quarter.
Surveillance: 100% Inspection Surveillance Performed by: COR, PM, CO, or other Government personnel as directed.

Incentive/Disincentive: Any quality deficiencies or missing deadlines may adversely impact CPARs ratings.

4
Communication Plan
Quality: The plan shall effectively outline communication strategies and stakeholder engagement approaches.

Timeline: Initial phase

The Government review of the document only identifies minor updates or changes necessary for compliance.
Surveillance: 100% Inspection Surveillance Performed by: COR, PM, CO, or other Government personnel as directed.

Incentive/Disincentive: Any quality deficiencies or missing deadlines may adversely impact CPARs ratings.

5
Configuration Management Report
Quality: The report shall detail configuration management processes and integration with IRS systems.

Timeline: As needed

The report is complete and accurate, with only minor corrections needed.
Surveillance: 100% Inspection Surveillance Performed by: COR, PM, CO, or other Government personnel as directed.

Incentive/Disincentive: Any quality deficiencies or missing deadlines may adversely impact CPARs ratings.

6
Security Compliance Support
Quality: Compliance with all relevant security policies and standards is maintained as described in section 8.

Timeline: Ongoing

Compliance is consistently achieved with only minor adjustments required. The IRS will audit the solution to ensure that it is compliant with internal security requirements, while the FedRAMP board will engage in continuous monitoring to ensure FedRAMP compliance.
Surveillance: 100% Inspection Surveillance Performed by: COR, PM, CO, or other Government personnel as directed. Incentive/Disincentive: Any quality deficiencies or missing deadlines may adversely impact CPARs ratings.
7
Cloud VDI Project Schedule
Quality: Accurately captures project timeline and milestones, resources, responsibilities and dependencies. Updated at agreed to frequency.

Timeline: Ongoing Compliance is consistently achieved with only minor adjustments required.

Surveillance: 100% Inspection Surveillance Performed by: COR, PM, CO, or other Government personnel as directed. Incentive/Disincentive: Any quality deficiencies or missing deadlines may adversely impact CPARs ratings.

8
Risk Management Plan
Quality: Compliance with relevant IRS IT Risk Management reporting and evaluation policies and standards.

Timeline: As needed Compliance is consistently achieved with only minor adjustments required.

Surveillance: 100% Inspection Surveillance Performed by: COR, PM, CO, or other Government personnel as directed. Incentive/Disincentive: Any quality deficiencies or missing deadlines may adversely impact CPARs ratings.

9
VDI Training and Technical/User Documentation
Quality: Training materials, resources, and documentation support Train-the-Trainer model.

Timeline: As per needed

Training materials and sessions are clear, comprehensive, and delivered on time, with no more than one late delivery per quarter.
Surveillance: 100% Inspection Surveillance Performed by: COR, PM, CO, or other Government personnel as directed. Incentive/Disincentive: Any quality deficiencies or delays in training delivery may adversely impact CPARs ratings.

Constraints The following constraints will shape the VDI Cloud Solution.

· Regulatory Compliance: Mandatory compliance with IRS standards and policies and federal laws and guidelines.

· Standard Adherence: Mandatory adherence to IRS, NIST, FISMA, and Federal Information Processing Standards (FIPS) standards for cloud security and information management. Periodic audits, as specified in Federal Acquisition Regulation (FAR) Subpart 42.15, will assess compliance.

· One Solution Delivery Lifecycle (OneSDLC) Integration: Contributions to IRS' cloud modernization must align with the IRS' OneSDLC requirements and follow IRS and NIST frameworks for information security and privacy management.

· Project Coordination: The effectiveness of IRS coordination, evaluated against IRS and NIST guidelines, will be measured by meeting project milestones and OneSDLC requirements.

Performance Requirements Summary The Performance Requirements Summary is the list of performance elements and standards that must be performed by the contractor. The table below details the delivery or required service, performance standard, acceptable quality level, and method of surveillance the COR will use to validate and inspect these performance elements. Inspection of each element will be documented in the COR file.

Required VDI Services
Performance Standard
Acceptable Quality Level
Surveillance Method

VDI Service Availability (SOO Section 6, 8, and 10)

The contractor shall ensure continued availability of the VDI service with established commercially available SLAs and metrics. The Contractor shall continuously log and monitor availability to report system performance.
99.9% Availability during weekdays between 6am – 9pm Eastern.

99% Availability during weekday off-hours (9pm – 6am) and weekends.

COR and/or PM continuous surveillance, which may include, but is not limited to the following: electronic dashboard and log reviews, periodic inspections, report reviews, random observations, and/or planned observations.

VDI Service Latency (SOO Section 8)

The contractor shall make reasonable efforts to minimize latency within the scope of their responsibilities and ensure that the solution’s performance meets or exceed the current desktop response time.
The performance standard is met 95% of the time.
COR and/or PM continuous surveillance, which may include, but is not limited to, the following: periodic inspections, report reviews, random observations, and/or planned observations.

VDI Solution Authorization (SOO Section 5, 7, and 8)

The contractor shall ensure that the VDI Solution receives and maintains its authorization through automated security scanning and Security Technical Information Guides (STIGs) and remain in compliance with RMF requirements.
Minimum of 95% of all security artifacts and processes are documented and validated by the Government Information System Security Manager (ISSM) or other government official.
COR and/or PM continuous surveillance, which may include, but is not limited to, the following: periodic inspections, report reviews, random observations, and/or planned observations.
Incident Response Time
The Contractor shall respond to VDI Solution outages or critical incidents within 15 minutes.
95% of outages or critical incidents should meet the response time standard.
COR and/or PM continuous surveillance, which may include, but is not limited to, the following: periodic inspections, report reviews, random observations, and/or planned observations.
Resolution Time for Issues
The Contractor shall resolve VDI Solution non-critical issues within 4 hours.
90% of non-critical issues should be resolved within the specified time frame.
COR and/or PM continuous surveillance, which may include, but is not limited to, the following: periodic inspections, report reviews, random observations, and/or planned observations.
User Support and Help Desk
The Contractor shall resolve user queries within one hour during weekdays between 6am – 9pm Eastern.
95% of user queries should be resolved within the specified time frame.
COR and/or PM continuous surveillance, which may include, but is not limited to, the following: periodic inspections, report reviews, random observations, and/or planned observations.

Performance

· Place of Performance: This work will be performed at contractor facilities. Local travel (within a 50-mile radius of Washington, DC, or any IRS field offices) required for on-site meetings will not be reimbursed by the IRS. The Contractor must provide the COR, Government Technical Monitor (GTM), and other IRS staff, as appropriate, with advance notice to make necessary arrangements.

· Period of Performance: The performance period for any resulting award will consist of a 12-month base period followed by a 12-month option period. The agency will evaluate the option to execute FAR 52.217-8, Option to Extend Services.

Travel No travel other than local travel is expected under this contract.

Appendix A - Selected Unique Requirements

Table A1. Selected VDI Unique Requirements

Name
Requirement Statement
Recovery Time Objective
The solution shall be able to restore full functionality 24 hours after detection of issues following and related to the disaster event.
Disaster Recovery
The solution shall be able to leverage Disaster Recovery backups and copies of software for capability restoration on hardware in a separate geographical location for critical use cases.
Outage Support
The solution shall have access to technical support for troubleshooting and restoration of service in case of a VDI-specific outage not caused by a general network outage.
Address Management
The solution shall be able to access address management services (i.e., Internet Protocol Address Management, for example Dynamic Host Configuration Protocol and DNS services).
Temporary Storage
The solution shall ensure that non-persistent workstations user data is not stored permanently on virtual machines.
Automated Deployment
The solution shall allow the IRS to automate image deployment to multiple virtual machines and delivery groups.
Centralization
The solution shall be able to administer all virtual workstations from a single centralized interface.
Command Line
The solution shall have the capability to be administered using command line and scripting interfaces (e.g., PowerShell, Bash).
Compliance Configuration
The solution shall allow for configuration of compliance settings to meet regulatory requirements.
Configuration
The solution shall allow for configuration of the core/essential functions and capabilities of the VDI solution that enables it to provide user workstations.
Remote Management1
The solution shall allow IRS technicians to remotely manage and troubleshoot virtual workstations from their IRS-issued laptops.
Remote Management2
The solution shall allow IRS technicians to remotely manage and troubleshoot virtual workstations from any device that complies with IRS BYOD policy.
Master Service Level Agreement (MLSA)
The solution will adhere to the IRS MSLA.
Splunk
The solution shall integrate with the IRS Enterprise Security Audit Trails (ESAT (Splunk) infrastructure for capture, storage, and analysis of all auditable events and logs generated from the system components.
Business Unit (BU)
The solution shall have the capability to produce reports for aggregation of system resource consumption to a specific BU or group of BUs.
Compliance Tracking
The solution shall provide data and metrics to be used for tracking and managing compliance with regulatory mandates and policies, as well as with SLAs.
Transaction History
The solution shall maintain a complete, accessible, and auditable history of all transactions and activities within a configuration management database.
Optimization
The solution shall be able to perform intelligent workload analysis to determine optimal resource allocation and management.
Bandwidth
The solution shall have the network and application bandwidth required to accommodate 4,000 concurrent virtual workstation users for CY25 increasing to up to 8,000 concurrent users for CY26.
End Users Scaling
The solution shall support a VDI implementation (to cover a mix of IRS employees and contractors for the IRS) starting with 4,000 seats for CY25 increasing to up to 8,000 seats for CY26.
Technical Performance
The solution shall result in acceptable virtual workstation performance and be supportive of user productivity including real-time audio/video conferencing and video playback when the user provides desktop and network capabilities specified as sufficient.
VDI Session Rules
The solution shall be able to apply rules for persistent and non-persistent VDI sessions.
Response Time
The solution shall provide a COE desktop application response that should be equal to or less than experienced on a hardware laptop during peak usage hours.
Boot Time
The solution shall have a virtual desktop load and log in time that is less than or equal to the time to boot up a hardware laptop, log in, and remotely connect to IRS network.
Access Control
The solution shall provide the ability to limit users’ access to specific virtual machines and virtual machine pools.
Least Privilege
The solution shall enable roles-based access that defines granular entitlements and permissions for all roles applying least privilege principles (including, but not limited to, end users, administrators, developers and managers).
Certificate Management
The solution shall use key and certificate management associated with encryption capabilities across the solution.
Encryption (Data In Motion)
The solution shall ensure all data in motion is encrypted between Network components.
Encryption (Data At Rest)
The solution shall ensure all data at rest is encrypted.
Data Security
The solution shall ensure all user data is secure and not accessible by other users.
Security Policy
The solution shall allow for configuration of security policy to be applied to all system components.
Network Routing
The solution shall maintain existing network routing limitations and security policies for all previously configured workstations.
Proxy
The solution shall allow users to access the internet from their IRS virtual desktop only through existing IRS proxy(s) utilizing existing IRS proxy rules.
Forensic
The solution shall allow the IRS to identify logons to virtual machines by users and snapshot said machines for forensic purposes.
Patch Management
The solution shall allow for the capability to run operating system patches and software updates in line with the COE image either through direct distribution or image redeployment.
Asset Control
The solution shall integrate with current high-value asset control mechanisms.
Domain Policy
The solution shall allow the IRS to impose IRS domain group policy on all virtual workstations and delivery groups.
Software Integration
The solution shall fully integrate with all security controls, security tools, and systems that support the IRS desktop infrastructure, including but not limited to Splunk, Symantec Endpoint Protection, and ActiveClient.
Monitoring
The solution shall permit IRS staff to monitor and control all traffic in and out of the virtual machines.
Multiple Monitors
The solution shall support at least two monitors on the client side.
Security Infrastructure
The solution shall integrate with the IRS desktop support infrastructure for security, including policy enforcement, security monitoring, software update, audit log forwarding, and support tools.
Section 508
The solution shall provide Section 508 accessibility compliance that allows users to leverage accessibility devices, options, and methods currently supported by the COE image.
Cameras
The solution shall allow for the sharing of end point cameras with virtual workstations.
Audio Input
The solution shall allow users to leverage microphones and other audio input devices attached to the client device (USB, line-in, etc.).
Audio Output
The solution shall allow users to hear audio played on VM in real-time.
Printing
The solution shall provide the capability to permit authorized users to access local printing devices as well as IRS Managed Print Services for printing.
Roaming Profiles
The solution shall allow users of non-persistent workstations to move from workstation to workstation without losing profile settings and user specific data (Roaming profiles)
Non-Persistent Use Cases
The solution shall allow for the use of roaming profiles and /or folder redirection to enable non-persistent use cases.
Software Continuity
The solution shall allow software running on current virtual workstations to continue to operate on the user’s workstation instance.
DNS
The solution shall integrate with the appropriate IRS system for DNS name resolution for virtual machines.
Firewalls, Proxies, Ports, and Protocols
The solution shall support the need for all virtual workstations to connect to the IRS's network using existing and approved firewalls, proxies, ports, and protocols.
Image Uploads
The solution shall have the capability to upload workstation images from within the IRS network.
Segmentation
The solution shall be configured so all virtual machines reside in network segments consistent with the current IRS topology.
Network Access
The solution shall permit virtual workstation access to the IRS private network space consistent with current workstation network access.
Remote Authentication (Control Plane)
The solution shall support PIV compliant credentials for authentication to the Control Plane from any IRS issued laptop or government furnished iPad.
Remote Authentication (Control Plane) BYOD
The solution shall support credentials for authentication to the Control Plane from any device that complies with IRS BYOD policy.
Remote Authentication virtual machine (VM)
The solution shall support PIV compliant credentials for authentication to the (VM) log-on from any IRS-issued laptop or government furnished iPad.
Identity Access Management
The solution shall use existing Active Directory or AD Federation for Identity Access Management (IAM) including single sign-on for user authentication and authorization.
SAML2
The solution shall support use of Security Assertion Markup Language (SAML) version 2 for authentication to the Control Plane.
PIV Authentication (Control Plane)
The solution shall support PIV Card authentication to the Control Plane from any authorized client device compatible with the VDI solution.
PIV Authentication (VM)
The solution shall support Personal Identity Verification (PIV) Card authentication to the VM from any authorized compatible client device.
Remote Access
The solution shall provide the capability to limit users’ access to the VMs from remote locations using client access policies based on device trust, geographic location, and certificate or ADFS authentication.
Sign In
The solution shall be able to provide authorized users the ability to sign in to the Control Plane using their existing domain accounts.
Workflows
The solution shall be able to use pre-built and customized workflows and scripts to automate VDI resource, service, and administrative full lifecycle management processes.
Report Delivery
The solution shall enable scheduled and on-demand delivery of dashboard information and reports.
Report Export
The solution shall be able to export report information and historic data in a delimited format (e.g., JSON, CSV, and XML).
Alerts, Notices, Reports
The solution shall be able to organize data and information into both pre-configured and customizable alerts, notices, and reports delivered via e-mail and the portal.
Inventory
The solution shall support monitoring, discovering, and maintaining an accurate, on-going inventory of resources.
Resource Monitoring
The solution shall have capability to monitor resources and performance status of systems and services using customizable reports.
Data Protection
The solution shall protect user data stored within the system boundaries against hardware failure.
Standard Image
The solution shall use the standard IRS image (i.e., the COE image) as a foundation for virtual workstations.
Snapshots
The solution shall be able to modify existing VM images and produce snapshots, while also managing multiple VM versions.
Query Issues
The solution shall be able to query deployment issues and errors within the solution.
Versioning
The solution shall be able to store and manage multiple image versions.

Table A2. Selected Security Unique Requirements

Name
Requirement Statement
General
The contractor shall ensure IRS information and information systems are always protected. The contractor shall develop, implement, and maintain effective controls and methodologies in its business processes, physical environments, and human capital or personnel practices that meet or otherwise adhere to the security and privacy controls, requirements, and objectives described in applicable security and privacy control guidelines, and their respective contracts. Pursuant to the Federal Information Security Modernization Act (FISMA) and Federal Risk and Authorization Management Program (FedRAMP), the contractor shall provide minimum security controls required to protect Federal information and information systems in accordance with IRS and National Institute of Standards and Technology (NIST) requirements.
Business Entitlement Access Request System (BEARS) /Entitlement - Role-based user permission groups
The contractor shall ensure all applications and platforms integrate with the IRS to establish least privilege BEARS entitlements for all roles that prevent any one role from authorizing a transaction from end to end.
Privileged User Management and Access System (PUMAS)
The contractor shall ensure all applications and platforms integrate with the IRS’s PUMAS to secure, provision, manage, control, and monitor all activities associated with all types of privileged identities to include, but not limited to, privileged user accounts, service accounts, and secrets management for on-premises and cloud-based applications and infrastructure.
Log Management and ESAT.
The contractor shall ensure systems provide audit trails in an approved automated format acceptable to the IRS for all user actions and activities when using or maintaining the system. In accordance with NIST 800-53 Audit and Accountability (AU) controls, applications and platforms shall integrate with ESAT for audit logging to support organization-wide analysis and correlation for situational awareness.

The contractor shall provide to the IRS to be used in accordance with OMB Memo 21-31, the system logs for both services implemented on servers within the authorization boundary and services deployed on Cloud Service Offerings. The contractor shall collect and maintain network and system logs on Federal Information Systems for both on-premises systems and connections hosted by third parties, and when it is necessary to address a cyber incident on Federal Civilian Executive Branch Information Systems.

Federated Authentication Services Technology (FAST)/Homeland Security Presidential Directive 12 (HSPD-12) Compliant Authentication
The contractor shall ensure the system enforces the use of phishing resistant, modern multifactor authentication (MFA) compliant with Treasury, Federal and HSPD-12 Policy/Guidance. Use of MFA shall be at the exclusion of all other authentication methods i.e., username and password.

The contractor shall support a secure, multi-factor method of remote authentication and authorization to identified IRS Administrators that will allow IRS designated personnel the ability to perform management duties on the system. The contractor shall support MFA including phishing resistant MFA (e.g., Fast Identity Online/Web Authentication and public key infrastructure (PKI)) as required by Office of Management and Budget (OMB) Memo 22-09. The contractor shall support a secure, multi-factor method of remote authentication and authorization to identified contractor administrators that will allow contractor designated personnel the ability to perform management duties on the system.

Use of federated MFA may be leveraged by adopting one or more of the following Treasury/IRS Enterprise Services:

i. Secure Access Digital Identity (SADI) for authenticating external users.

ii. IRS Active Directory Federation Services (ADFS) for internal IRS users

iii. Common Access Identity Assurance (CAIA)/Treasury Enterprise Authentication Service (TEAS) in support of all Treasury.

Cryptography Key Establishment and Management (System and Communications Protection (SC-12))
The contractor shall establish and manage cryptographic keys for required cryptography employed within the information system in accordance with centralized management of key generation, distribution, storage, access, and destruction in accordance with NIST SP 800-57, Recommendation for Key Management.
Data-at-Rest and Data-in-Motion Encryption of all IRS Data.
The contractor shall ensure all applications encrypt data at rest (per NIST 800-53, latest revision, SC-28) and data in transit (per NIST 800-53, latest revision, SC-9). SC-28 and SC-9 must pass all objective criteria stated in NIST 800-53. In addition, the encryption solution must meet or exceed all Federal Information Processing Standards (FIPS) 140 standards. All web traffic will enforce Hypertext Transfer Protocol (HTTPS) Secure Sockets Layer/Transport Layer Security (SSL/TLS) protocols.
Data Jurisdiction
The contractor and subcontractors shall identify all data centers that the data at rest or data backup will reside. All data will be guaranteed to reside (and transit) within the United States (or U.S. territories).
Non-repudiation
The contractor shall ensure the sender of information is provided with proof of delivery, and the recipient is provided with proof of the sender’s identity. The IRS uses digital certificates to confirm the identity of Internet users sending x.509 standard encrypted information, to verify the integrity and origin of file contents. The contractor shall agree to install United States Treasury TLS site certificates for the purpose of authenticating traffic between the contractor application and the IRS. The use of SSL or TLS to facilitate arbitrary transmission control protocol (TCP) and user datagram protocol (UDP) or other protocols (effectively, anything other than HTTP) inside the encrypted TLS tunnel between an internal IRS client and an external server cannot be used. Site-to-site virtual private network (VPN) or internet protocol security (IPsec) can be used as long as there are verifiable controls to ensure that the vendor end of that tunnel is an environment that is a closed environment. That is, the environment must be isolated at the network layer from other customers services by the offeror and does not provide for communications to other services (e.g., a gateway or routing service to endpoints outside of the control of the vendor submitting the proposal, etc.).
Media Transport
The contractor shall document activities associated with the transport of IRS agency information stored on digital and non-digital media and employ cryptographic mechanisms to protect the confidentiality and integrity of this information during transport outside of controlled areas. The contractor shall ensure all digital media, containing IRS information, that is transported outside of controlled areas must be encrypted using FIPS 140-2 level 2, FIPS 140-3 or National Security Agency (NSA) approved cryptography; nondigital media must be secured using the same policies and procedures as paper. The contractor shall ensure media, containing IRS information that is transported outside of controlled areas must ensure accountability. This can be accomplished through appropriate actions such as logging and a documented chain of custody form. IRS data that resides on mobile/portable devices (e.g., USB flash drives, external hard drives, and SD cards) must be encrypted. All IRS data residing on laptop computing devices must be protected with NIST-approved encryption software.
Boundary Protection
The contractor shall ensure that IRS information, other than unrestricted information, being transmitted from Federal government entities to external entities using cloud services is inspected by Trusted Internet Connections (TIC) processes, or the contractor shall route all external connections through a TIC in accordance with OMB Memo 19-26.
Security Alerts, Advisories, and Directives
The contractor, subcontractor or cloud service provider shall provide a list of personnel, identified by role, with system administration, monitoring, and/or security responsibilities who shall receive security alerts, advisories, and directives.
Developer Security Testing and Evaluation
The contractor shall provide the IRS with all test plans and test results at least 30 days prior to the release of any new code, settings, enhancement(s) or deprecation of features.
Software Bill of Materials (SBOM)/Attestation
The contractor shall provide a software build/bill of materials, and attestation in accordance with OMB Memo 22-18 using CISA templates.
RA-05 Vulnerability Mitigation

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 .