I will onboard any log source into elastic siem with ingest pipelines and ecs

Morocco

I speak English, Arabic, French, Spanish

Elastic SIEM engineer: detection rules, log pipelines, dashboards

I'm a SOC and detection engineer working every day in a 24/7 multi-client SOC (retail and fintech on AWS). I deploy and administer Elastic Security and Wazuh, from a single node to a multi-node cluste...
About this Gig

Logs arriving in Elastic as one unreadable message field? Or a source with no integration at all?


I onboard log sources into Elastic for a 24/7 SOC: Windows, Linux, firewalls, AWS, Microsoft 365, Cloudflare and web servers. I parse them properly so your dashboards and detection rules actually work.


What I do:

  • Elastic Agent and Fleet integrations, Beats or Logstash
  • Custom ingest pipelines: grok, dissect, JSON, date and GeoIP
  • Mapping to the Elastic Common Schema (ECS)
  • Index templates and lifecycle (ILM)
  • Data quality checks: missing fields, mapping conflicts, silent sources
  • Custom Python collectors for APIs with no integration, run as a hardened service


Sources I have onboarded: Windows event logs, Linux, firewalls, AWS CloudTrail, GuardDuty and VPC Flow Logs, Microsoft 365 and Entra ID, Cloudflare, nginx, EDR tools.


Message me with the source, a sample log line (sensitive data removed) and your Elastic version.

Destination Platform:

Other

Tools & Platforms:

Other

Related tags