generated: '2026-08-02'
method: searched
source: https://docs.axonius.com/docs/bishop-fox-adapter
also_source:
- https://docs.brinqa.com/docs/connectors/bishopfox/
- https://bishopfox.com/services/cosmos
api: Bishop Fox Cosmos API (v5)
versioning:
  scheme: uri-path
  current: v5
  path_prefix: /v5/
  docs: null
  docs_note: >-
    The Cosmos API reference is published inside the authenticated Cosmos portal
    (https://cosmos.bishopfox.com/); there is no anonymously reachable versioning policy page.
deprecation:
  policy_url: null
  policy_published: false
  sunset_header: unknown
  events:
  - version: v1
    status: retired
    date: '2025-12-05'
    evidence: https://docs.axonius.com/docs/bishop-fox-adapter
    note: >-
      Recorded by Axonius, which still ships a v1 adapter option and documents that the Bishop Fox V1 API
      was deprecated on 2025-12-05. Bishop Fox itself publishes no deprecation policy page, so no
      Deprecation pointer is wired in apis.yml.
sla:
  url: null
  uptime_target: null
status_page:
  url: null
  probed:
  - {host: status.bishopfox.com, result: NXDOMAIN}
  note: No public status page could be found; no StatusPage pointer is wired.
changelog:
  url: null
  note: >-
    No public, dated changelog or release-notes page. Product announcements are published as press releases
    under https://bishopfox.com/news (e.g. the Jira and ServiceNow integration launches), which is
    marketing-cadence, not an API changelog.
delivery_model:
  managed: true
  note: >-
    "Cosmos is operated and managed by Bishop Fox as part of our services; customers do not deploy or
    maintain the platform themselves." — https://bishopfox.com/services/cosmos
deprecated_operations: []
x-evidence:
- url: https://docs.axonius.com/docs/bishop-fox-adapter
  http_status: 200
  fetched: '2026-08-02'
- url: https://bishopfox.com/services/cosmos
  http_status: 200
  fetched: '2026-08-02'