Meraki Dashboard URL Update - PCI Compliance
Click 日本語 for Japanese
Overview
As part of our ongoing commitment to security and compliance, Cisco Meraki is rolling out an enhancement to our network infrastructure in alignment with Payment Card Industry (PCI) standards and to further protect your data. PCI DSS 4.0 mandates the use of a Web Application Firewall (WAF) for public-facing web applications. This requirement, specifically PCI DSS 4.0 requirement 6.4.2, mandates an automated technical solution to detect and prevent web-based attacks. For Meraki customers in industries that process card payment data, the Meraki Dashboard is required to be PCI compliant because it stores the network configurations for those organizations. In addition, those customers require our PCI certification for their own certification. This change involves an update to Meraki dashboard URLs.
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
• Note: The URL change will not impact any functionality or performance of the Meraki cloud platform.
Customer Action
Required Action
Most customers will not need to take any action. However, if your organization uses:
• URL filtering
• Domain allowlisting
Please ensure the new dashboard.meraki.com subdomain is added to your allowlist by August 17, 2025 to avoid any disruption in dashboard access from end user devices in 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.