- Home
- Offensive Security & Hunting
- Penetration testing
We attack you before someone else does,
and prove every finding.
Ragnarök is our penetration testing practice. With written permission, we test your networks, applications, cloud and people the way a criminal would, then re-test to confirm the fixes worked.
A list of what an attacker can actually do.
A scanner tells you what might be wrong. A penetration test shows what an attacker can do with it. Our testers validate every finding by hand and chain weaknesses together into real attack paths, from an exposed service to domain admin, or from a phishing click to your customer data.
Every engagement runs under agreed rules of engagement with real-time communication during exploitation. Each finding comes with the evidence that it is real, a severity ranked to your business, and a specific fix. When you have closed them, we test again to confirm the fix held.
- An executive summary written for leadership and the board
- Technical findings with proof-of-concept evidence for each one
- A severity on every finding, ranked to your business context
- Step-by-step remediation guidance your engineers can act on
- A re-test after remediation, with an updated report
Scope, attack, report, re-test.
Scope and permission
We agree targets, timing and rules of engagement in writing, sized to your risk and any audit or customer requirement you are testing for.
Reconnaissance
Open-source intelligence and attack-surface enumeration, the same groundwork a real attacker does first.
Exploit, with care
Automated and manual testing, controlled exploitation and post-exploitation to show what access really means, with a live line to your team throughout.
Report and re-test
Findings with proof, severity and a fix. Once you have remediated, we re-test and confirm.
Every surface an attacker would try.
Network
External perimeter, internal networks, VPN and remote access, wireless, and segmentation validation.
Active Directory
Kerberoasting, NTLM relay, delegation abuse and the lateral-movement paths that lead to domain admin.
Web applications and APIs
OWASP Top 10, authentication and session handling, REST and GraphQL endpoints, and business-logic flaws.
Cloud
Identity and permission paths, exposed storage and misconfiguration across your cloud tenants.
Mobile and IoT
Mobile applications, their back-end APIs and connected devices on your network.
Industrial systems
OT and ICS testing scoped around safety and uptime, on systems that cannot simply be rebooted.
People
Phishing, voice pretexting, helpdesk testing and physical entry, where in scope.
Segmentation
Confirmation that the boundaries you designed actually stop an attacker from crossing them.
Recognised frameworks, applied by hand.
- Aligned to PTES, the OWASP Testing Guide and NIST SP 800-115
- Written rules of engagement before any testing starts
- Manual validation of every finding, no scanner dumps
- Chained findings to show real attack paths and business impact
- Real-time contact with your team during exploitation
- Re-test after remediation, included
Who it is for
Anyone facing an audit, a customer security questionnaire, or a board that wants proof rather than reassurance. Also anyone who has changed their environment since the last test.
- Vulnerability assessment, every asset scanned and ranked between tests
- Red team, test your defenders, not just your systems
- Cyber war gaming, rehearse the response to what we found
- Application security, fix the code the findings point to
What buyers ask.
We had a test last year.
Then you have a list. Did anything change since, and did anyone check the fixes worked? Your environment moves every quarter. Re-testing is included so the second question always gets answered.
How is this different from a vulnerability scan?
A scan lists what might be wrong. We prove what an attacker can actually do with it, chain weaknesses together and show the business impact, with evidence for each finding.
Will testing break production?
Testing runs under written rules of engagement. Exploitation is controlled, risky actions are agreed in advance, and your team has a live line to us throughout. Fragile systems such as OT are scoped around safety and uptime.
Will the report satisfy our auditor or customer?
It is written to. You get an executive summary for leadership, technical evidence for engineers, a severity on every finding and a re-test report showing what was closed.
Find it before they do.
Put an engineer on a call to scope a Ragnarök test for your environment. No charge, no commitment.