Find out how an attacker
would get in.
ORD is the offensive security team inside HLD Group. With your written permission, we attack your systems, devices and people the way a real adversary would, then show you what we reached and how to close it off.
- Written authorisation before any testing
- Agreed scope and rules of engagement
- Reports for engineers and executives
When to engage ORD
The moments teams usually call us
Most engagements start with one of these situations. If yours is different, we can still help you work out what to test.
Before a major launch
A new platform, app or cloud environment is about to go live and you want it tested by people who think like attackers.
After a big change
A merger, migration or new identity provider has changed what is exposed, and nobody has checked it end to end.
When someone asks for evidence
Your board, insurer, a customer or a regulator wants proof that your controls hold up against a real attempt.
To test your detection
You have invested in monitoring and want to know whether your team would notice and respond to a real intrusion.
What we test
Four areas, one team
Real attackers move between technology, devices and people. ORD covers all of them, so findings in one area can be followed into the next.
Networks, cloud and identity
Controlled attacks on your infrastructure to find out whether a real compromise is possible and how far it would go.
- Penetration testing
- Red team operations
- Cloud compromise simulation
- Network intrusion testing
- Active Directory exploitation
- Stealth adversary emulation
Exploit research
Our own research into new weaknesses, how they could be weaponised, and the practical fixes that stop them.
- Vulnerability discovery
- Exploit development
- Reverse engineering
- Malware analysis
- Proof-of-concept exploits
- Vulnerability intelligence
Hardware and devices
Testing the phones, embedded systems and connected devices that sit outside most security reviews.
- Mobile devices
- Embedded systems
- IoT infrastructure
- Firmware review
- Hardware interfaces
- Device authentication
People and physical access
Authorised simulations that show how someone could get around your technical controls through staff, doors and processes.
- Phishing and social engineering
- Security awareness testing
- Access control systems
- Facility security
- Insider threat simulation
- Operational resilience
Engagement types
Pick the question you need answered
Each type of engagement answers a different question. Not sure which fits? We will recommend one during scoping.
“Where are we exploitable right now?”
Best for
A defined system, application or environment that needs a thorough, hands-on check.
“Would we stop the kind of attacker most likely to target us?”
Best for
Benchmarking your defences against the techniques a specific adversary is known to use.
“Could a determined attacker reach what matters most, and would we notice?”
Best for
Organisations that want to test detection, response and resilience over a longer campaign.
Alongside engagements, ORD publishes technical reports, vulnerability disclosures and advisories from its research, written so your team can act on them.
How an engagement works
Authorised and documented from the first call.
Offensive testing is only useful when it is safe and legal. Every ORD engagement runs under strict legal and ethical controls, with a written scope that you approve before we touch anything.
- 01
Scope
We agree with you on targets, goals, systems that are off limits, and when testing can happen.
- 02
Authorise
Someone with the authority to approve the work signs off in writing. No testing starts before this.
- 03
Test
We carry out the agreed work and keep a record of every action we take along the way.
- 04
Report and fix
You get the findings, the attack paths behind them and a remediation plan ordered by risk, written for both engineers and executives.
What you receive
Proof of what an attacker could do
A long list of weaknesses is hard to act on. We show how the important ones connect, so you can see which single fix breaks the most attack paths.
Executive summary
What we found and what it means for the business, written for leadership.
Technical findings
Each issue with evidence and the steps needed to reproduce it.
Attack path maps
How individual weaknesses chained together, from first access to impact.
Remediation plan
Fixes ordered by what an attacker would use first, so effort goes where it counts.
Example attack path
Illustrative- 1
Initial access
A phishing email captures a staff member's password.
- 2
Foothold
The same password works on the VPN, which has no MFA.
- 3
Escalation
A misconfigured service account grants domain admin rights.
- 4
Impact
Read access to the customer database.
Common questions
Before you get in touch
How is this different from a vulnerability scan?
A scanner lists known issues it can detect automatically. ORD combines weaknesses the way a person would, to show which ones lead somewhere that matters. That tells you what to fix first.
Is offensive testing legal?
Yes, when the owner of the systems authorises it in writing and the work stays inside the agreed scope. Every ORD engagement has both in place before testing begins.
Will testing disrupt our operations?
Testing windows and off-limits systems are agreed during scoping. If something is sensitive or fragile, we plan the work around it before we start.
How does ORD relate to Sentinel and Overwatch?
ORD tests your defences from the attacker's side. HLD Sentinel and Overwatch are our defensive platforms that detect and contain threats. What ORD finds can inform how those defences are tuned.
Talk to ORD about an engagement
Tell us what you want tested and we will come back with a proposed scope.