Full red teaming assessment
A goal driven simulation of a real attacker, across people, process and technology.
- External attack surface and initial access
- Phishing and social engineering, where authorised
- Lateral movement and privilege escalation
- Active Directory and identity attack paths
- Detection and response by your blue team
- Access to agreed crown jewel objectives
The business problem
A penetration test tells you what is vulnerable. It does not tell you whether your team would notice a determined intruder, or how far that intruder would get before anyone reacted.
Scope of assessment
Scope is agreed with you before any work starts. A typical engagement covers the areas below, adjusted to your environment, your priorities and any testing windows you need.
- External attack surface and initial access
- Phishing and social engineering, where authorised
- Lateral movement and privilege escalation
- Active Directory and identity attack paths
- Detection and response by your blue team
- Access to agreed crown jewel objectives
Methodology
Automated coverage first, then manual work where it counts. Every finding is validated before it reaches you.
- Discovery
- Reconnaissance
- Threat modeling
- Scanning
- Manual testing
- Exploitation
- Validation
- Risk analysis
- Reporting
- Remediation support
- Retesting
Typical engagement timeline
Usually several weeks. Set by objectives and rules of engagement.
Standards and references
- MITRE ATT&CK
- TIBER style threat led testing
- PTES
Tools and techniques
- Custom tooling
- Command and control frameworks
- Open source intelligence
- Manual tradecraft
What you receive.
- Attack narrative with timeline
- ATT&CK technique mapping
- Detection gaps and blue team observations
- Prioritised hardening plan
- Executive debrief
Benefits
- Know which weaknesses are real and exploitable
- Fix in the order that reduces the most risk
- Give leadership and auditors clear evidence
- Confirm fixes work through retesting
Full red teaming assessment report
Executive summary
Each finding: evidence, impact, steps to reproduce, fix.
Why us.
- Experienced security professionalsAssessments are led by practitioners who do this work every day.
- Offensive security expertiseWe think like attackers because that is our core discipline.
- Manual validationEvery finding is confirmed by a person before it reaches your report.
- Enterprise focused assessmentsScoping, communication and reporting that fit large organisations.
- Transparent reportingEvidence, reproduction steps and plain language. No padding.
- Actionable remediationSpecific fixes your developers and administrators can apply.
Questions.
How long does a penetration test take?
It depends on scope. A single application often takes one to three weeks, and larger estates take longer. We confirm the timeline during scoping, before work begins.
What does a security assessment report contain?
An executive summary, scope and methodology, each finding with severity, evidence and reproduction steps, the business risk, and specific remediation guidance.
Do you provide remediation support?
Yes. We walk your developers and administrators through each finding and stay available for questions while they fix it.
Do you provide retesting?
Yes. Once fixes are in place we retest the affected items and update the report with the verified status.
What security standards do you follow?
Our work references the OWASP Top 10, OWASP API Security Top 10, OWASP ASVS, OWASP MASVS, CWE Top 25, PTES, NIST guidance and MITRE ATT&CK, as applicable to the engagement.
