Information for Cisco Meraki for Government users

Overview 

Cisco Meraki is investing significant resources into launching “Cisco Meraki for Government” to provide Meraki services to US Federal agencies, US government contractors, and critical infrastructure customers. We have received our Agency Authorization to Operate (ATO) under the Federal Risk and Authorization Management Program (FedRAMP) and are currently designated as “In PMO Review.” This is a requirement for any cloud service provider to operate a service for the US Federal Government to use. 

This document will cover key technical information for customers looking to get started with the Meraki for Gov service or migrate their existing Meraki networks. 

Creating Organizations in Cisco Meraki for Government 

Cisco Meraki for Government dashboard is currently live at dashboard.gov-meraki.com. Users can create an account at Cisco Meraki for Government on this page. You can find step by step instruction on Creating a Dashboard Account and Organization in Cisco Meraki for Government.

Supported Meraki Devices

The following lists out the hardware devices supported by the Cisco Meraki for Government service 

* MS120 has limited TAA Compliance
** MX67C-HW-WW & MX68CW-HW-WW devices are not supported at this time
*** CW9166D1 & CW9163E devices are not supported at this time. Pending MR30 firmware FIPS 140 Compliance letter

In order for certain features to work as expected, the following minimum product firmware versions should be used for nodes hosted in Cisco Meraki for Government:

• The Cisco Meraki for Government service requires FIPS encryption therefore all devices will need to be running at least the minimum version with FIPS enabled device-to-cloud connectivity. You can find them under “Certifications” on the following link https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Meraki_Device_to_Cloud_Connectivity_-_FIPS

When migrating devices below the minimum version you will see a delay in time required for the device to check in. The device will reach out to the Cisco Meraki for Government service, try to connect, and will be redirected to upgrade their firmware to a newer version. During this time, the device will not be providing any data to Dashboard and will appear offline. This can take upwards of 20 minutes. If the device does not connect by then please reach out to Meraki support.

Upcoming features in the Cisco Meraki for Government

• MX & MR Advanced licensing features, SDW+ (MI)

• SMS Two-Factor Authentication
   

  Unsupported Features 

  NOTE The following features are not supported for devices that are configured in the Cisco Meraki for Government Cloud service : 

• SM

• MV

• MI

• MT

• MX & MR Advanced Licensing

• SIG-Connector

• HTTP proxy for cloud communication

• Configuration fetch using HTTP (devices must use HTTPS for configuration fetch)

Note that these services are subject to change

Firewall Requirements for Cloud Connectivity

Please note that the standard firewall allow list requirements for cloud connectivity are different for Cisco Meraki for Government. The requirements for Cisco Meraki for Government connectivity can be found on the Firewall info page.

For the tests that monitor the connectivity status of MX Appliances in Cisco Meraki for Government, you can simply grant ICMP access to the IP addresses of our test servers. You no longer need to use Google’s 8.8.8.8 as a test destination.

API Endpoints and Considerations

For the Cisco Meraki for government environment, use api.gov-meraki.com as the end point URL.

How to contact Support and Open a case

FAQ