MSF RCP study plan
MSF RCP · Give each week a clear focus.
8 weeks · About 7 hours per week
Metasploit Framework fundamentals and architecture & Installation, configuration, and console operation
Diagram the Metasploit architecture from memory: msfconsole, msfvenom, msfrpcd, module tree, database backend, and how Rex/core/msfbase libraries layer together
Install Metasploit Framework on a dedicated lab VM and initialize the PostgreSQL database, confirming msfdb status reports connected
Enumerate the console's core commands (search, use, info, show options, set, setg, back, sessions, workspace) and record each command's purpose in your own notes
Configure a workspace per engagement and capture the exact commands used in a reproducible setup script
Your checkpoint
A one-page architecture diagram plus a working installation script that provisions a fresh VM and attaches the database
Exploitation with modules and payloads & Metasploit Framework fundamentals and architecture
Explain how a module's mixins, options, targets, and payload compatibility rules determine what payloads can pair with an exploit
Run at least three exploits against intentionally vulnerable lab targets (e.g., Metasploitable) using both reverse and bind payloads, and compare reliability
Practice generating payloads with msfvenom, setting LHOST/LPORT, encoders, and output formats, and verify each artifact runs in the lab
Use check where a module supports it and interpret the returned vulnerability code
Your checkpoint
A table of five exploit/payload pairings with observed success rates and the exact resource script (.rc) that reproduces each run
Exploitation with modules and payloads & Meterpreter and post-exploitation
Transition sessions from raw shell to Meterpreter and demonstrate migration, process listing, and privilege context checks
Execute post-exploitation modules for credential harvesting, local enumeration, and persistence in the lab, documenting each module's required options
Use the route and portfwd commands to pivot through a compromised host to a second lab subnet
Script a repeatable workflow with resource files that automates exploitation through post-exploitation steps
Your checkpoint
A pivot lab write-up showing a two-hop network path with command transcripts and a working .rc automation file
Information gathering and scanning & Vulnerability analysis and validation
Integrate Nmap and auxiliary scanner modules with the Metasploit database, then query results with hosts, services, and vulns
Import third-party scan output (e.g., Nmap XML) and use search with database-backed filters to prioritize targets
Validate at least three suspected vulnerabilities manually with auxiliary modules and explain how false positives arise
Map findings to a severity ranking and justify each rating with evidence from the lab
Your checkpoint
A validated findings register for one lab subnet: host, service, suspected vuln, validation method, confirmed/refuted, severity
Client-side and social engineering attacks & Exploitation with modules and payloads
Build a client-side attack chain (e.g., browser or document exploit) in the lab and explain each stage from delivery to session
Set up a controlled listener and demonstrate payload delivery through a local test page or file, verifying the callback
Compare client-side payload formats and explain trade-offs in detection, reliability, and user interaction
Document defensive indicators that would reveal the attack in logs or endpoint telemetry
Your checkpoint
A client-side attack lab report with screenshots described in text, the callback transcript, and a list of detection artifacts
Meterpreter and post-exploitation & Vulnerability analysis and validation
Perform thorough post-exploitation enumeration on a compromised lab host: users, privileges, network shares, and installed software
Demonstrate credential extraction from memory or configuration in the lab and explain the operational risk of each technique
Configure and verify a persistence mechanism, then clean it up completely and confirm removal
Review Meterpreter extension commands and note which ones require elevated context
Your checkpoint
A post-exploitation checklist with command transcripts, plus proof that persistence was installed and fully removed
Metasploit Pro workflows and reporting & Ethics, scope, and legal compliance
Walk through a Metasploit Pro project lifecycle in a trial or lab instance: discovery, exploitation, evidence collection, and report generation
Produce a client-ready report from the platform and critique its accuracy, clarity, and remediation guidance
Draft a rules-of-engagement and scope document covering authorization, target boundaries, data handling, and stop conditions
Apply an ethical decision framework to three gray-area scenarios (out-of-scope host discovered, sensitive data encountered, testing window exceeded)
Your checkpoint
A complete sample engagement package: signed-style scope document, generated report, and a written remediation summary
Metasploit Framework fundamentals and architecture & Installation, configuration, and console operation & Information gathering and scanning & Vulnerability analysis and validation & Exploitation with modules and payloads & Meterpreter and post-exploitation & Client-side and social engineering attacks & Metasploit Pro workflows and reporting & Ethics, scope, and legal compliance
Run a timed full-scope lab engagement end to end, from recon through reporting, without consulting notes for core commands
Revisit every missed or uncertain objective from weeks 1-7 and close each gap with a hands-on retest
Explain the architecture, module mechanics, and post-exploitation flow aloud in a ten-minute self-review
Finalize a personal command reference and remediation checklist for future use
Your checkpoint
A timed end-to-end lab engagement report plus a personal quick-reference sheet covering every domain
Milestones
Week 2: Can install the framework, initialize the database, and land a Meterpreter session on a lab target from a clean VM in under 30 minutes using only your own notes
Week 4: Can import scan data, query the database, and produce a validated findings register where every severity rating cites specific evidence
Week 6: Can pivot to a second subnet, harvest credentials, install and remove persistence, and explain each step's detection footprint
Week 8: Complete a timed full-scope lab engagement with a written report that includes scope compliance, validated findings, and remediation guidance