In this post, I'll be configuring site-to-site VPN with ASA as peers. This post won't be a very long one because the configuration is almost identical to configuring it on a router using crypto maps with some slight syntax changes.
In this blog post, we're going to walk through NAT Traversal and the different considerations to think about when a firewall is in the path of the VPN peers.
In this post, we are going to go over troubleshooting our VPN using debug commands. This is particularly useful for the folks out there reading this that only have access to only one side of the VPN or have a VPN to a 3rd party. I wanted this to remain a separate post from my ASA and IOS site-to-site VPN configuration posts because troubleshooting this is almost entirely identity on both a router or an ASA so I wanted to combine the troubleshooting to a single post.
In this post, I'm going to go through configuring site-to-site VPN on IOS. We're going to take what we learned in the last blog post and apply it here. I think the best way this was explained to me was by Khawar Butt where you should think about your VPN configuration by break it down by the phases and then create your base VPN configuration on that. For the folks who don't know who Khawar Butt is, I'll be writing a review of his class shortly but you can see a sample of his work here.
In this post, I'm going to go over a high level explanation of VPNs and specifically IPSec. This is going to be the first in a series of VPN posts focusing on the various types of VPNs one might see on the CCIE Security lab or on the job. I think it's important to have this overview because as you configure IPSec VPN or troubleshoot it, it'll help you to know what's going on under the covers of that configuration.
In this blog post, I'm going to be taking a test drive of Cisco's DNA Center and SD-Access. Unfortunately, I don't have this set up in my lab yet so I'll be utilizing dCloud for this and documenting as I go.
In this post, I'm going to veer away from the network security side of Splunk and more on the network operations side of things by introducing the Cisco Networks Splunk app. This app will gather syslog and Call Home data from various network devices in the network and visualize it in some rather interesting ways.
In this blog post, I'll be going over aggregating all of the various security addons for Splunk into the Cisco Security Suite. This will a very short port since most of the work has already been done in our previous Spunk posts.
In this blog post, I will be detailing how I added WSA logs to my Splunk instance. There's a few ways you can do this but I'm doing to be uploading the logs to Splunk via FTP. You can also utilize SCP but I chose not to go that route.
In this blog post, I'll be writing about adding Firepower logs to Splunk. With Firepower, we will utilize the built in eStreamer to send this data securely to our Splunk server.
This post is going to be a bit different. I'm configuring Splunk in my lab currently for reporting and as I go through it, I'm going to detail my configurations here. I am going to use Splunk to aggregate my ISE logs to it. In order to do so, we're going to have to install the Spunk for Identity Services (ISE) app onto Splunk. Before starting, please download the app
I'm currently adding Splunk to my lab so as I'm going through the configuraitons, I'm going to list out what I do here as a series of blog posts. Splunk is a pretty power SIEM that works to aggregate and correlate data across your network and security tools. If you ever wanted to try it out for free, go to splunk.com and you should be able to download it for free for use up to a certain point. The nice thing about Splunk is that there are tons of free pre-built apps and dashboards for multiple vendors which you can download
This is going to be more of a fun post since people usually ask how much a CCIE costs or the the time it takes. This post is going to go over the time and money costs of getting my CCIE Data Center.
This blog post is for my ISE 2.1 notes
These are my notes from reading the config guide for clustering and labbing it out.
My notes on ASA high availability. I'll go through tips and tricks with Active/Standby and Active/Active.
My ASA context notes from studying for the CCIE Sec v5
As promised in the last post, I added a list of free or low-cost training and labbing options for folks.
I've been thinking about writing this post all week and decided to wait until I processed my thoughts a little more before I wrote it out. There's a lot of fear, uncertainty and doubt that's been going on in the field for years and here are some of repetitive questions I tend to hear on Linkedin, Techexams and other social media:
- Is it worth going into networking/getting a CCIE/etc if SDN is going to take over?
- There's so many engineers out there, why do companies choose to hire H1Bs?
- Do I have to worry about my job getting outsourced to another country?
- Do I have to worry about H1Bs taking my job?
In this blog post, I'm going to go ahead and add a NAT configuration cheatsheet. This isn't intended to be an explanation of NAT but instead to just highlight the configuration differences between the different types of NAT.