Common issues and how to resolve them

A quick reference for the problems we're asked about most. If your issue isn't here, the in-app chat (bottom-right) and support@cybaura.io are always available.

I can't log in

• If your organisation uses SSO, use the Sign in with SSO option rather than a password.
• Check that your account hasn't been deactivated by an administrator.
• Clear cookies for app.cybaura.io and try again, or use a private window.

My agents aren't producing findings

• Confirm the agent is enabled and has a schedule set (Agents → [agent] → Settings).
• Agents need data to work with — make sure your DNA is finalised and relevant assets are present.
• Check the Agent Activity Feed; a run may have completed with nothing to report, which is normal.

My compliance coverage looks wrong

• Re-check the frameworks you've activated under Compliance → Frameworks.
• Coverage updates as controls gain evidence — newly added controls start uncovered.

SSO login fails

• The most common cause is a missing email attribute mapping in your identity provider.
• Signing certificates rotate periodically — re-import your IdP metadata.
• See Connecting your identity provider (SSO).

BYOK access alert

• Your KMS key permissions may have changed. Confirm CybAura's service identity still has encrypt/decrypt rights.
• Re-validate the key under Settings → BYOK.

API requests return 401 or 429

• 401 — the API key is missing, malformed, or revoked. Generate a new key under Settings → API Keys.
• 429 — you've hit the rate limit. Honour the Retry-After header and back off.

Something looks broken

1. Check the status page at status.cybaura.io for any ongoing incidents.
2. Try a hard refresh (Ctrl/Cmd + Shift + R).
3. Note what you were doing and any error message, then contact support.

Contacting support

• In-app chat — bottom-right of the app, fastest for quick questions.
• Email — support@cybaura.io, ideal for anything needing screenshots or detail.