import { motion } from "framer-motion"; import { ArrowLeft, Calendar, Users, Tag, BookOpen, Target, FlaskConical, BarChart3, Shield, FileText, ExternalLink } from "lucide-react"; import { Link } from "react-router-dom"; const ResearchReport = () => { return (
{/* Top bar */}
{/* Header */}

> Research Report Template

[Research Project Title]

[One-line subtitle or thesis statement summarizing the research]

[Publication Date] [Author(s)] [Domain: Malware / Network / AppSec / etc.] RPT-[ID]
{/* Table of Contents */}

Table of Contents

    {[ "Abstract", "Introduction & Motivation", "Threat Landscape / Background", "Methodology", "Findings & Analysis", "Case Studies / Proof of Concept", "Mitigations & Recommendations", "Conclusion & Future Work", "Appendix & References", ].map((item, i) => (
  1. {i + 1}. {item}
  2. ))}
{/* Sections */}
{/* 1. Abstract */}
} number="01" title="Abstract">

A concise summary (150–300 words) of the entire report. Cover the problem, approach, key findings, and significance. This should stand alone — a reader should understand the research scope without reading further.

Write the abstract LAST, after completing all other sections. It should answer: What? Why? How? What did you find? Why does it matter?
{/* 2. Introduction */}
} number="02" title="Introduction & Motivation">

Set the stage for your research. Why is this topic important? What gap in knowledge or capability are you addressing?

{/* 3. Threat Landscape */}
} number="03" title="Threat Landscape / Background">

Provide context. What does the reader need to know to understand your research? Cover relevant prior work, current threat actors, and existing defenses.

{`3.1 Historical Context - Evolution of [threat/technology] - Key incidents / milestones 3.2 Current State - Active threat actors & TTPs (MITRE ATT&CK mapping) - Existing detection / defense mechanisms - Known gaps and limitations 3.3 Related Work - Academic papers & industry reports - How your research extends or differs from prior work`}
{/* 4. Methodology */}
} number="04" title="Methodology">

Detail your research approach so others can replicate it. Be specific about tools, datasets, environment, and procedures.

{[ { label: "Research Type", value: "[Empirical / Analytical / Experimental / Survey]" }, { label: "Environment", value: "[Lab setup, OS versions, hardware specs]" }, { label: "Dataset", value: "[Source, size, collection period, any sampling]" }, { label: "Tools & Frameworks", value: "[List primary tools with versions]" }, ].map((item, i) => (

{item.label}

{item.value}

))}
{`Step 1: [Data Collection / Sample Gathering] - Describe sources and collection methods Step 2: [Analysis / Processing] - Describe analytical techniques applied Step 3: [Testing / Validation] - Describe how you validated results Step 4: [Documentation] - How results were recorded and verified`}
{/* 5. Findings */}
} number="05" title="Findings & Analysis">

Present your results with data, evidence, and analysis. Use tables, charts, and code samples to support findings. Separate raw findings from your interpretation.

{`Finding #1: [Title] Severity: [Critical / High / Medium / Low / Informational] Evidence: [Data points, logs, screenshots] Impact: [What this means for defenders / attackers] Confidence: [High / Medium / Low] Finding #2: [Title] ... Statistical Summary: - [X]% of samples exhibited [behavior] - [Metric] increased by [X]% compared to baseline - [Other quantitative results]`} Always distinguish between correlation and causation. Be transparent about limitations in your data or methodology.
{/* 6. Case Studies */}
} number="06" title="Case Studies / Proof of Concept">

Provide concrete examples that demonstrate your findings. Each case study should follow a consistent format.

{`=== Case Study [#]: [Descriptive Title] === Background: [Context for this specific example] Setup: [Environment, configuration, preconditions] Execution: [Step-by-step walkthrough with evidence] Results: [What happened, with supporting data] Analysis: [How this supports your broader findings]`} If including exploit PoCs, follow responsible disclosure. Redact sensitive information and include appropriate warnings.
{/* 7. Mitigations */}
} number="07" title="Mitigations & Recommendations">

Provide actionable recommendations organized by audience and priority.

{[ { priority: "Critical", desc: "[Immediate actions to address highest-risk findings]" }, { priority: "High", desc: "[Important changes for near-term implementation]" }, { priority: "Medium", desc: "[Best-practice improvements to adopt over time]" }, { priority: "Low", desc: "[Long-term strategic enhancements]" }, ].map((item) => (
{item.priority}

{item.desc}

))}
{/* 8. Conclusion */}
} number="08" title="Conclusion & Future Work">
{/* 9. Appendix */}
} number="09" title="Appendix & References">

Include supplementary material: raw data tables, full configuration files, extended code samples, and a complete bibliography.

{`[1] Author(s). "Title." Publication/Source, Year. URL [2] Author(s). "Title." Publication/Source, Year. URL [3] CVE-YYYY-XXXXX — [Brief description]. NIST NVD. [4] MITRE ATT&CK — [Technique ID]: [Technique Name]`}
{/* Footer */}

COBRA Research Group · Report ID: RPT-[XXX] · Classification: [PUBLIC / TLP:CLEAR]

← Back to Home
); }; /* ---- Reusable sub-components ---- */ const Section = ({ icon, number, title, children }: { icon: React.ReactNode; number: string; title: string; children: React.ReactNode }) => (
{icon}

{number}{title}

{children}
); const CodeBlock = ({ title, children }: { title: string; children: string }) => (
{title}
      {children}
    
); const Note = ({ type, children }: { type: "info" | "warning"; children: React.ReactNode }) => (
{children}
); const InfoBox = ({ title, children }: { title: string; children: React.ReactNode }) => (

{title}

{children}

); const Checklist = ({ items }: { items: string[] }) => ( ); export default ResearchReport;