Penetration Test — Networks, Web Apps and Cloud

Q: Which framework do you use for a penetration test engagement?

We choose the framework based on scope and context. Web applications follow OWASP and PTES. Red Teaming and APT simulations are structured around MITRE ATT&CK. Regulated clients use NIST SP 800-115. Large multi-domain assessments draw from OSSTMM and ISSAF.

A penetration test is not an automated scan. It is a manual simulation conducted by certified experts who think like a real attacker: exploiting chained vulnerabilities, bypassing security controls, and attempting to reach business objectives. Every AptGetDefence engagement produces an operational report — not just a CVE list — with real-world impact, attack path, and a prioritised remediation plan.

Our testers hold OSCP / OSCP+ CRTO — Red Team Operator

6 PT frameworks — adapted to scope and client context

100% Manual testing — not just automated scanners

CVSSv3 Standard scoring for every vulnerability

NIS2 Evidence for audits and regulatory compliance

Test types

Network Penetration Test

Attack simulation against network infrastructure: firewalls, routers, switches, VPN, segmentation. External (from the internet) or internal (from within the corporate network).

Web Application Penetration Test

Manual analysis of web applications, REST/GraphQL APIs, B2B portals and e-commerce platforms. Includes OWASP Top 10, injection, broken auth, IDOR, business logic flaws.

Cloud Security Review

Assessment of AWS, Azure or GCP configuration: IAM, storage, networking, secrets, logging. Identification of misconfigurations exploitable by an attacker.

OT/ICS Security Assessment

Security assessment of industrial environments: PLCs, SCADA, HMI, OT protocols (Modbus, DNP3, Profinet). Non-intrusive approach to ensure operational continuity.

Methodology

Frameworks we follow

We adapt our approach to the scope, environment, and client's regulatory context — drawing from the industry's most rigorous and widely recognised testing standards.

OWASP

Open Web Application Security Project

Web Applications

The reference standard for web and API security testing. Covers the Top 10 vulnerability categories, ASVS verification levels, and detailed testing guides for REST APIs, GraphQL, mobile backends, and single-page applications.

PTES

Penetration Testing Execution Standard

General Pentest

Defines the complete lifecycle of a penetration test: pre-engagement interactions, threat modelling, intelligence gathering, vulnerability analysis, exploitation, post-exploitation, and structured reporting. Our baseline process for all engagements.

NIST SP 800-115

Technical Guide to Information Security Testing and Assessment

Government & Enterprise

The US Government and enterprise standard for security assessments. Used for clients in regulated sectors — NIS2, ISO 27001, DORA — requiring formal compliance documentation and audit-ready testing evidence.

OSSTMM

Open Source Security Testing Methodology Manual

Operational Security

A peer-reviewed, scientific methodology for measuring operational security across networks, systems, and human factors. Produces quantified security metrics (RAV score) alongside qualitative findings — useful for comparing security posture over time.

MITRE ATT&CK

Adversary Behavior and Tactics Framework

Red Team / APT Simulation

Maps the techniques and tactics used by real-world threat actors across the full attack lifecycle. Used to structure Red Teaming scenarios and APT simulations — and to map our findings to specific detection gaps in your SOC or EDR coverage.

ISSAF

Information System Security Assessment Framework

Comprehensive Assessment

A multi-domain framework covering network, system, application, database, and social engineering vectors under a single coherent methodology. Used for large-scope engagements requiring unified coverage across multiple attack surfaces and asset types.

What we do

Reconnaissance (OSINT, footprinting, enumeration)
Vulnerability identification (scanning + manual verification)
Exploitation with real attack simulation
Post-exploitation: lateral movement, privilege escalation
Step-by-step attack documentation
Immediate remediation guidance (fix calls)
Retesting of remediated vulnerabilities (optional)

What you receive

Executive report: summary for management
Technical report: vulnerabilities, screenshots, attack path
CVSSv3 scoring for each finding
Remediation plan prioritised by impact
Executive presentation (if requested)
Evidence for NIS2, ISO 27001, DORA audits
Debriefing call with the technical team

Target

IT Manager / CTO CISO CEO / Board Compliance OT/ICS Manager

FAQ

What is the difference between a vulnerability assessment and a penetration test?

A vulnerability assessment identifies and lists weaknesses using automated tools. A penetration test goes further: our certified testers manually attempt to exploit those weaknesses, chain vulnerabilities together, and demonstrate the real business impact of a successful attack — including lateral movement and data exfiltration. The deliverable is not a scanner report but a narrative of what a real attacker could do.

Which framework do you use for my engagement?

We choose the framework — or combination of frameworks — based on scope and context. Web applications follow OWASP and PTES. Red Teaming and APT simulations are structured around MITRE ATT&CK. Regulated clients requiring formal documentation use NIST SP 800-115. Large multi-domain assessments draw from OSSTMM and ISSAF. We explain the rationale in the proposal.

How long does a penetration test take?

Duration depends on scope. A focused web application test typically takes 3–5 days. An internal network test for a mid-size company is 5–10 days. A Red Teaming engagement can run 2–6 weeks. We scope engagements individually and always provide a timeline in the proposal before work begins.

Corporate Penetration Test