Relating to the application of the open meetings law and public information law to government information related to certain cybersecurity measures.

Contracts

You must restructure how you draft agreements with government entities to trigger the "solely intended" exemption in Sec. 552.1391(b)(1).

• Segregate SOWs: Do not bundle cybersecurity services with general operational maintenance. Create a standalone Statement of Work (SOW) or contract *solely* for cybersecurity/critical infrastructure protection. Bundled contracts risk losing the exemption.
• Mandatory Notice Clause: Insert a provision requiring the government client to send the statutory 5-day notice of potential disclosure to a specific, monitored email address (e.g., `legal@yourfirm.com`).

Hiring/Training

• Sales Teams: Train sales staff to request Closed Sessions (under Sec. 551.0761) for any portion of a pitch or negotiation involving security specifications or network schematics.
• Project Managers: Staff handling government accounts must be trained to watermark all deliverables (maps, configs, reports) as confidential under this specific statute before submission.

Reporting & Record-Keeping

• Insurance Disclosures: When providing Certificates of Insurance (COI) or policy documents to government clients, you may now submit full policy details. However, you must explicitly label the coverage limits and deductible amounts as confidential under Sec. 552.1391(b)(2) to prevent them from becoming a "menu" for ransomware actors.
• Incident Reporting: Any breach notification or incident report submitted to a government client must be stamped confidential under Sec. 552.1391(b)(3).

Fees & Costs

• No New Fees: The state imposes no new filing fees.
• Cost Impact: Minimal administrative costs related to contract redrafting and document management system updates.