Category: Uncategorized

  • Exam Review: Cisco SCOR 350-701

    I have been putting off writing this review for a year and a half now.  I did finally pass the SCOR exam and earn my CCNP Security certification, but only after four attempts and more hours than I care to try and estimate.  Don’t get me wrong – this is the first time I’ve ever framed a certification and hung it in my cubicle because I remember vividly what I went through to attain it.  I’m very happy and proud to have passed, but it seriously burned me out on studying for exams.

    After I passed the SISE exam in July of 2020, I immediately began studying for the SCOR exam.  My first attempt at it was in late September.  The next three attempts were all in the month of October, with my final passing result coming on October 24th.

    A major problem I had was specifically due to the official Cisco course guide being very scattered and irrelevant to the exam material, as well as my own lack of hands-on experience with any of the technologies covered by the exam apart from Identity Services Engine.  I also had some experience in studying for the retired IINS exam which included ASAs and VPNs, but I still do not have any experience with ESAs, WSAs, Umbrella, FirePOWER, or any of the other solutions covered by the SCOR.

    The greatest asset I had during my SCOR studies was a study group that was arranged by Martin B.(@martinmbne / mbne.net) for several of us who were all pursuing the CCNP Security certification.  We all shared our study notes, white papers we’d found, our wins, our losses, and they were a constant source of inspiration and motivation for me.  I would be remiss if I didn’t also mention Carl Zellers (@cfzellers4) and Kim Pedersen (@kpjungle / packet-forwarding.net) for offering their support and commiserations as I worked through my many exam attempts.

    Score Results

    This exam frustrated me for many reasons. One of those reasons is how close I came to passing on my second and third attempts. I’ve included the exam results of all of my attempts below for transparency.

    Exam TopicAttempt #1Attempt #2Attempt #3Attempt #4
    Security Concepts 80% 76% 84% 88%
    Network Security 52% 67% 67% 81%
    Securing the Cloud 67% 73% 80% 100%
    Content Security 64% 64% 71% 79%
    Endpoint Protection & Detection 70% 70% 50% 70%
    Secure Network Access, Visibility & Enforcement 80% 87% 80% 87%

    Study Materials and Cost

    For preparation, I used the following resources:

    CCNP and CCIE Security Core SCOR 350-701 Official Cert Guide (Cisco Press) – Cost: $73.60
    The nicest thing that I have to say about this book is that it I highly recommend it, at least as a starting point. You need to understand up front that this book does not do an adequate job of covering the exam material in enough detail — and honestly, doesn’t cover some exam material at all. You will not pass the SCOR exam solely by reading this book. If anything, my personal opinion is that this book gets you less than half the way there.

    Implementing and Operating Cisco Security Core Technologies (SCOR) v1.0 (Cisco Learning Library) – Cost:  $500
    Just like with the SISE exam, I’ve listed the retail cost here, but since I used Cisco learning credits this resource ended up being free to me.  I would still recommend it if you can afford it – or have learning credits available for use.  It makes a good companion to the printed materials and includes practice questions which aren’t carbon copies of those found in the OCG practice test.

    CCNP and CCIE Security Core SCOR 350-701 Complete Video Course (Pearson LiveLessons) – Cost: $129.89
    This video series is given by the same person who authored the OCG book, Omar Santos. I went into this with high expectations of exam-relevant content. If I had to do it again…I’m not sure I would invest in this product. About the only useful thing I got out of it were the practice test questions.

    Integrated Security Technologies and Solutions – Volume I: Cisco Security Solutions for Advanced Threat Protection with Next Generation Firewall, Intrusion Prevention, AMP, and Content Security (Cisco Press) – Cost: $56.28
    Integrated Security Technologies and Solutions – Volume II: Cisco Security Solutions for Network Access Control, Segmentation, Context Sharing, Secure Connectivity and Virtualization (Cisco Press) – Cost: $56.28
    After my second exam attempt, I think it was, these two books were recommended to me as resources by members of my study group. These are great resources. Again, you will not pass the exam with only these books, but I highly recommend them as a supplement to the OCG.

    Network Security Technologies and Solutions (Cisco Press) – Cost: $91.68
    I found this book on my own simply by browsing through the Cisco Press catalog of publications. It was not recommended to me, and I don’t believe anyone else in the study group used it. If you can afford to add this to your studies then I do recommend purchasing it. That said, if I had to choose only between this and the two volumes listed above, I’d pick those two.

    Exam Fees – Cost: $1,600.00
    Pretty self-explanatory here. Each exam attempt was $300, and I took it four times before I passed.

    In Retrospect…

    I spent a long time cursing the name of Omar Santos after this exam. I recently saw his name as one of the listed authors on a Cisco Press book that I was thinking about buying and immediately decided against it.

    In hindsight, I don’t know what kind of situation this exam was developed under…the material was the worst of any Cisco exam I have ever taken, but how closely did Cisco work to ensure that the material accurately reflected the exam?

    I don’t know, and I shouldn’t take that all out on Omar. I don’t even know the guy.

    My pockets are a lot lighter now and I’m fairly positive that I gained several new grey hairs (probably also lost a few permanently) as a result of this exam. But like I said before…I feel a great sense of accomplishment now that I have this certification, and I have gotten a fair amount of recognition from people I work with for having attained it.

    What’s Next?

    To be frank, I’m not really sure. I did take (and fail) the ENWLSD exam last year, mostly just because I thought it would be something quick and easy. I’m applying for some positions doing network security which require knowledge of Palo Alto firewalls and IPsec site-to-site VPNs, though, so I may pursue either the PCNSA or SVPN exams in order to bolster my knowledge with those solutions.

    I’m also roughly halfway through an associates degree program now which has severely limited my free time that I once used to study for certifications…but that’s not a terrible problem to have either.

  • Cisco ISE 2.x: MAC Authentication Bypass (MAB)

    MAC Authentication Bypass (MAB) is a method of network access authorization used for endpoints that cannot or are not configured to use 802.1x authentication.  MAB uses the hardware address (MAC address) of the device connecting to the network to authenticate onto the network.

    This hardware-based authentication happens when a device connects to a Network Access Device (NAD) either wired or wirelessly – i.e., a switch, wireless access point, or VPN concentrator.  In this article I will be assuming that the NAD being used is a switch.

    Packets that are sent before MAB occurs and packets that are used to learn the MAC address are dropped by the switch.  Almost any packet can be used for MAB, but there are specific types of packets that cannot be used.  These include LLDP, spanning tree, and DTP packets.

    Once the switch learns the MAC address of the device attempting to connect to the network, the switch builds a RADIUS Access-Request packet using the MAC address of the device as the User Name and Calling-Station-ID.

    ISE then uses the MAC address from this RADIUS Access-Request packet to query its endpoint identity database for a match.  If a match is found, ISE returns an Access-Accept authorization to the switch and the device is allowed onto the network with a specific VLAN ID tag as configured by the ISE endpoint identity profile.

    If there is no matching endpoint identity in ISE, then the device is authentication session is put into an Unauth state and packets from that device are dropped by the NAD.

    Prerequisites

    In order for MAB to function, the switch must be configured to use the ISE server(s) for RADIUS authentications.  This configuration is outside of the scope of this article, and it is assumed that this configuration has already taken place.

    If issues are discovered with all MAB authentication on a specific switch, it may be best to troubleshoot the RADIUS configuration before troubleshooting MAB.

    MAB Host Mode Options

    There are four host mode options which can be used by MAB:

    Single-Host Mode:  MAB configured in single-host mode will allow only a single device to be allowed onto the network at a time.  If multiple devices are detected on the switchport, the switch will put the switchport into an err-disabled state.

    Multidomain Authentication Host Mode:  This host mode was created specifically for IP telephony.  Multidomain authentication allows one device to connect to each of the two switchport domains – one device can connect to the DATA domain, and one device can connect to the VOICE domain.

    Multi-Authentication Host Mode:  Multiple hosts are individually authenticated onto the network.  This host mode is used when there are multiple devices connecting to a single shared switchport through a hub or bridge such as an unmanaged switch.  Authorized devices are allowed onto the network as normal; packets from unauthorized devices are dropped and the switchport remains in the connected state.  This allows each device to be granted a specific VLAN ID according to its endpoint identity profile configured in ISE.

    Multihost Mode:  The first device to the network will be submitted to ISE for authentication.  If that device is authenticated, then the switchport will allow multiple other devices to access the network without requiring separate authentication of each device.  All connected devices will share the VLAN ID of the authenticated device.

    Typical Interface Configuration

    The standard interface configuration for deployments is as follows:

    mab
    authorization order dot1x mab
    authorization host-mode multi-auth
    authorization port-control auto

    Broken down, each of these commands accomplish the following:

    mab:  This command enables MAB on the interface.

    authorization order mab:  Establishes the order of authentication types to use.  Because MAB is typically used as a failover from 802.1x authentication, it is listed second.

    authorization host-mode multi-auth:  Specifies that MAB should use the multi-authentication host mode which allows multiple devices to authenticate onto the network each with its own VLAN ID.

    authentication port-control auto:  Turns on authentication for the switchport.

    Troubleshooting MAB

    Verify MAB status of an interface from the command line:

    show interface status | include [xyz]:  Confirm that the interface shows as connected.

    show interface status err-disabled:  If the interface shows err-disabled, this command will display the reason the interface is disabled.  This could be caused by issues such as single-host mode MAB with multiple devices connected or bpduguard.

    show run interface [xyz]:  View the interface configuration to ensure that the MAB commands are in place and complete.

    show mac address-table interface [xyz]:  Verify that the switchport has learned a MAC address for the device.  Note:  if the connected device has an Unauth session, you may not see a MAC address with this command.

    show authentication sessions interface [xyz]:  View the current authorization table for an interface.  This will display all MAC address learned by the interface as well as an Auth/Unauth status for each.

    show device tracking database interface [xyz]:  This command (specific to newer IOS versions) will display the MAC address and IP address of a connected device if device tracking is configured on the interface.  Some connection issues can be caused by a mismatch between a device with a static IP configured for a specific VLAN that does not match with the ISE endpoint identity profile.  This can also verify for VLANs with DHCP if the device has been unable to negotiate an IP address with its DHCP server by showing an APIPA address (i.e., 169.254.x.x).

    show ip device-tracking interface [xyz]:  Same command as above, but used for older IOS versions typically found on chassis-based switches.