Redact story Name and Description

[pmamut]

No description provided.

[spazmodius]

This redaction is poorly targeted, and unlikely to accomplish what is intended.

We blindly redact a certain asset's Name and Description, regardless of whether they contain the sensitive text.

• The sensitive text may be on other fields.
• The sensitive text may occur in historical variations of the current text.
• An innocent Name value may be shared with other assets.

I believe we should target text based on a pattern that the user supplies.

[pmamut]

This redaction is poorly targeted, and unlikely to accomplish what is intended.

We blindly redact a certain asset's Name and Description, regardless of whether they contain the sensitive text.

The customer intended for the entire story to be permanently removed, as if it never existed in the first place, including any possible non-sensitive historical values. Customer agreed to text content redaction as a proxy for complete removal of the story in question.

* The sensitive text may be on other fields.

Indeed, that was one outstanding question we still need to ask.

* The sensitive text may occur in historical variations of the current text.

Not sure what you mean. The redaction occurs historically against all Name and Description variants referenced by BaseAsset.

* An innocent Name value may be shared with other assets.

Possibly, if the story in question was ever named as something other than what is now sensitive content, and another story ever happened to share that original name. While we can detect string value being shared across multiple assets, we have no practical way of establishing its innocence.

I believe we should target text based on a pattern that the user supplies.

The customer was unwilling to disclose any information about the sensitive content to be redacted.