guides:user:compliance:examples:tacacs
Differences
This shows you the differences between two versions of the page.
| guides:user:compliance:examples:tacacs [2022/04/29 08:39] – created pgels | guides:user:compliance:examples:tacacs [2024/07/03 12:31] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ======Verify if tacacs is configured ====== | ||
| + | |||
| + | TACACS+ is a security application that provides centralized validation of users attempting to gain access to a router or network access server. | ||
| + | Below example helps in validating tacacs configuration using NetYCE Compliance module | ||
| + | |||
| + | ===Example config=== | ||
| + | campus01-b02-access01 and campus01-b02-access02 are the two reference devices which we are using for this example. | ||
| + | |||
| + | ==campus01-b02-access01# | ||
| + | |||
| + | {{: | ||
| + | |||
| + | ==campus01-b02-access02# | ||
| + | {{: | ||
| + | |||
| + | ===How its done=== | ||
| + | Below are the steps to create new policy. | ||
| + | //Operate -> Compliance -> Policies -> New->// | ||
| + | {{: | ||
| + | |||
| + | Click on the Node Group to select the relevant group of devices to add. | ||
| + | Node group named " | ||
| + | {{: | ||
| + | |||
| + | Rule -> New | ||
| + | |||
| + | {{: | ||
| + | |||
| + | |||
| + | ===Report/ | ||
| + | Below is how to create reports to see the results of the compliance policies. | ||
| + | |||
| + | //Operate -> Compliance -> Reports -> New -> Report Name “test” -> Report type “Policies” -> Policy Name “Sample5 : TACACS Configuration” -> Show Report// | ||
| + | |||
| + | {{: | ||
| + | |||
| + | This was a simple example to understand how to implement compliance policy to verify tacacs configuration. | ||