Laserfiche WebLink
11 <br />proposed to address the incident, and the identity and contact information of <br />Contractor’s designated incident response lead. <br />b.Investigation and Remediation. Cooperate fully with City to investigate and resolve <br />the Security Incident, including providing the City with timely access to all relevant <br />logs, forensic analysis, and documentation. Contractor shall promptly implement all <br />necessary remedial measures to contain, mitigate, and prevent recurrence of the <br />incident. <br />c.Regulatory Compliance. Comply with all applicable breach notification laws, <br />including California Civil Code §1798.82 (California Data Breach Notification Law) <br />and any other applicable state or federal requirements. Contractor shall bear all costs <br />associated with legally required breach notifications to affected individuals, including <br />notification preparation, mailing, credit monitoring services (if applicable), and any <br />call center support. <br />d.Post-Incident Review. Within thirty (30) days following resolution of the Security <br />Incident, provide City with a written post-incident report that includes: root cause <br />analysis, a timeline of events, actions taken to remediate the incident, and a plan for <br />preventing similar incidents, including any changes to business practices, security <br />controls, or system architecture. <br />e.Security Standards. Contractor shall maintain, at a minimum, SOC 2 Type II <br />compliance and shall provide the City with a current SOC 2 Type II report annually. <br />Contractor shall conduct penetration testing at least annually by a qualified third party <br />and shall share a summary of findings and remediation actions with the City upon <br />request. Contractor shall maintain and follow a vulnerability management program <br />that includes patching Critical vulnerabilities within fifteen (15) days, High <br />vulnerabilities within thirty (30) days, and Medium vulnerabilities within sixty (60) <br />days of discovery or vendor release. <br />f.Definition. “Security Incident” means any unauthorized access, acquisition, use, <br />disclosure, modification, or destruction of City Data, or any breach or compromise of <br />any system, network, or application used to store, process, or transmit City Data, <br />including but not limited to: data breaches, ransomware attacks, denial of service <br />attacks, unauthorized system access, malware infections, and any incident requiring <br />notification under applicable law. <br />29.Substitution of Securities in Lieu of Retention. Pursuant to Section 22300 of the <br />Public Contract Code, the Contractor may substitute securities for any money held by the <br />City to insure performance of the contract. At the request and expense of the Contractor, <br />securities equivalent to the amount withheld shall be deposited with the City or federally- <br />chartered banks as an escrow agent, who shall return such securities to the Contractor <br />upon satisfactory completion of the contract. <br />Docusign Envelope ID: D15BA154-47D3-8EAA-8171-B89F63E73DD1