Starting February 26th, 2026, the CMS Hybrid Cloud Team will begin the Q1 2026 CMS Enterprise Security Campaign.

Any findings will be tracked via Jira tickets and assigned to the respective teams to remediate risks. The Q1 CMS Enterprise Security Campaign is targeting a list of 74 Critical Common Vulnerabilities and Exposures (CVEs) that pose a high risk to CMS systems.

On March 10th, 2026, new AWS Security Hub Cloud Security Posture Management (CSPM) Guard Rails will be added to all accounts to prevent reintroduction of certain findings back into the CMS environment.

Benefits

Resolving findings in customers' Jira tickets ensures CMS systems remain secure. Participating in proactive, routine security activities, such as this CMS Enterprise Security Campaign, reduces the risk of unauthorized and/or malicious activity.

The CMS Enterprise Security Campaign will target and identify the following vulnerabilities and CVEs:

Targeted Vulnerabilities and Common Vulnerabilities and Exposures (CVEs)

Note: Operating System (OS)-level findings are remediated by the CMS Hybrid Cloud Team for customers who receive regular CMS Gold Image patching services. Please note that CMS customers are responsible for patching any software installed on top of the provided CMS Gold Image.

• CMS Hybrid Cloud will deploy auto-remediation for the following Security Hub controls:
  • GuardRails / auto-remediations (Security Hub controls):
    • RDS.1 - RDS snapshot should be private (all accounts)
    • DynamoDB.2 - DynamoDB tables should have point-in-time recovery enabled (all accounts)
    • EC2.15 - Amazon EC2 subnets should not automatically assign public IP addresses (for Marketplace accounts to catch up from 2025 Q4)
  • CMS customer teams with existing findings for these Security Hub controls will receive a Jira ticket.
    • Teams will either need to resolve the finding or obtain an exemption.

Expected Actions

• CMS customers with findings will receive a Jira ticket.
  • If you would like to obtain an exemption, you will need to complete an attestation.
• CMS customers should resolve all received Jira tickets as soon as possible.
  • For help, please refer to the "Questions or Concerns" section below for instructions on how to submit a Hybrid Cloud Support ticket.
• Failure to resolve findings can lead to compromised systems that result in greater risks for unauthorized and/or malicious activity.
• Unresolved system flaws will result in Plan of Action and Milestones (POA&Ms) being issued against the Federal Information Security Modernization Act (FISMA) boundary.

Timeline

• February 26th, 2026: CMS customers with findings will receive Jira tickets for the findings noted in the "Benefits" section above.
• March 10th, 2026: CMS Hybrid Cloud will add new AWS Security Hub Cloud Security Posture Management (CSPM) GuardRails to all accounts to protect CMS systems from reintroducing findings back into the environment.

Additional Information

• Learn about Security Hub Campaigns
• Exemption Policy Guide

Questions or Concerns

We look forward to helping you and your team. Reach out to your IUSG Hosting Coordinator with any questions. For further help, please fill out a Hybrid Cloud Support ticket specifying Service as "Security Hub" and Request as "Security Hub Findings".