# זיהוי סודות בקבצים מצורפים

**URL:** <https://meta.discourse.org/t/detecting-secrets-in-attachments/322660>\
**Category:** Feature\
**Created:** [21 באוגוסט,‏ 2024,‏ 8:44am UTC](https://meta.discourse.org/t/detecting-secrets-in-attachments/322660 "2024-08-21T08:44:41Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Colin\_Mueller](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/colin_mueller/32/220223_2.png) [@Colin\_Mueller](https://meta.discourse.org/u/Colin_Mueller)\
**Post date:** [21 באוגוסט,‏ 2024,‏ 8:44am UTC](https://meta.discourse.org/t/detecting-secrets-in-attachments/322660/1 "2024-08-21T08:44:41Z")

</div>

Hey there!

We run a support community where users often upload log files. We encourage open support discussions whenever possible and only exceptionally raise private messages to collect logs (when we think there’s a lot of value in having the unredacted logs or it’s a novel situation we’d like to debug as soon as possible).

We’ve encountered a recurring issue: users inadvertently exposing “secrets” (tokens) in their attachments.

This puts us in a tricky position. We have to inform users about compromised tokens and educate them on safe sharing practices while trying to maintain a balance between open support and confidentiality (not blurring the lines between our confidential professional support and community support).

We’d love to see a feature that scans attachments for secrets, similar to the existing AV scanning functionality (which we use). Ideally, this feature would warn users when secrets are detected in their uploads and possibly alert administrators about potential exposures.

I know it’s not a particularly small task, [we’re in the business of scanning code for secrets](https://rules.sonarsource.com/secrets/), but maybe there’s some traction!

WDYT?

---

_[View the full topic](https://meta.discourse.org/t/detecting-secrets-in-attachments/322660)._
