Skip to main content

Wiz

Read Wiz issues, vulnerabilities and cloud inventory with a service account.

Connect it with: Service account. Wiz's own documentation: https://win.wiz.io/reference/prerequisites.

What agents can do​

Connect Wiz so the agents working your tasks can reach it. With it connected, they can:

  • List open Wiz issues for a project or cloud account and summarize the critical ones.
  • Look up the vulnerabilities on a container image, VM or package a task is about.
  • Find which cloud resources an alert refers to, and their owners and tags.
  • Check whether a fix removed an issue after a deploy.

Before you start​

  • A Wiz tenant on the commercial cloud (app.wiz.io) and a Wiz role that may create service accounts (Global Admin, or a project admin for project-scoped accounts).
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Wiz​

Jaah connects to Wiz with a service account, not with a sign-in button.

Connect with an API key​

Find each value first:

  • Client ID: Wiz > Settings > Access Management > Service Accounts > Add Service Account: name it Jaah, Type Custom Integration (GraphQL API), choose the API scopes (read:issues, read:vulnerabilities, read:resources for read-only use), select Add, then copy the Client ID.
  • Client secret: Shown once, beside the Client ID when you create the service account: copy it before closing, or rotate the secret on the service account.
  • API endpoint: Wiz > your profile icon > Tenant Info > General > API Endpoint URL, without the trailing /graphql (for example https://api.us17.app.wiz.io).

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Wiz card.
  2. Name the secret and choose who can use it.
  3. Fill in Client ID, Client secret, API endpoint.
  4. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Not used: Jaah connects to Wiz with a service account, not through an OAuth app.

Test the connection​

Select Test on the secret. Jaah first signs in at POST https://auth.app.wiz.io/oauth/token with the client ID and secret, then calls Wiz's API once with the token it got back (POST <API endpoint>/graphql), and shows whether Wiz accepted it, or which value Wiz refused and the status it answered. Jaah also tests automatically when you save or reconnect.

The last result and its time stay on the secret's page, so you can see whether it still works without testing again.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A key connection hands the agent its fields: client_id, client_secret, api_endpoint.

Tell the agent in your task description which secret to use, for example “use the Wiz secret org/wiz”.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Wiz once the test passes. Steps: Replace or delete a secret.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Wiz's side too, delete the service account's key in its cloud console.

Limitations​

  • Read-only by design: give the service account only read scopes unless agents must resolve issues.
  • A project-scoped service account sees only its projects' resources.
  • Wiz for Government (wiz.us) tenants use a different sign-in host and are not supported by this connection yet.
  • Wiz rate-limits API calls per service account; very large inventory queries must be paginated.
  • Agents can do only what the connected Wiz service account and its roles allow.

Troubleshooting​

Test says Wiz rejected the client ID and client secret (401)

The secret was rotated or mistyped, or the service account was deleted. Rotate the secret on the service account and select Replace on both values.

Test says Wiz cannot be reached at that address

API endpoint is not your tenant's: copy it again from Tenant Info > General > API Endpoint URL, without /graphql.

Test passes but agents get an authorization error on a query

The service account lacks that scope (for example read:vulnerabilities). Edit its scopes in Service Accounts.

Still stuck? Select Test and read the result: it names the value Wiz refused and the status it answered.

FAQ​

What does the Test do?

It exchanges the client ID and secret for a token at Wiz's sign-in service, then sends the smallest possible GraphQL query to your tenant. No data is read.

Which scopes should the service account have?

read:issues, read:vulnerabilities and read:resources cover investigation. Add write scopes only if agents should change issues.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Wiz account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.