Hi, thank you for a great product!

I have a small request:

Currently, when StackRox logs the contents of processes inside a container like a curl requests (for example, in the UI, logs, or in external integrations such as Slack notifications), sensitive information such as tokens, authorization headers, API keys, or other secrets may be included in plain text. This poses a security risk by potentially leaking credentials to users with access to logs, UI, or integrations.

To make matters worse, StackRox's only one DeploymentExtension:Read permission controls both network flows and the display of processes and startup arguments, requiring this permission to be granted to anyone who needs network browsing access.

Feature Request:

Please add a feature that enables automatic masking or removal of sensitive data when logging processes inside a container like a curl requests or sending request data to external integrations (such as Slack).

Desired Behavior:

• Sensitive data fields should be replaced with a placeholder (like [REDACTED]) before being logged or sent to the UI/integrations.
• There should be a configuration option to disable or enable showing and loggin of processes launch options.
• The masking/removal should be applied consistently across all logs, UI displays, and outgoing integrations (such as Slack notifications).

Example:

Before:
curl -H "Authorization: Bearer secret_token_123" -H "x-api-key: myapikey" https://api.example.com/data

After:
curl [REDACTED]

Thank you for considering this feature request! Please let me know if additional details or clarifications are needed.