1. Join Trafficswarm.com and get a Free Lifetime Membership today. Surf your TrafficSwarm Page and view only the sites that interest you.Start increasing blog traffic today. It just couldn’t be any easier!
2. Submit your blog to as many blog and rss directories as you can. Here is a good place to start http://www.earnbonus.com/feed-directories/
3. Signup at technorati.com and add your blog then ping it when you update.
4. Get a free account at mybloglog.com and add your blog then join the communities and make friends. There is even a cool widget you can add to your blog like what you see on the right here.This is a great way to increase blog traffic.
5. Signup at Stumbleupon.com and make friends in your niche. You can then stumble your post and get your friends to also.Its a good way for increasing blog traffic.
6. Go to Socialposter.com and fill in the exact url to your blog post then title,general summary text then your tags. Now submit to as many social sites as you can. If this is your first time to use these sites then you will need to signup.
7. Leave comments on blogs in your related niche. This is a great way to increase links back to your site and get free blog traffic. Here is a great free tool to monitor popular blogs in your niche so you can be notified and make one of the first good quality comments. Check it out at Commentsniper.com
8. Make sure and add your blog url to your forum signature on any forums you are a member. This can be a powerful way to attract visitors especially if you have quality forum posts.
9. Find one of the top bloggers in your niche then write a good review post of them. Let them know and they will probably link back to you.
10. Join Squidoo.com and make a lens then add a link to your blog.
Enjoy trying!
Showing posts with label Network. Show all posts
Showing posts with label Network. Show all posts
Monday, September 20, 2010
Friday, June 25, 2010
Demilitarized zone (DMZ)
Figure A : DMZ Sample Topology
A DMZ is the most common and secure firewall topology. It is often referred to as a screened subnet. A DMZ creates a secure space between your Internet and your network, as shown in Figure A.
A DMZ will typically contain the following:
- Web server
- Mail server
- Application gateway
- E-commerce systems (It should contain only your front-end systems. Your back-end systems should be on your internal network.)
Why DMZ?
- considered very secure because it supports network- and application-level security in addition to providing a secure place to host your public servers. A bastion host (proxy), modem pools, and all public servers are placed in the DMZ.
- Furthermore, the outside firewall protects against external attacks and manages all Internet access to the DMZ. The inside firewall manages DMZ access to the internal network and provides a second line of defense if the external firewall is compromised. In addition, LAN traffic to the Internet is managed by the inside firewall and the bastion host on the DMZ. With this type of configuration, a hacker must compromise three separate areas (external firewall, internal firewall, and the bastion host) to fully obtain access to your LAN.
Many companies take it one step further by also adding an intrusion detection system (IDS) to their DMZ. By adding an IDS, you can quickly monitor problems before they escalate into major problems.
Best Practice For Web Server Deployment
Network filtering:
Place your web server(s) in a DMZ. Set your firewall to drop connections to your web server on all ports but http (port 80) or https (port 443).
Host based security:
Remove all unneeded services from your web server, keeping FTP (but only if you need it) and a secure login capability such as secure shell. An unneeded service can become an avenue of attack.
Limit the number of persons having administrator or root level access.
Apply relevant security patches as soon as they are announced and tested on a pre-production system.
Disallow all remote administration unless it is done using a one-time password or an encrypted link.
If the machine must be administered remotely, require that a secure capability such as secure shell is used to make a secure connection. Do not allow telnet or non-anonymous ftp (those requiring a username and password) connections to this machine from any untrusted site. It would also be good to limit these connections only to a minimum number of secure machines and have those machines reside within your Intranet.
Configuring the Web service/application:
If you must use a GUI interface at the console, remove the commands that automatically start the window manager from the .RC startup directories and then create a startup command for the window manager. You can then use the window manager when you need to work on the system, but shut it down when you are done. Do not leave the window manager running for any extended length of time.
Run the web server in a chroot-ed part of the directory tree so it cannot access the real system files.
Run the anonymous FTP server (if you need it) in a chroot-ed part of the directory tree that is different from the web server's tree.
Remove ALL unnecessary files such as phf from the scripts directory /cgi-bin.
Remove the "default" document trees that are shipped with Web servers such as IIS and ExAir.
Apply relevant security patches as soon as they are announced and tested on a pre-production system.
Auditing/logging:
Log all user activity and maintain those logs either in an encrypted form on the web server or store them on a separate machine on your Intranet, or write to "write-once" media.
Monitor system logs regularly for any suspicious activity.
Install some trap macros to watch for attacks on the server (such as the PHF attack).
Create macros that run every hour or so that would check the integrity of passwd and other critical files.
When the macros detect a change, they should send an e-mail to the system manager, write a message to logs, set off a pager, etc..
Content management:
Do all updates from your Intranet. Maintain your web page originals on a server on your Intranet and make all changes and updates here; then "push" these updates to the public server through an SSH or SSL connection. If you do this on a hourly basis, you can avoid having a corrupted server exposed for a long period of time.
Write a script to download HTML pages and check against a template, if changes are noted, upload the correct version.
Intrusion Detection:
Scan your web server periodically with tools like ISS, Nmap, Nessus or Satan to look for vulnerabilities.
Have intrusion detection software monitor the connections to the server. Set the detector to alarm on known exploits and suspicious activities and to capture these sessions for review. This information can help you recover from an intrusion and strengthen your defenses.
Subscribe to:
Posts (Atom)
