APIs are where your data actually moves, from the web, from mobile apps and from partner systems. Most API vulnerabilities are authorization flaws, and scanners miss them because finding them means knowing who should be able to reach what. MAYASEVEN tests APIs and the cloud behind them by hand. Every finding is verified by an expert and comes with a CVSS score and a proof-of-concept.
Whether a user can change an identifier in a request and reach another user's data. It is the first item in the OWASP API Security Top 10.
Whether a standard user can call administrator functions, and whether the API returns or accepts fields that user should not see or change.
API keys, JWT, OAuth and token handling, tested for forgery, replay and cross-user use.
Whether the API limits request volume and payload size, to stop password guessing, bulk data extraction and usage that runs up abnormal cost.
Webhooks, callbacks and partner-facing APIs, including server-side request forgery (SSRF) that turns an API into a way into internal systems.
Whether the identities and roles behind the API are broader than needed, and how far an attacker who compromises the API can move into other cloud resources.
APIs behind web and mobile apps, and APIs exposed to partners or customers.
Field-level authorization, and deeply nested queries or queries that pull large volumes of data in one request.
APIs between internal services and connections to third-party providers.
An OpenAPI (Swagger) file or Postman collection with sample requests helps us cover every endpoint.
At least two sets of API keys or test accounts per privilege level, so cross-user access can be tested.
The cloud provider, accounts and services in scope, so that testing stays within that provider's penetration-testing policy.
Our own on-prem AI agent reads the API documentation and calls every endpoint with each role's credentials to find where authorization is inconsistent. Done entirely by hand, that takes a long time. Our experts then review the results, remove what is not a real vulnerability, and chain flaws together to prove business impact. A named expert signs off every report.
A web application test starts from the screens a user sees. An API test exercises every endpoint directly, including ones the web or mobile front end never calls, so it finds flaws that screen-driven testing cannot see. If you run a web app, a mobile app and partner APIs, scope the API separately.
Yes. We collect endpoints by using the web or mobile app. Documentation gives more complete coverage in the same time.
It is OWASP's list of the most common API risks, such as Broken Object Level Authorization (BOLA), Broken Authentication and Broken Function Level Authorization. We use it as a minimum reference and also test the logic specific to your system.
Each cloud provider publishes its own penetration-testing policy, which sets out the services that can be tested and the activities that are not allowed. We check the policy of the provider you use during scoping and test only resources you own.
The main factors are the number of endpoints, the number of privilege levels and the complexity of the integrations. Pricing is based on scope, not a fixed package. We send a quote after a short scoping conversation, and a lead expert replies within one business day.
Talk to MAYASEVEN to scope the work and get a quote — a lead expert replies within one business day.