+PW.9 Configure Software to Have Secure Settings by Default
---+PW.9.1 Define a secure baseline by determining how to configure each setting that has an effect on security or a security-related setting so that the …
---+PW.9.2 Implement the default settings (or groups of default settings, if applicable), and document each setting for software administrators.

PW.9 Configure Software to Have Secure Settings by Default

Statement

Help improve the security of the software at the time of installation to reduce the likelihood of the software being deployed with weak security settings, putting it at greater risk of compromise.

1. Übersicht

PW.9.1 Define a secure baseline by determining how to configure each setting that has an effect on security or a security-related setting so that the …

Statement

Define a secure baseline by determining how to configure each setting that has an effect on security or a security-related setting so that the default settings are secure and do not weaken the security functions provided by the platform, network infrastructure, or services.

Example 1:

Conduct testing to ensure that the settings, including the default settings, are working as expected and are not inadvertently causing any security weaknesses, operational issues, or other problems.
PW.9.2 Implement the default settings (or groups of default settings, if applicable), and document each setting for software administrators.

Statement

Implement the default settings (or groups of default settings, if applicable), and document each setting for software administrators.

Example 1:

Verify that the approved configuration is in place for the software.

Example 2:

Document each setting’s purpose, options, default value, security relevance, potential operational impact, and relationships with other settings.

Example 3:

Use authoritative programmatic technical mechanisms to record how each setting can be implemented and assessed by software administrators.

Example 4:

Store the default configuration in a usable format and follow change control practices for modifying it (e.g., configuration-as-code).

1.1 Referenzen

1.2 Identifizierte Anforderungen

1.3 Zugehörige Regulierungen

2. Identifizierte Anforderungen

Anforderungen

3. Zugehörige Regulierungen

Regulierungen

Verknüpfte Vorgänge

Verknüpfungen
is blocked by Secure Settings By Default
  • NIST -

    EN: Publications of the National Institute of Standards and Technology (NIST), U.S. Department of Commerce, https://www.nist.gov/, from their electronic versions (OSCAL; SP 800-63-4 from its HTML version, https://pages.nist.gov/800-63-4/). Works of NIST employees are not subject to copyright protection in the United States (17 U.S.C. § 105); the OSCAL content is dedicated to the public domain worldwide (CC0 1.0); outside the United States NIST grants the right to reprint its technical series publications in all formats (NIST copyright statement). Republished courtesy of the National Institute of Standards and Technology; each document names its citation. Divided into sections and converted into the GRCA format, the wording unchanged. Only the versions published by NIST are authoritative.

    DE: Veröffentlichungen des National Institute of Standards and Technology (NIST), U.S. Department of Commerce, https://www.nist.gov/, aus ihren elektronischen Fassungen (OSCAL; SP 800-63-4 aus ihrer HTML-Fassung, https://pages.nist.gov/800-63-4/). Werke von NIST-Beschäftigten sind in den USA urheberrechtlich nicht geschützt (17 U.S.C. § 105); die OSCAL-Inhalte sind weltweit gemeinfrei gestellt (CC0 1.0); außerhalb der USA räumt das NIST das Recht ein, seine Technical-Series-Publikationen in allen Formaten neu zu veröffentlichen (Copyright-Hinweis des NIST). „Republished courtesy of the National Institute of Standards and Technology“; jedes Dokument nennt seine Zitierangabe. In Abschnitte aufgeteilt und in das GRCA-Format umgewandelt, der Wortlaut unverändert. Maßgeblich sind allein die vom NIST veröffentlichten Fassungen.