Skip to main content

📝 AWS DMS Migration Task Logging is not enabled 🟢

  • Contextual name: 📝 Migration Task Logging is not enabled 🟢
  • ID: /ce/ca/aws/dms/migration-task-logging
  • Located in: 📁 AWS DMS

Flags​

Our Metadata​

  • Policy Type: COMPLIANCE_POLICY
  • Policy Category:
    • SECURITY

Similar Policies​

Logic​

Description​

Open File

Description​

This policy checks that AWS DMS Replication Tasks have CloudWatch logging enabled for key replication components. It verifies that the following components are configured to emit logs at the default severity level or higher:

  • TARGET_APPLY – Data and DDL statements applied to the target database.
  • TARGET_LOAD – Data batches being loaded into the target database.
  • SOURCE_CAPTURE – Change data capture (CDC) records sourced from the origin database or service and handed off to the DMS sorter.
  • SOURCE_UNLOAD – Data extracted from the source database during full-load operations.

DMS supports the following log severity levels, each inclusive of messages from all lower tiers:

  • LOGGER_SEVERITY_ERROR – Only error events.
  • LOGGER_SEVERITY_WARNING – Warnings and error events.
  • LOGGER_SEVERITY_INFO – Informational, warning, and error events.
  • LOGGER_SEVERITY_DEFAULT – Default informational, warning, and error events (equivalent to INFO).
  • LOGGER_SEVERITY_DEBUG – Debug, informational, warning, and error events.

... see more

Remediation​

Open File

Remediation​

From Command Line​

To enable CloudWatch logging for all key components on an existing AWS DMS Replication Task, use the AWS CLI’s modify-replication-task command with an updated Settings JSON payload.

Retrieve the current task settings​
aws dms describe-replication-tasks \
  --filters Name=replication-task-arn,Values={{replication-task-arn}} \
  --query "ReplicationTasks[0].ReplicationTaskSettings" \
  --output json > {{current-settings}}.json
Update settings to include Logging​
{
  "Logging": {
    "EnableLogging": true,
    "LogComponents": [
      {
        "Component": "TARGET_LOAD",
        "Severity": "LOGGER_SEVERITY_DEFAULT"
      },
      {
        "Component": "TARGET_APPLY",
        "Severity": "LOGGER_SEVERITY_DEFAULT"
      },
      {
        "Component": "SOURCE_CAPTURE",
        "Severity": "LOGGER_SEVERITY_DEFAULT"
      },
      {
        "Component": "SOURCE_UNLOAD",
        "Severity": "LOGGER_SEVERITY_DEFAULT"
      }
    ]
  }
}
Apply the modified settings immediately​
aws dms modify-replication-task \

... [see more](remediation.md)

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlags
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [DMS.7] DMS replication tasks for the target database should have logging enabled1
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [DMS.8] DMS replication tasks for the source database should have logging enabled1
💼 Cloudaware Framework → 💼 Logging and Monitoring Configuration53
💼 FedRAMP High Security Controls → 💼 AC-2(4) Automated Audit Actions (M)(H)116
💼 FedRAMP High Security Controls → 💼 AC-6(9) Log Use of Privileged Functions (M)(H)726
💼 FedRAMP High Security Controls → 💼 AU-2 Event Logging (L)(M)(H)17
💼 FedRAMP High Security Controls → 💼 AU-3 Content of Audit Records (L)(M)(H)128
💼 FedRAMP High Security Controls → 💼 AU-6(3) Correlate Audit Record Repositories (M)(H)8
💼 FedRAMP High Security Controls → 💼 AU-6(4) Central Review and Analysis (H)8
💼 FedRAMP High Security Controls → 💼 AU-10 Non-repudiation (H)7
💼 FedRAMP High Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)265
💼 FedRAMP High Security Controls → 💼 CA-7 Continuous Monitoring (L)(M)(H)210
💼 FedRAMP High Security Controls → 💼 SI-4(20) Privileged Users (H)4851
💼 FedRAMP Low Security Controls → 💼 AU-2 Event Logging (L)(M)(H)17
💼 FedRAMP Low Security Controls → 💼 AU-3 Content of Audit Records (L)(M)(H)14
💼 FedRAMP Low Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)65
💼 FedRAMP Low Security Controls → 💼 CA-7 Continuous Monitoring (L)(M)(H)110
💼 FedRAMP Moderate Security Controls → 💼 AC-2(4) Automated Audit Actions (M)(H)16
💼 FedRAMP Moderate Security Controls → 💼 AC-6(9) Log Use of Privileged Functions (M)(H)26
💼 FedRAMP Moderate Security Controls → 💼 AU-2 Event Logging (L)(M)(H)17
💼 FedRAMP Moderate Security Controls → 💼 AU-3 Content of Audit Records (L)(M)(H)128
💼 FedRAMP Moderate Security Controls → 💼 AU-6(3) Correlate Audit Record Repositories (M)(H)8
💼 FedRAMP Moderate Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)65
💼 FedRAMP Moderate Security Controls → 💼 CA-7 Continuous Monitoring (L)(M)(H)210
💼 NIST CSF v2.0 → 💼 DE.AE-02: Potentially adverse events are analyzed to better understand associated activities31
💼 NIST CSF v2.0 → 💼 DE.AE-03: Information is correlated from multiple sources46
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events114
💼 NIST CSF v2.0 → 💼 DE.CM-02: The physical environment is monitored to find potentially adverse events10
💼 NIST CSF v2.0 → 💼 DE.CM-03: Personnel activity and technology usage are monitored to find potentially adverse events81
💼 NIST CSF v2.0 → 💼 DE.CM-06: External service provider activities and services are monitored to find potentially adverse events31
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events133
💼 NIST CSF v2.0 → 💼 ID.IM-01: Improvements are identified from evaluations20
💼 NIST CSF v2.0 → 💼 ID.IM-02: Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties33
💼 NIST CSF v2.0 → 💼 ID.IM-03: Improvements are identified from execution of operational processes, procedures, and activities34
💼 NIST CSF v2.0 → 💼 ID.RA-01: Vulnerabilities in assets are identified, validated, and recorded26
💼 NIST CSF v2.0 → 💼 ID.RA-07: Changes and exceptions are managed, assessed for risk impact, recorded, and tracked28
💼 NIST SP 800-53 Revision 5 → 💼 AC-2(4) Account Management _ Automated Audit Actions1316
💼 NIST SP 800-53 Revision 5 → 💼 AC-4(26) Information Flow Enforcement _ Audit Filtering Actions9
💼 NIST SP 800-53 Revision 5 → 💼 AC-6(9) Least Privilege _ Log Use of Privileged Functions1719
💼 NIST SP 800-53 Revision 5 → 💼 AU-2 Event Logging417
💼 NIST SP 800-53 Revision 5 → 💼 AU-3 Content of Audit Records31328
💼 NIST SP 800-53 Revision 5 → 💼 AU-6(3) Audit Record Review, Analysis, and Reporting _ Correlate Audit Record Repositories8
💼 NIST SP 800-53 Revision 5 → 💼 AU-6(4) Audit Record Review, Analysis, and Reporting _ Central Review and Analysis8
💼 NIST SP 800-53 Revision 5 → 💼 AU-10 Non-repudiation57
💼 NIST SP 800-53 Revision 5 → 💼 AU-12 Audit Record Generation44765
💼 NIST SP 800-53 Revision 5 → 💼 CA-7 Continuous Monitoring610
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(9) Boundary Protection _ Restrict Threatening Outgoing Communications Traffic11
💼 NIST SP 800-53 Revision 5 → 💼 SI-3(8) Malicious Code Protection _ Detect Unauthorized Commands5
💼 NIST SP 800-53 Revision 5 → 💼 SI-4(20) System Monitoring _ Privileged Users5
💼 NIST SP 800-53 Revision 5 → 💼 SI-7(8) Software, Firmware, and Information Integrity _ Auditing Capability for Significant Events8
💼 PCI DSS v3.2.1 → 💼 10.6.2 Review logs of all other system components periodically based on the organization's policies and risk management strategy, as determined by the organization's annual risk assessment.5
💼 PCI DSS v4.0.1 → 💼 10.4.2 Logs of all other system components are reviewed periodically.15
💼 PCI DSS v4.0 → 💼 10.4.2 Logs of all other system components are reviewed periodically.15