Techbanq

Offensive security · perimeter

Scope it from discovery, not from the asset register

Every external test we have run has found hosts the client did not list. A staging box from a project that finished, a vendor appliance with a management port open, a subdomain pointing at a service nobody renewed.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Market
Saudi Arabia
Written for
CISO
Decision
Understand what an attacker can reach from the internet

Cybersecurity credentials

  • National Cybersecurity Authority, Saudi Arabia

    NCA registration

    Registered cybersecurity service provider

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

Starting point

The asset register is a claim, not a scope

We do not have an office in Saudi Arabia

We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.

An external test that begins by accepting the client's list of addresses tests the part of the perimeter someone was already thinking about. The exposure that causes incidents is on the part nobody was thinking about, which by definition is not on the list. So the engagement starts with discovery, and the scope is agreed after discovery rather than before it.

Discovery is not intrusive and does not need authorisation to run against public records: certificate transparency logs name every host anyone has ever requested a certificate for, DNS history preserves records long after they were retired, and reverse lookups across the netblocks a company owns return machines with names that describe their function. An attacker builds the same picture in a day, without asking.

What follows is a conversation rather than a report line. Some of what discovery returns is out of scope because it belongs to a supplier or a subsidiary that has to authorise its own testing. Some of it should be decommissioned rather than tested. Establishing which is which is the first useful output of the engagement, and it happens before any packet is sent in anger.

Sequence

Four stages, and the one that produces the surprises

STAGE 01

1 · Discovery

Certificate transparency logs, DNS enumeration, reverse lookups on the netblocks, and historical records for hosts that were public and may still be. The output is routinely larger than the supplied scope. A confirmed inventory, and the delta against yours.

STAGE 02

2 · Exposure assessment

What each host runs, at what version, and which of those services should be reachable from the internet at all. A management interface exposed is a finding regardless of whether it is patched. Service inventory with an exposure judgement per entry.

STAGE 03

3 · Authentication surfaces

Every login reachable from outside: default credentials, password policy, lockout behaviour, and whether credential stuffing would be visible to anyone monitoring. Weak or absent controls on each authentication point.

STAGE 04

4 · Controlled exploitation

Enough to demonstrate impact and no further, within a boundary agreed in writing. The purpose is to establish what an attacker gains, not to hold access. Demonstrated impact per finding, with the stopping point stated.

What we find

The recurring five

  1. 01

    Forgotten hosts

    A staging environment from a finished project, still running an old build with debug enabled and no monitoring. Present in most external tests we run.

  2. 02

    Exposed management planes

    A firewall, hypervisor or appliance admin interface reachable from anywhere, usually because a temporary rule outlived the person who added it.

  3. 03

    Subdomain takeover

    A DNS record pointing at a cloud service that was decommissioned, leaving the name available for anyone to claim and serve content from.

  4. 04

    Credential reuse into the perimeter

    A VPN or webmail login accepting credentials that appear in public breach corpora, with no lockout and no alerting on repeated failures.

  5. 05

    Information disclosure

    Version banners, verbose errors, directory listings and backup files left in a web root — individually minor, collectively a map of what to attack next.

Scope boundary

What the perimeter test answers

What we do

  • Report the assets discovery found that the supplied inventory did not, with the evidence that ties each one to you.
  • Verify every automated result by hand before it reaches the report, so a version banner is not filed as a vulnerability.
  • Stop at demonstrated impact, at a boundary agreed in writing before the test begins.

Cloud and hosting providers set their own rules for what a customer may test on their platform. Confirm the provider's testing policy for the specific services in scope before authorising the engagement — the permission a provider grants for your own compute rarely extends to its managed services.

Primary source

Common questions

What buyers ask

How is this different from an automated external scan?+

A scan enumerates services and compares versions against a vulnerability database. It will not chain three low-severity findings into an entry, will not recognise that a forgotten staging host shares credentials with production, and will not tell you which of the four hundred results actually matters for your estate. Both have a place: scanning is the continuous control, testing is the periodic examination that interprets it.

Do you need us to whitelist your IP addresses?+

Usually not, and often we prefer you did not — part of the value is finding out whether your controls detect and block the activity. Where a WAF or scrubbing service will simply drop everything and produce no information, we run the test both ways and report the difference, because that difference is itself a finding about your detection.

What do we have to give you before the test starts?+

Written authorisation from someone empowered to give it, the address ranges and domains in scope, and — where any of it sits with a hosting or cloud provider — confirmation that their testing policy permits it. Most major cloud providers allow customer-authorised testing of your own resources, but the boundary differs by provider and by service, and a shared appliance you do not own is usually outside it. We confirm that during scoping, because discovering it mid-test costs days.

Next step

Send your ranges for discovery

Send your public IP ranges and domains. Discovery usually returns more than the list you sent, and that difference is the first finding.

Send your ranges for discovery

What happens next

  1. 1We reply within one business day.
  2. 2A 30-minute scoping call with a senior consultant.
  3. 3A written proposal with scope, team, and timeline.

Or reach us directly

By submitting this form you agree to our Terms of Use and Privacy Policy.