tag: Compliance · 9 items
- Platform/SRE — Plan: GA hardware-level audit logging for Azure Cloud HSM is a concrete compliance and forensic capability; orgs using HSM for key management should schedule enablement and integrate log feeds into their SIEM/observability pipeline this quarter.
- CI/CD — Skip
- Leader — Learn: Informs compliance posture for regulated environments relying on Azure Cloud HSM, but introduces no licensing, pricing, or vendor-risk change that requires a leadership decision now.
- Signals: GA announcement
- Platform/SRE — Learn: Shapes how platform engineers think about structuring compliance evidence and control ownership on shared Kubernetes infrastructure, particularly for teams operating in EU-regulated environments — no operational change required today.
- CI/CD — Skip
- Leader — Learn: Useful framing for leaders clarifying accountability boundaries between platform and application teams under EU regulatory mandates, but contains no new deadlines or decisions — organizational context only.
- Platform/SRE — Plan: If ‘record all resource types’ is enabled, these 77 types—including EC2, GuardDuty, Inspector, and S3—will be tracked automatically, which quietly expands coverage and may increase Config costs. Review the new type list against your compliance rules and cost baseline this quarter.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Learn: New opt-in encryption option for Transcribe custom vocabularies and models; relevant if you operate Transcribe-based workloads with compliance requirements around key ownership, but no action required unless you need BYOK for audit or regulatory reasons.
- CI/CD — Skip
- Leader — Learn: If the org uses Transcribe custom resources in regulated environments, this new BYOK option could satisfy compliance or data-sovereignty requirements worth flagging to security/compliance stakeholders.
- Platform/SRE — Learn: Pre-written compliance policies in HCP Terraform could simplify governance guardrails for teams using the managed service; worth evaluating for adoption but no operational urgency.
- CI/CD — Skip
- Leader — Plan: If the org uses HCP Terraform, evaluate whether native pre-written policy sets can replace or augment custom Sentinel/OPA work to reduce compliance overhead — schedule a review this quarter.
- Platform/SRE — Plan: New GA S3 Object Lock capability lets you anchor WORM retention to a future event (contract close, audit complete) rather than a fixed date — relevant for platform teams managing compliant storage under SEC 17a-4(f), FINRA 4511, or CFTC 1.31. Evaluate updating your S3 bucket policies and IAM condition keys to adopt event holds for regulated data this quarter.
- CI/CD — Skip
- Leader — Learn: If the org operates in regulated industries, this Cohasset-assessed S3 capability closes a gap in event-driven retention compliance at no additional cost — useful context for understanding your AWS compliance posture, but no strategic decision or budget action required.
- Platform/SRE — Plan: New GA Config coverage for resources platform teams commonly operate — EKS::PodIdentityAssociation, RDS::DBProxy, EC2 route servers, and Organizations::Policy — is worth enabling in your Config recording and aggregator configuration this quarter to close compliance gaps. No deadline, but teams already using Config for compliance should audit which of the 60 new types overlap with their environment.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Learn: New audit log events for GitHub Code Quality enablement changes give CI/CD teams better visibility into who toggled code quality settings on repos, useful for compliance or troubleshooting.
- Leader — Learn: Audit trail for Code Quality configuration changes improves governance posture; worth noting if your org is building compliance evidence around code scanning enablement.
- Platform/SRE — Learn: IAM Identity Center can now be used for FedRAMP Class C workloads in four US regions — relevant if you operate in a federal or regulated environment, but no action required for non-FedRAMP shops.
- CI/CD — Skip
- Leader — Learn: Broadens the compliance posture of a core AWS identity service; worth noting for organizations pursuing or maintaining FedRAMP authorization, but no strategic decision is forced without an active compliance program in scope.