Bishop Fox · OAuth Scopes

Bishop Fox OAuth Scopes

OAuth 2.0 searched

Bishop Fox publishes 7 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Bishop Fox API on a user’s behalf.

Tokens are issued from https://bishopfox.auth0.com/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyCybersecurityOffensive SecurityPenetration TestingAttack Surface ManagementExposure ManagementRed TeamingVulnerability ManagementSecurity FindingsAsset DiscoveryContinuous Threat Exposure ManagementAuthentication
Scopes: 7 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://bishopfox.auth0.com/oauth/token
Flows
clientCredentials

Scopes (7)

ScopeDescriptionFlows
get:assets Read individual discovered attack-surface assets. clientCredentials
list:assets List/enumerate discovered attack-surface assets across the asset-view resources. clientCredentials
update:assets Update asset records (e.g. attribution, ownership, or state changes). clientCredentials
get:findings Read validated Cosmos findings and finding definitions. clientCredentials
update:findings Update findings (e.g. triage state, comments, remediation status). clientCredentials
read:ingest Read ingestion configuration/state for customer-supplied seed data. clientCredentials
write:ingest Submit seed data into the Cosmos ingestion pipeline. clientCredentials

Source

OAuth Scopes

bishop-fox-scopes.yml Raw ↑
generated: '2026-08-02'
method: searched
source: https://docs.brinqa.com/docs/connectors/bishopfox/
docs: https://docs.brinqa.com/docs/connectors/bishopfox/
note: >-
  Bishop Fox publishes no public scope reference — the Cosmos API documentation lives inside the
  authenticated portal. The scope set below is the one granted to a Cosmos API key/secret pair as documented
  by Brinqa's published Cosmos connector documentation, which records the scopes returned on the
  client-credentials token for the cosmos_public audience. Not derived from an OpenAPI (none is published)
  and not exhaustive — a Cosmos customer with portal access should confirm against the in-portal reference.
schemes:
- name: CosmosOAuth2ClientCredentials
  type: oauth2
  source: https://bishopfox.auth0.com/.well-known/openid-configuration
  audience: cosmos_public
  flows:
  - flow: clientCredentials
    tokenUrl: https://bishopfox.auth0.com/oauth/token
scopes:
- scope: get:assets
  description: Read individual discovered attack-surface assets.
  flows: [clientCredentials]
  sources: [https://docs.brinqa.com/docs/connectors/bishopfox/]
- scope: list:assets
  description: List/enumerate discovered attack-surface assets across the asset-view resources.
  flows: [clientCredentials]
  sources: [https://docs.brinqa.com/docs/connectors/bishopfox/]
- scope: update:assets
  description: Update asset records (e.g. attribution, ownership, or state changes).
  flows: [clientCredentials]
  sources: [https://docs.brinqa.com/docs/connectors/bishopfox/]
- scope: get:findings
  description: Read validated Cosmos findings and finding definitions.
  flows: [clientCredentials]
  sources: [https://docs.brinqa.com/docs/connectors/bishopfox/]
- scope: update:findings
  description: Update findings (e.g. triage state, comments, remediation status).
  flows: [clientCredentials]
  sources: [https://docs.brinqa.com/docs/connectors/bishopfox/]
- scope: read:ingest
  description: Read ingestion configuration/state for customer-supplied seed data.
  flows: [clientCredentials]
  sources: [https://docs.brinqa.com/docs/connectors/bishopfox/]
- scope: write:ingest
  description: Submit seed data into the Cosmos ingestion pipeline.
  flows: [clientCredentials]
  sources: [https://docs.brinqa.com/docs/connectors/bishopfox/]
summary:
  scope_count: 7
  pattern: verb:resource
  verbs: [get, list, read, update, write]
  resources: [assets, findings, ingest]
x-evidence:
- url: https://docs.brinqa.com/docs/connectors/bishopfox/
  http_status: 200
  fetched: '2026-08-02'
  kind: third-party connector documentation

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This scope set
curl "https://apis.io/api/v1/scopes/bishop-fox-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.