merge V14.3.1 to V7.4.1

[elarlang]

14.3.1

V14.3.1 Verify that web or application server and framework error messages are configured to deliver user actionable, customized responses to eliminate any unintended security disclosures.

The requirement is duplicate with V7.4.1:

V7.4.1 Verify that a generic message is shown when an unexpected or security sensitive error occurs, potentially with a unique ID which support personnel can use to investigate.

I think wording should me merged that points and keys from both are covered and only V7.4.1 should stay. Category should be "Error handling", because even "to show errors or not" is question of configuration, then proper error handling must be also done with program code.

[jmanico]

+1 Good call Elar, very astute observation

…

-- Jim Manico @manicode

On Dec 9, 2020, at 3:16 AM, Elar Lang ***@***.***> wrote:  14.3.1 V14.3.1 Verify that web or application server and framework error messages are configured to deliver user actionable, customized responses to eliminate any unintended security disclosures. The requirement is duplicate with V7.4.1: V7.4.1 Verify that a generic message is shown when an unexpected or security sensitive error occurs, potentially with a unique ID which support personnel can use to investigate. I think wording should me merged that points and keys from both are covered and only V7.4.1 should stay. Category should be "Error handling", because even to show errors are not is question of configuration, then proper error handling must be also done with program code. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[elarlang]

Proposal:

• keep 7.4.1 as it is and remove 14.3.1 as it's duplicate.

[jmanico]

Good proposal. Would you care to do a PR for this? Let's do it.