Differences

This shows you the differences between two versions of the page.

--- guides:user:compliance:examples [2022/04/29 08:36] – pgels
+++ guides:user:compliance:examples [2022/04/29 08:42] (current) – pgels
@@ Line 1: / Line 1: @@
+====== Compliance Examples======
+Below are few of the practical examples of implementing Network Compliance policies.
+These are only for sample reference and actual implementation might differ.
+===== Verifying banner =====
+Network //[[guides:user:compliance:examples:banner]]// are electronic messages that provide notice of legal rights to users of
+computer networks.
+This example is to verify if the login banners are configured using NetYCE Compliance.
+  * Rule Type: Configuration
+  * Search based on: Config lines
+===== Verifying telnet =====
+Protocols such as //[[guides:user:compliance:examples:telnet]]// transmit data without any encryption, so it is advised to be disabled.
+This example is to verify if telnet is disabled for remote login purpose using Compliance
+  * Rule Type: Configuration
+  * Search based on: Config blocks
+===== Verify that the passwords are encrypted =====
+//[[guides:user:compliance:examples:pwd_encrypt|Passwords]]// are sensitive information and to be displayed in encrypted format.
+This example shows us how to implement compliance policy to verify the devices are configured to show passwords in encrypted format.
+  * Rule Type: Configuration
+  * Search based on: Config lines
+===== Verifying remote-access ACLs =====
+//[[guides:user:compliance:examples:remote_acl]]//s are used to restrict the management access to network devices.
+This example shows how to implement compliance policy to verify the necessary configuration.
+  * Rule Type: Configuration
+  * Search based on: Config blocks
+===== Verifying tacacs =====
+//[[guides:user:compliance:examples:tacacs]]// is a security application that provides centralized validation of users attempting to gain access to a router or network access server.
+This example helps in validating tacacs configuration using NetYCE Compliance module
+  * Rule Type: Configuration
+  * Search based on: Config lines
+===== Verifying rfc1583 compatibility =====
+//[[guides:user:compliance:examples:rfc1583]]// the method used to calculate summary route costs.
+To minimize the chance of routing loops, all Open Shortest Path First (OSPF) routers in an OSPF routing domain should have RFC compatibility set identically.
+This example shows how to implement compliance policy to verify the necessary configuration.
+  * Rule Type: Configuration
+  * Search based on: Config blocks