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
- 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.
- Create a key. Give it a name and choose its access level: Read for reporting only, or Read and write to also provision tenants.
- Choose whether the key applies to organizations beneath this one. Leave that off to limit the key to a single organization.
- Copy the client ID (it starts with
pc_) and the client secret (it starts withpcs_). 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
- Open Connectors, then CYRISMA.
- Enter the address in Instance address, the key's client ID in Client ID and its secret in Client secret.
- 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_jobuntil it is deployed. The country you choose also decides where the tenant is hosted and its data stored. Send anidempotency_keyof your own: a retry with the same key returns the original job instead of a second tenant. - Update changes a tenant's details. Setting
trialto 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_tenantsto 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
Tenants
Provisioning
Users and technicians
Reporting
Was this helpful?
More in Connector guides
Connect 3CXConnect AbleSignConnect Acronis Cyber Protect CloudConnect Action1Still need help? Ask the team