SECURITY / 07

Vulnerability Assessment & Penetration Testing.

Manual, adversarial testing across fifteen categories — three depths of access, a fixed scope agreed in writing, every finding verified by a person.

Start a Conversation
A security tester at a multi-screen console, the main display showing a penetration testing run with reconnaissance and vulnerability analysis complete and exploitation in progress.

SECTION OVERVIEW

Your systems believe they’re secure. We test whether that’s true.

Manual, adversarial security testing for businesses in the Philippines — three depths of engagement, a fixed scope agreed in writing, every finding verified by a person before it reaches your report.

An attacker needs one working path in. You have to defend all of them. That asymmetry doesn’t go away because a system has shipped without incident so far — it just means the gap hasn’t been found yet, by someone willing to report it.

HOW AN ENGAGEMENT RUNS

Six phases

01

Scope & rules of engagement

We agree on targets, testing windows, and what’s off-limits before anything starts.

02

Reconnaissance & mapping

We map the real attack surface — including what you may not know is exposed.

03

Testing

Manual testing across all 15 categories, augmented by Hiraya for coverage and speed.

04

Verification

Every finding is manually confirmed. Nothing goes into your report on a scanner’s word alone.

05

Reporting

Severity-ranked findings with reproduction steps and concrete remediation guidance.

06

Retest

Once you’ve fixed what we found, we confirm it’s actually closed.

DEPTH OF ACCESS

Three depths of access

Choose how much access we get before we start. More access finds more, faster — but even without credentials, we find what an outside attacker would.

Blackbox

Outside in

No credentials, no source. We test the way an opportunistic attacker would — from the outside, against what’s actually exposed.

1 week · 1–30 applications

Graybox — DAST

Authenticated depth

Working logins for each role, without source access. Dynamic testing against the running application catches what only shows up at runtime — broken access control between roles, session handling, business logic.

1–2 weeks · 1–20 applications

Whitebox — SAST

Source-level review

Read access to the repository. We analyse the code directly, tracing an issue to the exact function rather than inferring it from behaviour.

2 weeks · 1–10 applications

Engagements run either as a onetime assessment or as a retainer covering continuous testing on the same scope. Either way the work is quoted against your scope. Ask us for a quote.

GO DEEPER

The detail behind an engagement

LET'S CONNECT

Want to know more of our solutions?

Contact us to start the conversation.

Contact Us
PROD / v3.0