API and authentication security testing
Authorization, GraphQL and authentication checks for REST and GraphQL APIs, including multi-identity BOLA/BFLA testing.
How it works
API checks look for access-control gaps that only appear when the same request is replayed as different users, plus GraphQL-specific abuse and weak authentication. Supply test identities to unlock the multi-identity authorization checks.
7 checks in this area
Broken object / function-level authorization (BOLA / BFLA)
Check id authz-bypass
GraphQL insecure direct object references
Check id graphql-idor
GraphQL abuse (introspection, suggestions, batching)
Check id graphql-advanced
Mass assignment
Check id mass-assignment
API excessive data exposure
Check id api-data-exposure
Token forgery with weak signing secrets
Check id token-forgery
Authentication testing (weak credentials, rate limiting, user enumeration)
Check id auth-testing
Other security testing areas
Web application security testing
Injection, request-forgery and misconfiguration checks against your live web app, with a reproducible proof for every confirmed finding.
LLM and AI application security testing
Prompt-injection testing for apps with a language model behind the HTTP surface, mapped to the OWASP LLM Top 10 (2025).
TLS / SSL configuration testing
Find deprecated protocols, weak keys and certificate problems before your users or an auditor do.
DNS attack surface and subdomain takeover
Enumerate subdomains from certificate transparency and catch dangling DNS records before someone claims them.
Cloud storage exposure testing
Detect publicly listable S3, Google Cloud Storage and Azure buckets that your own site references.
Exposed network service testing
Opt-in checks for data stores and file services left open to the internet without authentication.