We encourage Cisco ISE customers and partners to share custom ISE Endpoint Profiles that are not included with ISE or distributed via the Profiler Feed Service. In some cases, the profiles provided here may modify those provided in the shipping product or via Feed Service.
Cisco is not responsible for profiles shared to the community. As with all new profiles, it is highly recommended that they first be installed in a lab environment to verify functionality and potential impact.
Posted profiles may be unique to a specific vertical market, as in the case of the Cisco ISE Medical NAC Profile Library. In other cases, the profiles may not have been fully validated by the Cisco ISE Profiling team, but are posted "as-is" to offer a quicker method to deliver new profiles of potential interest.
Get Endpoint Profiles
All network device profiles uploaded to the ISE community should be tagged with ise-endpoint-profile.
You may view a filtered list of all documents assigned a specific tag such as ise-endpoint-profile using the URL
Attach your exported Endpoint Profile XML (.xml) file.
Write a Description that includes the details about how it was configured and what hardware and software you tested with.
Label your document as Identity Services Engine (ISE)
Include ise-endpoint-profile as one of the Tags. You may include other tags (ise, endpoint, profile, <vendor>, etc.) but using ise-endpoint-profile is how we enable you to quickly filter all documents within the Communities site for just network device profiles!