Detection: Config Configuration Recorder Stopped
Overview
Detect when an AWS Config configuration recorder was stopped. When recording is stopped, resource configuration changes are no longer captured, creating gaps in monitoring and compliance enforcement. Monitoring the recording status ensures continuous tracking of configuration changes and adherence to defined policies.
References:
Usage
Run the detection in your terminal:
powerpipe detection run aws_cloudtrail_log_detections.detection.config_configuration_recorder_stoppedSnapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe detection run aws_cloudtrail_log_detections.detection.config_configuration_recorder_stopped --shareSQL
This detection uses a named query:
select tp_timestamp as timestamp,string_split(event_source, '.')[1] || ':' || event_name as operation,request_parameters ->> 'configurationRecorderName' as resource,user_identity.arn as actor,tp_source_ip as source_ip,tp_index as account_id,aws_region as region,tp_id as source_id,*
from aws_cloudtrail_logwhere event_source = 'config.amazonaws.com' and event_name = 'StopConfigurationRecorder' and error_code is null
order by event_time desc;