|
We have thousands of posts on a wide variety of open source and security topics, conveniently organized for searching or just browsing.
|
|
|
Source: Network World - Posted by Alex
|
|
Firewall audit products are maturing, but the product class is still a relatively young, small market, defined by compliance requirements. You have a fairly limited choice of vendors, including Tufin Software Technologies, AlgoSec, Secure Passage and Athena Security, which all come with firewall audit pedigrees, and RedSeal Systems and Skybox Security, which are primarily vendors of risk-mitigation tools, and so go beyond firewall audit to feature sophisticated risk-assessment and risk-management capabilities. |
|
|
Source: Network World - Posted by Alex
|
|
Firewall audit tools automate the otherwise all-but-impossible task of analyzing complex and bloated rule sets to verify and demonstrate enterprise access controls and configuration change-management processes. |
|
|
Source: Darknet - Posted by Anthony Pell
|
|
iScanner is free open source tool lets you detect and remove malicious codes and web pages viruses from your Linux/Unix server easily and automatically. This is a neat tool for those who have to do some clean up operation after a mass-exploitation or defacement on a shared web-host. |
|
|
Source: 503 Service Unavailable Blog - Posted by Anthony Pell
|
|
Today I will show you the iptables rules I set on my main personal computer, with detailed comments about why I came to use these rules after several years of Linux desktop usage. The rules I use now have been simplified as much as I could and are based on common rules and advice that can be found on the network and also on input I got from experienced network administrators. I’ve been using them unmodified for a few years. They are designed for desktop users either directly connected to the Internet or behind a router. They are a bit restrictive in some aspects but we’ll see you can easily create a few holes for specific purposes. |
|
|
Source: Darknet - Posted by Anthony Pell
|
|
Flint examines firewalls, quickly computes the effect of all the configuration rules, and then spots problems so you can:
- CLEAN UP RUSTY CONFIGURATIONS that are crudded up with rules that can’t match traffic.
- ERADICATE LATENT SECURITY PROBLEMS lurking in overly-permissive rules
- SANITY CHECK CHANGES to see if new rules create problems.
|
|
|
Port Knocking
|
03 March 2010
|
|
|
Source: IT World - Posted by Anthony Pell
|
|
Fred Stluka from Bristle.com just introduced me to port knocking -- a method of opening ports on a firewall by trying to connect with a series of ports in a pre-determined order. The sequence of "knocks" acts like a secret access code -- like tapping out the first couple of bars from your favorite song to tell someone inside that it's you. |
|
|
Source: cyberciti - Posted by Anthony Pell
|
|
ow do I restrict the number of connections used by a single IP address to my server for port 80 and 25 using iptables?
You need to use the connlimit modules which allows you to restrict the number of parallel TCP connections to a server per client IP address (or address block).
This is useful to protect your server or vps box against flooding, spamming or content scraping. |
|
|
Source: The Register - Posted by Anthony Pell
|
|
On Tuesday, hacker Samy Kamkar demonstrated a way to identify a browser's geographical location by exploiting weaknesses in many WiFi routers. Now, he's back with a simple method to penetrate hardware firewalls using little more than some javascript embedded in a webpage. |
|
|
Source: Tech Republic - Posted by Anthony Pell
|
|
With the prevalence of “black box” appliance firewalls available for $50 or less, one might wonder why you would look for a do-it-yourself solution. Linksys and D-Link, among other vendors, create simple and easy to configure firewall solutions for cheap. And let’s face it, a firewall isn’t something you can choose to use anymore; a firewall is your first line of defense, and a critical one at that. |
|
|
Source: CIO / InfoWorld - Posted by Anthony Pell
|
|
In the beginning was the firewall, and it was pretty good. A big box of rules that sat between your network and the evils of the Internet, the firewall examined ports and protocols to decide which packets got in and which were barred at the door. Then things got, as things often do, complicated. New threats came sneaking in on trusted protocols, ports and protocols became tangled, and looking inside packets became just as important as noting their source, destination, and type. |
|
|
<< Start < Prev 1 2 3 Next > End >>
|
| Results 11 - 20 of 314 |
