// Infrastructure Pentest

Infrastructure & Network Penetration Testing.

Infrastructure penetration testing is a simulated attack on your networks, servers, and Active Directory — from the external perimeter and from an insider position — to find and prove how far an attacker could move, escalate privileges, and reach sensitive systems inside your environment.

01 // What we test

We assess both the external perimeter and your internal network, following the PTES and NIST SP 800-115 process, then simulate a real intruder once inside.

hub // 01

External perimeter

Internet-facing hosts, exposed services, VPNs, and edge devices — discovering the gaps an outside attacker would use first.

hub // 02

Internal network

Assumed-breach testing from inside: network segmentation, lateral movement, and the blast radius of one compromised host.

hub // 03

Active Directory

Kerberoasting, AS-REP roasting, delegation abuse, ACL paths, and domain-privilege escalation to Domain Admin.

hub // 04

Service & patch posture

Unpatched services, default and weak credentials, and known-CVE exploitation across the estate.

hub // 05

Cloud & hybrid

Misconfigured identities, over-permissive roles, and exposed storage across cloud and hybrid environments.

hub // 06

Segmentation & egress

Whether network segmentation and egress controls actually contain an intruder the way they are supposed to.

02 // What you get
  • check_circle An executive summary with a clear picture of attack paths and business risk.
  • check_circle Every finding with reproduction steps, evidence, and CVSS-scored severity.
  • check_circle Prioritized, practical remediation mapped to the underlying root cause.
  • check_circle A complimentary retest to confirm the path is closed.
03 // Standards & methodology

Our infrastructure testing follows recognized industry methodologies and maps findings to the Indonesian regulatory context. Warpstar is a collective of certified operators; we do not claim organizational certifications we do not hold.

verified_user PTES (Penetration Testing Execution Standard)
verified_user NIST SP 800-115 technical testing process
verified_user MITRE ATT&CK for technique coverage
verified_user Findings mapped to OJK and UU PDP expectations
04 // Frequently asked questions
What is the difference between external and internal infrastructure testing? add

External testing attacks your internet-facing perimeter as an outsider with no access. Internal testing simulates an attacker who is already inside — a malicious insider or a compromised laptop — to measure how far they could move. Most organizations benefit from both.

Do you test Active Directory? add

Yes. Active Directory is central to internal infrastructure testing — we attempt realistic privilege-escalation paths from a low-privileged foothold up to Domain Admin, then show you exactly which misconfigurations made it possible.

Is the testing safe for our production network? add

Yes. Rules of engagement are agreed in advance, denial-of-service is excluded by default, and we coordinate testing windows so business operations are not disrupted.

How much does an infrastructure pentest cost? add

It scales with the number of live hosts and IP ranges in scope and whether it is external, internal, or both. Share your scope and we will provide a fixed quote before any work begins.

05 // Related services

Have infrastructure that needs testing?