OASIS HIVE Limited
Home Projects Pricing Contact

Security

Penetration Testing

Find the holes before someone else does

What this involves

How we approach penetration testing at Oasis Hive.

A penetration test is only useful if it changes what you do next. We test the way a real attacker would, then write it up so both engineers and leadership can act.

Authorised attacks on your apps and infrastructure, reported in plain language.

What we do

Web and API testing

Authentication, authorisation, injection, logic abuse and data exposure.

Infrastructure testing

External and internal network, host configuration and service enumeration.

Mobile application testing

Local storage, transport security, reverse engineering and platform flaws.

Reporting and retest

Executive summary, technical detail, risk ratings and a free retest.

What you end up with

  • Evidence-backed findings with reproduction steps
  • A prioritised remediation roadmap by business impact
  • A retest confirming fixes actually work
  • Documentation that supports client and regulator assurance

Tools and technologies

We choose per project rather than by habit. These are the ones we most often reach for here.

OWASP Top 10 Burp Suite Nmap Metasploit PTES methodology

Questions about this service

At least annually, and after any significant change to your architecture or authentication. Regulated environments often require more.
We agree scope, windows and rate limits in advance, and avoid destructive techniques unless you specifically request them.

Delivered properly

One team from scoping through to support

The people who design the system are the people who answer for it in production, so nothing falls between suppliers.

How the work runs

Six steps, no surprises

Step 01

Listen and map

We interview the people doing the work, review the systems in play and write down how things actually flow.

Step 02

Design the solution

We propose what to build first, what to leave alone, what it will cost and what we are assuming. Options come with trade-offs.

Step 03

Build in increments

Working software every two weeks, demonstrated against real data. You can redirect early while changes are still cheap.

Step 04

Verify and secure

Automated tests, security review and load checks run throughout, not at the end, so findings are fixed while the context is fresh.

Step 05

Launch with support

We plan the cutover with you, migrate data carefully, train your team and stay close through the first weeks in production.

Step 06

Run and improve

Monitoring, support and a regular review of what to improve next. Maintained systems stay valuable.

Next step

Let us scope penetration testing properly

A short discovery gives you a written specification, a schedule and a fixed price. No obligation to continue afterwards.