Skip to content

Commit

Permalink
docs: add some advice regarding logs
Browse files Browse the repository at this point in the history
  • Loading branch information
Freax13 committed Oct 9, 2024
1 parent a7df9e4 commit 1eb695b
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions docs/docs/architecture/security-considerations.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,3 +54,13 @@ Ideally, a volume is mounted as a raw block device and authenticated encryption

[`docker pull` documentation]: https://docs.docker.com/reference/cli/docker/image/pull/#pull-an-image-by-digest-immutable-identifier
[downward API]: https://kubernetes.io/docs/concepts/workloads/pods/downward-api/

### Logs

By default, container logs are visible to the host.
Sensitive information should not be logged.

As of right now, hiding logs isn't natively supported.
If `ReadStreamRequest` is denied in the policy, the Kata Agent stops reading the logs.
This causes the pipes used for standard out and standard error to fill up and potentially deadlock the container.
If absolutely required, standard out and standard error should be manually redirected to `/dev/null` inside the container.

0 comments on commit 1eb695b

Please sign in to comment.