Build log forwarding to the SIEM

Abierto
  • ¿Algo no está bien?
#94 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
bash, linux, powershell
Área
security

Línea de trabajo

Start on branch phase-6/log-forwarding; read spec design 14 section 4 and issue #79 first. Implement modules observe.forward_linux, observe.forward_windows, observe.searches in phases/observe/modules/, using Splunk Forwarder with syslog/HEC fallbacks. Write bats and Pester acceptance tests listed in the issue; done means those tests pass and no SIEM address sits in the repo.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area: logging phase: observe platform: linux platform: windows type: build

Location & Context

Roadmap branch phase-6/log-forwarding. Spec: design 14 section 4. Planned module IDs: observe.forward_linux, observe.forward_windows and observe.searches, in phases/observe/modules/. Depends on #79.

Current Behavior

Logs do not leave the hosts, so traps and checks cannot be seen in one place.

Remediation Plan

  1. Install or use the Splunk Universal Forwarder on Linux and Windows, from what is present or its pinned download.
  2. Add syslog on Linux and the HEC script on Windows as fallbacks.
  3. Add the saved searches, including the outbound log rule that blocks nothing.
  4. Open no network flow other than the one to the SIEM.
  5. Write these acceptance tests first (bats and Pester):
    • A marker event from every lab host arrives in the SIEM.
    • With no forwarder and no download possible, the HEC script ships the marker event; restarting the task neither loses nor repeats an event.
    • A SIEM certificate whose thumbprint does not match is refused.
    • On a host whose forwarder already sends elsewhere, the destination change is listed for approval, not made.
    • With the SIEM stopped, hosts keep running and local logs stay under their size cap.
    • The repository contains no SIEM address or event value, only templates.
    • A negative test: protected accounts and scored services are untouched before and after.
Lenguaje dominante
PowerShell
Estrellas
0
Forks
0
Merge medio
54 min
PR fusionados (30 d)
43

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de dotnetdork/Labyrinth

Todos los issues de dotnetdork/Labyrinth

Issues similares

Más issues de Security

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.