Meraki Dashboard URL Update - PCI Compliance
Click 日本語 for Japanese
Overview
Cisco Meraki is enhancing its network infrastructure to comply with Payment Card Industry (PCI) standards and improve data protection. PCI DSS 4.0 requires a Web Application Firewall (WAF) for public-facing web applications, specifically under requirement 6.4.2, which mandates an automated solution to detect and prevent web-based attacks. For customers processing card payment data, the Meraki Dashboard must be PCI compliant because it stores network configurations. These customers also need Cisco’s PCI certification for their own compliance. This update includes changes to the Meraki dashboard URLs to meet these requirements
Impact
Some services accessed through the Meraki dashboard will begin using a new subdomain.
For example:
• Current URL: n23.meraki.com
• New URL: n23.dashboard.meraki.com
The updated “.dashboard.meraki.com” subdomain will become the new standard moving forward. The original URLs will remain supported and automatically redirect.
As part of this effort, Meraki services will adopt a new certificate chain. This chain should be trusted by modern browsers, but older browsers or systems may require updates to stay compatible.
Timeline
- New URL rollout: August 18, 2025
- The URL change will not impact any functionality or performance of the Meraki cloud platform.
Customer Action
Required Action
Most customers do not need to take any action. If the organization uses:
• URL filtering
• Domain allowlisting
Add the new dashboard.meraki.com subdomain to your allowlist by August 17, 2025, to prevent disruption of dashboard access from end-user devices on that network.
Additional Information
FAQ
- Will this change affect SAML logins?
- SAML URLs will remain the same and will not be affected by this change.
- Will this change affect API requests?
- API requests sent to api.meraki.com will not be impacted. However, if customers are sending API requests directly to shard hostnames—an action not officially supported after the introduction of API megaproxy—and their script cannot handle HTTP redirects, they will be impacted. Customers should use the officially supported API infrastructure and update their scripts to send API requests to api.meraki.com as per our documentation.