Skip to main content
Connector guides

Connect CYRISMA

CYRISMA is a vulnerability and risk management platform. An MSP runs it for each customer organization, and its New Partner API lets the MSP read the state of all of them and provision new ones.…

Written By Christopher Scaminaci

Last updated 13 days ago

CYRISMA is a vulnerability and risk management platform. An MSP runs it for each customer organization, and its New Partner API lets the MSP read the state of all of them and provision new ones. StackJack connects an AI assistant to that API.

Connecting CYRISMA to StackJack gives your AI assistant a family of cyrisma_ MCP tools. MCP (Model Context Protocol) tools are the standardized commands an AI assistant can call through StackJack. With them, your AI can:

  • Find what is exposed - open vulnerabilities across your customer tenants, by CVE or by root cause (the product, package or setting behind many CVEs), and the assets each one affects
  • Track posture over time - current score and letter grade per tenant, the vulnerability trend, rollups ranked by CVE, root cause, severity or asset type, and secure-baseline results by asset
  • Report usage - endpoint usage by day or month, for billing and capacity checks
  • Read the structure - the tenants you manage, their users, and the technicians you can assign
  • Provision tenants (on Pro plans, with a Read and write key) - create, update, suspend, reactivate and decommission a tenant

How StackJack authenticates to CYRISMA

CYRISMA uses an API key: a client ID and a client secret. StackJack exchanges the pair for a short-lived token on its own, asks for exactly the access a tool needs, and never shows the token. You enter the pair and your instance address.

Creating the key

  1. Sign in to CYRISMA and open Settings, then API Keys. Keys exist at the organization level and at the instance level. A key belongs to the one you create it under.
  2. Create a key. Give it a name and choose its access level: Read for reporting only, or Read and write to also provision tenants.
  3. Choose whether the key applies to organizations beneath this one. Leave that off to limit the key to a single organization.
  4. Copy the client ID (it starts with pc_) and the client secret (it starts with pcs_). CYRISMA shows both once. If you lose the secret, revoke the key and create a new one, which has a new client ID.

Finding your instance address

Your instance address is the address you sign in to CYRISMA at, for example https://ccnnnnnn.cyrisma.com. It always ends in cyrisma.com. Enter the host only: StackJack adds the paths itself.

Connect it in StackJack

  1. Open Connectors, then CYRISMA.
  2. Enter the address in Instance address, the key's client ID in Client ID and its secret in Client secret.
  3. Click Test connection. StackJack asks CYRISMA for a new token and reads the first tenant of the tenant list. Both steps change nothing.

Enter all three values again whenever you save the connection, including when you only rename it.

What is worth knowing before you start

Read keys and Read and write keys

A Read key serves every reporting, tenant, user and lookup tool. The tools that change a tenant, and two that read provisioning state (a provisioning job's status and the technicians you can assign), need a key with Read and write access. On a Read key they fail with a clear message, and that failure does not count against the connection.

Tenants and the reach of a key

Every call is limited to the organizations the key reaches: the one it was created under, plus everything beneath it when the key applies to sub-organizations. Start with cyrisma_list_partner_tenants to see the tenants and their ids. The reporting tools take an optional tenantIds list (comma-separated) to narrow a read, and includeDescendants to widen each id to the tenant and everything beneath it. A tenant outside the key's reach is refused with a 403, whether or not it exists.

Paging

The reporting lists use an opaque cursor: read the first page, then pass the next_cursor it returns back unchanged until it is null. pageSize is 1 to 500 (default 100). The tenant, user and technician lists page by number: page from 1 and pageSize from 1 to 100 (default 50).

Changing a tenant

Five tools change tenants. They are on the Pro tier, are marked destructive and ask for approval before they run:

  • Provision creates a billable tenant and returns a job. Poll cyrisma_get_provisioning_job until it is deployed. The country you choose also decides where the tenant is hosted and its data stored. Send an idempotency_key of your own: a retry with the same key returns the original job instead of a second tenant.
  • Update changes a tenant's details. Setting trial to false ends a trial and starts billing. That cannot be undone.
  • Suspend and reactivate switch a tenant's access off and on, optionally for the tenants beneath it. They cannot target your own tenant.
  • Decommission removes a tenant: it is disabled at once and deleted when the job finishes. Every tenant beneath it must already be suspended, disabled or deleted. Every decommission needs a fresh idempotency key.

What is not offered

CYRISMA does not let an API key manage a tenant's authentication policy or create, change, disable or reset the MFA of a user: those routes need a signed-in user's token. StackJack offers no tool for them. Users and technicians are read-only here.

When CYRISMA refuses a call

  • The key is refused: the client ID or secret is wrong, or the key was revoked. Create a key under Settings, then API Keys, and paste the three values again.
  • The key does not have the access level the tool needs: create a key with Read and write access.
  • The key's tenant is not active: the organization the key belongs to may be suspended.
  • A tenant is outside the key's reach: use cyrisma_list_partner_tenants to see which tenants the key reaches. On the provisioning routes CYRISMA answers a bare 401 for the same reason.
  • A tenant is in the wrong state (409): suspend needs an active tenant and reactivate needs a suspended one. Read the tenant's status with cyrisma_get_admin_tenant.
  • A filter, window or cursor is rejected: the answer names it. The rollups and usage reads need both a from and a to date, written yyyy-MM-dd.
  • Rate limited: CYRISMA does not publish a limit. StackJack paces its calls and backs off when CYRISMA asks it to slow down.

Plans and limits

Reads are available on the Free tier. The five tenant provisioning tools are Pro. Business reaches the same tools as Pro and differs by monthly call quota.

See the generated CYRISMA tool reference for the current inventory, plan assignment, input schemas and destructive-action labels.

CYRISMA tools

cyrisma_ · 35 tools · Free 30 · Pro 5

Lookups

ToolWhat it does
cyrisma_list_countries
Free · Read-only
Lists every country, ordered by name.
cyrisma_list_currencies
Free · Read-only
Lists the currencies prices can be shown in, ordered by code.
cyrisma_list_industries
Free · Read-only
Lists the industries a tenant can have.
cyrisma_list_tenant_types
Free · Read-only
Lists the tenant types.
cyrisma_list_user_roles
Free · Read-only
Lists the roles a user can be given, as the key strings other CYRISMA routes take.

Tenants

ToolWhat it does
cyrisma_get_admin_tenant
Free · Read-only
Returns the full details of one tenant.
cyrisma_list_admin_tenants
Free · Read-only
Lists a tenant and every tenant beneath it, ordered by name.
cyrisma_update_tenant
Pro · Destructive
DESTRUCTIVE.

Provisioning

ToolWhat it does
cyrisma_decommission_tenant
Pro · Destructive
DESTRUCTIVE.
cyrisma_get_provisioning_job
Free · Read-only
Returns the current state of a create or decommission job.
cyrisma_list_eligible_technicians
Free · Read-only
Lists the users who can be assigned as technician to a tenant you are about to provision: enabled users with write access to the parent tenant.
cyrisma_provision_tenant
Pro · Destructive
DESTRUCTIVE.
cyrisma_reactivate_tenant
Pro · Destructive
DESTRUCTIVE.
cyrisma_suspend_tenant
Pro · Destructive
DESTRUCTIVE.

Users and technicians

ToolWhat it does
cyrisma_get_user
Free · Read-only
Returns one user and their first access grant within tenantId and the tenants beneath it.
cyrisma_list_technicians
Free · Read-only
Lists the users who can be assigned as technician to an existing tenant: enabled users with write access to it.
cyrisma_list_users
Free · Read-only
Lists the users with access to a tenant or any tenant beneath it, ordered by email unless sort is given.

Reporting

ToolWhat it does
cyrisma_export_vulnerability_events
Free · Read-only
Returns a single-page export of live vulnerability detection events within a bounded time window, as JSON.
cyrisma_get_cve
Free · Read-only
Returns the details of a single CVE, scoped to the authorized partner's tenants.
cyrisma_get_overall_dashboard
Free · Read-only
Returns one row per tenant in the authorized partner's tenant scope: where the tenant sits in the hierarchy and its headline figures.
cyrisma_get_partner_tenant
Free · Read-only
Returns one tenant plus every tenant beneath it in the hierarchy, narrowed from the key's authorized scope.
cyrisma_get_posture
Free · Read-only
Returns each tenant's current score (0 to 100) and letter grade (A+ to F) for overall risk and vulnerability posture.
cyrisma_get_root_cause
Free · Read-only
Returns the details of a single vulnerability root cause, scoped to the authorized partner's tenants.
cyrisma_get_usage
Free · Read-only
Returns endpoint usage history, bucketed by day or month, over a bounded date range for the authorized partner tenants.
cyrisma_get_vulnerability_rollups
Free · Read-only
Returns per-tenant vulnerability rollups, grouped and ranked by the requested dimension, over a bounded date range.
cyrisma_get_vulnerability_series
Free · Read-only
Returns a per-tenant vulnerability trend series, one data point per day over the requested range.
cyrisma_get_vulnerability_state
Free · Read-only
Returns an aggregated vulnerability posture snapshot for the authorized partner tenants: open finding counts by severity and the affected assets.
cyrisma_list_assets
Free · Read-only
Returns a cursor-paginated list of assets across the authorized partner's tenant scope.
cyrisma_list_baseline_assets
Free · Read-only
Returns a cursor-paginated list of secure-baseline posture by asset: score, grade and benchmark.
cyrisma_list_cve_assets
Free · Read-only
Returns a cursor-paginated list of the assets affected by one CVE, scoped to the authorized partner's tenants.
cyrisma_list_cves
Free · Read-only
Returns a cursor-paginated list of CVEs observed across the authorized partner's tenant scope.
cyrisma_list_partner_tenants
Free · Read-only
Returns every tenant the key is authorized for, as a flat list ordered by position in the hierarchy.
cyrisma_list_root_cause_assets
Free · Read-only
Returns a cursor-paginated list of the assets affected by one vulnerability root cause, scoped to the authorized partner's tenants.
cyrisma_list_root_causes
Free · Read-only
Returns a cursor-paginated list of vulnerability root causes (the products, packages or settings behind many CVEs) across the authorized partner's tenant scope.
cyrisma_list_vulnerability_events
Free · Read-only
Returns a cursor-paginated list of live vulnerability detection events across the authorized partner tenants.