Task access, submissions and review cost ₹0. A verified certificate is optional at ₹99 after required approvals and the program's date conditions.
Learn to define permission before running a security exercise
This track moves from foundations and virtual lab setup to reconnaissance, simulated testing, OSINT, a web audit and a vulnerability report. Prepare basic networking and command-line skills and confirm that your lab can run safely. Use authorized targets and the current task instructions; public accessibility is not authorization.
A good report separates an observation, the evidence supporting it, potential impact and a proposed remediation. Do not claim exploitation or a confirmed vulnerability from an unexplained scanner output. Keep private identifiers and credentials out of screenshots. If you prefer building protective scripts to conducting an assessment, compare Cyber Security. Use the portfolio checklist to present safe lab evidence with its limitations.
Seven stages of an authorised assessment
The standard roadmap includes all seven briefs and LinkedIn offer-letter onboarding. The starter assigns onboarding, fundamentals and lab setup. These tasks create their own lab evidence, so unrelated filler datasets are not needed.
1. Cybersecurity Fundamentals
Research the CIA triad and threat-mitigation principles. Connect each concept to a concrete defensive example and cite the references you use.
Submit: A structured technical PDF report.
2. Virtual Lab Setup
Configure an isolated VirtualBox or VMware lab with Kali Linux and a target virtual machine. Document the network boundaries and how the setup stays separate from unrelated systems.
Submit: A lab configuration PDF with setup screenshots.
3. Networking & Reconnaissance
Use the brief's networking tools to study an authorised target. Record the scope, observations and limits of the results rather than simply pasting command output.
Submit: A reconnaissance scan and analysis PDF.
4. Penetration Testing Simulation
Demonstrate a controlled assessment of the vulnerable lab VM. Keep the proof confined to the exercise and explain the conditions required for the observed issue.
Submit: A simulation report PDF with the requested proof of concept.
5. OSINT Investigation
Assess publicly available metadata within an authorised scope. Distinguish directly observed information from inference and avoid compiling private personal profiles.
Submit: An exposure assessment PDF.
6. Web Application Audit
Audit the intentionally vulnerable application specified by the brief, such as DVWA or Juice Shop. Explain the issue and a defensive correction within that lab.
Submit: A web audit PDF with remediation snippets.
7. Final Vulnerability Report
Compile the assessment into an executive-readable report using the CVSS version requested in the dashboard brief. Make severity reasoning, evidence and recommended remediation easy to trace.
Submit: The final penetration-testing and vulnerability-assessment PDF.
Evidence with boundaries
Work only on systems you own or are explicitly authorised to test. Do not scan or exploit Workora, classmates' devices or public services as part of this internship. Remove secrets and private data from screenshots.
Use headings for scope, method, findings, impact, limitations and remediation. State whether a finding was reproduced or only suspected. Check signed-out access to your submitted report. The Cyber Security roadmap is a different option focused on defensive programming utilities.
Participation and completion rules
Standard registration offers 30, 45 or 60 days with eight total tasks. The 7 Days Starter Instant Internship has three tasks and no deadline while unpaid. Verified optional payment after those approvals sets the starter end date. Standard certificates follow their scheduled access rules and confirmed dashboard options.
No job, stipend, placement, accreditation or college-credit outcome is guaranteed. Review fees and program formats.