STIGQter STIGQter: STIG Summary: Infrastructure Router Security Technical Implementation Guide Juniper Version: 8 Release: 29 Benchmark Date: 25 Jan 2019: Management connections to a network device must be established using secure protocols with FIPS 140-2 validated cryptographic modules.

DISA Rule

SV-15452r4_rule

Vulnerability Number

V-3069

Group Title

Management connections must be secured by FIPS 140-2.

Rule Version

NET1638

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Configure the network device to use secure protocols with FIPS 140-2 validated cryptographic modules.

Check Contents

Review the network device configuration to verify only secure protocols using FIPS 140-2 validated cryptographic modules are used for any administrative access. Some of the secure protocols used for administrative and management access are listed below. This list is not all inclusive and represents a sample selection of secure protocols.

-SSHv2
-SCP
-HTTPS
-SSL
-TLS

JUNOS Example:
[edit system services]
ssh {
root-login (allow | deny | deny-password);
protocol-version [ v2 ];
macs [hmac-sha1 hmac-sha1-96];
ciphers [aes128-cbc aes192-cbc aes256-cbc];
}
[edit interfaces]
lo0 {
unit 0 {
family inet {
filter {
input protect-routing-engine;
}
address 192.168.1.2/32;
}
}
}

[edit firewall]
family inet {
filter protect-routing-engine {
term terminal-access {
from {
source-address {
192.168.1.10;
192.168.1.11;
}
protocol tcp;
port ssh;
}
then {
syslog;
accept;
}
}

term default-action {
then {
syslog;
discard;
}
}
}
}

If management connections are established using protocols without FIPS 140-2 validated cryptographic modules, this is a finding.

Vulnerability Number

V-3069

Documentable

False

Rule Version

NET1638

Severity Override Guidance

Review the network device configuration to verify only secure protocols using FIPS 140-2 validated cryptographic modules are used for any administrative access. Some of the secure protocols used for administrative and management access are listed below. This list is not all inclusive and represents a sample selection of secure protocols.

-SSHv2
-SCP
-HTTPS
-SSL
-TLS

JUNOS Example:
[edit system services]
ssh {
root-login (allow | deny | deny-password);
protocol-version [ v2 ];
macs [hmac-sha1 hmac-sha1-96];
ciphers [aes128-cbc aes192-cbc aes256-cbc];
}
[edit interfaces]
lo0 {
unit 0 {
family inet {
filter {
input protect-routing-engine;
}
address 192.168.1.2/32;
}
}
}

[edit firewall]
family inet {
filter protect-routing-engine {
term terminal-access {
from {
source-address {
192.168.1.10;
192.168.1.11;
}
protocol tcp;
port ssh;
}
then {
syslog;
accept;
}
}

term default-action {
then {
syslog;
discard;
}
}
}
}

If management connections are established using protocols without FIPS 140-2 validated cryptographic modules, this is a finding.

Check Content Reference

M

Target Key

510

Comments