SSQ.AISSQ.AI
English
help!

Business Logic & Service Abuse Validation

Whether your business rules hold outside the normal procedure

We find, before anyone else does, the losses that slip through the gaps in your service’s rules: coupons used twice, wrongful refunds, another client company’s data on view.

We look at everything from business rules such as payments, benefits and approvals, through the core logic inside your apps and devices, to the boundaries between roles and between client companies.

Do our business rules still hold when someone steps outside the normal procedure?

For each scenario that would break a condition: whether it can really be abused, the evidence, the business impact and where to stop it first.

Expert reviewed

FLOW Normal procedure Wrongful payout Request Check Approve Pay out A path outside the procedure RULE ‘Nothing is paid out without approval’
The normal procedure runs through request, check, approval and payout. If a path that skips the check and the approval is open, the condition ‘nothing is paid out without approval’ breaks.

When it fits

  • Money and rewards change hands in your service

    Commerce, bookings and ticketing, finance and points, games, subscriptions: services where use outside the normal procedure turns straight into lost money or unearned benefits.

  • A promotion or payment policy is new or changing

    Launching or changing coupons, referral rewards, refund rules or pricing plans? Check before it goes live that the conditions you set leave no room for abuse.

  • Critical logic ships inside an app or device

    If your mobile app or IoT device carries payment, sign-in or licence logic along with keys and settings, we check whether taking the app or device apart and modifying it gets around that logic.

  • Many client companies share one service

    On a B2B SaaS product or platform, you want to know that one client company's data and functions are not open to other client companies, or to admin and support functions, beyond what is needed.

The SAFE SQUARE approach

The conditions, written down first

We first write down with you the conditions the business relies on, such as ‘a seat can be booked by only one person’, then validate the scenarios that would break them. The results answer, condition by condition, whether each one held.

Into the logic inside apps and devices

Alongside the server APIs, we analyse the payment and sign-in logic, keys and settings inside your mobile apps and IoT devices, and check whether a modified app or device can get around the rules.

Boundaries between roles and client companies

For each role that sees a different part of the service, such as ordinary user, client administrator and support agent, we check for any way data or functions could pass to another role or client company.

What we look at

Every service has its own rules: we pick and combine what fits your worry from the examples below, and add what else is needed.

  • RULESBusiness rules and flows
    • Price, quantity and discount calculations
    • Payment, cancellation and refund flows
    • Coupons, points and rewards used more than once
    • Skipped processing steps and approvals
    • Protection against bulk automated requests such as macros and bots
  • CLIENTLogic inside apps and clients
    • How well the app or client code resists being taken apart (obfuscation)
    • Integrity checks and tamper detection
    • Keys, settings and critical logic shipped inside the app
    • How well payment, authentication and licence logic are protected
  • TENANTRoles and client boundaries
    • Using features meant for another user's role
    • Separation of data, files and search between client companies
    • How far admin and support functions reach
Conditions we might test

‘Once a payment is complete, its amount cannot change’
‘A modified app cannot use payment or sign-in features’
‘One client company's data is never visible to another’

How it runs

  1. Set the protection goal

    We pick the loss you are worried about, then set the conditions that must hold to prevent it and the functions and business flows involved.

  2. Agree scenarios and safety

    We choose the scenarios that could break the conditions and, before we start, agree how far we go.

  3. Validate the scenarios

    We follow each scenario and see whether the condition holds, breaks, or has nothing in place to protect it.

  4. Explain the results

    For each scenario: the result and the evidence, the business impact, where to stop it first and how to improve.

Where money moves, as with payments and points, we agree the test environment and method with you so that real customers and transactions are not affected.

What you receive

Results by scenario

Each scenario is marked stopped, got through or needs work, with the conditions that make it so.

Business impact

What each result would cost in money, benefits or data: discounts paid twice, wrongful payouts, another client company's data exposed.

Evidence

The steps and proof needed to reproduce what we found.

Where to stop it first, and how

Where to stop it first and how to improve, with the rules and flows not covered this time written down.

A sample validation resultFictional example
Protection goal

A coupon or points can be used only once, under the set conditions

Target: a commerce app and its order and payment APIs

ScenarioResultEvidence
Normal order and paymentStoppedThe server recalculates the discounted amount itself.
Cancellation overlapping with reuseGot throughThe same coupon can be applied a second time.
The price the app sendsStoppedThe price sent by the app is ignored; payment uses the server value.
Referral pointsNeeds workPoints build up with every new account, with no limit and no check for bulk sign-ups.
Business impact
Discounts paid out more than once, and promotion rewards going to accounts created only for points.
How to improve
Handle coupon use and restoration as one step; add identity checks, payout limits and checks for bulk sign-ups to referral points.

Finding and testing technical vulnerabilities across a whole system is covered by Vulnerability Assessment & Penetration Testing (VAPT).

  1. Tell us what worries you, or what you want checked. A few lines are enough.

  2. We reply with a proposed scope, schedule and cost, and settle them with you.

  3. Once agreed, the work begins. Results and next steps come to you as it runs.