# Ensure Consistency Between Running and On-Disk Configuration

- Source: https://support.icompaas.com/support/solutions/articles/62000234994-ensure-consistency-between-running-and-on-disk-configuration
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [CIS Amazon Linux 2 Benchmark v3.0.0](https://support.icompaas.com/support/solutions/62000112696) › [CIS Amazon Linux 2 Benchmarks](https://support.icompaas.com/support/solutions/folders/62000169265)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Profile Applicability: **• Level 2**

Description:  
 The running system configuration refers to the current active settings in memory, while the on-disk configuration refers to saved configuration files. Ensuring these are consistent prevents discrepancies that can cause unexpected behavior or security gaps.

Rationale:  
 Maintaining synchronization between running and saved configurations ensures system stability, security compliance, and predictable behavior after reboots.

Impact:  
 Pros:

-   Prevents configuration drift and security vulnerabilities.  
    
-   Ensures intended policies and settings persist.  
    

Cons:

-   Requires administrative diligence to maintain consistency.  
    
-   Misalignment may cause system instability or security risks.  
    

Default Value:  
 Systems may have differences due to unsaved changes or manual edits.

Pre-requisites:

-   Root or sudo privileges to audit, compare, and apply configuration changes.  
    

Remediation:

### Test Plan:

Using Linux command line:

1.  Compare running configuration with saved files:  
    
    -   For services, check current status and compare with config files (e.g., sshd, firewalld).  
        
    -   Use tools like diff or configuration management systems.
        

### Implementation Plan:

Using Linux command line:

1.  Save running configuration to disk using appropriate commands (e.g., service reload, systemctl daemon-reload).  
    
2.  Manually update configuration files to match running settings or vice versa.  
    
3.  Verify consistency by rechecking differences.  
    

### Backout Plan:

Using Linux command line:

1.  Restore previous configurations from backups if inconsistencies cause issues.  
    
2.  Document and monitor changes to prevent recurrence.  
    

References:

-   CIS Amazon Linux 2 Benchmark v3.0.0  
    
-   [NIST SP 800-53 Revision 5 - CM-6](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final#cm-6)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.