Docs / Go deeper

Testing behind a login

Scan as a signed-in user, check whether one user can reach another user's data, and confirm blind bugs with a callback.

Authenticated scanningPro and up

Most of an application is behind a login, and an unauthenticated scan never sees it. Crossfyre stores credentials in your arsenal and signs in for you, so the session-gated surface actually gets tested.

What it supports

  • Static tokens and API keys, sent as headers or cookies.
  • Form logins, for applications that just want a username and password posted.
  • OAuth2 / OIDC, non-interactive (client credentials, password grant) and interactive (authorization code).
  • SSO and MFA flows, driven by a headless broker.

How your secrets are handled

Credentials are encrypted at rest. When a scan needs to authenticate, the broker performs the sign-in and hands the engine only a resolved token; your raw secrets are never put on the message bus and never reach an engine. Credentials belong to your team or personal account, not to one workspace, and are limited to the hosts you attach them to.

Using it

Add a credential under Arsenal → Credentials, attach it to the hosts it applies to, and select it when you launch a scan. The Web Tracer can also seed a session you already have: browse the target while capturing and the cookies and bearer headers you used can be stored as an arsenal credential for later scans.

Authenticated scanning unlocks on Pro, and the server enforces it.

Authorization testing (BOLA / BFLA / BOPLA)Pro and up

The serious bugs in an API are usually one user reading or doing something that belongs to another. A scanner that logs in as a single identity cannot see them, because the response looks like a perfectly healthy 200.

Crossfyre runs authorization testing as a mode inside a scan. You give it several identities (say admin, user A, user B, and anonymous), it replays each endpoint as every identity, and it diffs the responses. What it is looking for:

  • BOLA (broken object level authorization): user B retrieves user A's object by changing an id.
  • BFLA (broken function level authorization): a lower-privileged identity reaches a privileged action.
  • BOPLA / mass assignment: fields a caller should not be able to set are accepted, or fields they should not see come back.
  • Excessive data exposure: the endpoint returns more than the caller is entitled to.

Coverage spans REST paths, query parameters and GraphQL, and every candidate goes through the same confirm-before-report step as the rest of plessor, so what reaches your findings is what reproduced.

Setting it up

Add one credential per identity in the arsenal, label the role, and select them when you launch the scan. The more distinct the privilege levels you give it, the more it can tell you.

Authorization testing unlocks on Pro, and the server enforces it.

Out-of-band confirmation (OAST)

Some vulnerabilities produce no visible response: a blind SSRF, a blind command injection, an out-of-band SQL injection. The only proof is the target reaching out to a server you control. That is what OAST is for.

plessor injects a unique callback address into the payloads it sends, then watches for the DNS or HTTP interaction that confirms the target actually executed it. If no interaction arrives, there is no finding.

Managed or your own

  • Managed poolPro and up: nothing to run.
  • Bring your own: point a scan at an OAST endpoint you operate.
  • Self-hosted: run the open-source server yourself on your own domain with crossfyre oast setup, which installs it as a service and obtains wildcard TLS. Self-hosting is free on every plan.

Zero-knowledge by design

Interactions are sealed to a per-scan key. Even the operator of the OAST server holds only ciphertext, so running the managed pool does not mean we can read what your targets sent. Manage endpoints from the OAST page in your dashboard.