> Source: https://docs.nometa.az/v4.8.0/device-panels/fmc

# Cisco FMC

SAMURAI Networks reads Cisco FMC for everything it manages across the FTD fleet: registered devices, access-control and NAT policy, network and service objects, and site-to-site VPN.

> Open a device from the **Devices** page or the sidebar to reach these tabs.

## Devices

FTD devices registered to this FMC, with health and software version.

![Devices](https://docs.nometa.az/img/05-device-panels/fmc/fmc-01-devices.webp)

## Access Policies

Access-control policy and its rules.

![Access Policies](https://docs.nometa.az/img/05-device-panels/fmc/fmc-02-access-policies.webp)

## NAT

NAT rules with the original and translated packet side by side: zones, addresses, and dynamic or static translations down to the egress interface. A row expands to the full original-versus-translated breakdown.

![NAT](https://docs.nometa.az/img/05-device-panels/fmc/fmc-03-nat.webp)

## Objects

Network, host and service objects, resolved to their values.

![Objects](https://docs.nometa.az/img/05-device-panels/fmc/fmc-04-objects.webp)

## S2S VPN

Site-to-site VPN topologies and their endpoints.

![S2S VPN](https://docs.nometa.az/img/05-device-panels/fmc/fmc-05-s2s-vpn.webp)

## Changes

Configuration changes for this device, grouped by sync on a timeline. Added, removed and reordered rules render as structured cards (source and destination zones, addresses, applications and services laid out like the rule itself), each attributed to the responsible admin and access method where audit data is available. **Compare** diffs any two snapshots, and **Analyze with AI** explains a change in place when an AI provider is configured.

![Changes](https://docs.nometa.az/img/05-device-panels/fmc/fmc-07-changes.webp)