8 Steps To Protect Your Cisco Router 31
Daniel B. Cid writes "I wrote the article '8 steps to Protect your Cisco router' (PDF). This small text gives to the reader eight steps (very easy to understand) showing how minimize your Cisco router exposure, by turning off some unused services, applying some access control lists and applying some security options available on that."
What a retarded article (Score:1, Funny)
8 Steps (Score:3, Funny)
2.) Disconnect the power
3.) Remove all network cables
4.) Remove router from rack, replacing it with a cheap Linux box with some high-end network cards, a hardened kernel and a good iptables script.
5.) Return your Cisco router to original styrofoam packaging. Lock it away somewhere safe.
6.) Your Cisco router is now protected
7.)
8.) Profit!!
Re:8 Steps (Score:2, Funny)
From the terrible secret of space.
Cheaper alternatives for most users (Score:2, Interesting)
I became a much happier person when I moved to a linux machine with a nice shorewall iptables script.
There is one thing I have to say about the cisco 506E, it had a form factor that beats the hell out of a plain pc. I would have loved to run linux on it. It was very small/qu
Since when does the 506E support failover (Score:1)
Also, the lack of "free" for the DES upgrades came from the lack of a support contract, something which i had no control over (i didnt control the budgeting for this unit). And if they are free now, it wasnt free when we used it.
I did not give up on IOS, we used the cisco firwewall at that company until I left, although I did ask for another network admin's help to set it up.
I'd also like to see what you've gotten a 506E to do that linux cant do, i believe
Re:Since when does the 506E support failover (Score:1)
I'd be happy to show you how to set up an iptables ruleset if you are having difficulties configuring one.
Re:Since when does the 506E support failover (Score:2)
Comment removed (Score:3, Interesting)
Re:the nsa... (Score:3, Informative)
Anti-spoofing section (Score:4, Insightful)
access-list 111 deny ip 169.254.0.0 0.0.255.255 any
which is used for APIPA ("Automatic Private IP Addressing", the serverless "DHCP" thing) which a lot of people overlook. Also, while looking for that I spotted that you have the wrong subnet masks for 172.16.0.0 (it's a /12 not a /16) and 192.168.0.0 (it's a /16, not a /8), so you should have:
access-list 111 deny ip 172.16.0.0 0.15.255.255 any
access-list 111 deny ip 192.168.0.0 0.0.255.255 any
Couldn't see anything else obvious to suggest, but I've only scanned it so far.
Re:Only one step needed... (Score:2)
Cisco is doomed (Score:2)