Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
TetraWiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Category:Alstom
Category
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=='''Alstom ELK Training session'''== ==Training on Alstom ELK Training session. Dated 17 Feb 2024 - Tetra Support Staff - Biswajit Banerjee== {{#ev:youtube|R6xAaw4J0-o|640}} '''Video summary:''' Detailed 1-hour session on the ELK (Elasticsearch/Logstash/Kibana) security log monitoring platform built for Alstom, a French rail-solutions company, as part of a Central Security Program (CSP) requiring centralized log capture and alerting across their Windows and Linux estate. Architecture: an rsyslog relay server receives logs from all devices on ports 514 (TCP) and 8514 (UDP) and forwards them to a 2-node Elasticsearch cluster (both nodes configured as master, for redundancy) via Logstash, with a custom Logstash filter/pipeline tagging entries by hostname and program name. Covers building alert rules from specific Windows Event IDs (account disabled/enabled/deleted, privilege/security-group escalation, failed logins, password resets, audit log clears) and equivalent Linux alerts (sudo escalation, failed su attempts, anti-brute-force config changes), plus McAfee (ePO) event alerts and ELK's own internal health alerts (cluster health, disk/CPU usage, shard/thread-pool sizing). Also walks through building Kibana dashboards for authentication-failure trends, and the snapshot/backup mechanism -- an LVM volume shared across both nodes via NFS, snapshotted via Elasticsearch's Curator/snapshot API, which the presenter had already used once to recover from an accidental data deletion during setup.
Summary:
Please note that all contributions to TetraWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
TetraWiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)