Integration · Topic 5 of 8
FMC Integration with ISE Using pxGrid
Learn how the FMC uses pxGrid to subscribe to Cisco ISE session data, how certificate trust is set up, and how identity and attributes feed access control.
- 4 min
- pxGrid lets the FMC subscribe to session data from ISE.
- ISE is the publisher, and the FMC is the subscriber.
- The data includes users, groups and ISE attributes such as security group tags.
What it is
pxGrid is a framework that lets security products share context, and the FMC uses it to learn from Cisco Identity Services Engine (ISE).
ISE knows who is on the network, on which device and with what access. The firewall can use that knowledge to write rules about users and groups instead of only about IP addresses.
In the pxGrid model, ISE is the publisher of session information, and the Secure Firewall Management Center (FMC) is a subscriber.
How it works
The FMC connects to ISE, they trust each other with certificates, and ISE then sends data.
What the FMC learns
When a user or device is authenticated, ISE has a session record that ties the IP address to the user, the device and other details. Through pxGrid, the FMC receives these records.
The data includes the user name and groups, and the address that the session uses. It can also include ISE attributes such as the security group tag, the endpoint device type and the endpoint profile.
The firewall can then use these in rules. Access control rules can match on users and groups, and on ISE attributes, which is much easier to read than a list of addresses.
Setting up the connection
The setup has three parts.
- ISE side. The pxGrid service has to be enabled on an ISE node. The FMC appears as a client, and ISE can either approve it automatically or wait for an administrator to approve it.
- Certificates. Each side needs to trust the certificate of the other. You import the ISE certificates into the FMC as trusted authorities, and you give the FMC a certificate that ISE trusts.
- FMC side. In the FMC identity source settings, you add the ISE server and give the pxGrid and monitoring node names, the trusted authorities and the FMC certificate. A test button checks the connection.
Name resolution and time must be right. Certificate problems and wrong time are the most common reasons for a failed connection.
Realms and identity policy
For user and group names to be useful, the FMC also needs a realm for the directory, such as Active Directory. ISE provides the session, and the realm provides the user and group list.
An identity policy can then use ISE as a passive source. The firewall learns the user without asking the user to log in again. You can see the user names in events once this is working.
What pxGrid can do besides identity
The subscription is not the only use of pxGrid. The FMC can also send an action to ISE, for example to quarantine an endpoint. That is covered in the Rapid Threat Containment page.
Troubleshooting
If no user data appears, check these points in order.
- Is the pxGrid service running on ISE, and is the FMC approved as a client?
- Do the certificates match, and is each side trusted by the other?
- Can the FMC resolve and reach the ISE host names?
- Are the clocks in step?
- Does the realm exist and is it downloading users and groups?
Benefits
Rules that use identity follow the user from one address to another. When a person moves to a new network or a new IP address, the rule still applies. Events also become easier to read, because they show names instead of addresses.
What to remember for the exam
Seven facts cover the usual questions.
- pxGrid lets the FMC subscribe to session data from ISE.
- ISE is the publisher, and the FMC is the subscriber.
- The data includes users, groups and ISE attributes such as security group tags.
- The two sides must trust each other's certificates.
- ISE can approve the FMC client automatically or manually.
- A realm for the directory supplies user and group lists.
- Access control rules can then match users, groups and ISE attributes.
When a question asks how a firewall rule can use ISE security group tags or user names without a captive portal, think of pxGrid.
Common mistakes
These four mistakes are common with pxGrid.
Missing certificate trust. The connection fails if either side does not trust the other.
Forgetting to approve the client. ISE may wait for manual approval of the FMC.
No realm. Without it the FMC has session data but no user and group lists.
Wrong time or DNS. Certificates fail and names do not resolve.
A pxGrid failure leaves rules with identity conditions without data. Test the connection and monitor it after any certificate change.
Check yourself
Work through these three questions.
Which product publishes session data and which one subscribes?
ISE publishes the session data, and the FMC subscribes to it.
Why does the FMC also need a realm?
The realm supplies the user and group lists, and ISE supplies the session that links an address to a user.
What are the two most common reasons for a failed pxGrid connection?
Certificate trust problems and wrong time or name resolution.
Topic 5 of 8 in Integration
Test yourself on Integration
The full Cisco CCNP 300-710 SNCF question bank has 865 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Cisco. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.