blur circle
Ellipse 15
blur circle
blur circle
Ellipse 15
blur circle
Infrastructure & Cloud Security

Infrastructure
Penetration Testing

Real-world attack techniques. Actionable findings. No scanner output — manual testing by certified ethical hackers across CZ, EU and beyond.

Real data from 2025 testing
5.5 CVSS
Average score per engagement
10.5 findings
Average per engagement
218+
Organisations tested in 2025
8.5 MD
Average project duration
NDA from first contact
Quote within 24 hours
NIS2 · ISO 27001 · DORA
Based in Prague · EU & beyond
Infrastructure Penetration Testing | INTEGRA

What We Test — and How

Each service area is a standalone engagement with its own methodology and deliverable. We define scope individually — below is a precise breakdown of what each test covers.

01

Internal Penetration Test

Active Directory Internal Network ADCS Lateral Movement 8–15 MD

We simulate a breach scenario — attacker already inside via a compromised workstation, phishing link, stolen VPN credential or physical network access. We don't assess the perimeter. We answer the question that actually matters: how far can an attacker get once they're in? The output is a precise attack chain from unprivileged domain user to full domain compromise.

Network Reconnaissance & Mapping

Active host discovery, open port enumeration and service fingerprinting. OS and version identification. VLAN and segmentation mapping, management interfaces (iDRAC, IPMI, web consoles).

  • TCP/UDP port scanning, service enumeration
  • SNMPv1 community string enumeration
  • Default credentials on network devices and management interfaces
  • Detection of cleartext internal protocols (Telnet, FTP, HTTP)
Test Workflow
1
Scoping
Scope definition, rules of engagement, NDA and authorisation letter.
2
Access & Recon
Establishing access, enumerating the AD environment, mapping the internal network.
3
Exploitation
AD attacks, privilege escalation, lateral movement.
4
Post-Exploitation
Credential dumping, data access, persistence simulation.
5
Report & Debrief
CVSS scoring, full attack chains, prioritised remediation plan — plus a debrief session with your IT team.
What We Need From You
  • VPN or on-site access — no credentials to your systems required upfront.
  • A standard read-only domain user account in AD.
  • An IT contact available during the engagement for coordination.
Tooling Nmap BloodHound Impacket CrackMapExec Mimikatz Rubeus Certipy Metasploit
Controlled testing: Destructive techniques (DoS, data wipe) are always agreed in advance. Exploitation runs in coordination with your IT team within defined time windows.
02

External Penetration Test

Perimeter VPN / RDP / SSH ASM Proof-of-Concept 3–10 MD

An attacker on the internet who knows nothing about you — only your domain name. We start with passive reconnaissance and Attack Surface Management, exactly as a real threat actor would. We regularly discover systems our clients didn't know were exposed. Every finding is validated as a working proof-of-concept — no theoretical results without demonstrated impact.

Attack Surface Mapping (ASM)

We identify everything visible from the internet — including forgotten systems and shadow IT that never made it into your asset inventory.

  • Subdomain enumeration — passive and active techniques
  • TCP/UDP scanning, OS and service version fingerprinting
  • Detection of exposed HTTP(S), VPN, RDP, SSH, SMTP and FTP endpoints
  • TLS/SSL audit — certificate validity, weak ciphers, HSTS enforcement
  • Technology stack fingerprinting and software version identification
Test Workflow
1
Scoping
Target IP ranges and domains, rules of engagement.
2
OSINT & ASM
Passive recon, subdomain enumeration, breach database checks.
3
Active Scanning
Port scanning, fingerprinting, CVE identification.
4
Exploitation & PoC
Validated exploitation with a working proof-of-concept for every critical finding.
5
Report
Executive summary + technical detail + prioritised remediation plan.
What We Need From You
  • List of IP ranges and domains in scope
  • Whitelist our IP at your SOC / SIEM to suppress false-positive alerts
  • Point of contact for coordination in case of a critical finding
Tooling Nmap Shodan Amass Nuclei Metasploit Burp Suite ffuf Censys
03

Wi-Fi Penetration Test

WPA2 / WPA3 802.1X Evil Twin VLAN Segmentation 2–5 MD

An attacker physically present near your building — a parked car, the reception area, a conference room. No network access required, proximity is enough. Most common critical finding: guest Wi-Fi and production network sharing the same VLAN — printers, NAS and internal systems reachable from the lobby.

Wireless Environment Reconnaissance

We map everything broadcasting near your premises — visible and hidden networks, rogue APs and encryption strength.

  • SSID mapping including hidden networks and rogue APs
  • Protocol analysis — WPA2, WPA3, 802.1X, WPS
  • Identification of weak authentication configurations
  • Passive traffic capture and handshake collection
Test Workflow
1
Scoping
Target location(s), SSIDs in scope, on-site access logistics.
2
Passive Recon
Full SSID survey, passive traffic capture, client and AP fingerprinting.
3
Active Attacks
Evil Twin, deauth, cracking, 802.1X testing.
4
Post-Connect
VLAN isolation testing, lateral movement attempts post-connection.
5
Report
Per-SSID and per-location findings, CVSS scoring, remediation steps.
What We Need From You
  • Physical access to the target building or campus.
  • SSIDs to be included in scope.
  • IT or security contact available during the engagement.
Tooling Aircrack-ng Kismet Hostapd-wpe hcxdumptool hashcat Wireshark
04

Cloud Penetration Test

AWS Azure GCP IAM Privilege Escalation CIS Benchmarks 5–12 MD

Cloud pentest from the perspective of an attacker with minimal access — or no access at all when resources are publicly exposed. Most common critical finding: IAM privilege escalation from a restricted account to administrator via misconfigured roles. We test AWS, Azure and GCP against CIS Benchmarks and our own methodology built from real-world cloud incidents.

S3 / Blob Storage & Exposed Credentials

The most common source of cloud incidents — public storage buckets with sensitive data and leaked credentials in public repositories.

  • Publicly accessible S3 / Blob Storage buckets containing sensitive data
  • API keys and tokens in public GitHub repositories and CI/CD pipelines
  • Credentials in configuration files and paste sites
  • Databases and storage exposed without authentication
Test Workflow
1
Scoping
Cloud accounts and regions in scope, services to be tested, rules of engagement.
2
Reconnaissance
Asset inventory, IAM role and policy mapping, public exposure review.
3
IAM Exploitation
Escalation path testing from restricted user to cloud administrator.
4
CIS Audit
Automated tooling (Prowler, ScoutSuite) combined with manual review.
5
Report
Findings ranked by business impact — from full tenant takeover to billing abuse.
What We Need From You
  • Read-only IAM role — not a full admin account.
  • List of cloud accounts and subscriptions to be tested.
  • A cloud architect or DevOps contact for technical questions during the engagement.
Tooling Prowler ScoutSuite Pacu CloudSploit PowerZure ROADtools AWS CLI
Cloud provider policies: AWS, Azure and GCP each have their own penetration testing terms. We always operate within provider policies and secure any required permissions in advance.
05

OSINT Analysis

Passive — no system contact Technical OSINT Personnel OSINT Dark Web 3–6 MD

No scanning. No system contact. No exploitation. We work entirely from public sources — the same way a threat actor researches a target before the first breach attempt. OSINT runs as a standalone digital footprint audit or as the reconnaissance phase before an external test. All we need to get started is your domain name.

Technical Attack Surface

A complete map of what a potential attacker knows about your infrastructure — including forgotten assets and shadow IT.

  • Domains and subdomains — passive and active enumeration
  • Forgotten infrastructure, shadow IT, expired certificates
  • Shodan / Censys — exposed ports and services
  • Publicly visible technologies and versions with associated CVEs
How It Works
1
Seed Information
Your domain name — we build the full picture from there.
2
Technical OSINT
Infrastructure mapping, subdomains, certificates, Shodan and Censys.
3
Data Leaks
Breach databases, GitHub history, paste sites, dark web monitoring.
4
Personnel OSINT
Key roles, digital footprint, supplier and third-party relationships.
5
Attack Surface Report
Attack surface map, all findings, reduction recommendations and external test inputs.
What We Need From You (minimum)
  • Your domain name
  • Optional: list of key roles for the personnel OSINT phase
Tooling Maltego Shodan theHarvester SpiderFoot Recon-ng GitLeaks HaveIBeenPwned
Infrastructure Penetration Testing | INTEGRA

Who Needs Infrastructure Penetration Testing

Infrastructure penetration testing is not just for enterprise. We test networks of all sizes — from funded startups to regulated financial institutions across the EU. Here are the most common reasons clients come to us.

Regulation
NIS2 Obligated Entities
  • Test output serves directly as evidence for your auditor
  • Covers Art. 21 NIS2 — technical and organisational measures
  • Proven experience with regulated entities across CZ, SK and EU
Certification
ISO 27001 Implementation & Recertification
  • Support for both initial certification and recertification
  • Report formatted for acceptance by certification auditors
  • Findings mapped to specific Annex A controls
Financial Sector
DORA — Financial Institutions
  • Experience with TLTP / TIBER-CZ methodology
  • Testing critical infrastructure of banks and insurance companies
  • Report compatible with CNB and EBA requirements
Post-Incident
After a Security Incident
  • Attack vector identification and compromise scope assessment
  • Verification that infrastructure is clean post-incident
  • Rapid deployment — available within 5 business days
Frequency
How Often Should You Run an Infrastructure Pentest?
NIS2 / DORA
At least annually
Statutory obligation for obligated entities. Test output serves as audit evidence.
After Major Changes
Ad-hoc Test
Cloud migration, new AD deployment, network architecture change or new infrastructure owner.
Non-Regulated Environment
Once every 24 months
Minimum baseline for stable environments with no regulatory obligation.

Frequently Asked Questions

Find Out Where Your Infrastructure Is Exposed

We respond within 24 hours. We'll propose a scope that fits your environment and walk you through the process — no commitment required. Based in Prague, operating across CZ, SK and the EU.

Response within 24 hours NDA from first contact NIS2, ISO 27001 & DORA experience
Book a Free Consultation

or download sample report · +420 604 200 062

Žadost o vzorovou zprávu výsledků z testu