42 lines
1.2 KiB
Plaintext
42 lines
1.2 KiB
Plaintext
======================
|
|
AVERAGE/HIGH PRIORITY:
|
|
======================
|
|
|
|
- Comment all the code!!!
|
|
- Support for more logs
|
|
- True bayesian temporal correlation
|
|
|
|
=============
|
|
LOW PRIORITY:
|
|
=============
|
|
|
|
- Managing clusters for addresses, timestamps (and more?)
|
|
- Splitting the distinct subgraphs of the output graph
|
|
|
|
=====
|
|
DONE:
|
|
=====
|
|
|
|
+ PostgreSQL support
|
|
+ Regex comp cache
|
|
+ Managing hyperalert graph connection inside the alert structure itself
|
|
+ Keeping track of all the streams and alerts even after clustered
|
|
+ Dynamic cluster_min_size algorithm
|
|
+ Add alerts' history serialization to db.c as well
|
|
+ Bayesian learning among alerts in alert log
|
|
+ Split bayesian correlation out of correlation.c
|
|
+ Clustering alerts with time constraints
|
|
+ Save clusters and correlations to db
|
|
+ Uniformed error messages format
|
|
+ Full PostgreSQL support for output db
|
|
+ Web interface
|
|
+ Function names (private functions with _ or __ ?)
|
|
+ Saving packet flows as .pcap
|
|
+ Manual alert correlation from the web interface
|
|
+ Neural network for alert correlation
|
|
+ Supporting extra modules for alert correlation
|
|
+ Testing more scenarios, making more hyperalert models
|
|
+ Code profiling
|
|
+ Geographical IP localization and visualization
|
|
|