Cyber Security
API Security
Security testing of REST and GraphQL APIs.
01
Who needs it
SaaS products, mobile backends and partner integrations.
02
Key advantages
- Covers authorization flaws like BOLA/IDOR
- Checks rate limits and data exposure
- Developer-ready findings
03
Core features
- Endpoint inventory
- Auth and authorization tests
- Input and schema testing
- Rate-limit testing
04
Security considerations
- Methodology referencing the OWASP API Security Top 10
- Test accounts provided by you
- No production data altered
05
Typical integrations
- OpenAPI / Postman collections
- API gateway
06
Recommended technology
- Burp Suite
- Postman
07
Expected outcome
APIs that only return what each caller is allowed to see.
08
Timeline
- Website security audit
- 1–2 weeks
- API or application assessment
- 2–4 weeks
- Secure code review
- 1–4 weeks, by codebase size
- Hardening engagement
- 1–3 weeks
Typical ranges for cyber security projects. Confirmed after discovery; not a guarantee.
09
Engagement model
- 01Fixed scopeA defined scope, price and timeline. Best when requirements are clear.
- 02Dedicated teamA monthly team for ongoing product development and priorities that change.
- 03Time and materialsBilled by effort for discovery, assessments or evolving work, with regular reporting.
Our delivery standard
The same ten stages apply to every cyber security engagement, scaled to the size of the project.
- 01Requirement discovery
- 02Scope definition
- 03Architecture
- 04UX/UI
- 05Development
- 06Security review
- 07Testing
- 08Client review
- 09Deployment
- 10Post-launch support
Discuss your api security project
Tell us what you're building. We reply with questions, a suggested approach and next steps.