It sets an access class ACL on VTY lines.
It enables TCP intercepts.
It provides an option for configuring SNMPv3 on all routers.
It enables the Secure Copy Protocol (SCP).
It supports AAA configuration.
Network IPS is operating system-dependent and must be customized for each platform.
Network IPS is incapable of examining encrypted traffic.
Network IPS is unable to provide a clear indication of the extent to which the network is being attacked.
Network IPS sensors are difficult to deploy when new networks are added.
Network IPS has a difficult time reconstructing fragmented traffic to determine if an attack was successful.
Client-based IPsec VPN using AnyConnect
Client-based IPsec VPN using Cisco VPN Client
Clientless SSL VPN
Site-to-site IPsec VPN
Client-based SSL VPN using AnyConnect
Clientless IPsec VPN
The thin client mode functions without requiring any downloads or software.
It supports all client/server applications.
It is compatible with DMVPNs, Cisco IOS Firewall, IPsec, IPS, Cisco Easy VPN, and NAT.
It has the option of only requiring an SSL-enabled web browser.
It supports the same level of cryptographic security as an IPsec VPN.
Apply the ACL to the vty lines without the in or out option required when applying ACLs to interfaces.
The ACL is applied to the Telnet port with the ip access-group command.
The ACL must be applied to each vty line individually.
The ACL should be applied to all vty lines in the in direction to prevent an unwanted user from connecting to an unsecured port.
The ASA console will display an error message.
The ASA will not allow traffic in either direction between the Inside interface and the DMZ.
The ASA allows traffic from the Inside to the DMZ, but blocks traffic initiated on the DMZ to the Inside interface.
The ASA allows inbound traffic initiated on the Internet to the DMZ, but not to the Inside interface.
Authenticates a packet by using either the HMAC MD5 or HMAC SHA algorithms and encrypts the packet with either the DES, 3DES or AES algorithms
Authenticates a packet by using the SHA algorithm only
Authenticates a packet by using either the HMAC with MD5 method or the SHA method
Authenticates a packet by a string match of the username or community string
SSL VPNs provide support for more applications.
SSL VPNs do not require any pre-installed client software.
SSL VPNs provide superior authentication.
SSL VPNs provide stronger encryption as a remote-access solution.
FW(config)# interface g0/1 FW(config-if)# ip inspect OUTBOUND in FW(config-if)# ip access-group INSIDE out
FW(config)# interface g0/1 FW(config-if)# ip inspect OUTBOUND in FW(config-if)# ip access-group INSIDE in
FW(config)# interface g0/0 FW(config-if)# ip inspect OUTBOUND in FW(config-if)# ip access-group INSIDE in
W(config)# interface g0/0 FW(config-if)# ip inspect INSIDE in FW(config-if)# ip access-group OUTBOUND in
Cisco VPN client mode
Full client mode
Thin client mode
The classic firewall will perform the same inspection on all traffic that goes through a specific interface.
The classic firewall can only have one policy that affects any given traffic.
The classic firewall security posture is to block unless explicitly allowed.
The classic firewall is limited to two interfaces.
The classic firewall relies heavily on ACLs.
An IDS uses signature-based technology to detect malicious packets, whereas an IPS uses profile-based technology.
An IDS would allow malicious traffic to pass before it is addressed, whereas an IPS stops it immediately.
An IDS can negatively impact the packet flow, whereas an IPS can not.
An IDS needs to be deployed together with a firewall device, whereas an IPS can replace a firewall.
The state of packets related to the attack
The total number of packets in the attack
The network bandwidth consumed by all packets
The attacking period used by the attacker
A packet-filtering firewall typically can filter up to the transport layer, whereas a stateful firewall can filter up to the session layer.
Both stateful and packet-filtering firewalls can filter at the application layer.
A packet-filtering firewall uses session layer information to track the state of a connection, whereas a stateful firewall uses application layer information to track the state of a connection.
A stateful firewall can filter application layer information, whereas a packet-filtering firewall cannot filter beyond the network layer.
ASA ACLs use the subnet mask in defining a network, whereas IOS ACLs use the wildcard mask.
ASA ACLs do not have an implicit deny all at the end, whereas IOS ACLs do.
ASA ACLs use forward and drop ACEs, whereas IOS ACLs use permit and deny ACEs.
Multiple ASA ACLs can be applied on an interface in the ingress direction, whereas only one IOS ACL can be applied.
ASA ACLs are always named, whereas IOS ACLs can be named or numbered.
Use ISL encapsulation on all trunk links.
Disable STP on all nontrunk ports.
Disable trunk negotiation for trunk ports and statically set nontrunk ports as access ports.
Use VLAN 1 as the native VLAN on trunk ports.
To have stronger encryption options
To support secure access for users on a multitude of devices
To have stronger authentication options
To provide stronger overall security
It allows users on the 10.5.0.0/24 network access via HTTPS to remote devices on the 10.7.150.0/28, 10.7.151.0/28, 10.7.160.0/28, and 10.7.161.0/28 networks.
It allows devices on the 10.7.150.0/28, 10.7.151.0/28, 10.7.160.0/28, 10.7.161.0/28 networks to receive TCP-based broadcasts.
It allows any TCP traffic with port 443 from the 10.7.150.0/28, 10.7.151.0/28, 10.7.160.0/28, and 10.7.161.0/28 networks access to the 10.5.0.0/24 network.
It allows devices on the 10.5.0.0/24 network to have telnet and web access to the 10.7.150.0/28, 10.7.151.0/28, 10.7.160.0/28, and 10.7.161.0/28 networks.
A copy of the router configuration file has been made.
The Cisco IOS image file is hidden and cannot be copied, modified, or deleted.
The Cisco IOS image filename will be listed when the show flash command is issued on R1.
A copy of the Cisco IOS image file has been made.
The secure boot-config command was issued on R1.
The copy tftp flash command was issued on R1.
Implement a strong password policy.
Deploy antisniffer software.
Include a firewall and IPS in the network security design.
Design the network by using the principle of minimum trust.
The root user must be assigned to each privilege level that is defined.
It is required that all 16 privilege levels be defined, whether they are used or not.
Views are required to define the CLI commands that each user can access.
There is no access control to specific interfaces on a router.
Creating a user account that needs access to most but not all commands can be a tedious process.
Commands set on a higher privilege level are not available for lower privilege users.
Digitally signed private key
Digitally signed public key
Here's an interesting quiz for you.