Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PII logs of application running on client data center may get printed in ECS control plane #6

Open
gopalc opened this issue Jun 30, 2021 · 1 comment

Comments

@gopalc
Copy link

gopalc commented Jun 30, 2021

We have observed that logs of application running on client data center may get printed in ECS control plane. If application is printing PII data in logs(unknowingly or knowingly), then it will get shared in ECS Control plane. Is there any mechanism to avoid printing PII data in ECS Control plane?

Logs in ECS control plane

@mreferre
Copy link
Contributor

mreferre commented Jul 1, 2021

This is a very interesting question. First and foremost consider that the story of PII in this tutorial was fictitious and primarily inspirational. In other words we did not put a lot of efforts in making sure we were not sending specific data that would break this story to the region. Having that said what you log is at your own discretion. For example in this tutorial I am printing the directory name (which matches the SQS message name). I have assumed that PII related data were within the file (and I am not logging any of the content). I am no PII expert but, in a similar real case scenario where I am concerned to log something that would break my PII requirements, I would simply either not log it OR I would consider, for EXTERNAL tasks, to not use CW logs and leave logs locally (parsed with other mechanisms). It is a very interesting topic, thanks for bringing this up. I may add these considerations right in the tutorial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants