Taming the beasts… aka suricata blueprint
-
As far as I can tell, there have been recent cases where regionals did exactly that. They reclaimed wasted IPv4 space, since it's far easier to waste a couple of years legally pursuing a decision in a court to reclaim them, than to go ahead and enable IPv6. Not saying that I'll reclaim IPs from Microsoft, I'm saying that it's not impossible to do it.
-
I'm ready for IPv4 to die really. I took my first IPv6 class in the late 90s and I've been pushing for adoption every since. It's been my experience that FUD has prevented more IPv6 than any technical reason.
-
I'm ready for IPv4 to die really. I took my first IPv6 class in the late 90s and I've been pushing for adoption every since. It's been my experience that FUD has prevented more IPv6 than any technical reason.
What, no +1000 button on this forum? ;)
Exactly. Personally I'm in a position where I'm dealing with the provider side of things. If I don't enable it, ISPs have no reason to enable it. I enable IPv6 for all my clients (where applicable) so at least I'm doing my part for it. It's exactly like you said, there is no technical reason not to enable it, it's just 60 year old sysadmins have a fear for large numbers. It's exactly the same thing as IPv4, but with more characters in an address, nothing more.
Queue the "but what about ISP routers not supporting IPv6, switches, ETHERNET CABLES NOT SUPPORTING IPv6!" crowd. Every single device out there in production use that is lvl2 or lower, can handle IPv6. If anyone disagrees, please file your resignation first thing tomorrow morning. There are a lot of new people out there just dieing to get your job.
-
I do provider infrastructure and lots of them are still on the "Wait and see" fence for IPv6. I've shown them how easy it is to run dual stack and they still just don't get it. I'm a gray beard myself and numbers are my friends. :)
-
I agree with you. Things aren't going to change though, because instead of the regionals doing their part and giving out all the remaining IPs and be done with it, they are hoarding them whispering "My preciooooouuusssss". If there is no IP shortage, you aren't forced to move to IPv6. If all the addresses are taken, and you want to bring up a new network, you are forced to go to IPv6.
All OSes these days are already shipping ready for IPv6. As long as the router understands IPv6, there is NOTHING stopping you from actually using IPv6. Switches? lvl2=>IPv6. WIFI APs? lvl2=>IPv6. Bridged modems? lvl2=>IPv6. Routed modems (like DSL modems)? majority is already able to do it.
Just guessing, but I'd say that 80% of the equipment out there is IPv6 capable, it's just the "sysadmins" (just quoting, if I start calling them names, I'll fill the entire post) can't be bothered with it.
The cycle is this:
Website > ISP > client > ISP > Website
As long as 1 of the 3 has access to new IPv4s, the other 2 will not be bothered to make the transition. What needs to be done is google, facebook and twitter stop using IPv4s and start using IPv6 exclusively. That would trigger a few (million) angry calls from clients, which would force ISPs to be bothered with it. But since we are living in a greed-driven society, that will never happen, and we are back to zero.
-
I agree with you both of you… I work for a major MSO in the states who over the last year has deployed IPv6 to almost every market.. Expect, the customer facing support folks don't officially support it. The norm, the engineers deploy something but forget to let the support know about it. I can't speak for all OSs but Windows 7 prefers IPv6 over IPv4. With that being said, pretty much most of the major sites I go to are routing IPv6: facebook, yahoo, google. I guess in one way, this MSO is trying to get IPv6 out there; at least ready before it is required by all.
-
@Cino: Yeap, seen that too. A certain ISP in Cyprus (don't want to point any fingers :o) has enabled IPv6 internally but is just refusing to enable it on their customer side. I can even tell you their answer if you ask for it: "IPv6?!?! I've spent 30 years in the telecom industry and I've never heard of it. Oh, we are actually using it? Well due to incompatibility with our customer modems, we can't currently offer it to our customers." When escalating to the department manager here is his response: "No, he didn't mean we can't use it, er… I'm sure it was a misunderstanding. It's just that having to change the settings on the modem takes a lot of time. Imagine having to do that for all our customers."
Translating both of their responses to normal talk: "We don't actually talk to other departments because we can't be bothered extending our arm to pick up the phone unless the customer is paying us several hundreds of thousands of €/month".
And yes, it's an actual story, not about IPv6, about them adding an IP to their ACL after 15 months of constant DoS attacks. Complements to the attacker's upstream for gulp going as far as ACTUALLY CHANGING the attacker's IP. Because everyone in the IT industry (from the person wiping the floors, to the CEOs) knows that changing an IP simply fixes the problem. I feel so special for them to finally do this for me! ::)
What actually gets on my nerves is that there are persons with far greater knowledge and will to work than the 60 year olds infesting the IT industry. Persons that are currently starving without a job because the idiots are sworn to occupy the positions until all that's left of them is their skeletons strapped to their chairs. If you do point out this fact, they get mad at you for some reason...
-
LOL, I love the way you write man!!
At the company I work for, we dont have that problem with people stuck to the old ways of doing things in IT…. Usually they end up with a package if they can't adapt to the ever changing corporate borg. Or they find themselves with a handset in Tech Support with Customer Service.
I was having an issue on how the modem was handing out the IPv6 prefix, luckily for me I have contacts that work on that side of the house... Couple hours later my /56 was working great at home... Before doing this tho, I asked the Tech Support Teir 3 folks that handle customer calls first.. Yeah its not supported but there is going to be a pilot test rolling out soon, do you want to be part of it?... I told them, Yeah man, but IPv6 addresses are already being handed out to the modems right now are we speak... He didn't believe until I showed a screenshot of my computer IP settings.... We have some awesome tools that were develop in-house to troubleshoot modem issues but they haven't been updated yet to include IPv6. Wouldn't surprise me if that programmer left the company
-
Another deleted rule 2012688 !!! That's 3 rules out of my list in a week. Someone is being naughty and reading my list ;). Keep it up guys, with this pace we'll go through the entire list by next year's end.
-
Ars Technica has a good article about IPv6 adoption up. We were running IPv6 is labs in the early 2ks and it continues to run heavily in the labs. I can enable services rapidly and easily for IPv6 on ADCs and run dual stack with keeping the backend IPv4 but still, interest remains low.
Good to see some of the rules getting addressed. I need to review the ones I've disabled to determine what's wrong with them. So much stuff to do, so little stuff I get paid to do. :)
-
@jflsakfja:
EDIT!!!! MISSED THE QUICK CHECKBOX. TICK THAT!
Question re floating rules for those who understand the black magic…
I've got my floating rules setup as earlier in this thread, all works fine except I now have a client who hosts his site on GoDaddy which conflicts which an IP in one of the PRI2 lists.
I can fix it easily by disabling the QUICK match on PRI2 rules as I have a whitelist in my LAN interface page which allows this address - but this seems inefficient, to my limited knowledge at least.
I tried to create a PASS/Quick rule in floating page higher up than the PRI2 entries but this doesn't work...it kind of half does but I still get a failed to load page ultimately although not as quickly. I suspect like outbound might work but not the accompanying inbound PASS...although Im way out of my depth here trying to debug it. Do PASS entries work in the floating page and if so, any guidance for a novice?
thx in adv -
@irj972:
Question re floating rules for those who understand the black magic…
For the Pass Floating Rule, did you select both the inbound and outbound interfaces?
-
I duplicated what I had with the PRI1 etc for in & out with same set of interfaces, i.e
Whitelist Source = WAN (& VPN_WAN)
Whitelist Dest = LAN (& VPN_LAN)
pic attached in case it helpsEDIT: I trimmed some info from my setup to reduce noise however I now suspect this omission might have something to do with my problem. I suspect a gateway related issue as I run a VPN and it possibly doesn't know how to route packets originating from the VPN interface….I'll try and verify.
If anyone knows any good resources on how to build good firewall rules Id appreciate the pointer, learning by trial and error is tough going. thx again.
-
About IPv6 blacklisting.
It seems that experts in general have an opinion that blacklisting has not been all that effective in IPv4 world, so may as well just abandon it for IPv6, and concentrate on other tactics instead.
Say we still want to blacklist, I think we are going to quit blacklisting individual addresses all together, and ban entire /64 or /42 outright.
Has anyone dabbled in IPv6 blacklisting yet? How is the quality of public IPv6 blacklists? -
@G.D.:
About IPv6 blacklisting.
It seems that experts in general have an opinion that blacklisting has not been all that effective in IPv4 world, so may as well just abandon it for IPv6, and concentrate on other tactics instead.
Say we still want to blacklist, I think we are going to quit blacklisting individual addresses all together, and ban entire /64 or /42 outright.
Has anyone dabbled in IPv6 blacklisting yet? How is the quality of public IPv6 blacklists?Have yet to be hit by anything "massive" in IPv6, so I'll just speculate.
IPv6 /64s are the equivalent of IPv4 /24s. An attacker can "move" within that subnet (dynamic IP, or just fast changing static IPs), and as long as he moves, the blacklisting has already gone to hell. I understand that an attacker can also move to a different subnet, but the same thing applies.
The way I currently do it, is if I see a single IP from a subnet, I block it (already taken care by suricata). If I see multiple IPs blocked from that subnet, I block the entire subnet and alert their upstream. If I'm ignored (suricata still firing up alerts), I look into the subnet more. What country does it come from? Does the upstream already have a different subnet on my permanently banned lists? How long (going back a few years) is that subnet being "naughty"? Did the same ISP have any other interesting subnet (again, going back a few years)? Depending on the answer to those questions and the severity of the traffic, The entire subnet is added to my permanently banned lists.
That's why I strongly disagree with using every single list that's out there. Use the bare essentials, weed out 90% of the traffic, let suricata weed out another 5% and only deal with the 5% that remains. Where it becomes difficult to keep it all together is hosts on the permanently banned list still causing alerts in suricata. There is a way to ignore them using a passlist, but it's not ideal. What I really need to do is ignore the packets originating from a predefined alias and not send them to suricata, but that a different story.
I think that the way IPv6 will be handled will be similar to what I described above. The bad thing about blocking entire subnets are the "innocent" people that go down with them. I consider them as collateral damage. In practice (as described in this guide) the way to perfect (and yes there IS perfect) network security is approaching it in a layered way. And anyone already typing "but eventually you will make a mistake" stop typing and read on.
By layered I mean:
- build a trench around your castle. You have already stopped the horsemen.
- build high strong walls, with sentries and hot oil. You have already stopped the heavy infantry.
- build a strong gate. You have already stopped the rams.
What about catapults? What about them setting your gate on fire? Setting the gate on fire is easily circumvented. Get an iron gate. Catapults? You should already know that catapults are coming, and you should have already sabotaged them. What good are spies if you don't use them?
No I didn't go off in a tangent. Dealing with portscanners shouldn't be your priority. That should already be handled by suricata/pfsense. If the person doesn't know what's running on your hosts, then he can't just guess "ah, they are running ubuntu, let's launch this exploit hoping it will work". How many of your webservers are advertising the server's version in the response? Why not just say "webserver"? The attacker is already trying to find vulnerabilities to your network by interacting with the server. Does your server respond in a way that will alert suricata that host X is poking around, resulting in automatic banning? Does the host handle the automatic banning itself, then push the blocked host to your router? Is the software running on the server properly updated, or is it a 13 year old software (sidenote: checked a long list of hosts the other day (not mine) and some of them were running 13 year old software!!!). If it's not updated, why is it not updated? If it is updated, are there any other mitigations enabled? Is the underlying OS hardened in any way? Or is it happily running a completely up to date X ftp server, but also happily refusing logins without enforcing maximum retries? Is every ssh client connected jailed? Is every single php script running in the same pool? Are basedir restrictions being applied, or can the attacker simply upload a script anywhere and execute it? Does the webserver have access to the same memory that the ssh server uses? Can it write to it?
If you did your absolute best to secure a network and somebody managed to get in, you didn't make a mistake. You simply didn't try hard enough.
Using lists+pfsense+suricata you have already cut down the bad traffic by a LARGE amount. Don't simply sit idling and watch the rest of the traffic go through. Did something new pop up in the logs? Investigate it and don't ignore it.
MLS systems aren't simply installing SELinux and setting it to MLS and boasting "Hey, look at me, I'm running an MLS system!". NO. MLS systems are systems that were designed to separate security into different layers, and each layer dealing with something as efficiently as possible.
As long as the systems are capable of protecting themselves, you shouldn't need to worry about mass blocking hosts. That will naturally come on its own. What this does is add yet another layer to the security: Security through obscurity. Note to industry leaders: FOR THE MILLIONTH TIME: SECURITY THROUGH OBSCURITY IS REAL SECURITY.
Now, if there was a way to keep track of the blocked hosts and identify subnets that could be automatically banned…I'm looking at you BBcan177 ;) (same thing the script does, but using pfsense's snort2c table)
Reaction after previewing the post: "When did I type all that?"
-
Getting a lot of these errors from lists in my syslog:
php: rc.filter_configure_sync: The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/AbusePalevo.txt.tmp' 'https://127.0.0.1:43/badips/AbusePalevo.txt'' returned exit code '1', the output was 'fetch: https://127.0.0.1:43/badips/AbusePalevo.txt: Operation timed out' -
Port is wrong on your aliases should be: https://127.0.0.1:443/badips/AbusePalevo.txt not 43
Something looks off on the directory to…
Getting a lot of these errors from lists in my syslog:
php: rc.filter_configure_sync: The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/AbusePalevo.txt.tmp' 'https://127.0.0.1:43/badips/AbusePalevo.txt'' returned exit code '1', the output was 'fetch: https://127.0.0.1:43/badips/AbusePalevo.txt: Operation timed out' -
Port is wrong on your aliases should be: https://127.0.0.1:443/badips/AbusePalevo.txt not 43
Something looks off on the directory to…
Here is where my de-duplicated lists are:
$ ls /usr/local/www/badips ALIENVAULT.txt AbusePalevo.txt AbuseSpyeye.txt AbuseZeus.txt Atlas_Attacks.txt Atlas_Botnets.txt Atlas_Fastflux.txt Atlas_Phishing.txt Atlas_SSH.txt Atlas_Scans.txt Blut_TOR.txt CIArmy.txt DRG_SSH.txt DRG_VNC.txt DRG_http.txt DangerRulez.txt ET_Comp.txt ET_TOR.txt Feodo_Bad.txt Feodo_Block.txt Geopsy.txt IBlock_BT_FS.txt IBlock_BT_Hijack.txt IBlock_BT_Spy.txt IBlock_BT_Web.txt IBlock_Badpeer.txt IBlock_Onion.txt Infiltrated.txt MDL.txt MalwareGroup.txt NOThink_BL.txt NOThink_Malware.txt NOThink_SSH.txt OpenBL.txt SRI_Attackers.txt SRI_CC.txt Shunlist.txt Spamhaus_drop.txt Spamhaus_edrop.txt VMX.txt WatchGuard.txt dShield_Block.txt dShield_Top.txt malc0de.txtOk so it should really be "https://127.0.0.1:443/usr/local/www/badips/AbusePalevo.txt"?
When done correctly shouldn't the IPs show up in the lists' Values in Firewall>>>> Aliases?
Also, would pfBlocker.widget.php_PATCH and diag_dns.php_PATCH work with 2.1.5?
When i try to test the patches i get this error:
Output of full patch apply test: /usr/bin/patch --directory=/usr/local/www/ -t -p1 -i /var/patches/5401274d202ba.patch --check --forward --ignore-whitespace Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- /usr/local/www/widgets/widgets/pfBlocker.widget.php 2014-06-28 13:11:18.000000000 -0400 |+++ /usr/local/www/widgets/widgets/pfBlocker.widget.php 2014-06-28 13:06:55.000000000 -0400 -------------------------- No file to patch. Skipping... Hunk #1 ignored at 2. Hunk #2 ignored at 29. Hunk #3 ignored at 39. Hunk #4 ignored at 53. Hunk #5 ignored at 61. Hunk #6 ignored at 84. Hunk #7 ignored at 92. 7 out of 7 hunks ignored--saving rejects to usr/local/www/widgets/widgets/pfBlocker.widget.php.rej doneOutput of full patch apply test: /usr/bin/patch --directory=/usr/local/www/ -t -p1 -i /var/patches/5401259cb1b0c.patch --check --forward --ignore-whitespace Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- /usr/local/www/diag_dns.php 2014-06-23 14:22:26.000000000 -0400 |+++ /usr/local/www/diag_dns.php 2014-06-23 14:22:02.000000000 -0400 -------------------------- No file to patch. Skipping... Hunk #1 ignored at 114. Hunk #2 ignored at 158. Hunk #3 ignored at 179. Hunk #4 ignored at 276. 4 out of 4 hunks ignored--saving rejects to usr/local/www/diag_dns.php.rej done -
Getting a lot of these errors from lists in my syslog:
php: rc.filter_configure_sync: The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/AbusePalevo.txt.tmp' 'https://127.0.0.1:43/badips/AbusePalevo.txt'' returned exit code '1', the output was 'fetch: https://127.0.0.1:43/badips/AbusePalevo.txt: Operation timed out'How did you configure the Alias Table? It Should be a "URL Table".
I would also recommend just using the existing IR_ Tables that the Script already created. This saves you the effort of making dozens of Alias Tables.
/usr/local/www/aliastables/IR_MAIL
/usr/local/www/aliastables/IR_PRI1
/usr/local/www/aliastables/IR_IB
/usr/local/www/aliastables/IR_SEC1
/usr/local/www/aliastables/IR_PRI2
/usr/local/www/aliastables/IR_SEC3
/usr/local/www/aliastables/IR_TOR
/usr/local/www/aliastables/IR_SEC2
/usr/local/www/aliastables/IR_PRI3 -
@G.D.:
About IPv6 blacklisting.
It seems that experts in general have an opinion that blacklisting has not been all that effective in IPv4 world, so may as well just abandon it for IPv6, and concentrate on other tactics instead.
Say we still want to blacklist, I think we are going to quit blacklisting individual addresses all together, and ban entire /64 or /42 outright.
Has anyone dabbled in IPv6 blacklisting yet? How is the quality of public IPv6 blacklists?I haven't even started to look at IPv6. I found this old link on Spamhaus website
http://www.spamhaus.org/organization/statement/012/spamhaus-ipv6-blocklists-strategy-statement
I don't know of any IPv6 Blocklists? If anyone has time to research, please forward to the group and we can begin to work out a process to include those.
@jflsakfja:
Now, if there was a way to keep track of the blocked hosts and identify subnets that could be automatically banned…I'm looking at you BBcan177 ;) (same thing the script does, but using pfsense's snort2c table)
In regards to the snort2c file, I think keeping track of Repeated Offenders is a great Idea. This should also involve the pfSense Firewall Blocks also.
I have been working away at getting a Beta of pfBlocker that incorporates my script and some other new features. I believe that I am 90% there. Would be nice to get help from the pfBlocker developers but they seem to have no interest in supporting a new release of pfBlocker. I am not even sure if the Devs want or will support it when I get it finalized. It may end up being a new package…..
A few members have been helping to beta test the package and that is helping weed out issues. If anyone has real time to spare, drop me a PM if you have interest in helping BETA test. Thanks to Cino and wcrowder for their support!! ;) ;)
