This record is generated by AI from the cited source. How AI is used
IP allowlisting for server-to-server Data API requests, rejecting unlisted IPs even with a valid key, with per-rule audit and call-count tracking.
- Platform
- MoEngage
- Capability
- Security & certifications · Governance also: APIs & extensibility
- Vendor's name
- API Firewall
- First recorded
- Record last updated
Record dates describe acquisition and updates, not human review. About corrections.
Lifecycle history 1 state
- GAJul 2026First recorded 28 Sep 2026 · recorded from the source history · vendor release notes · moengage.com ↗ · archived copy, 26 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 MoEngage in Security & certifications
- PGP encryption for message archivalGAAug 2026