Skip to main content

What Is OWASP OFFAT?

OWASP OFFAT (Offensive API Tester) maps an API attack surface from source code, including decorator routes, routers, and OpenAPI or Swagger specs, and proves source-to-sink data flows on a code property graph for Python and JavaScript/TypeScript. A Rust engine executes the test plan over HTTP/1.1, HTTP/2, WebSocket, and gRPC, with identity-aware differential checks for BOLA and BFLA. Results come out as SARIF, Markdown, HTML, JUnit, and an OWASP API Top 10 compliance report. The earlier spec-only Python CLI has been retired in favor of this platform.

Use Cases

Authorized API testing of services whose source code is available, from source-only analysis in CI to live runs against test targets.

Strengths and Limitations

Strengths

  • +Source-only mode maps, plans, triages, and reports without sending traffic.
  • +Identity-aware differential checks for BOLA and BFLA.
  • +A GitHub Action scans every push and publishes results to code scanning.

Limitations

  • -Live runs need the separately built Rust execution engine and an explicit --yes flag.
  • -The code graph covers Python and JavaScript/TypeScript.
  • -AI triage needs an Anthropic API key or a signed-in Claude Code or Codex CLI; without one a deterministic heuristic is used.

Defensive Use

Finding broken object-level and function-level authorization in APIs before release, with each finding tied to the HTTP route that reaches it.

OWASP OFFAT Alternatives

3 tools
ToolPricing
42Crunch

API security platform auditing OpenAPI definitions and enforcing conformance at runtime.

Freemium
Akto

Open source API security platform for discovery, inventory, and automated API testing.

Free / Commercial
APIsec

API security testing platform that maps endpoints and runs exploit tests for authorization flaws such as BOLA, with a free plan.

Freemium

Frequently Asked Questions

What is OWASP OFFAT?→

OWASP OFFAT (Offensive API Tester) maps an API attack surface from source code, including decorator routes, routers, and OpenAPI or Swagger specs, and proves source-to-sink data flows on a code property graph for Python and JavaScript/TypeScript. A Rust engine executes the test plan over HTTP/1.1, HTTP/2, WebSocket, and gRPC, with identity-aware differential checks for BOLA and BFLA. Results come out as SARIF, Markdown, HTML, JUnit, and an OWASP API Top 10 compliance report. The earlier spec-only Python CLI has been retired in favor of this platform.

What is OWASP OFFAT used for?→

Authorized API testing of services whose source code is available, from source-only analysis in CI to live runs against test targets.

What are the strengths of OWASP OFFAT?→
  • +Source-only mode maps, plans, triages, and reports without sending traffic.
  • +Identity-aware differential checks for BOLA and BFLA.
  • +A GitHub Action scans every push and publishes results to code scanning.
What are the limitations of OWASP OFFAT?→
  • +Live runs need the separately built Rust execution engine and an explicit --yes flag.
  • +The code graph covers Python and JavaScript/TypeScript.
  • +AI triage needs an Anthropic API key or a signed-in Claude Code or Codex CLI; without one a deterministic heuristic is used.
How is OWASP OFFAT used defensively?→

Finding broken object-level and function-level authorization in APIs before release, with each finding tied to the HTTP route that reaches it.