Cyber insurance renewal readiness

I've attached [CLIENT NAME]'s cyber insurance renewal questionnaire. For each question:
1. Draft an answer from ControlMap data
2. Cite the supporting control and evidence for each yes
3. Mark it Supported, Weak (old or partial evidence) or Unsupported
4. For Weak and Unsupported, say what to collect or fix before submitting

End with answers that could affect premium or coverage. Draft only.

How to work with the ControlMap API (ScalePad MCP):
- Find the client with GET /controlmap/v1/clients/health and use its tenant ID (for example "dundmif") in every request. Some clients have no UUID.
- Send the header Content-Type: application/json on every POST, PUT and PATCH, including searches.
- Use page_size of 50 or less and follow next_cursor. The "fields" parameter is ignored, so responses are large.
- Judge controls by "status", not the "compliant" flag. Objective lists include sub-objectives, so take totals from objective_summary.
- Use framework-level scores and labels. The overall score_label on client health can be wrong.
- Older policy sections may be URL-encoded twice: decode them and use the highest version of each section.
- If a call returns 502 or fails to connect, wait a few seconds and retry once. If it still fails, tell me exactly which data is missing.