Future Interns Header

Cyber Security Task 1 (2026)

Vulnerability Assessment Report for a Live Website (Read-Only Scope)

πŸ” About the Task

Every business today owns a website β€” but most websites are not secure.

Small businesses, startups, and agencies often:

  • use outdated plugins or frameworks
  • misconfigure security headers
  • expose sensitive information unknowingly

Clients usually don’t ask for hacking.
They ask for clarity:

β€œIs my website safe?”
β€œWhat are the risks?”
β€œWhat should we fix first?”

This task teaches you how to do exactly that β€” professionally and ethically.

🎯 Objective

Your goal is to:

  • Analyze a public website for common security weaknesses
  • Classify risks in a business-friendly way
  • Explain issues clearly (no technical jargon overload)
  • Suggest practical remediation steps
  • Present everything in a professional audit report

You are learning security consulting, not hacking.

⚠️ Scope & Ethics (Very Important)

This task follows strict ethical guidelines.

Allowed

  • Public-facing pages only
  • Passive scanning
  • Header checks
  • Configuration analysis

Not Allowed

  • Login bypass
  • Exploitation
  • Brute force attacks
  • Denial-of-Service (DoS)
  • Any activity that can harm the website

Think like a security auditor, not an attacker.

πŸ› οΈ Tools You’ll Use

You do not need advanced tools or paid software.

Security & Analysis Tools

  • Nmap – basic port & exposure analysis
  • OWASP ZAP (Passive Scan) – identify vulnerabilities without attacking
  • Browser DevTools – inspect headers, cookies, and client-side issues

Reporting Tool

  • Canva – to design a professional vulnerability assessment report

βœ… What You’ll Do (Step-by-Step)

As part of this task, you will:

  1. Select a public website
    (demo website, personal site, or permitted test domain)
  2. Perform read-only analysis
    • Identify exposed services
    • Check security headers
    • Detect outdated components (if visible)
  3. Document findings
    • What is the issue?
    • Why does it matter?
    • What is the risk level?
  4. Classify risks
    • Low / Medium / High
  5. Suggest clear remediation
    • Practical fixes a business can understand

✨ Key Features of Your Report

Your final report should include:

βœ” List of identified vulnerabilities
βœ” Risk classification (Low / Medium / High)
βœ” Simple explanation (non-technical language)
βœ” Clear remediation steps
βœ” Clean, professional layout

βœ… GitHub Repositories You Can Use as Inspiration

πŸ”Ή Sample Vulnerability Assessment Report – A real VAPT report example showing how findings are documented.
πŸ‘‰ https://github.com/harygovind/Sample-vulnerability-report-for-testphp.vulnweb GitHub

πŸ”Ή Pentest Report Template – A reusable report structure that helps you format professional findings.
πŸ‘‰ https://github.com/MTK911/pentest-report-template GitHub

πŸ”Ή Public Penetration Test Reports Collection – A large list of publicly published security reports for real-world context.
πŸ‘‰ https://github.com/juliocesarfort/public-pentesting-reports GitHub

🧠 Additional Helpful Resources

(Not full report templates, but extremely useful for learning how to structure testing and reporting)

πŸ”Ή OWASP Web Security Testing Guide (WSTG) – A comprehensive guide covering how tests should be done, including reporting best practices.
πŸ‘‰ https://github.com/OWASP/www-project-web-security-testing-guide GitHub

πŸ”Ή Example Web Penetration Test Report Sample (includes doc/pdf)
πŸ‘‰ https://github.com/h0tPlug1n/Web-Penetration-Testing-Report-Sample GitHub

πŸ”Ή Security Audit Report Template (basic structure)
πŸ‘‰ https://github.com/darkoid/SecurityAuditReportTemplate Gi

πŸ“€ Final Deliverable

You must submit:

  • A Vulnerability Assessment Report:
    • Designed in Canva
    • Includes findings, risk levels, and fixes
  • Supporting evidence:
    • Screenshots (where applicable)
    • Tool outputs (cleanly documented)
  • A public GitHub repository containing:
    • Report PDF
    • Evidence
    • README explaining:
      • website tested
      • scope
      • tools used

Your submission should feel like something you could confidently send to:

  • a business owner
  • an agency client
  • a security consultant

🌟 Showcase Your Work

After completion:

  • Share your dashboard design onΒ LinkedIn
  • Explain:
    • which agency you designed it for
    • how the workflow improves efficiency
  • TagΒ Future Interns

https://www.linkedin.com/company/future-interns

Scroll to Top