Back

Audit the configuration of organizational assets, as necessary.


CONTROL ID
13653
CONTROL TYPE
Audits and Risk Management
CLASSIFICATION
Detective

SUPPORTING AND SUPPORTED CONTROLS




This Control directly supports the implied Control(s):
  • System hardening through configuration management, CC ID: 00860

This Control has the following implementation support Control(s):
  • Audit assets after maintenance was performed., CC ID: 13657


SELECTED AUTHORITY DOCUMENTS COMPLIED WITH




  • Periodically auditing the access device configurations and patch levels (Critical components of information security 25) iii.f., Guidelines on Information Security, Electronic Banking, Technology Risk Management and Cyber Frauds)
  • Banks should ensure that each wireless device connected to the network matches an authorized configuration and security profile, with a documented owner of the connection and a defined business need. Organizations should deny access to those wireless devices that do not have such a configuration and… (Critical components of information security 28) iv., Guidelines on Information Security, Electronic Banking, Technology Risk Management and Cyber Frauds)
  • The FI should review and verify the configuration information of its hardware and software on a regular basis to ensure it is accurate and up-to-date. (§ 7.2.2, Technology Risk Management Guidelines, January 2021)
  • Review configuration settings regularly to ensure they correspond to current requirements. (Annex A1: Computer Network Security 34, Singapore(PDPC) Guide to Securing Personal Data in Electronic Medium, Revised 20 January 2017)
  • Content filters deployed in a CDS are subject to rigorous security assessment to ensure they mitigate content-based threats and cannot be bypassed. (Security Control: 1524; Revision: 1, Australian Government Information Security Manual)
  • configuration management controls to ensure that the configuration minimises vulnerabilities and is defined, assessed, registered and maintained; (¶ 54(b), The AD_offical_Name should be: APRA Prudential Practice Guide 234: Management of security risk in information and information technology, May 2013)
  • Implement internal control, security and auditability measures during configuration, integration and maintenance of hardware and infrastructural software to protect resources and ensure availability and integrity. Responsibilities for using sensitive infrastructure components should be clearly defin… (AI3.2 Infrastructure Resource Protection and Availability, CobiT, Version 4.1)
  • Be applied when new systems are configured and verified as in place before or immediately after a system component is connected to a production environment. (2.2.1 Bullet 5, Payment Card Industry Data Security Standard Requirements and Testing Procedures, Defined Approach Requirements, Version 4.0)
  • Examine configuration settings and interview personnel to verify that system configuration standards are applied when new systems are configured and verified as being in place before or immediately after a system component is connected to a production environment. (2.2.1.c, Payment Card Industry Data Security Standard Requirements and Testing Procedures, Defined Approach Testing Procedures, Version 4.0)
  • Be applied when new systems are configured and verified as in place before or immediately after a system component is connected to a production environment. (2.2.1 Bullet 5, Self-Assessment Questionnaire A-EP and Attestation of Compliance for use with PCI DSS Version 4.0)
  • Be applied when new systems are configured and verified as in place before or immediately after a system component is connected to a production environment. (2.2.1 Bullet 5, Self-Assessment Questionnaire C and Attestation of Compliance for use with PCI DSS Version 4.0)
  • Be applied when new systems are configured and verified as in place before or immediately after a system component is connected to a production environment. (2.2.1 Bullet 5, Self-Assessment Questionnaire D for Merchants and Attestation of Compliance for use with PCI DSS Version 4.0)
  • Be applied when new systems are configured and verified as in place before or immediately after a system component is connected to a production environment. (2.2.1 Bullet 5, Self-Assessment Questionnaire D for Service Providers and Attestation of Compliance for use with PCI DSS Version 4.0)
  • CIs shall be controlled. Changes to CIs shall be traceable and auditable to maintain the integrity of the configuration information. The configuration information shall be updated following the deployment of changes to CIs. (§ 8.2.6 ¶ 3, ISO/IEC 20000-1:2018, Information technology — Service management —Part 1: Service management system requirements, Third Edition)
  • review of documented information (including computer logs and configuration data); (§ 6.4.7.2 a), ISO/IEC 27007:2020, Information security, cybersecurity and privacy protection — Guidelines for information security management systems auditing, Third Edition)
  • Audits and reviews activities associated with configuration-controlled changes to the information system; and (CM-3f., StateRAMP Security Controls Baseline Summary Category 2, Version 1.1)
  • Audits and reviews activities associated with configuration-controlled changes to the information system; and (CM-3f., StateRAMP Security Controls Baseline Summary Category 3, Version 1.1)
  • Audits and reviews activities associated with configuration-controlled changes to the information system; and (CM-3f., StateRAMP Security Controls Baseline Summary High Sensitivity Level, Version 1.1)
  • Generally, IT processing is inherently consistent; therefore, the service auditor may be able to limit the testing to one or a few instances of the control operation. An automated control usually functions consistently unless the program, including the tables, files, or other permanent data used by … (¶ 3.138, Reporting on Controls at a Service Organization: Relevant to Security, Availability, Processing Integrity, Confidentiality, or Privacy (SOC2), current as of January 1, 2018)
  • Server security configuration parameters may be scanned and analyzed for consistency with policy. (¶ 3.117 Bullet 3, Reporting on Controls at a Service Organization: Relevant to Security, Availability, Processing Integrity, Confidentiality, or Privacy (SOC2), current as of January 1, 2018)
  • Regularly assesses and documents compliance with the entity's baseline configuration. (App A Objective 13:3d, FFIEC Information Technology Examination Handbook - Architecture, Infrastructure, and Operations, June 2021)
  • Audits and reviews activities associated with configuration-controlled changes to the information system; and (CM-3f. High Baseline Controls, FedRAMP Baseline Security Controls, 8/28/2018)
  • Audits and reviews activities associated with configuration-controlled changes to the information system; and (CM-3f. Moderate Baseline Controls, FedRAMP Baseline Security Controls, 8/28/2018)
  • Monitor and review activities associated with configuration-controlled changes to the system; and (CM-3f., Control Baselines for Information Systems and Organizations, NIST SP 800-53B, High Impact Baseline, October 2020)
  • Monitor and review activities associated with configuration-controlled changes to the system; and (CM-3f., Control Baselines for Information Systems and Organizations, NIST SP 800-53B, Moderate Impact Baseline, October 2020)
  • Monitor and review activities associated with configuration-controlled changes to the system; and (CM-3f., Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, NIST Special Publication 800-161, Revision 1, Appendix A, C-SCRM Level 3 Controls)
  • Audits and reviews activities associated with configuration-controlled changes to the information system; and (CM-3f. Moderate Baseline Controls, Guide to Industrial Control Systems (ICS) Security, Revision 2)
  • Audits and reviews activities associated with configuration-controlled changes to the information system; and (CM-3f. High Baseline Controls, Guide to Industrial Control Systems (ICS) Security, Revision 2)
  • The security controls present during system validation testing (e.g., factory acceptance testing and site acceptance testing) are still installed and operating correctly in the production system. (§ 6.2.3 ICS-specific Recommendations and Guidance ¶ 1 Bullet 1, Guide to Industrial Control Systems (ICS) Security, Revision 2)
  • Perform Windows registry analysis. (T0397, Reference Spreadsheet for the Workforce Framework for Cybersecurity (NICE Framework)”, July 7, 2020)
  • Audits and reviews activities associated with configuration-controlled changes to the information system; and (CM-3f., Security and Privacy Controls for Federal Information Systems and Organizations, NIST SP 800-53, High Impact Baseline, Revision 4)
  • Audits and reviews activities associated with configuration-controlled changes to the information system; and (CM-3f., Security and Privacy Controls for Federal Information Systems and Organizations, NIST SP 800-53, Moderate Impact Baseline, Revision 4)
  • Audits and reviews activities associated with configuration-controlled changes to the information system; and (CM-3f., Security and Privacy Controls for Federal Information Systems and Organizations, NIST SP 800-53, Revision 4)
  • Monitor and review activities associated with configuration-controlled changes to the system; and (CM-3f., Security and Privacy Controls for Information Systems and Organizations, NIST SP 800-53, Revision 5)
  • Audits and reviews activities associated with configuration-controlled changes to the information system; and (CM-3f., Supply Chain Risk Management Practices for Federal Information Systems and Organizations, NIST Special Publication 800-161, April 2015)
  • Audits and reviews activities associated with configuration-controlled changes to the information system; and (CM-3f., TX-RAMP Security Controls Baseline Level 2)