K9 is both an ordering code as well as a designator in an image filename to indicate that the unit has the strong encryption license included. On a ASA, that means the 3DES-AES license.
If an ASA was originaly procured without the k9 code, the license can be added later (it's free). That's assuming the requester is not from a prohibited region (i.e., North Korea, Syria, Sudan, etc.) to which it is illegal for a US manufacturer to export strong encryption technology.
To form and HA failover pair, the units must be the same hardware models as shown by the "show inventory" output. They should also be runnig the same ASA software image.
Setting up some 3rd party devices for my Fire and Rescue trucks that will VPN back to our FPR-2110. I can blatantly see what's going on with the IKEv2 platform and protocol debugs on. It's selecting the wrong dynamic map!IKEv2-PLAT-4: (32): Cry...
On January 22, 2020, the Cisco Product Security Incident Response Team (PSIRT) disclosed a vulnerability in the web-based management interface of Cisco Firepower Management Center (FMC). The vulnerability could allow an unauthenticated, remote attac...
Meet the Authors Event - A Cybersecurity Deep Dive with Omar Santos
(Live event – Thursday, January 23rd, 2020 at 10:00 a.m. Pacific / 1:00 p.m. Eastern / 7:00 p.m. Paris)
This event will have place on Thursday 23rd, January 2020 at 10hrs PDT
Posting this for anyone interested in using a Raspberry PI as a flow collector for Stealthwatch. We created a very lightweight version of our software. It can create flows if the eth port is attached to a SPAN or you can forward NetFlow/IPFIX ...