● Talk to a security engineer: +92 323 8295031info@protonyte.com  ·  PCSF batch enrolling now

Network penetration testing, from the internet and from inside the office

Two different questions, and most organizations only ever ask the first. From outside: what can somebody reach without an account. From inside: once one laptop is compromised, how far does it go, and how long before anybody notices. Protonyte runs both for companies in the US, the UK and the Gulf, following NIST SP 800-115 and the PTES, with Active Directory treated as the main event rather than an afterthought.

footholddomain admin one account to the whole domain

ENGAGEMENT SCOPEtypical 1 - 3 week test

External perimeter and exposed servicesIN SCOPE
Internal network and workstationsIN SCOPE
Active Directory and domain escalationIN SCOPE
Network segmentation checksIN SCOPE
Firewall and VPN configuration reviewIN SCOPE
Phishing and physical entryOPTIONAL
// the basics

External and internal, and why you need both

An external test answers the question your insurer asks: what is reachable from the internet, and can it be used. Exposed management interfaces, forgotten test servers, unpatched edge devices, VPN portals with no second factor.

An internal test answers the question that decides how bad a bad day gets. We start from a normal user account or a plugged-in laptop, exactly where a phishing email or a stolen password would leave an attacker, and see how far it goes. In most environments the honest answer is domain administrator in under a day - not because anything was unpatched, but because of how Active Directory was configured years ago and never revisited.

  • 01Both directionsThe perimeter and the inside, because they fail in completely different ways.
  • 02Active Directory firstKerberoasting, delegation, ACL abuse and credential reuse, which is how real intrusions escalate.
  • 03Segmentation provedWe try to cross from one zone to another and write down what actually stopped us, if anything.
  • 04Detection notedWhich of our actions your tools saw, and which they did not, handed to whoever runs them.
// coverage

What we go after

Structured on NIST SP 800-115 and the Penetration Testing Execution Standard, so the coverage is defensible and the report maps to something your auditor recognises.

// from outside

The perimeter

Everything answering on your public addresses.

  • Full port and service discovery
  • Exposed management and remote access
  • VPN, mail and edge device configuration
  • Unpatched and end-of-life services
// getting a foothold

Credentials and access

How an attacker turns reachable into logged in.

  • Default and reused credentials
  • Password spraying within agreed limits
  • Multi-factor coverage and gaps
  • Exposed credentials in public sources
// once inside

Internal network

Starting where a phished user would leave an attacker.

  • Network and host enumeration
  • SMB, LLMNR and NetBIOS abuse
  • Service and share permissions
  • Local privilege escalation
// the domain

Active Directory

The single most productive target in most corporate networks.

  • Kerberoasting and AS-REP roasting
  • Unconstrained and constrained delegation
  • ACL and group-membership abuse
  • Certificate services misconfiguration
// the walls

Segmentation

Whether the zones on the diagram exist on the wire.

  • Server, user and guest zone boundaries
  • Cardholder and sensitive scope isolation
  • Access from guest Wi-Fi into corporate
  • Management network reachability
// who noticed

Detection and response

Recorded as we go, and compared with your logs at the end.

  • Timeline of every noisy action
  • What was alerted on and what was not
  • Logging gaps by host and by control
  • Quick wins for your defenders
// methodology

How the work runs

  1. 1

    Scope and authorisation

    Address ranges, the office or offices, the test window and the stop conditions, in writing.

    • In-scope ranges and exclusions
    • External, internal or both
    • Out-of-hours windows if needed
    • Emergency contacts on both sides
  2. 2

    Discovery

    A full picture of what is answering, before anything is attacked.

    • Host and service discovery
    • Version and patch-level fingerprinting
    • Public exposure and leaked credentials
    • Targets ranked by what they would give
  3. 3

    Exploitation

    Careful, agreed and evidenced. We prove access rather than take anything.

    • Verified exploitation only
    • No denial of service
    • Screenshots and command output as evidence
    • Immediate call on anything critical
  4. 4

    Escalate and move

    From one foothold to the next, the way an intrusion actually progresses.

    • Local to domain privilege escalation
    • Credential harvesting and reuse
    • Lateral movement between zones
    • Reach to the data that matters
  5. 5

    Report and retest

    A route map of how we got in, a fix list in priority order, and a free retest.

    • Attack path, step by step
    • Fixes ranked by what they close
    • Detection notes for your SOC
    • Retest and closure summary
// the deliverable

What you are left holding

Two documents and a conversation. Written so the person who signs the invoice and the person who writes the fix can both use them.

  • Executive summary in plain language, with the business risk first
  • Technical findings with the evidence that proves each one
  • CVSS score and a risk rating that reflects your business, not a template
  • Remediation written for the stack you actually run
  • A free retest, and a closure summary you can hand to a customer
  • A debrief call with the tester who did the work, not an account manager
Ask for a sample report
// the standards

Measured against something

The work follows NIST SP 800-115, PTES, MITRE ATT&CK and CIS Benchmarks, so the coverage can be checked rather than taken on trust, and the report maps to what your auditor or your enterprise customer already recognises.

This page is one part of our penetration testing service. Where a finding needs a different kind of engagement to answer properly, we say so in the report rather than selling you the test we happen to be running.

// faq

Common questions

What is the difference between an external and an internal network test?

External is run from the internet with no access, and answers what a stranger can reach. Internal is run from inside your network with a normal user account or a connected laptop, and answers how far a phished employee or a stolen password gets. They find different things, and most organizations only buy the first.

Do you need to come to our office?

Not necessarily. An internal test can be run from a small device we ship to you, or from a virtual machine on your network, which keeps the cost down for Gulf clients. We do travel where the engagement needs it, and wireless or physical testing has to be on site.

Will you take our systems down?

No. Denial-of-service techniques are excluded by default and exploitation is agreed in advance. We prove access and stop; we do not encrypt, delete or move your data. Fragile or legacy hosts can be marked for enumeration only.

How often should we run one?

Annually as a floor, and again after a significant change - a new office, a datacentre move, a merger, a new edge device. PCI DSS requires it at least annually and after any significant change, and requires segmentation testing on top of that.

Can you test our Active Directory specifically?

Yes, and it is normally the most valuable part. Delegation, certificate services, group nesting and service accounts accumulate quietly over years, and the result is usually a short path from a normal user to domain administrator that no patch would have closed.

// start here

Let's protect your business together.

Tell us what you need tested. Our team will reply with a clear scope and quote.

By submitting, you agree to our Terms of Use and Privacy Statement.