4.2.5 Ensure IS-IS Hello authentication check is not suppressed


IS-IS Neighbors should be authenticated.


Where it is deployed, IS-IS routing is vital for normal operation of an organization's network infrastructure. Correct route information is required for routers to correctly direct traffic through the network. An attacker posing as one of the target routers IS-IS neighbors may inject incorrect information into the route table resulting in DoS attack or loss of confidential data through a Man in the Middle attack. On JUNOS routers it is possible to suppress some authentication features to aid integration with other vendors IS-IS implementations.

One of these interoperability features allows you to configure the router to ignore authentication for Hello messages from other routers. This potentially leaves the router open to attack through Hello messages to the same extent as it would be were authentication not configured at all.

NOTE: IS-IS does not appear to be configured on the target. This check is not applicable.


If you have deployed IS-IS in your network and have disabled hello authentication checking, re-enable it by issuing the following command from the [edit protocols isis] hierarchy for each level at which it was configured:

[edit protocols isis]
user@host#delete level <level> no-hello-authentication

Default Value:

No IS-IS routing is configured by default.

Hello Authentication is not suppressed by default when IS-IS is configured.

See Also


Item Details


References: 800-53|IA-5, 800-53|IA-5(1), CSCv7|16.4

Plugin: Juniper

Control ID: c9cb5ae67abe4b1b2cfbb304ae9cb452579bd9361fd69d1f35a6816a56f9886c