Skip to content

NEMEA Appliance

Jump to bottom Edit New page
Tomas Cejka edited this page Oct 12, 2016 · 2 revisions

About

NEMEA Appliance should be:

  • standalone
  • configurable
  • out-of-box deployable
  • monitorable and managable system, where all needed and useful parts are already installed and preconfigured.

The appliance should be deployable as a physical machine as well as virtual one.

General features

Some of them might be unused/switched off, depending on deployment.

  • flow collection (netflow/IPFIX/...); IPFIXcol; optional
  • flow export; NEMEA FlowMeter; optional - may be replaced by IPFIXcol
  • flow analysis and detection; NEMEA
  • longterm status monitoring; munin
  • watching the system status and health with notification (running processes, memory and disk space, incoming data in last N minutes, dropped messages); zabbix client/nagios client;
  • alerts visualization; NEMEA Dashboard
  • flow visualization; SecurityCloudGUI
  • report alerts into Warden; warden client; optional
  • configuration; ?

Installed software

  • ipfixcol
  • nemea
  • munin
  • nemea-dashboard
  • securitycloudgui
  • zabbix-agent
  • nagios-node
  • warden_client
Add a custom footer
Add a custom sidebar
Clone this wiki locally