6108 Questions-Responses.pdf
PDF 51 KB Posted
- Solicitation number
- S-KE0010-00014491
- Issued by
- Lane County, Oregon
About this file
This is a Questions and Responses document related to a patch management solution procurement for the Oregon Department of Human Services (ODHS) and Oregon Health Authority (OHA). The document addresses clarifications regarding system integration requirements, deployment capabilities, and validation mechanisms. Key requirements have been clarified to specify nine mandatory capabilities: supported platforms and applications, automation capabilities, security of patch delivery with United States-based cloud data storage, compliance support and zero-day patch availability, centralized management console with ease of deployment, enterprise scalability, and Active Directory integration. Additionally, three capabilities are designated as preferred: granular control with reporting and alerts, vulnerability management integration, and integration with existing systems including SCCM, Intune, and SIEM platforms. The procurement specifies that while integration with the existing SIEM system (currently utilizing Q-RADAR and Microsoft Sentinel, owned and operated by DAS-EIS) is desired, it is not mandatory. The solution must support geographical deployment across different organizational locations and regions with scheduling flexibility to accommodate varying time zones.
Post-deployment validation of patch success and system stability has been confirmed as a vendor responsibility within the scope of the RFQ, with emphasis on post-deployment reporting capabilities. The patch management solution must demonstrate capability to track and validate deployment outcomes across the organization's infrastructure. No specific response deadlines, award dates, contract terms, or pricing information is provided in this clarification document.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Notice of Intent_Fleet_CAT 938 Loader.pdf |
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
Number Question
1 The Key requirements state that there must be integration with e SIEM system. Are we required to create a new SIEM solution to track the patch management solution, or will this be integrated with ODHS/OHA’s existing SIEM?
The current SIEM is owned and operated by DAS-EIS. Integration is desired but not a requirement. DAS-EIS uses Q-RADAR and Microsoft Sentinel.
2 The Patch Deployment Flexibility requirement asks for “Geographical Support”. What exactly does this mean? Does this just mean that the solution can be accessed from anywhere?
The solution must support deploying patches across different organizational locations and geographic regions, with scheduling flexibility to accommodate local time zones.
3 Key Requirements; multiple requirements listed have a “Yes or No” followed by “Required”.
Some just say “Required”. For example “Automation Capabilities: No, Required”. What is the Yes/No for? Can you clarify what is required from this list?
Here is a rebuild of those Key Requirements for clarity:
1. Supported Platforms and Applications: Required
2. Automation Capabilities: Required
3. Granular Control, Reporting, and Alerts: Preferred
4. Vulnerability Management Integration: Preferred
5. Security of Patch Delivery and Cloud Data Stored in the United States:
Required
6. Compliance Support and Zero-Day Patch Availability: Required
7. Centralized Management Console and Ease of Deployment: Required
8. Scalability for Enterprise Operations: Required
9. Integration with Active Directory: Required SCCM: Preferred Intune: Preferred SIEM: Preferred
4 Do mechanisms exist for validating patch success and system stability post-deployment? Is this something to be scoped into this RFQ as a vendor responsibility?
Validating patch success is a requirement. Thinking in terms of post-deployment reporting.
File details come from the government source that posted it. Updated .