Spaces:
Running on Zero
Running on Zero
Harvester ZeroGPU runner — full upload
Browse files- app.py +1 -0
- cybersecurity_defense_tasks.json +141 -0
app.py
CHANGED
|
@@ -52,6 +52,7 @@ TASK_BANKS = {
|
|
| 52 |
"maslow_hierarchy_tasks.json": "Maslow's Hierarchy & Human Motivation (15 tasks) → Qwen Coder",
|
| 53 |
"family_dynamics_tasks.json": "Family Dynamics & Human Bonds (15 tasks) → Qwen Coder",
|
| 54 |
"cognitive_architecture_tasks.json": "Cognitive Architecture & HCI (15 tasks) → Qwen Coder",
|
|
|
|
| 55 |
}
|
| 56 |
|
| 57 |
|
|
|
|
| 52 |
"maslow_hierarchy_tasks.json": "Maslow's Hierarchy & Human Motivation (15 tasks) → Qwen Coder",
|
| 53 |
"family_dynamics_tasks.json": "Family Dynamics & Human Bonds (15 tasks) → Qwen Coder",
|
| 54 |
"cognitive_architecture_tasks.json": "Cognitive Architecture & HCI (15 tasks) → Qwen Coder",
|
| 55 |
+
"cybersecurity_defense_tasks.json": "Cybersecurity Defense & Self-Protection (15 tasks) → Qwen Coder",
|
| 56 |
}
|
| 57 |
|
| 58 |
|
cybersecurity_defense_tasks.json
ADDED
|
@@ -0,0 +1,141 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
{
|
| 2 |
+
"bank_name": "cybersecurity_defense",
|
| 3 |
+
"description": "Defensive cybersecurity — understanding attacker tools and methodology for self-protection. Based on Kali Linux toolkit categories. Every task is framed as defense, detection, or analysis — never offensive exploitation.",
|
| 4 |
+
"tasks": [
|
| 5 |
+
{
|
| 6 |
+
"id": "cyber_defense_01",
|
| 7 |
+
"title": "Port Scan Detector",
|
| 8 |
+
"description": "Build a system that analyzes network connection logs and detects port scanning patterns. Given a list of connection attempts (timestamp, source_ip, dest_port, protocol), identify: sequential port scans (nmap-style), SYN flood patterns, stealth scan signatures (half-open connections), and service enumeration attempts. Classify scan type, estimate attacker intent, and recommend firewall rules to block without disrupting legitimate traffic. Handle at least 4 scan types: TCP connect, SYN stealth, UDP, and FIN scan.",
|
| 9 |
+
"language": "python",
|
| 10 |
+
"difficulty": 3,
|
| 11 |
+
"category": "network_defense",
|
| 12 |
+
"tags": ["nmap", "port-scanning", "ids", "firewall-rules", "network-monitoring"]
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"id": "cyber_defense_02",
|
| 16 |
+
"title": "Vulnerability Assessment Analyzer",
|
| 17 |
+
"description": "Create a vulnerability scoring and prioritization engine. Given a list of discovered vulnerabilities (CVE ID, CVSS base score, affected service, network exposure, exploit availability), calculate adjusted risk scores that account for: network position (internet-facing vs internal), exploit maturity, asset criticality, and compensating controls. Output a prioritized remediation plan with estimated effort and risk reduction per fix. Implement CVSS v3.1 temporal and environmental score adjustments.",
|
| 18 |
+
"language": "python",
|
| 19 |
+
"difficulty": 4,
|
| 20 |
+
"category": "risk_assessment",
|
| 21 |
+
"tags": ["vulnerability-scanning", "cvss", "risk-prioritization", "openvas", "remediation"]
|
| 22 |
+
},
|
| 23 |
+
{
|
| 24 |
+
"id": "cyber_defense_03",
|
| 25 |
+
"title": "SQL Injection Pattern Recognizer",
|
| 26 |
+
"description": "Build a web request analyzer that detects SQL injection attempts in HTTP parameters. Given raw HTTP request data (URL, query params, POST body, headers), identify: classic injection patterns (OR 1=1, UNION SELECT), blind injection timing attacks, error-based extraction attempts, and encoded/obfuscated payloads (hex, URL encoding, comment injection). Score each request's threat level and generate WAF rules to block detected patterns while minimizing false positives on legitimate queries.",
|
| 27 |
+
"language": "python",
|
| 28 |
+
"difficulty": 4,
|
| 29 |
+
"category": "web_defense",
|
| 30 |
+
"tags": ["sqlmap", "sql-injection", "waf", "input-validation", "owasp-top-10"]
|
| 31 |
+
},
|
| 32 |
+
{
|
| 33 |
+
"id": "cyber_defense_04",
|
| 34 |
+
"title": "Password Strength Auditor",
|
| 35 |
+
"description": "Create a password policy analyzer that evaluates password strength against real-world attack methods. Given a password, estimate crack time against: dictionary attacks (common wordlists), rule-based mutations (hashcat rules — leet speak, appending numbers, capitalization), brute force at various hardware tiers (CPU, GPU cluster, ASIC), and rainbow table lookups for common hash algorithms. Output entropy bits, estimated crack times per method, and specific weakness explanations. Do NOT store or transmit passwords — analysis only.",
|
| 36 |
+
"language": "python",
|
| 37 |
+
"difficulty": 3,
|
| 38 |
+
"category": "authentication_defense",
|
| 39 |
+
"tags": ["john-the-ripper", "hashcat", "password-policy", "entropy", "bruteforce-estimation"]
|
| 40 |
+
},
|
| 41 |
+
{
|
| 42 |
+
"id": "cyber_defense_05",
|
| 43 |
+
"title": "Wireless Intrusion Detector",
|
| 44 |
+
"description": "Build an analyzer for wireless network security events. Given a log of 802.11 frames (frame type, source MAC, dest MAC, BSSID, signal strength, timestamp, encryption type), detect: deauthentication flood attacks, evil twin access points (same SSID different BSSID), WPS brute force attempts, PMKID capture attempts, and rogue AP detection. For each threat, classify severity, identify the attack tool signature (aircrack-ng patterns, Wifite patterns), and recommend countermeasures.",
|
| 45 |
+
"language": "python",
|
| 46 |
+
"difficulty": 4,
|
| 47 |
+
"category": "wireless_defense",
|
| 48 |
+
"tags": ["aircrack-ng", "deauth-detection", "evil-twin", "wids", "802.11-security"]
|
| 49 |
+
},
|
| 50 |
+
{
|
| 51 |
+
"id": "cyber_defense_06",
|
| 52 |
+
"title": "Phishing Email Analyzer",
|
| 53 |
+
"description": "Create a phishing detection engine that analyzes email metadata and content. Given email headers (From, Reply-To, Received chain, SPF/DKIM/DMARC results, X-headers) and body content, detect: sender spoofing, domain typosquatting, urgency manipulation tactics, credential harvesting links, attachment-based payload delivery, and social engineering patterns. Score phishing probability, identify the specific social engineering technique used (authority, scarcity, reciprocity), and generate a human-readable threat report.",
|
| 54 |
+
"language": "python",
|
| 55 |
+
"difficulty": 3,
|
| 56 |
+
"category": "social_engineering_defense",
|
| 57 |
+
"tags": ["set-toolkit", "phishing-detection", "email-headers", "spf-dkim", "social-engineering"]
|
| 58 |
+
},
|
| 59 |
+
{
|
| 60 |
+
"id": "cyber_defense_07",
|
| 61 |
+
"title": "Log Forensics Engine",
|
| 62 |
+
"description": "Build a security log correlation engine. Given logs from multiple sources (syslog, auth.log, Apache access log, firewall log), reconstruct an attack timeline. Detect: brute force login attempts, privilege escalation sequences, lateral movement indicators, data exfiltration patterns (unusual outbound data volumes), and log tampering (gaps in timestamps, modified entries). Output a forensic timeline with kill chain stage mapping (Recon → Weaponize → Deliver → Exploit → Install → C2 → Actions).",
|
| 63 |
+
"language": "python",
|
| 64 |
+
"difficulty": 5,
|
| 65 |
+
"category": "forensics",
|
| 66 |
+
"tags": ["autopsy", "sleuthkit", "log-analysis", "kill-chain", "incident-response"]
|
| 67 |
+
},
|
| 68 |
+
{
|
| 69 |
+
"id": "cyber_defense_08",
|
| 70 |
+
"title": "Network Traffic Anomaly Detector",
|
| 71 |
+
"description": "Create a network traffic baseline and anomaly detection system. Given PCAP-like flow data (src_ip, dst_ip, src_port, dst_port, protocol, bytes, packets, duration, flags), establish normal traffic patterns and detect: C2 beaconing (periodic callbacks), DNS tunneling (high-entropy DNS queries), data exfiltration via ICMP or DNS, ARP spoofing, and port knocking sequences. Use statistical methods (z-score, IQR) for baseline deviation and implement Markov chains for protocol behavior modeling.",
|
| 72 |
+
"language": "python",
|
| 73 |
+
"difficulty": 5,
|
| 74 |
+
"category": "network_defense",
|
| 75 |
+
"tags": ["wireshark", "tcpdump", "anomaly-detection", "c2-detection", "dns-tunneling"]
|
| 76 |
+
},
|
| 77 |
+
{
|
| 78 |
+
"id": "cyber_defense_09",
|
| 79 |
+
"title": "Cryptographic Implementation Auditor",
|
| 80 |
+
"description": "Build a code analyzer that reviews cryptographic usage for common mistakes. Given code snippets using crypto libraries, detect: use of deprecated algorithms (MD5, SHA1, DES, RC4), hardcoded keys or IVs, ECB mode usage, insufficient key lengths, missing authentication (encrypt without MAC), predictable random number generation, and improper certificate validation. For each finding, explain the vulnerability, the realistic attack scenario, and the correct implementation.",
|
| 81 |
+
"language": "python",
|
| 82 |
+
"difficulty": 4,
|
| 83 |
+
"category": "crypto_defense",
|
| 84 |
+
"tags": ["openssl", "crypto-audit", "key-management", "tls-verification", "cipher-suites"]
|
| 85 |
+
},
|
| 86 |
+
{
|
| 87 |
+
"id": "cyber_defense_10",
|
| 88 |
+
"title": "Privilege Escalation Path Mapper",
|
| 89 |
+
"description": "Create a system configuration analyzer that identifies privilege escalation paths. Given system state data (SUID binaries, cron jobs, file permissions, sudo rules, running services, kernel version, environment variables), map potential escalation routes from unprivileged user to root. Classify each path by: exploitability (easy/medium/hard), required conditions, detection difficulty, and remediation steps. Handle both Linux and Windows escalation vectors (SUID abuse, DLL hijacking, unquoted service paths, weak permissions).",
|
| 90 |
+
"language": "python",
|
| 91 |
+
"difficulty": 5,
|
| 92 |
+
"category": "system_defense",
|
| 93 |
+
"tags": ["linpeas", "winpeas", "privilege-escalation", "suid", "misconfiguration"]
|
| 94 |
+
},
|
| 95 |
+
{
|
| 96 |
+
"id": "cyber_defense_11",
|
| 97 |
+
"title": "API Security Boundary Validator",
|
| 98 |
+
"description": "Build an API security analyzer that tests endpoint configurations for common vulnerabilities. Given API endpoint definitions (route, method, auth requirements, rate limits, input schemas, response schemas), detect: broken access control (IDOR patterns), missing authentication, excessive data exposure in responses, mass assignment vulnerabilities, missing rate limiting, and SSRF-vulnerable parameters. Map findings to OWASP API Top 10 categories and generate security middleware recommendations.",
|
| 99 |
+
"language": "python",
|
| 100 |
+
"difficulty": 4,
|
| 101 |
+
"category": "web_defense",
|
| 102 |
+
"tags": ["burpsuite", "api-security", "owasp-api-top-10", "idor", "access-control"]
|
| 103 |
+
},
|
| 104 |
+
{
|
| 105 |
+
"id": "cyber_defense_12",
|
| 106 |
+
"title": "Malware Behavior Classifier",
|
| 107 |
+
"description": "Create a behavioral analysis engine for suspicious processes. Given process activity logs (file operations, registry changes, network connections, child processes spawned, DLL loads, API calls), classify behavior patterns as: ransomware (mass file encryption), keylogger (input hook installation), RAT (reverse shell, screen capture), cryptominer (high CPU, mining pool connections), or worm (self-replication, network scanning). Score confidence per classification and recommend containment actions.",
|
| 108 |
+
"language": "python",
|
| 109 |
+
"difficulty": 5,
|
| 110 |
+
"category": "malware_defense",
|
| 111 |
+
"tags": ["malware-analysis", "behavioral-detection", "sandbox", "process-monitoring", "containment"]
|
| 112 |
+
},
|
| 113 |
+
{
|
| 114 |
+
"id": "cyber_defense_13",
|
| 115 |
+
"title": "Prompt Injection Shield",
|
| 116 |
+
"description": "Build a defense system specifically for AI/LLM applications. Given user inputs to an AI system, detect: direct prompt injection (attempts to override system instructions), indirect prompt injection (malicious content in retrieved documents), jailbreak attempts (roleplay escapes, DAN-style attacks), data extraction attempts (asking the model to reveal training data or system prompts), and context window poisoning. Score threat level, classify injection technique, and implement input sanitization that preserves legitimate queries.",
|
| 117 |
+
"language": "python",
|
| 118 |
+
"difficulty": 5,
|
| 119 |
+
"category": "ai_defense",
|
| 120 |
+
"tags": ["prompt-injection", "llm-security", "input-sanitization", "jailbreak-detection", "ai-safety"]
|
| 121 |
+
},
|
| 122 |
+
{
|
| 123 |
+
"id": "cyber_defense_14",
|
| 124 |
+
"title": "Supply Chain Attack Detector",
|
| 125 |
+
"description": "Create a dependency security analyzer. Given a project's dependency tree (package names, versions, sources, checksums, maintainer history), detect: typosquatting packages, compromised maintainer accounts (ownership transfers), dependency confusion attacks (private vs public registry conflicts), known malicious packages, unusual post-install scripts, and version pinning vulnerabilities. Score risk per dependency, map the blast radius of each compromised package, and recommend lockfile strategies.",
|
| 126 |
+
"language": "python",
|
| 127 |
+
"difficulty": 4,
|
| 128 |
+
"category": "supply_chain_defense",
|
| 129 |
+
"tags": ["dependency-check", "supply-chain", "typosquatting", "sbom", "package-security"]
|
| 130 |
+
},
|
| 131 |
+
{
|
| 132 |
+
"id": "cyber_defense_15",
|
| 133 |
+
"title": "Incident Response Orchestrator",
|
| 134 |
+
"description": "Build an incident response decision engine. Given an active security incident (alert type, affected systems, current containment status, available responders, business impact), generate a response plan following NIST SP 800-61 phases: Detection & Analysis, Containment, Eradication, Recovery, Post-Incident. Prioritize actions by impact reduction, estimate response time per action, handle escalation triggers, preserve forensic evidence chain of custody, and schedule stakeholder communications. Handle simultaneous incidents with resource conflicts.",
|
| 135 |
+
"language": "python",
|
| 136 |
+
"difficulty": 5,
|
| 137 |
+
"category": "incident_response",
|
| 138 |
+
"tags": ["nist-800-61", "incident-response", "containment", "forensic-preservation", "business-continuity"]
|
| 139 |
+
}
|
| 140 |
+
]
|
| 141 |
+
}
|