Skip to main content

CC7.1

CC7.1
To meet its objectives, the entity uses detection and monitoring procedures to identify (1) changes to configurations that result in the introduction of new vulnerabilities, and (2) susceptibilities to newly discovered vulnerabilities.
Category
Security
Subcategory
System Operations

Points of Focus​

Uses Defined Configuration Standards

The entity has defined configuration standards to be used for hardening systems.

Monitors Infrastructure and Software

The entity monitors infrastructure and software for noncompliance with the standards, which could threaten the achievement of the entity's objectives.

Implements Change-Detection Mechanisms

The IT system includes a change-detection mechanism (for example, file integrity monitoring tools) to alert personnel to unauthorized modifications of critical system files, configuration files, or content files.

Detects Unknown or Unauthorized Components

Procedures are in place to detect the introduction of unknown or unauthorized components.

Conducts Vulnerability Scans

The entity conducts infrastructure and software vulnerability scans designed to identify potential vulnerabilities or misconfigurations on a periodic basis and after significant changes are made to the environment. Action is taken to remediate identified deficiencies in a timely manner to support the achievement of the entity's objectives.

Evidence Requests​

Area of FocusArtifactDescription
Asset ManagementIT Asset Management (ITAM)Documented evidence of an IT Asset Management (ITAM) program that addresses the due diligence and due care activities associated with maintaining both secure and compliant systems, applications and services.
Asset ManagementConfiguration ManagementDocumented evidence of standardized configuration management practices.
Asset ManagementSecure Baseline Configurations ReviewsDocumented evidence of a review process to ensure Secure Baseline Configurations (SBC) are current and applicable (e.g., system configuration settings and associated documentation).
Asset ManagementSecure Baseline Configurations - Cloud-Based ServicesDocumented evidence of secure baseline configurations for all deployed types of cloud-based services or applications.
Asset ManagementSecure Baseline Configurations - DatabasesDocumented evidence of secure baseline configurations for all deployed types of databases.
Asset ManagementSecure Baseline Configurations - Embedded TechnologiesDocumented evidence of secure baseline configurations for all deployed types of embedded technologies.
Asset ManagementSecure Baseline Configurations - Major ApplicationsDocumented evidence of secure baseline configurations for all deployed types of major applications.
Asset ManagementSecure Baseline Configurations - Minor ApplicationsDocumented evidence of secure baseline configurations for all deployed types of minor applications.
Asset ManagementSecure Baseline Configurations - Mobile DevicesDocumented evidence of secure baseline configurations for all deployed types of mobile devices.
Asset ManagementSecure Baseline Configurations - Network DevicesDocumented evidence of secure baseline configurations for all deployed types of network devices.
Asset ManagementSecure Baseline Configurations - Server Class SystemsDocumented evidence of secure baseline configurations for all deployed types of server-class operating systems.
Asset ManagementSecure Baseline Configurations - Workstation Class SystemsDocumented evidence of secure baseline configurations for all deployed types of workstation-class operating systems.
Event Log MonitoringIntegrity MonitoringDocumented evidence of integrity monitoring, where files and/or configurations on critical systems, applications and/or services are actively monitored for changes that could indicate unauthorized changes.
Vulnerability ManagementVulnerability AssessmentsDocumented evidence of internal and external vulnerability assessment activities.

Policies​

Example Organization Controls​

  • CC7.1.1 - Management has defined configuration standards in the information security policies and procedures.
  • CC7.1.2 - Policies and procedures are in place regarding detection, logging, and monitoring of unknown or unauthorized components into the environment.
  • CC7.1.3 - The entity monitors key activities and alerts are generated when those activities are outside normal tolerances.
  • CC7.1.4 - Alerts are generated to those responsible for taking action.
  • CC7.1.7 - An independent third-party performs a penetration test annually to identify and exploit vulnerabilities identified within the environment. Security vulnerabilities that are detected are monitored through resolution.

Example Control Objectives​

  • Security configuration management - System configurations are managed according to defined security standards.

Example Control Implementations​

  • vulnerability-scanning - Continuous vulnerability scanning is implemented across the software supply chain. Implementation includes: - Dependabot and Renovate scan dependencies for vulnerabilities - Trivy scans container images before deployment - SonarQube performs static code analysis on every PR - Critical vulnerabilities addressed within 7 days per software development lifecycle (SDLC) Policy - High vulnerabilities addressed within 30 days - Annual third-party penetration testing

Example Evidence​

  • Penetration Test Report - Most recent third-party penetration test report and remediation evidence

Example Action Plans​

  • Annual penetration test - Annual penetration test by qualified third-party vendor to identify vulnerabilities in production systems. Required for System and Organization Controls 2 (SOC 2) compliance.
  • Dependency vulnerability remediation - Renovate and Dependabot have identified vulnerabilities requiring remediation within service level agreement (SLA) timeframes.

Example Remediations​

  • auth-service-cve-remediation - Update authentication service dependencies to patch CVE-2024-12345 privilege escalation vulnerability.