Website security · Raksha guide
API Security Testing: Authentication, Permissions and Exposed Operations
API security testing examines who can call an endpoint, which records they can access and what actions the server permits. A public website scan cannot establish most logged-in API permissions. Useful tests need an endpoint inventory, approved accounts and evidence of the actual behaviour.
By Raksha · Reviewed 16 November 2026
What API testing should cover
| Area | Question | Evidence to seek |
|---|---|---|
| Authentication | Are private operations inaccessible without a valid session? | Compare unauthenticated, expired and valid test sessions. |
| Object-level authorisation (BOLA / IDOR) | Can user A read or change user B’s private record? | A reproducible cross-user response involving a known synthetic fixture. |
| Function-level authorisation | Can a normal user perform an administrative action? | A demonstrated role boundary, not just a visible route name. |
| Property-level permissions | Can forbidden fields be read or changed? | Expected field policy compared with actual returned or accepted data. |
| Inventory and exposure | Are old versions, debug routes or unintended operations reachable? | An accessible operation with a supported consequence. |
| Abuse and workflow controls | Are sensitive operations appropriately bounded? | An approved test plan; no uncontrolled load or destructive actions. |
A CORS header or HTTP 200 alone does not prove account takeover, data theft or broken authorisation.
Website scan versus API test
A website check sees public responses. An API review needs endpoint and method coverage, and often authenticated roles. OpenAPI can describe operations and schemas, but declared security requirements do not prove that the server enforces them.
Inventory undocumented routes, legacy versions and browser-used endpoints as well. An incomplete description creates a coverage gap, not a clean pass for omitted endpoints.
A safe two-user access-control test
- Use an approved staging system or explicitly scoped production fixture.
- Create two controlled accounts and a private synthetic record owned by B.
- Confirm B can read the fixture and document its intended permissions.
- Request that same fixture as A using A’s own session.
- Check whether B’s known private marker is actually returned—not just a generic 200 page.
- Retain redacted evidence, repair the server-side check and repeat the authorised test.
Do not enumerate real customer records, transfer funds or alter production data to prove a permission defect. Shared or intentionally public objects do not establish cross-user private access.
What Raksha supports
Raksha has an API-description review and supported web/API probes, with connected two-user access checks in Deep review. They are distinct workflows: a URL scan does not automatically perform a complete authenticated API assessment. Plan access and depth follow your workspace entitlements.
Active probes require verified ownership, a signed engagement, defined scope and a testing window. Request budgets and supported attack classes limit coverage. Complex business logic, race conditions and complete browser journeys are not guaranteed.
Review available testing capabilitiesWhen to arrange deeper testing
Test when shipping a new API, changing authentication or roles, exposing sensitive data or preparing evidence for an auditor. Repeat relevant checks after fixes and significant changes. Use a human-led assessment where the risk depends on multi-step workflows that the supported automated checks cannot exercise.
Is an API test a penetration test?
It can be part of one, but a schema check alone is not a full penetration test.
Do I need OpenAPI?
It helps establish endpoint coverage. Verify it matches the deployed API and supplement it with controlled accounts and expected permission rules.
Sources and further reading
Consult current official documentation before changing a production system. Examples are illustrative, not live findings or universal configurations.
Start with a site you are authorised to test
A free passive check needs no card. Sign-in, email confirmation, ownership rules and usage limits apply. It is not an unrestricted penetration test.