Penetration
testing
Hands-on testing of your applications and infrastructure. You get verified findings, the steps to reproduce them, and advice on what to fix first.
Talk about scopeBetter on your side.
We spend a lot of time figuring out how things break. We put that work into testing your applications, infrastructure, and defenses.
01 / What we do
Agree the scope.
Test it properly.
Make the findings useful.
Hands-on testing of your applications and infrastructure. You get verified findings, the steps to reproduce them, and advice on what to fix first.
Talk about scopeWe agree on an objective, then test whether your defenses can detect and stop a realistic attack. Afterwards, we walk through what happened with your team.
Talk about scopeSome questions need more than a standard test. We investigate specific software, security boundaries, and attack paths, and build tools when we need them.
Talk about scopemacOS · Red team
Exploring macOS sandbox boundaries, browser sessions, and the assumptions between them.
DNS / Tool development 2021.07
Building a DNS transport for Mythic, including message ordering, caching, and connection recovery.
Read the research on Medium (opens in a new tab)Covenant / Networking 2020.06
Adding reverse port forwarding to Covenant, from the agent to socket management.
Read the research on Medium (opens in a new tab)Vulnerability research 2020.03
How weaknesses in BookStack’s image upload could lead to remote code execution.
Read the research on Medium (opens in a new tab)03 / The Nemesis mindset
The research is
part of the job.
Working out how a sandbox can be escaped or how a tool handles network traffic changes the way you approach a security test.
That is the work behind Nemesis.red. The writing here covers macOS security, tooling for red team operations, and web vulnerabilities. It is published openly so other people can use it, question it, and build on it.
Tell us what needs testing
and when you need it done.