You may reprint or publish this article free of charge as long as bylines are included.Original URL (The Web version of article)
------------
How A Security Specialist Fell Victim To Attack
Title
-----
How A Security Specialist Fell Victim To Attack
E-mail Attacks - A Bad Day For Submitting Articles
-----------------------------------------------
These days, I write several pages for our site plus two to three articles per week. The first places these articles are posted are DefendingTheNet.com and CastleCops.com. Several days later, I post these articles on other submission sites. This is standard operating procedure in world of article submissions.
E-mail Attacks
--------------
For most part, articles are re-published without you even knowing. You typically find out when someone visits your site from another where article has been posted. Other times, site that plans on posting article e-mails you and asks you to review it before it goes live. Two weeks ago, I received one of these e-mails. Email attack - It was all downhill from there.
To Click Or Not To Click, That Is The Question
----------------------------------------------
Our systems are protected by state of art security systems. Our SPAM filter is a hardware device that is nearly 100% effective. It also helps in protecting against Spyware and other malicious code. Our Firewall is similar to those you would find in large corporations. Our Anti-Virus system has served us well and we've not had problems with virus for years. I'm not claiming that our systems are 100% protected as there is no such system at this point in time. However, we are fairly confident in our security systems.
Two weeks ago, I received approximately twenty e-mails requesting review and approval of Defending The Net articles published on other sites. I thoroughly review e-mails to make sure they seem legitimate. I review url's included to make sure they are valid and not redirected to a site that is IP only. The last e-mail I reviewed seemed to be in proper order. When I clicked on URL to article, site failed to load.
Approximately five minutes later, my system slowed to a crawl. I reviewed running services on machine and found that "SYSTEM" process was running at 100% CPU utilization. A thorough review of system did not reveal anything out of ordinary. Yet, machine was barely operating.