SECURITY SERVICES / 01

Web application penetration testingin South Africa

Find out whether your users can access, change or misuse more than they should. Hands-on testing gives your developers evidence they can reproduce and a clear route to fixing it.

Web applications

Test the controls your customers rely on.

WHAT WE LOOK AT

Look past the login screen.

A working login does not tell you whether one customer can read another customer’s records, or whether a normal account can perform an administrative action. We work through the application’s roles, data flows and important transactions to find weaknesses with a practical business impact.

Authentication & sessions

Sign-in, account recovery, session handling and changes to credentials.

Access control

Permissions across roles, individual records and separate customer accounts or tenants.

Input & data exposure

How the application handles input, returns errors and protects private information.

Business logic

Registration, approvals, checkout and other workflows that can be used in unintended ways.

BEFORE WE BEGIN

Get the scope right.

Share the application URLs, the main user roles and the workflows that matter most. We agree the environment, test accounts, timing, exclusions and written authorisation before testing begins.

A black-box test starts with limited knowledge. A grey-box test can include accounts, documentation and technical context, so we can examine the parts of your application behind a login. API endpoints can be included in the agreed scope or covered in a dedicated API assessment.

WHAT YOU RECEIVE

Findings your team can work with.

A prioritised report explaining the findings, evidence, business impact and recommended remediation.

We can discuss findings with your developers or IT team while they make changes. Retesting checks whether the reported issues have been resolved; coverage and timing are agreed as part of the engagement.

  • Evidence and reproduction steps
  • Risk ratings with business context
  • Remediation guidance and agreed retesting

COMMON QUESTIONS

A few things to know.

When should we test a web application?

Before a release, after changes to authentication or permissions, or when a customer needs assurance. Leave enough time for fixes and retesting before your deadline.

Can you test an application that requires a login?

Yes. Accounts for the relevant roles let us test access control and workflows that a public visitor cannot reach. We agree how accounts and test data will be provided before starting.

LET’S TALK SECURITY

Talk through your requirements.

Share your systems, priorities and preferred timing. We’ll discuss the right scope together.

Discuss an assessment