If your answer is Yes, or you believe that blocking ICMP increases security, then please give some second thoughts for the poor support guy who gets called at 2 A.M. and needs to ping some hosts to ensure reachability….
Many network administrators feel that ICMP is a security risk, and should therefore always be blocked at the firewall. It is true that ICMP does have some security issues associated with it, and that a lot of ICMP should be blocked. But this is no reason to block all ICMP traffic!
ICMP has many important features; some are useful for troubleshooting, while some are essential for a network to function correctly. Here are details of some of the important ICMP traffic that you should know about, and consider allowing through your network.
Read the full article at http://shouldiblockicmp.com/
A Short Story for Engineers
You don’t have to be an engineer to appreciate this story.
A toothpaste factory had a problem: Due to the way the production line was set up, sometimes empty boxes were shipped without the tube inside. People with experience in designing production lines will tell you how difficult it is to have everything happen with timings so precise that every single unit coming off of it is perfect 100% of the time. Small variations in the environment (which cannot be controlled in a cost-effective fashion) mean quality assurance checks must be smartly distributed across the production line so that customers all the way down to the supermarket won’t get frustrated and purchase another product instead.
Understanding how important that was, the CEO of the toothpaste factory gathered the top people in the company together. Since their own engineering department was already stretched too thin, they decided to hire an external engineering company to solve their empty boxes problem. Continue reading “Good read: Money well spent??”
I have to admit that I’m obsessed with RFC1925 and do my best to apply it to all aspects of my work.
Just as a note to self, I post the Twelve Networking Truths here, and hopefully add more relevant ideas I find in the course of time.
- It Has To Work.
- No matter how hard you push and no matter what the priority, you can’t increase the speed of light.
- (corollary). No matter how hard you try, you can’t make a baby in much less than 9 months. Trying to speed this up *might* make it slower, but it won’t make it happen any quicker.
- With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead.
- Some things in life can never be fully appreciated nor understood unless experienced firsthand. Some things in networking can never be fully understood by someone who neither builds commercial networking equipment nor runs an operational network.
- It is always possible to aglutenate multiple separate problems into a single complex interdependent solution. In most cases this is a bad idea.
- It is easier to move a problem around (for example, by moving the problem to a different part of the overall network architecture) than it is to solve it.
- (corollary). It is always possible to add another level of indirection.
- It is always something
- (corollary). Good, Fast, Cheap: Pick any two (you can’t have all three).
- It is more complicated than you think.
- For all resources, whatever it is, you need more.
- (corollary) Every networking problem always takes longer to solve than it seems like it should.
- One size never fits all.
- Every old idea will be proposed again with a different name and a different presentation, regardless of whether it works.
- (corollary). See rule 6a.
- In protocol design, perfection has been reached not when there is nothing left to add, but when there is nothing left to take away.
This post is my snippet of Wikipedia article about ISMS.
The governing principle behind an ISMS is that an organization should design, implement and maintain a coherent set of policies, processes and systems to manage risks to its information assets, thus ensuring acceptable levels of information security risk.
- The Plan phase is about designing the ISMS, assessing information security risks and selecting appropriate controls.
- The Do phase involves implementing and operating the controls.
- The Check phase objective is to review and evaluate the performance (efficiency and effectiveness) of the ISMS.
- In the Act phase, changes are made where necessary to bring the ISMS back to peak performance.
Continue reading “Overview of ISMS”