Rule ID
SV-288236r1252938_rule
Version
V1R0.1
CCIs
Unauthorized changes to the baseline configuration could make the system vulnerable to various attacks or allow unauthorized access to the system. Changes to information system configurations can have unintended side effects, some of which may be relevant to security. Detecting such changes and providing an automated response can help avoid unintended, negative consequences that could ultimately affect the security state of the application. Examples of security responses include, but are not limited to the following: halting application processing; halting selected application functions; or issuing alerts/notifications to organizational personnel when there is an unauthorized modification of a configuration item. This requirement pertains to Configuration Management and Infrastructure as Code (IaC) types of applications, and can otherwise be considered Not Applicable.
Review the application documentation and deployed configuration to determine whether the application's alerting mechanism notifies the ISSO/ISSM, and rolls back the unauthorized change, when baseline configurations are changed in an unauthorized manner. If the application's alerting mechanism does not notify the ISSO/ISSM, and rolls back the unauthorized change, when baseline configurations are changed in an unauthorized manner, this is a finding.
Navigate to the alerting function configuration within the application. Configure the application's alerting mechanism to notify the ISSO/ISSM and undo the unauthorized change when baseline configurations are changed in an unauthorized manner.