Approach
How we run an engagement
The same eight steps, the same reporting standard and the same free retest, every time.
Workflow: AI for speed, testers for judgement
- 01Scope Tester
Objectives, systems, test windows and rules agreed in writing before we start.
- 02Reconnaissance AI runs · tester approves
AI maps what an attacker sees first: domains, apps, people, technology. A tester reviews it and approves before any active testing.
- 03Scanning AI runs · tester oversees
AI finds known weaknesses fast, within limits a tester sets.
- 04Enumeration AI runs · tester oversees
AI lists every role, endpoint and data object; a tester checks for gaps.
- 05Vulnerability analysis AI runs · tester verifies
AI flags suspects; a tester verifies each one by hand and removes false positives.
- 06Attack chaining Tester approves · human verified
One flaw rarely sinks you; chained together, they do. Every step is approved by a tester before it runs and verified by a person after.
- 07Reporting Tester
Each attack chain drawn as a map: impact the board understands, proof developers can reproduce.
- 08Remediation and retest Tester retests
Break the critical link and we retest free to confirm the whole chain is broken.
From single flaws to an attack chain
A scanner lists flaws one by one. We show how they connect, from the front door to your most important data, and which single fix breaks the whole chain.
Example from a red team exercise for a financial services provider, anonymised.
What is in the report
Illustration only: each report is written to the engagement scope.
Executive summary
Risk explained as business impact, for boards and management.
Technical findings
Each with a CVSS rating, affected assets, reproduction steps and screenshots.
Proof of concept
So your developers can reproduce and verify.
Remediation guidance
Prioritised and ready to act on.
Compliance mapping
Mapped to SFC, HKMA, critical infrastructure, OWASP and more.
Retest results
A free retest confirms each issue is closed.
Rules of engagement
- Scope, windows and limits agreed in writing before testing
- Testing outside office hours can be arranged to protect operations
- Test activity is logged automatically in Burp Suite and the log is available on request
- Critical findings are reported immediately, not held for the report
- Reports are jointly owned by DracoSec and the client
Standards and frameworks
Tools we commonly use (depending on scope)
Assurance
Your engagement is insured, start to finish
DracoSec carries cyber insurance covering its professional services, from scoping through the final report and remediation guidance. Our accountability is backed by contract, not just by promises.
Choose how you work with us
Single project
For a one-off test or a pre-launch assessment, with a clear scope and a fixed quote.
Token package
Pre-purchase assessment credit and draw it down per engagement. Unused tokens carry forward within the contract period.
Time and materials
For organisations whose scope keeps changing or goes beyond penetration testing.
Before your next audit, let us find the gaps.
Tell us about your systems and your deadline. We reply within one working day to set up a 15-minute scoping call.