Detect flaws in automated pipeline fetching logs for further processing

Description

AS A Product Owner
I WANT TO be confident that the pipeline transferring logs for further processing works as expected
SO THAT I could be confident that the logs that have been sent for further processing would not contain sensitive information and follow other rules defined for that purpose

Why is this important?

Processing application logs in the production environment would be unacceptable for many reasons. For example, writing to log files might get corrupted, processing the logs might cause other processes (including logging itself) to hang, etc. For this reason, transferring logs from their original source to another destination is necessary.

But it´s vital to make sure that sensitive information wouldn´t be transferred to any external location. This includes request IP, the content of request and response, and potentially many more. If these were to be processed outside of their original / intended location, it would be equal to a data breach of highly sensitive information.

Scope

Custom developments are needed.

Checklist

hide

Activity

Show:
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Priority

Checklist

Created August 4, 2023 at 9:30 AM
Updated August 4, 2023 at 3:27 PM

Flag notifications