|
|
|
Written by Paul Stewart
|
|
Saturday, 05 December 2009 |
RFC3330 is the list of bogons, or ip addresses that we should not see as the source addresses coming into our networks. Furthermore it is named in the CCIE Security Blueprint and therefore a topic that we must be familiar with. I would certainly read through all of the RFC's mentioned in the blueprint for some general familiarity. When it comes to RFC3330 the address ranges cannot be found in the online DocCD therefore, it seems that there is some daunting memorization that is necessary. However, there is really not that much to memorize. The problem is the order in which the address ranges are listed is numeric order instead of grouping them in a logical way that is easy to memorize. Let's simplify this a bit. |
|
Read more...
|
|
|
Written by Paul Stewart
|
|
Friday, 20 November 2009 |
|
I posted a couple of questions to Twitter this morning as both a challenge and a learning experience for myself and others. These two questions were as follows: - How does the ASA in transparent mode know which interface remote networks should be reached through?
- What is permitted at layer 2 disregarding- layer 3 restrictions?
In addition, I’d like to pose one more question: - In what case does the ASA in Transparent mode drop the first packet?
I promised an answer, but Twitter just didn’t allow enough characters to describe the behavior well. First of I have always assumed that the ASA in transparent mode acted like a bridge. In other words if a frame was received at interface A, it must be destined to interface B. While that seems logical, that is incorrect. The ASA has a CAM table like a switch, but does not behave the same way as a switch when an entry is missing. On a CAM miss, a switch floods the frames out all ports except the port the frame arrived on. When the ASA has a CAM table miss, it does not flood the traffic. |
|
Read more...
|
|
|
Written by Paul Stewart
|
|
Friday, 09 October 2009 |
|
The Cisco ASA has some interesting characteristics when dealing with traceroute. With most traffic, including ICMP echo, outbound traffic can be inspected to allow the incoming traffic associated with the same flow. Inspecting “ICMP” or even “ICMP Error” does not result in traceroute functioning through the ASA. |
|
Read more...
|
|
|
Written by Paul Stewart
|
|
Friday, 04 September 2009 |
|
Do you have a CCIE Blog? The Packet University would love to hear from you. Promote you CCIE related blog below. In 600 characters or less, tell the world about your CCIE Blog and post a link by clicking "add comment" below. Include a link in the comment by choosing the link option on the toolbar. Also make sure that you "Do the math to prove yourself human" before choosing post.
|
|
Read more...
|
|
|
Written by Paul Stewart
|
|
Friday, 28 August 2009 |
According to CCIE Security Proctor Yusuf Bhaiji in his recent Ask The Expert Q&A , the Microsoft CA server is no longer on the lab. He also names IOS as the Certificate Authority server in the Security Lab. It also leaves a remote possibility that an ASA could be used as a CA server. Additionally Bhaiji notes that there will be no direct access to the ACS server. Certain scenarios could require a certificate be placed on the ACS server so how is this possible? This post will outline installing a certificate on an ACS server without direct access. We will use an IOS based CA server to demonstrate. |
|
Read more...
|
|
|
Written by Paul Stewart
|
|
Tuesday, 04 August 2009 |
|
Quick Tips 8/4/09--Zone based firewalls. Zone based firewalls are incredibly flexible, but with flexibility comes complexity. When inspecting, there is a process that is used to determine what type of inspection should be performed on a flow. When inspecting keep in mind how the match will influence the inspection. When a flow is analyzed against the class-map, it will be inspected based on what criteria is matched when there is enough information to arrive at a positive match. match only access-group -- inspect based on PAM table match not protocol -- inspect based on PAM table match protocol tcp -- inspect tcp even if a L7 inspect exist |
|
Read more...
|
|
|
Written by Paul Stewart
|
|
Friday, 31 July 2009 |
|
As most who follow this blog or my twitter account know, I am in pursuit of CCIE Security and plan to clear the v3 lab soon. The purpose of this blog entry is a repository for two or three line "quick tips" that may help others pass their lab. Explanations will not be well polished, but if you are also pursuing the lab, these will make sense. Some you may already be familiar with, others you may not. If you want to add to the list, please use the comment feature below. Check back often as there will be new items added very regularly. The most recent version will always be at the PacketU main page. Quick Tips for 7/31/09 clear configure <section>--ASA commands to bulk remove sections of configuration default <section>--IOS command to return a configuration to its default. "NO" is not always the default. test aaa--allows a quick and easy test of AAA servers from the ASA or IOS. test regex--the ASA has a test Regex that might come in useful for testing expressions used anywhere in the lab. |
|
Read more...
|
|
|
Written by Paul Stewart
|
|
Saturday, 13 June 2009 |
|
Last night I had the opportunity to experiment a bit with Cisco's Flexible Packet matching. What really happened was I was going through IPExpert's Security Workbook 7a and found a task that I thought would fit the bill for something that was posted on Group Study a couple of weeks ago. I took an hour or so messing around with the two scenarios and it really helped me understand how Cisco's new and very special "class and policy type access-control" works. I really think getting sidetracked helped me understand this flexible way of parsing traffic. This post, while admittedly crude, will show how easy it is to match on strings inside a packet. |
|
Read more...
|
|
| << Start < Prev 1 2 3 4 Next > End >>
| | Results 1 - 8 of 28 |
|
|