Send audit records to storage mecak8s cannot change

Abierto
#2,846 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
go, kubernetes

Línea de trabajo

Read the Protection section in docs/drafts/agent-identity/audit.md, then inspect the reference deployment’s broker and gateway audit delivery configuration. Identify how to send records to storage with retention locks and document the required operator steps. Done means records already written cannot be changed or deleted by mecak8s during retention; the hourly signing collector is a stretch goal.

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

Descripción

agent-identity identity-broker security

Depends on: #2566 (audit records and delivery)

Problem

Audit records are only as trustworthy as where they are kept. A record that a compromised mecak8s can change or delete is not evidence.

Implements

Scope

  • A reference configuration points every component's sink (mecak8s, the broker, AS-1, AS-2, and the vMCP) at a store mecak8s cannot write to or delete from. It also gives investigators read-only access.
  • The operator steps are documented, including who owns retention and for how long.
  • AS-1 and AS-2 emit records from #2848 onward and use the same configuration.
  • Tamper evidence (hash chains, signed checkpoints, signed records) is #2808's.

Done when

  • In the reference deployment, records already delivered by any component cannot be changed or deleted by mecak8s within the retention period.
  • Investigators can read the records but not change them.
  • The operator steps are documented.
Lenguaje dominante
Go
Estrellas
309
Forks
29
Merge medio
15 h 56 min
PR fusionados (30 d)
225

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 stacklok/mecatl

Todos los issues de stacklok/mecatl

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.