Observe
Ingest alerts, code findings, asset context, CVEs or network events.
AGENTIC AI2026Cybersecurity HackathonTrack 01
Move from alert overload to explainable, controlled action.
Read the brief ↓
01The opportunity
Security teams work across noisy alerts, vulnerable code, threat intelligence and incomplete context. A useful defensive agent does more than classify an event: it gathers evidence, prioritises risk, proposes a response and keeps a human in control of consequential actions.
Agent behaviour
Ingest alerts, code findings, asset context, CVEs or network events.
Correlate evidence, rank urgency, explain confidence and identify missing context.
Recommend containment, draft a patch or create an incident action—with approval before impact.
What to develop
Build a defensive agent that investigates a security problem and produces an evidence-backed next step. It may analyse sample network flows, source code, vulnerability records or incident logs. Show its boundaries, approval points and a clear record of why it acted.
Recommended structure
Starter concepts
Group related alerts, reconstruct an incident timeline and recommend the next investigation step.
Combine exploit evidence, asset importance and exposure to rank what should be fixed first.
Find a defensible class of code flaws, validate the finding and propose a focused patch.
Turn logs and a playbook into a contained response plan with explicit approval gates.
Data & references
Use these as a starting point, or create a clearly documented synthetic dataset. Never test on systems or people without permission.
An example of an AI security workflow that scans, validates findings and prepares targeted fixes.
Open official source ↗University of New BrunswickLabelled benign and attack network flows in PCAP and CSV formats.
Open official source ↗CISAAn authoritative catalogue for testing risk-aware vulnerability prioritisation.
Open official source ↗Your submission should prove