CuraDevOps

tag: Aws-Security-Hub · 3 items

2026-10-02 · AWS What's New · source ↗ #aws-security-hub#guardduty#billing
  • Platform/SRE — Skip
  • CI/CD — Skip
  • Leader — Learn: AWS is consolidating GuardDuty Runtime Monitoring charges under Security Hub rather than billing them separately; no cost change is implied, but budget owners should verify Cost Explorer dashboards and alerts still reflect accurate Security Hub spend after the line-item restructuring.
  • Platform/SRE — Plan: New GA capability worth evaluating this quarter: remediation plans surface root-cause groupings with Terraform and CloudFormation fix examples, making it practical to reduce Security Hub noise and address misconfigurations at the source rather than per-finding.
  • CI/CD — Skip
  • Leader — Learn: Security Hub’s new prioritized remediation plans expand AWS’s native security posture tooling at no extra cost — worth tracking as it may influence how teams standardize on AWS-native vs. third-party CSPM solutions.
  • Platform/SRE — Plan: New GA capability that auto-discovers AI workloads (Bedrock, SageMaker, EC2, ECR) via Config, Inspector SBOM, and GuardDuty DNS telemetry — worth enabling this quarter for teams running AI workloads to close the visibility gap before it becomes a compliance issue.
  • CI/CD — Skip
  • Leader — Learn: Signals that AWS is building central AI governance tooling; relevant for leaders setting security standards around AI deployments, but no forced decision or pricing change — shapes thinking on AI risk posture policy rather than requiring action now.