Loading
Clarent360 runs 9 penetration testing disciplines across 41 named engagements — network, cloud, identity, wireless, and the social layer attackers actually use first. Every engagement is scoped, authorised, and reported the way a real attacker's campaign would run, minus the damage.
Our engagements map to the same stages a real attack follows — so you know exactly which part of the chain each service tests.
Each entry below links to a dedicated checklist or scope showing every named engagement we run under that discipline.
External Network Testing, Internal Network Testing, and segments validation.
Microsoft Azure Subscriptions, Microsoft 365, and Entra ID Cloud Testing.
Server OS, Database isolation pathways, and Virtualization hypervisors.
Wi-Fi networks, Rogue access point scans, Bluetooth, and remote access setups.
Active Directory forests, Entra ID configuration, and cross-realm IAM designs.
Phishing campaigns, voice vishing, spear phishing, and employee resistance tests.
Ransomware replication, insider threat playbooks, and exfiltration tracking.
Attack surface mapping, asset discovery, and continuous external management.
Executive reporting, technical debriefs, remediation retesting, and validation.
Every Clarent360 pentest runs under a signed scope and authorisation — no engagement starts without these four pillars agreed.
Signed scope and rules of engagement before any testing begins.
Exact systems, IP ranges, and techniques in scope, agreed up front.
Methods chosen to prove exploitability without causing operational damage.
A direct line to your team throughout the engagement, not just at the end.
Tell us what's in scope and what you're worried about — we'll recommend the right engagement, or a phased programme across several.