tag: Encryption · 4 items
- Platform/SRE — Plan: MSK Provisioned clusters now support TLS 1.3 as a GA opt-in via named security policies — evaluate applying a TLS 1.3-capable policy this quarter, particularly if your org has compliance frameworks requiring TLS 1.3 or if post-quantum readiness is on the roadmap.
- CI/CD — Skip
- Leader — Learn: MSK’s new TLS 1.3 support is a step toward post-quantum cryptography readiness and aligns with tightening compliance standards; no strategic or licensing decision is forced, but worth knowing if your security policy roadmap includes post-quantum preparedness.
- 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 — Plan: If you run Lambda durable functions in regulated industries, schedule adoption of CMK encryption to meet data governance requirements — no deadline, but this is a concrete security posture change worth queuing this quarter.
- CI/CD — Skip
- Leader — Learn: Lambda durable functions now offers CMK support, closing a compliance gap for financial services and healthcare workloads; relevant context if evaluating serverless for regulated data.
- Platform/SRE — Plan: A new GA security capability for AKS clusters using Azure Files NFS v4.1 volumes via the CSI driver — worth evaluating this quarter for workloads with data-in-transit compliance requirements. Review existing PersistentVolume configurations and enable EiT where encryption mandates apply.
- CI/CD — Skip
- Leader — Learn: This GA feature expands available encryption controls on AKS-backed storage, which may inform security standards or compliance posture for teams running NFS workloads on Azure, but no strategic decision is forced.
- Signals: GA announcement