Methodology
Built Around Your Environment

WHY SCOPE MATTERS

Scope Shapes Everything

The Foundation

Scope determines what a test can find before a single command runs. Get it wrong, and the engagement answers the wrong question.

A well-scoped test maps to how an attacker actually moves through your environment, covering cloud infrastructure, identity providers, internal networks, APIs, and AI integrations. It starts with a clear picture of what you are protecting and works backward from there. 

-From Entry to Impact

Testing That Follows Real Attack Chains

Attackers move through an environment in stages. Each phase below maps to how they actually operate, from the first probe outside your perimeter to the final impact inside it. Testing aligns to PTES, NIST SP 800-115, and the OWASP Web Security Testing Guide, with phases mapped to MITRE ATT&CK.

 
 
PHASE 01
Reconnaissance
Open source intelligence (OSINT), exposed credentials, certificate transparency, public asset inventory.

External

 
PHASE 02
Initial access
Exposed services, credential stuffing, phishing pretext, VPN and remote access exploitation, public misconfigurations.

Entry

 
PHASE 03
Persistence
Scheduled tasks, OAuth grants, service principals, sleeper accounts.

Foothold

 
PHASE 04
Privilege escalation
IAM misuse, token theft, Kerberoasting, ADCS abuse, delegation chains.

Escalate

 
PHASE 05
Lateral movement
Active Directory paths, segmentation gaps, trust abuse, platform pivots.

Spread

 
PHASE 06
Impact
Data exfiltration, ransomware simulation, business logic abuse, blast radius proven and bounded.

Impact

--Ten Attack Surfaces

Each Attack Surface Demands Its Own Approach

Every attack surface has its own threat model. Each one has its own entry points, techniques, and blind spots. The sections below break down how we approach each one.

01

AI

AI tools and agentic workflows operate with elevated trust attackers actively exploit. Prompt injection, tool abuse, and excessive agency let attackers reach data and execute actions your team never intended to expose. Most organizations have no visibility into where those boundaries sit. 

What attackers try
  • Prompt injection and jailbreaks 
  • Agent tool and action abuse 
  • Retrieval pipeline data leakage 
  • Excessive agency exploitation 
  • Plugin and integration hijacking 
What gets tested
  • Model endpoint and API exposure 
  • Prompt injection across all inputs 
  • Agent tool and action boundaries 
  • Plugin and integration trust review 
  • Retrieval pipeline data leakage 
01 / LLM / Agents / MCP
AI Webp
02 / iOS / Android / APIs
mobile-app
02

Mobile Applications

Mobile apps handle authentication, store sensitive data, and expose backend APIs attackers actively target. Insecure storage, weak authentication, and API abuse give attackers direct access to your systems.

What attackers try
  • Insecure storage exposing user data 
  • Session bypass to hijack accounts 
  • Backend API abuse for data access 
  • Binary reverse for credential theft 
  • Runtime manipulation to bypass controls
What gets tested
  • Sensitive data stored on device 
  • Authentication and session integrity 
  • Backend API access and authorization 
  • Binary protection and tampering risk 
  • Runtime behavior and control bypass 
03

Web Applications

Web apps are one of the most targeted surfaces across enterprise environments. Business logic flaws, broken authorization, and API vulnerabilities give attackers access that automated scanners consistently miss.

What attackers try
  • Broken access control 
  • OAuth token theft 
  • API abuse for data extraction 
  • Forged server requests 
  • Exposed shadow endpoints 
What gets tested
  • Access control per user role 
  • Authentication and sessions 
  • OWASP Top 10 and OWASP API Security Top 10 
  • Server-side request forgery 
  • Legacy and undocumented APIs 
03 / Applications / Services / APIs
Web-App
04 / AWS / Azure / GCP
Cloud
04

Cloud

Cloud misconfigurations and overprivileged identities sit behind some of the most damaging enterprise breaches. A single exposed role or storage bucket gives attackers a path to your most critical systems.

What Attackers Try
  • Overprivileged roles 
  • Public buckets exposing data 
  • Container abuse for pivoting 
  • SSO abuse to hijack identities 
  • Exposed secrets and API keys 
What Gets Tested
  • IAM privilege escalation paths 
  • Storage and serverless exposure 
  • Container and Kubernetes security 
  • Federation and SSO configuration 
  • Secret and key management gaps 
05

Network

Network infrastructure is where attackers move after gaining initial access. Misconfigurations, weak segmentation, and exposed services turn a single foothold into full environment access.

What Attackers Try
  • Credential relay and replay 
  • Kerberoasting for account access 
  • Firewall rule exploitation 
  • DNS poisoning and hijacking 
  • Legacy protocol abuse 
What Gets Tested
  • Network segmentation validation 
  • Active Directory attack paths 
  • Firewall and ACL configuration 
  • DNS security and exposure 
  • Legacy protocol risk 
05 / Active Directory / Firewall / DNS
Network
06 / WiFi / 802.11 / Rogue Access
Wireless-Network
06

Wireless Network

Wireless environments often run on configurations that predate the current threat landscape. Rogue access points, weak encryption, and misconfigured authentication are the entry points attackers look for first.

What Attackers Try
  • Rogue access point deployment 
  • WPA2 cracking and WPA3 downgrade attacks 
  • Evil twin attacks on users 
  • PMKID and handshake capture 
  • Client deauthentication attacks 
What Gets Tested
  • Encryption and auth protocols 
  • Rogue access point detection 
  • Guest network segmentation 
  • Wireless client security 
  • Coverage and signal boundaries 
07

IoT

Any unmanaged IoT device is a potential entry point your security team has no visibility into. Attackers target weak firmware, default credentials, and unencrypted communications to establish persistent footholds.

What Attackers Try
  • Default credential exploitation 
  • Firmware extraction and analysis 
  • Unencrypted protocol abuse 
  • Device impersonation attacks 
  • Physical port exploitation 
What Gets Tested
  • Firmware and software security 
  • Default and weak credentials 
  • Network protocol encryption 
  • Device authentication controls 
  • Physical interface exposure 
07 / Devices / Firmware / Protocols
IoT
08 / ICS / SCADA / PLCs
OT-and-ICS
08

OT and ICS

OT environments demand a different approach. Every assessment delivers advisory depth across industrial control systems, with uptime and safety as fixed constraints.

What Attackers Try
  • IT to OT boundary crossing 
  • Remote access and vendor abuse 
  • Legacy protocol exploitation 
  • Engineering workstation pivot 
  • PLC and SCADA manipulation 
What Gets Tested
  • IT and OT segmentation review 
  • Remote access path exposure 
  • Legacy protocol and PLC risk 
  • Vendor and third party access 
  • IEC 62443 control alignment 
09

Social Engineering

Your people are part of your attack surface. Attackers exploit trust, urgency, and authority to bypass technical controls that would otherwise stop them cold.

What Attackers Try
  • Spear phishing targeting executives 
  • Vishing and pretexting calls 
  • Credential harvesting campaigns 
  • MFA bypass via social tactics 
  • Vendor and supplier impersonation 
What Gets Tested
  • Phishing susceptibility by role 
  • Credential harvesting exposure 
  • MFA bypass resistance 
  • Security awareness gaps 
  • Executive targeting resilience 
09 / Phishing / Vishing / Pretexting
Social Engineering
10 / Access Control / Hardware / Facilities
Physical-Security
10

Physical Security

Breach simulations often stop at the network. Skilled attackers walk through your front door, clone a badge, plug in a device, and reach systems your technical controls never anticipated protecting.

What Attackers Try
  • Tailgating and piggybacking 
  • Badge and RFID cloning 
  • Hardware implant deployment 
  • Unlocked workstation access 
  • Physical server room access
What Gets Tested
  • Physical access control gaps 
  • Badge and RFID security 
  • Hardware port exposure 
  • Workstation lock policies 
  • Facility security procedures
-- Test Models

Your Threat Model Drives Our Test Model

The right model starts with your threat landscape, compliance requirements, and the outcomes that matter most.

Black Box B
External Attacker View
Black box
Minimum details only. Testing starts from the same position a real external attacker occupies, with nothing but what is publicly reachable.
Gray Box G
Assumed Breach
Gray box
Limited access, modeling an insider threat or an attacker who already has a foothold in your environment.
White Box W
Internal Deep Dive
White box
Full access to architecture and source code, delivering the deepest technical coverage in the shortest time.
Engagement Scoping

Every Scope Starts with What Matters Most to You

The scoping session maps your threat model, your crown jewels, and what you need to prove, before a single test runs.

How-We-Define-the-Scope-of-Every-Engagement
01
Map the Attack Surface

Our team maps every system, integration, and entry point before testing begins. We account for cloud infrastructure, identity providers, third-party connections, and AI integrations upfront. 

02
Identify Crown Jewels

Your team and ours identify what an attacker would target first. Customer data, financial systems, and privileged access paths anchor every engagement objective.

03
Agree on Rules of Engagement

Both teams define timing, boundaries, communication channels, and escalation paths together. We document constraints first, including stop conditions, data handling rules, and out-of-bounds assets. 

04
Align on the Test Model

Both teams select black, gray, or white box based on your threat landscape and what the engagement needs to prove. Once aligned, both teams document the decision before testing begins. 

-Beyond Standard Scope

Deeper Coverage Across More Surfaces

The most exploited gaps in enterprise environments are not technical vulnerabilities. They are the surfaces that never made it into the scope. We built our coverage around exactly those gaps.

Common Coverage Gaps
The surfaces most engagements leave out.
AI endpoints absent from scope
Wireless networks rarely assessed
IoT devices left unreviewed
OT and ICS treated as a line item
Physical access controls ignored
Third party integrations unreviewed
Mobile apps tested at surface only
Social engineering excluded entirely
Our Differentiator
Broader Coverage and Deeper Testing
AI surfaces tested against OWASP Top 10 for LLM
Wireless assessed to IEEE 802.11 standards
IoT firmware and protocol coverage
OT and ICS tested to IEC 62443 standards
Physical access tested end to end
Third-party connections mapped and tested
Mobile tested across app, API, and backend
Social engineering scoped into every engagement
Back
to Top