Skip to main content

262COS Custom Elastic Data Pipelines


tip

On a a DIP configured IAW 262COS-DIP-SOP-001, Logstash is able to listen on TCP/6000 - 6009 and UDP/7000 - 7009 for custom inputs, such as custom logs ingested by Filebeat - but proper ingestion requires that your Data Engineer create custom Logstash Input, Filter, and Output configurations.

This chart illustrates how host data is collected from a source and processed through the Elastic stack to populate an index in Elasticsearch:

Data LocationData SourceData ShipperLogstash InputElasticsearch IndexIndex Aliases
Remote HostWindows Event Logs⇨Winlogbeat⇨logstash:5045⇨cvah-winlogbeat*winlogbeat-cvah*
Remote HostLog Files⇨Filebeat⇨logstash:5045⇨cvah-filebeat*filebeat-external-cvah*
Remote HostSystem Auditing⇨Auditbeat⇨logstash:5045⇨cvah-auditbeat*auditbeat-external-cvah*
Remote HostSystem Auditing⇨Syslog TCP⇨tcp:\\logstash:5047⇨cvah-syslogsyslog-cvah*
Remote HostSystem Auditing⇨Syslog UDP⇨udp:\\logstash:514⇨cvah-syslogsyslog-cvah*
Remote HostEndgame Agent⇨Endgame SMP⇨http:\\logstash:9800⇨cvah-endgame.stream*endgame-cvah*
Remote HostEndgame Agent⇨Endgame SMP⇨syslogtcp:\\logstash:9801⇨cvah-endgame.forwardedendgame-cvah*
CVAH (Metasponse)Metasponse Jobs⇨Metasponse⇨N/A (Straight to Elasticsearch)⇨ms-*
Custom LocationsCustom Sources⇨Custom TCP Inputs⇨tcp:\\logstash:6000-6009⇨Custom Indices
Custom LocationsCustom Sources⇨Custom UDP Inputs⇨udp:\\logstash:7000-7009⇨Custom Indices