Skip to main content

Application security testing & secure development

Find security weaknesses before they become business risks.

Cyber Secret Society helps businesses assess web application and API security, identify vulnerabilities, and improve software security through practical testing and actionable remediation guidance.

  • Written scope and authorization
  • Manually validated findings
  • Remote, for international clients

Scope map · web app & API

01 · In scope where agreed · Authentication

Sign-in, password reset, multi-factor, and account recovery — can accounts be bypassed or taken over?

How we test this: Web application testing

Services

Security testing and review for the software you ship

Focused service lines, each scoped to your application, API, or codebase.

  1. 01Web Application Penetration TestingManual testing of web applications against real attack paths.
  2. 02API Security TestingAccess-control, data-exposure, and logic testing for APIs.
  3. 03Vulnerability AssessmentIdentify, validate, and prioritise known weaknesses.
  4. 04Secure Development & Code ReviewFind security flaws in source code before they ship.
  5. 05Security Training & CTFs for TeamsPractical workshops and authorised CTF exercises.

How we work

Why businesses work with Cyber Secret Society

Practical testing, clear findings, and guidance your team can act on — with the scope and rules agreed before anything starts.

Read our testing methodology
  1. 01

    Clearly defined scope

    Targets, test types, timing, and exclusions are agreed in writing before any testing begins.

  2. 02

    Practical, manual methodology

    Automated tools support the work; experienced manual testing finds the access-control and logic flaws scanners miss.

  3. 03

    Validated, actionable findings

    Each finding is confirmed and documented with evidence and steps to reproduce — not a raw scanner export.

  4. 04

    Prioritised remediation guidance

    Findings are rated by risk so your team knows what to fix first, with practical guidance on how.

  5. 05

    Clear, professional communication

    Plain-language summaries for decision-makers and technical detail for the engineers doing the fixes.

  6. 06

    Confidential handling

    Assessment information is treated as confidential and shared only with the contacts you nominate.

Engagement process

From first conversation to verified fixes

A simple, predictable process. Actual timing and deliverables depend on the scope we agree.

Swipe to see all 6 steps

  1. Step 01

    Initial discussion

    You tell us what you want assessed and why. We ask the questions needed to understand the application, API, or codebase.

  2. Step 02

    Scope & authorization

    We agree targets, test types, environments, timing, and exclusions — and obtain written authorization before any testing.

  3. Step 03

    Assessment or review

    Testing or code review is carried out within the agreed scope, with a named point of contact on both sides.

  4. Step 04

    Findings & reporting

    You receive a written report with risk-rated findings, supporting evidence, and reproduction steps.

  5. Step 05

    Remediation guidance

    We walk through the findings with your team and clarify how to fix each issue in your environment.

  6. Step 06

    Retesting, if agreed

    Where included in the engagement, we verify that fixes are effective and update the report.

Finding F-03

Illustrative example — not client data

HighAccess control · API

Order details readable across customer accounts

GET /api/orders/{id}

Evidence
Request and response showing an order belonging to a second test account returned to the first.
Reproduce
Sign in as test account A, request an order ID created by test account B, compare the response.
Remediation
Check on the server that the signed-in user owns the requested order before returning it; apply the same check to related endpoints.
Retest status recorded in the report when retesting is agreed
An illustrative example of how a finding is presented in a report. It is not taken from a client engagement.

Who we help

Built for teams that build and run software

Our services are designed for organisations whose risk lives in their applications, APIs, and code.

How our services fit your industry
  • 01

    SaaS businesses

    Multi-tenant products where a single access-control flaw can expose one customer's data to another.

  • 02

    Software development companies

    Teams that want independent security testing or code review before handing a product to their clients.

  • 03

    Web application owners

    Businesses running customer portals, e-commerce, or internal web platforms that hold sensitive data.

  • 04

    API-driven businesses

    Companies whose mobile apps, integrations, or partners depend on APIs that must enforce authorization correctly.

  • 05

    Digital agencies

    Agencies looking for a security-testing partner to assess the applications they build for their own clients.

FAQ

Questions about working with us

Can't find your answer? Ask us directly, or browse every question in the full FAQ.

It depends on the service and the scope we agree. A web application or API penetration test focuses on manual testing of areas such as authentication, authorization, session handling, input handling, and business logic. A vulnerability assessment identifies and validates known weaknesses across agreed assets. A code review examines source code for security flaws. The exact test areas are listed in the agreed scope before work starts.

Planning a security assessment?

Tell us about your application, API, or software security requirements. We can discuss the appropriate scope and next steps.

What happens next

  1. 01We review your enquiry and reply by email
  2. 02An initial discussion about your application and goals
  3. 03A written scope — nothing is tested until it's agreed