+APP.4.6.A12 Avoiding Generic Module Execution (S)

APP.4.6.A12 Avoiding Generic Module Execution (S)

Transactions, programs, function modules, and methods SHOULD NOT be generically executable. If there are important reasons for a generic execution, where and why this is happening SHOULD be documented in detail. In addition, a whitelist SHOULD be defined that contains all the permitted modules. Before a module is called, the user's input SHOULD be compared against the whitelist.

1. Vue d’ensemble

1.1 Références

1.2 Exigences identifiées

1.3 Réglementations associées

2. Exigences identifiées

Exigences

3. Réglementations associées

Réglementations

Tickets liés

Liens
blocks G 0.14 Interception of Information / Espionage
blocks G 0.19 Disclosure of Sensitive Information
blocks G 0.22 Manipulation of Information
blocks G 0.28 Software Vulnerabilities or Errors
blocks G 0.45 Data Loss
blocks G 0.46 Loss of Integrity of Sensitive Information