+APP.2.2.A3 Planning of Group Policy in Windows (B)

APP.2.2.A3 Planning of Group Policy in Windows (B)

There MUST be a concept for configuring group policies. Multiple overlaps MUST be avoided whenever possible in the group policy concept. It MUST be possible to recognise exceptions to the group policy concept in the documentation. All group policy objects MUST be protected by restrictive access rights. Secure specifications MUST be defined for the parameters in all group policy objects.

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.15 Eavesdropping
blocks G 0.18 Poor Planning or Lack of Adaptation
blocks G 0.19 Disclosure of Sensitive Information
blocks G 0.21 Manipulation with Hardware or Software
blocks G 0.23 Unauthorised Access to IT Systems
blocks G 0.32 Misuse of Authorisation
blocks G 0.36 Identity theft
blocks G 0.43 Attack with Specially Crafted Messages
blocks G 0.46 Loss of Integrity of Sensitive Information