The 10 Questions Partners Ask Most in Cynomi Office Hours

TU0LZJQA1-U0B3VV05084-10fa14008046-512
Diana Wright Publication date: 9 November, 2026
Education

Every two weeks, service providers running their security practice on Cynomi join Office Hours to work through the platform live with our partner and solutions teams. The questions are specific and practical: why an assessment suddenly looks half-finished, how to add a framework midway through an engagement, whether closing a task moves a risk score. If you deliver cybersecurity services on Cynomi, you’ve likely run into a few of these yourself.

We collected the 10 questions that came up most often across recent sessions and put the answers in one place. Use this guide as a quick reference before your next client review, or share it with team members who are newer to the platform.

Assessments, Scope, and Frameworks

1. Why do some of my migrated assessments look unanswered?

The New Assessment Experience maps one question to one task. In the legacy assessment, a single multi-select question could cover several tasks at once, so any option you left unselected never registered as an answer. During migration, each of those options became its own question, and the ones that were never answered now appear as open. The underlying tasks were always there in a not started status.

Legacy answers of “partial” and “I don’t know” were handled differently. Because one legacy answer could apply to several tasks, there was no precise way to translate it, so Cynomi cleared those answers and left every task status exactly as it was. Each affected question carries a searchable note with your original answer and any assessment notes. Task statuses, owners, dates, evidence, SOPs, and history all carried over untouched.

You don’t need to re-answer everything. When partners raised this during a live Q&A on migrated client data, the team explained that tasks and assessment answers now sync in both directions, so the assessment fills in as your team updates task statuses. If you’d rather close the gap directly, search the assessment for “partial” or “answer cleared automatically,” select the results, and update them in bulk. One thing to expect: tasks tied to legacy questionnaires that were never submitted were hidden from scoring before and now count, which can shift posture and compliance scores slightly for those clients.

2. How do I add a framework partway through an engagement?

Frameworks are now enabled in each client’s account settings, separate from scope. When you enable a new one, such as adding NIST CSF 2.0 for a client that started with SOC 2 (shown step by step in Office Hours), Cynomi shows how many of that framework’s tasks sit outside the current scope. Open the scope module and the platform suggests the missing tasks, already filtered to the new framework. Select them, save the scope, and the client is assessed against the full framework.

Cross-mapping carries your existing work forward, so overlapping questions are already answered. Removing tasks from scope is just as safe. Scope controls what’s visible and scored, while Cynomi keeps the underlying answers and task data, so anything you bring back into scope returns with its history intact. For a maturity path, you can also swap a client’s template outright. A client who started on CIS Controls IG1 can move to IG2 or a NIST CSF template in one step, and the platform shows exactly which tasks the change adds before you confirm.

3. What’s the best way to set up a SOC 2 assessment?

Start at the service provider level under Templates, the same flow we demonstrated live for a partner building a SOC 2 template. Create a template from scratch, filter the task library by SOC 2, select all, and save. When you create the client, apply that template as the scope and enable SOC 2 in the client’s framework settings so the compliance view reports against it. Applying a template doesn’t enable the matching framework on its own, and that second step is the one partners most often miss.

The same process works for any framework, and templates are reusable, so build them around how you sell: one per framework, one per vertical, or one per service tier. Filters currently work at the task level. Partners have asked to build templates from a specific list of controls, and that capability is in development.

4. Can I create a custom framework?

When a partner asked whether Cynomi supports custom frameworks, the answer came in two parts. You can combine tasks from any frameworks in the library into a custom template, which covers most regional or sector requirements built on an existing standard, such as a state regulation that references NIST CSF. Cynomi’s HIPAA-enhanced healthcare template follows the same approach, pairing the HIPAA Security Rule with incident response, business continuity, and data protection tasks the rule leaves out.

What you can’t do yet is create a framework with its own control names that appears in Compliance Management. For local requirements, add guidance to a task’s SOP field to apply it across every client, or use company notes for a single client. One related point of confusion: the compliance focus field in the Company Profile records the frameworks a client cares about now or expects to need later. It’s there to guide the conversation and doesn’t enable any framework.

Packages

5. What’s the difference between Core, Pro, and One-Time Assessments?

Cynomi Core supports ongoing engagements with clients who don’t have specific compliance requirements. The experience is task-centric and aligned to baseline frameworks such as CIS Controls IG1, NIST CSF 2.0, and Cyber Essentials. Many partners use Core across their managed services base to show clients what their current services already cover and where gaps remain. Cynomi Pro adds Compliance Management, Risk Management, and Business Impact Analysis (BIA) and Business Continuity Planning (BCP) for deeper advisory and compliance work. The Core versus Pro discussion in Office Hours covers how partners position each package with clients.

One-Time Assessments suit project-based engagements. Each runs for 90 days, after which the account becomes read-only. A recent update restored the full controls page (control notes, evidence upload, and export), task names and statuses, all integrations and scans, and access to the Remediation and Reports Coworkers. Task how-to guidance stays reserved for ongoing engagements, so your implementation playbook remains part of the recurring service. The pricing page has the full comparison.

Risk Management

6. Do I need to finish the assessment before adding risks?

No. Tasks are generated as soon as you define scope, so you can build and link risks before, during, or after the assessment. Residual risk will only become meaningful once linked tasks start moving, though.

When you create a custom risk, Cynomi suggests mitigating tasks based on its classification, name, and description, so write descriptions in detail. More context produces better suggestions. Suggestions only come from tasks in scope, which means a scope limited to the HIPAA Security Rule won’t surface privacy tasks for a privacy risk. For clients that already maintain a risk register, import it from XLSX or CSV and deactivate the system-generated risks you don’t need. The built-in register is grounded in the Secure Controls Framework (SCF) risk management model, and our risk register session walks through creating, linking, and importing risks end to end.

7. Does closing linked tasks update residual risk automatically?

Not automatically, and that’s deliberate. Residual risk is a judgment you make with the client about how much exposure remains once the work is done. Only linked tasks inform that judgment, and suggested tasks don’t count until you approve the link.

The Risk Coworker, demonstrated in the same risk management session, speeds up recalibration. It asks how thoroughly your controls are tested, what has changed since the last scoring, and what’s managed outside the platform, then proposes updated residual ratings with its reasoning. Nothing changes until you approve the recommendations you agree with, and approved updates are written to the register and captured in the audit log. Completing every mitigating task lowers a risk’s rating, but the risk stays on the register. For accepted risks, set a next review date and filter the register by overdue reviews to keep renewals on track.

Coworkers and AI

8. Who on my team can use the Coworkers?

At launch, Coworkers were limited to Service Provider Admins. The new Coworker Editor (MSP Only) role, introduced at the start of our Coworkers session, opens them to the rest of your team. It grants full Editor permissions plus access to the AI Space and Coworkers, with view-only access to branding settings, and Service Provider Admins can combine it with a user’s existing roles. The role stays MSP-only by design, since Coworkers exist to help your team produce client deliverables faster.

9. How do I reuse a report or policy across clients?

In the Reports Coworker, select Reuse this report to generate a prompt recipe, then paste it into a session for another client (the Coworkers session covers this workflow in detail). Partners get the strongest results by being specific in their requests. A few prompts that have worked well:

  • Call out which recommendations protect PHI for a healthcare client
  • Focus the body on unimplemented controls and move the full control list to an appendix
  • Add an empty recommendations column for your own commentary
  • Produce the report in the client’s language

Context Management removes much of that repetition. Record your tone of voice, methodology, and standing rules once at the service provider level, add client-specific context where needed, and the Reports and Policy Coworkers apply it on every turn. Client context wins where the two differ. Context shapes how output is framed and worded and never changes values Cynomi calculates, such as risk scores or statuses. Custom policies from the Policy Coworker can be saved straight to the client’s Documents area, and you can ask the Coworker to include version history as you refine them.

10. How do uploaded documents work, and what happens to sensitive data?

AI Suggestions in the New Assessment Experience draw on the Company Profile, connected scans and integrations, and uploaded documents. Upload existing policies, spreadsheets, or even a photo of a whiteboard (an example our sales engineering team shared in Office Hours), and Cynomi reads the content, adds a description, and suggests which questions and tasks it supports as evidence. Every suggestion includes a confidence level, reasoning, and sources, and you control the final answer.

For sensitive content, the model masks items such as credentials before it generates suggestions, so they won’t surface in recommendations. The file itself is stored as uploaded, so keep passwords and secrets out of anything you upload.

Bring Your Questions to the Next Office Hours

These answers came straight from partner questions, and the next session will be shaped the same way. Office Hours runs every two weeks with open Q&A and live walkthroughs in the platform, and recordings are available online. Bring the edge cases from your own client base, and suggest topics you’d like covered.

Register for the next Office Hours session here