Page locked

This page is currently locked for editing by another user. You have to wait until this user finishes editing or the lock expires.

Currently locked by: 216.73.216.48
Lock expires at: 2025/12/06 09:57 (10 min)

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

**__CISCO ISE__**
\\
{{:network_stuff:cisco:ise1.png?400|}}
\\
[[http://www.cisco.com/c/en/us/td/docs/security/vpn_client/anyconnect/anyconnect30/administration/guide/anyconnectadmin30/ac05hostscanposture.html]]\\
\\
The posture services workflow is comprised of three main configuration sections:
  * Client provisioning
  * Posture policy
  * Authorization policy

The posture policy defines the set of requirements for an endpoint to be deemed compliant based upon file
presence, registry key, process, application, Windows, and anti−virus (AV)/anti−spyware (AS) checks and
rules. Posture policy is applied to endpoints based upon a defined set of conditions such as user identity and
client OS type. The compliance (posture) status of an endpoint can be:
  * Unknown: No data was collected in order to determine posture state.
  * Noncompliant: A posture assessment was performed, and one or more requirements failed.
  * Compliant: The endpoint is compliant with all mandatory requirements.


----

__TO CREATE A NEW POLICY__:

Add the device we want to be Authorised with ISE:

Admin. > Network Devices > Add


Policy sets: They have all the policy type. Authoriz and Authentication


Create the Authorization profile:

Policy > Policy Elements > Results > Authorization > Authorization profiles


Add the corresponding authorization and authentication policies:

Policy > Policy Sets


VPN posture completed and testing done to complete
TSHOOT:

 

updated the security policy before doing so (gpupdate /force) on each machine

PROFILING

 

POSTURING


----
__ISE NODES TYPES AND ROLES__
  * Node type:
    * Admin (PAN)
    * Policy Service (PSN): handles traffic between network devices and ISE (its IP is used aS [[https://www.cisco.com/c/en/us/support/docs/security-vpn/remote-authentication-dial-user-service-radius/12433-32.html|RADIUS]] for devices).
  * Roles:
    * Primary
    * Secondary


In order to access the nodes simply browse to node using https. Active Directory account can be used for login. \\
For the PAN nodes, the concept of primary/secondary must be understood __purely from the **user management** interface point of view__. Operationally, the secondary node does exactly the same as the primary one. The only difference is that the primary one allows the user to access all the management features (like logging or policy configuration)

----

__PAN FAILOVER__\\
Cisco advises to have PAN failover disabled.\\
If one of the ISE PAN nodes fails and we want to have admin features available in the healthy one, we manually promote the secondary to primary: to do so, we log into the UI of the secondary node.  Promote to primary takes 10-15 mins and implies restarting services in both nodes. There's no impact in end users, just the Admin UIs get momentary unreachable. 

{{:network_stuff:cisco:ise-pan-failover.png?400|}}
----

RAISE TAC CASE:\\
  * Operations > Troubleshoot > Download Logs and under Appliance node list select the ISE node you have issues with > 'Support Bundle' tab
  * tick: debug logs ; local logs ; mon and reporting logs ; system logs ; from date to date 
  * encryption : public key enc 


----

CLI:\\
  show version    # to check version and patch number
  show disks
  show application status ise    # application server must be in 'running' state

dokucama

User Tools

Site Tools

Page locked

Page Tools