# NIST800 171 3.4.1 — Baseline Configuration

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_nist800171_341_756ec4a5cd-nist800-171-341-baseline-configuration
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [NIST SP 800-171 Readiness](https://support.icompaas.com/support/solutions/c_gen_nist800171) › [Configuration Management](https://support.icompaas.com/support/solutions/folders/f_gen_cgennist800171_configurationmanagement)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

NIST800 171 · Control 3.4.1 · Priority: high · Component: Configuration Management

### What this control covers

This control requires the development and Maintenance of a current baseline configuration of the system under configuration control. The baseline must be reviewed and updated at defined intervals or when system components are installed or modified. Baseline configurations document the system's components, operational procedures, network topology, and architecture, serving as the foundation for future system builds and changes. This control supports the Configuration Management System capability within the Configuration Management (3.4) family.

### Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

### How to implement

#### AWS

Codify the policy intent as **SCPs, AWS Config conformance packs, and Security Hub standards** so the cloud enforces what the document says.

#### Azure

Codify in **Azure Policy initiatives** (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

#### GCP

**Org Policy Service** for guardrails and **Config Validator** in CI to pre-check Terraform plans against policy as code (Rego).

#### GitHub

Apply **branch protection** on default and release branches: require PR review, status checks, signed commits, linear history, and dismiss stale reviews on new commits. Use **CODEOWNERS** for required reviewers, **Dependabot** + **CodeQL** for SAST, and the **Dependency graph / SBOM** export for vendor disclosures.

#### On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

### Evidence to collect

-   `policy_document` — A signed, version-controlled policy stating leadership intent and the named owner.
-   `infra_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.

Signed policy or standard documents the safeguard. Focus: Baseline Configuration.

### Quick checklist

-   Baseline — Management / Configuration
-   Configuration — Management / Configuration
-   System — Management / Configuration
-   Maintenance — Management / Configuration
-   Risk — Management / Configuration
-   Security — Management / Configuration

### Related articles on this site

-   [NIST 800-171 3.4.1 Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.](https://support.icompaas.com/support/solutions/articles/62000229280-nist-800-171-3-4-1-establish-and-maintain-baseline-configurations-and-inventories-of-organizational-s)
-   [CMMC 2.0 CM.2.061 Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.](https://support.icompaas.com/support/solutions/articles/62000229465-cmmc-2-0-cm-2-061-establish-and-maintain-baseline-configurations-and-inventories-of-organizational-sy)
-   [Ensure IAM password policy requires at least one uppercase letter](https://support.icompaas.com/support/solutions/articles/62000080729-ensure-iam-password-policy-requires-at-least-one-uppercase-letter)
-   [Ensure IAM password policy requires minimum length of 14 or greater](https://support.icompaas.com/support/solutions/articles/62000080817-ensure-iam-password-policy-requires-minimum-length-of-14-or-greater)

## Related compliance guidance

- [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): The CUI requirements CMMC Level 2 assesses, the SPRS score, POA&M rules and the phased DFARS rollout.
- [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): The federal catalogue 800-171 is derived from — useful when a contract also cites a FedRAMP baseline.