Cyber RFP Amendment_1.pdf

PDF 244 KB Posted

Attached to
Cybersecurity Assessments and Services
Solicitation number
BPM041211
Issued by
Maryland

About this file

This document is an amendment to a Request for Proposals (RFP) issued by the State of Maryland for Cybersecurity Assessments and Services. The amended RFP seeks to procure a variety of cybersecurity services, including assessments, penetration testing, authorization to operate, and architecture, engineering, and program services. The RFP outlines specific changes to sections related to staffing plans, offeror experience, insurance requirements, and problem escalation procedures. It also clarifies that offerors must submit a separate Minority Business Enterprise (MBE) Utilization and Fair Solicitation Affidavit & MBE Participation Schedule for each of the two functional areas they are proposing to.

The amended RFP provides details on the required qualifications and experience of key personnel, as well as the types of cybersecurity certifications the contractor must possess. Offerors are also required to provide information on their past experience with similar projects, their organizational structure, and their process for resolving billing errors. The RFP sets specific insurance requirements for the apparent awardee and outlines the need for a problem escalation procedure to be submitted.

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

Amendment #1

CYBERSECURITY ASSESSMENTS AND SERVICES

Request for Proposals (RFP)

# F50B4600024 / BPM041211

January 15, 2024

Ladies/Gentlemen:

This Amendment is being issued to amend and clarify certain information contained in the above referenced RFP. All information contained herein is binding on all Offerors who respond to this RFP. Specific parts of the RFP have been amended. The following changes/additions are listed below; new language has been double underlined and marked in bold (i.e., word) and language deleted has been marked with a strikeout (i.e., word).

1. Section 5.3.2G is amended as follows:

As part of the evaluation of the Proposal for this RFP, Offerors shall propose at least one key personnel for each category that the Offeror is proposing to and shall describe in a Staffing Plan how additional resources shall be acquired to meet the needs of the Department. All other planned positions shall be described generally in the Staffing Plan and may not be used as evidence of fulfilling company or personnel minimum qualifications.

The Offeror shall identify the qualifications and types of staff proposed to be utilized under the Contract including information in support of the Personnel Experience criteria in Section 3.10.2. Specifically, the Offeror shall:

1) Describe in detail how the proposed staff’s experience and qualifications relate to their specific responsibilities, including any staff of proposed subcontractor(s), as detailed in the Work Plan.

2) Provide an Organizational Chart outlining Personnel and their related duties. The Offeror shall include job titles and the percentage of time each individual will spend on his/her assigned tasks. Offerors using job titles other than those commonly used by industry standards must provide a crosswalk reference document.

2. Section 5.3.2H is amended as follows:

The Offeror shall include information on past experience with similar projects and services including information in support of the Offeror Experience criteria in Section

3.10.1. The Offeror shall describe how its organization can meet the requirements of this RFP and shall also include the following information:

1) The number of years the Offeror has provided the similar goods and services;

2) The number of clients/customers and geographic locations that the Offeror currently serves;

3) The names and titles of headquarters or regional management personnel who may be involved with supervising the services to be performed under the Contract;

4) Cybersecurity Certifications: The Contractor shall provide cybersecurity certification staffing numbers across enterprise software and hardware applications and platforms (i.e., Google Workspace, ServiceNow, Microsoft Active Director, Okta, Palo Alto, Cisco, Crowdstrike);

5) The Offeror’s process for resolving billing errors; and

6) An organizational chart that identifies the complete structure of the Offeror including any parent company, headquarters, regional offices, and subsidiaries of the Offeror.

3. Section 5.3.2L is amended as follows:

The Offeror shall provide a copy of its current certificate of insurance showing the types and limits of insurance in effect as of the Proposal submission date. The current insurance types and limits do not have to be the same as described in Section 3.7 3.6. See Section

3.7 3.6 for the required insurance certificate submission for the apparent awardee.

4. Section 5.3.2F4 is amended as follows:

4) The Offeror shall provide a draft Problem Escalation Procedure (PEP) that includes, at a minimum, titles of individuals to be contacted by the Contract Monitor should problems arise under the Contract and explains how problems with work under the Contract will be escalated in order to resolve any issues in a timely manner. Final procedures shall be submitted as indicated in Section 3.9 3.8.

5. The unnumbered paragraph of Section 4.26.2 is amended as follows:

An Offeror must properly complete and submit a separate Attachment D-1A, MBE Utilization and Fair Solicitation Affidavit & MBE Participation Schedule, for EACH Category Functional Area (I and II) for which it is submitting a proposal. If an Offeror is submitting a proposal for each of Functional Areas I and II, the Offeror must submit three two separate Attachment D-1As, one for each of the two Functional Areas.

Issued by: Carla Thompson, Procurement Officer

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