This record is generated by AI from the cited source. How AI is used
Treasure Data will drop support for TLS 1.0/1.1 on customer-facing endpoints effective February 28, 2026, requiring TLS 1.2 or higher.
- Platform
- Treasure AI
- Capability
- Security & certifications · Governance
- Vendor's name
- Deprecation of TLS 1.0/1.1
- First recorded
- Record last updated
Record dates describe acquisition and updates, not human review. About corrections.
Lifecycle history 1 state
- Deprecation announcedFeb 2026 Ends 28 Feb 2026 · End date passed · removal not confirmed in the recordFirst recorded 28 Sep 2026 · recorded from the source history · vendor release notes · docs.treasure.ai ↗ · archived copy, 4 Oct 2026 ↗
Something wrong or out of date in this record? , ideally with a link to better evidence. How corrections work
Security & certifications on other platforms latest first
- Adobe AEPVirtual-network allowlisting for Azure Event Hubs sourceDeprecation announced27 Oct 2026
- TealiumSalesforce connector Tealium-provided authenticationDeprecation announced7 Oct 2026
- HubSpotMinimum TLS 1.2 for HubSpot-hosted domainsAnnounced6 Oct 2026
- HubSpotPasskey-only login enforcementGAOct 2026
- TealiumApache Kafka connector SCRAM-SHA-512 authenticationGA23 Sep 2026
- Adobe AEPServer-side encryption for Amazon S3 sourceGA22 Sep 2026
- TealiumSalesforce connector OAuth Client Credentials authenticationGA9 Sep 2026
- SFMC EngagementMFA requirement for single sign-on accountsAnnouncedSep 2026
- SFMC EngagementAccount security posture dashboardGASep 2026
- SFMC EngagementData Extension access logging in Advanced Audit TrailGASep 2026
All Security & certifications changes →
More from Treasure AI in Security & certifications
- Per-chat isolated sandbox environmentGA12 Aug 2026
- Premium audit log events for Composable Audience StudioGA10 Jun 2026
- API key expiration policyGA27 May 2026
- Weak cipher suite deprecation in TLS 1.2Deprecation announced23 Apr 2026