CON.8.A5 Secure System Design (B)

The following basic rules of secure system design MUST be considered in the software to be developed:

All input data MUST be checked and validated before further processing takes place.
For client-server applications, the data MUST be validated on the server side.
The software's default settings MUST be set to facilitate secure operation.
In the event of errors in or failures of system components, sensitive information MUST NOT be disclosed.
It MUST be possible to run the software with as few privileges as possible.
Sensitive data MUST be transmitted and stored in encrypted form according to the specifications of the crypto concept at hand.
Trusted mechanisms that meet the security requirements of the application in question MUST be used for user authentication and access.
If passwords are stored for authentication, they MUST be stored using a secure hash procedure.
Security-relevant events MUST be logged in such a way that they can be evaluated afterwards.
Information that is not relevant for productive operation (e.g. comments with access data for the development environment) SHOULD be removed in delivered program code and configuration files.

The system design MUST be documented. It MUST be verified that the system design meets all the relevant security requirements.

1. Vue d’ensemble

Intitulé	Norme

Exigences
Source	Exigence

Réglementations
Source	Réglementation

Liens
Type de lien	Ticket
blocks	G 0.14 Interception of Information / Espionage
blocks	G 0.15 Eavesdropping
blocks	G 0.18 Poor Planning or Lack of Adaptation
blocks	G 0.19 Disclosure of Sensitive Information
blocks	G 0.20 Information or Products from an Unreliable Source
blocks	G 0.23 Unauthorised Access to IT Systems
blocks	G 0.25 Failure of Devices or Systems
blocks	G 0.40 Denial of Service
blocks	G 0.41 Sabotage
blocks	G 0.46 Loss of Integrity of Sensitive Information

BSI -
Copyright by Bundesamt für Sicherheit in der Informationstechnik (https://www.bsi.bund.de/)