APPENDIX A- 26-26.xlsx
XLSX spreadsheet 21 KB Posted
- Attached to
- 9280-26-R-IFBD-00029
- Solicitation number
- 3160007900
- Issued by
- Greene County, Mississippi
About this file
This appendix document outlines the detailed requirements and functions for the University of Southern Mississippi's managed cybersecurity services procurement (Solicitation 9280-26-R-IFBD-00029). The university seeks an enterprise-grade managed cybersecurity solution delivering 24/7 threat prevention, detection, investigation, and response capabilities across approximately 9,500 active users, 300 servers, and cloud-based infrastructure. The vendor must provide a comprehensive managed service—not solely software—including an initial cybersecurity assessment evaluating identity and access controls, email security, endpoint security, server security, and cloud workloads, with documented findings and recommendations for university approval prior to implementation. Required services encompass identity and access security with multi-factor authentication and conditional access controls, email and collaboration security protecting against malware, spam, and phishing threats, endpoint detection and response for workstations and managed devices, server and cloud workload monitoring with vulnerability assessment and threat detection, a staffed Security Operations Center providing human-led investigation and response, centralized SIEM with log collection and analytics, and penetration testing services. The sealed bid submission deadline is Monday, March 9, 2026, at 2:00 p.m. Central Time at Bond Hall, Room 214, Hattiesburg, Mississippi, with vendor questions due by 5:00 p.m. CST on March 3, 2026, and written responses provided by addendum no later than March 5, 2026. The university seeks a three-year agreement with potential two additional one-year renewals.
Vendors must demonstrate Microsoft alignment as verified Managed Security Services Providers through membership in the Microsoft Intelligent Security Association, Microsoft Security Partner Designation, Microsoft MDR/MXDR partner status, or documented security specializations, and must provide minimum three customer references from implementations within the last 12 months, preferably from higher education institutions. The vendor must maintain documented disaster recovery and business continuity plans, notify the university of confirmed high-severity incidents within seventy-two hours of discovery, maintain protected audit logs of administrative access and configuration changes, and return all university security data in non-proprietary format upon contract termination. Proposals will be evaluated on a 100-point scale with weightings of 45 points for Cost, 40 points for Requirements, and 15 points for Implementation Schedule. No specific budget range or award value is disclosed in the available solicitation documents, and no incumbent vendors or current contractors are identified. Annual invoicing is requested with payment processed within 45 days of invoice receipt in accordance with Mississippi Code Section 31-7-305. The solution must comply with the Mississippi Department of Information Technology Services' State Enterprise Cloud Offsite Internet Hosting Security Policy.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| ADDENDUM 2.pdf | ||
| download (1).pdf | ||
| USM BID 26-26 LEGAL AD.pdf | ||
| RFP 26-26-ENTERPRISE CYBERSECURITY MONITORING AND RESPONSE PROGRAM FINAL.pdf | ||
| APPENDIX A-RFP 26-26.xlsx | XLSX spreadsheet | |
| RFP-ENTERPRISE CYBERSECURITY MONITORING AND RESPONSE PROGRAM FINAL.pdf | ||
| download.xlsx | XLSX spreadsheet | |
| download.pdf | ||
| ADDENDUM 1.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
Sheet1
| Identifier | Req/Opt | Requirements and Functions | Yes/No | Details |
| General Requirements | ||||
| 1 | R | The vendor must provide enterprise grade managed cybersecurity services focused on threat prevention, detection, investigation, and response. | ||
| 2 | R | The vendor must be capable of supporting a higher education environment with a large population of users, endpoints, and servers. | ||
| 3 | R | The vendor must provide a solution delivered as a managed service and not solely as a software-only offering. | ||
| 4 | O | The solution should be designed to augment existing internal IT and information security staff rather than replace them. | ||
| 5 | O | The solution should be scalable to accommodate growth in users, devices, and infrastructure. | ||
| 6 | R | The vendor must acknowledge that all university security data remains the property of the university and must be returned in a non-prioriety format upon contract termination. | ||
| 7 | R | The vendor must maintain a documented disaster recovery and business continuity plan supporting continuity of monitoring and response services. | ||
| Vendor Qualifications | ||||
| 8 | R | The vendor must demonstrate experience delivering managed cybersecurity services in an enterprise environment by providing at minimum three customer references including contact information, that have implemented the proposed solution and/or services in the last 12 months; preferably from higher education institutions. | ||
| 9 | R | The vendor must demonstrate the operational capability to provide 24x7x365 security monitoring and incident response services. | ||
| 10 | R | The vendor must be a Microsoft aligned Managed Security Services Provider (MSSP) or equivalent. Meaning that the vendor shall demonstrate verified partnership with Microsoft in the delivery of managed security services leveraging Microsoft security technologies. | ||
| 11 | R | Acceptable evidence of Microsoft MSSP alignment must include one or more of the following: | ||
| o Membership in the Microsofr Intelligent Secutiy Association (MISA) | ||||
| o Microsoft Security Partner Designation | ||||
| o Microsoft verified managed detection and response (MDR or MXDR) partner status | ||||
| o Documented Microsoft security specializations or equivalent credentials | ||||
| 12 | O | The vendor should demonstrate advanced Microsoft security specializations related to: | ||
| o Secutiry operations | ||||
| o Threat detection | ||||
| o Identity security | ||||
| o Cloud security | ||||
| Security Assessment and Baseline Configuration | ||||
| 14 | R | The vendor must perform an initial cybersecurity assessment of the university's environment. | ||
| 15 | R | The assessment must evaluate identity and access controls, email security, endpoint security, server security, and cloud workloads. | ||
| 16 | R | The vendor must provide documented findings and recommended configuration changes for university review and approval prior to implementation. | ||
| 17 | O | The vendor should align recommendations with industry-recognized cybersecurity best practices. | ||
| 18 | O | The vendor should identify security gaps, misconfiguratioins, and areas of risk exposure. | ||
| Identity and Access Security | ||||
| 19 | R | The solution must support enforcement of multi-factor authentication for privileged and administrative accounts. | ||
| 20 | R | The solution must support conditional or risk based access controls. | ||
| 21 | R | The solution must provide monitoring and detection of identity based threats and anomalous authentication behavior. | ||
| 22 | R | The solution must support privileged access management workflows. | ||
| 23 | O | The solution should support identity risk scoring and automated remediation actions when appropriate. | ||
| Email and Collaboration Security | ||||
| 24 | R | The solution must provide managed protection against email based threats including: | ||
| o Malware | ||||
| o Spam | ||||
| o Phishing | ||||
| 25 | R | The solution must support inspection and protection of links and attachments. | ||
| 26 | R | The solution must support domain authentication and sender validation controls. | ||
| 27 | O | The solution should include ongoing policy tuning to reduce false positives and alert fatigue. | ||
| 28 | O | The solution should extend protection to collaboration platforms and shared content repositiories. | ||
| Endpoint Security | ||||
| 29 | R | The solution must provide managed detection and response for user workstations and managed endpoint devices. | ||
| 30 | R | The solution must include continuous monitoring for malicious or suspicious activity. | ||
| 31 | R | The solution must support investigation, isolation, and containment of compromised devices. | ||
| 32 | O | The solution should support automated remediation actions configurable to university preferences. | ||
| 33 | O | The solution should correlate endpoint telemetry with identiy, email, and server security signals. | ||
| Server and Cloud Workload Security | ||||
| 34 | R | The solution must provide managed security monitoring for server environments. | ||
| 35 | R | The solution must support vulnerability assessment and server inventory visibility. | ||
| 36 | R | The solution must support threat detection and response for on-premises and cloud-hosted servers. | ||
| 37 | O | The solution should support scalable onboarding methods for large server environments. | ||
| 38 | R | The solution must encrypt sensitive university data in transit and at rest using industry standard encryption protocols. | ||
| 39 | O | The solution should provide configuration recommendations to improve server security posture. | ||
| Security and Service Management | ||||
| 40 | R | The vendor must operate a security operations center (SOC) staffed by trained cybersecurity professionals. | ||
| 41 | R | The SOC must provide monitoring and response services twenty-four (24) hours a day, (7) days per week, including holidays. | ||
| 42 | R | The SOC must provide human led investigation and response, not solely automated alerting. | ||
| 43 | O | The SOC shoud provide proactive threat hunting capabilities. | ||
| 44 | R | The solution must include defined incedent severity classifications. | ||
| 45 | R | The solution must include documented incident response and escalation procedures. | ||
| 46 | R | The vendor must notify the university of confirmed high severity incidents within seventy-two (72) hours of discovery. | ||
| 47 | R | The vendor must coordinate incident reponse activities with university personnel. | ||
| 48 | O | The solution should support real-time collaboration during active incident response. | ||
| 49 | R | The vendor must define service level objectives related to incident investigation, escalation, and notification. | ||
| 50 | R | The vendor must define response expectations for high severity incidents. | ||
| 51 | R | The vendor must maintain protected audit logs of adminstrative access and configuration changes. | ||
| 52 | O | The vendor should provide historical or benchmark performance metrics upon request. | ||
| Security Information and Event Management (SIEM) | ||||
| 53 | R | The solution must provide centralized log collection and correlation across security domains. | ||
| 54 | R | The solution must support analytics and detection rules for identifying security threats. | ||
| 55 | R | The solution must provide dashboards or reporting for visibility into security events and incidents. | ||
| 56 | O | The solution should support custom detection logic and threat hunting queries. | ||
| 57 | O | The solution should integrate telemetry from multiple security control types. | ||
| Reporting and Visibility | ||||
| 58 | R | The solution must provide access to incident records and investigation details. | ||
| 59 | R | The solution must provide regular reporting on security posture and incident activity. | ||
| 60 | O | The solution should include recommendations for continuous security improvement. | ||
| 61 | O | The solution should support post incident or after action reporting of significant events. | ||
| Penetration Testing and Visibility | ||||
| 62 | R | The vendor must provide penetration testing services as part of the managed security offering or through an integrated solution. | ||
| 63 | R | The penetration testing must include documented findings and prioritized risk reporting. | ||
| 64 | O | The vendor should support both internal and external testing methodologies. | ||
| 65 | O | The vendor should support validation testing following remediation efforts. | ||
| Onboarding and Implementation | ||||
| 66 | R | The vendor must provide a structured onboarding and implementation process. | ||
| 67 | R | The onboarding process must include a project kickoff, planning, and defined milestones. | ||
| 68 | R | The vendor must document required prerequisites and access requirements. | ||
| 69 | O | The vendor should provide knowledge transfer and documentation to university staff. | ||
| 70 | O | The vendor should minimize the time between contract execution and full SOC monitoring. |
File details come from the government source that posted it. Updated .