<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!--Web 2.0 Content Powered by MyST Blogsite® (http://blogsite.com)-->
<!--A service of MyST Technology Partners, Inc. (http://myst-technology.com)-->
<?xml-stylesheet href="http://blogsite.com/public/styles/etc/object.xsl" type="text/xsl"?>

<?myst-baseUrl http://blogsite.com/public/?>

<MySmartChannels Public="true" UserID="76091" dT="50" t0="1214181338583">
     <GetChannelItem_Result>
      <Item>
       <Resource>
        <ObjectID>203049</ObjectID>
        <ObjectClass>Resource</ObjectClass>
        <OwnerID ObjectClass="Domain" Title="[Weblog] Marketing. Communication. Results.">76407</OwnerID>
        <CreatedByID ObjectClass="User" Title="aseidl">21</CreatedByID>
        <ModifiedByID ObjectClass="User" Title="aseidl">21</ModifiedByID>
        <CreateTime Title="2008-05-06 09:54:44 EDT">1210082084995</CreateTime>
        <ModifyTime Title="2008-05-06 09:54:44 EDT">1210082084995</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>Hacked and Attacked: Why?</Name>
        <Summary>San Diego Real Estate Blog and 18 Other Real Estate Sites Still Reeling</Summary>
        <Description>&lt;p&gt;One might morph the popular real estate adage for applicability to&amp;nbsp;marketing websites:&amp;nbsp; &lt;em&gt;Security, security, security&lt;/em&gt;.&lt;/p&gt;&lt;p&gt;A &lt;a title="Hacked and Attacked: Why?" href="http://sandiegopreviews.com/2008/04/18/hacked-and-attacked-why/" target="_blank"&gt;recent posting by Roberta Murphy&lt;/a&gt; describes how her WordPress-based San Diego Real Estate blog was viciously attacked by unknown entities who tried to delete everything ever written at San Diego Previews, &lt;a title="Luxury Homes Digest" href="http://luxuryhomedigest.com/" target="_blank"&gt;Luxury Homes Digest&lt;/a&gt;, and 18 or so other real estate blog sites.&amp;nbsp; Roberta is understandably angry about the incident which took her site down, leaving some wondering if she was still in the San Diego real estate business.&amp;nbsp; But more deeply, she was left wondering, Why someone would bother to hack her site since it did not contain credit card numbers or other sensitive data?&lt;/p&gt;&lt;p&gt;Having been responsible for the security side of the &lt;a title="Amplify Your Voice on the Web with a Professionally Managed MyST Blogsite" href="item/196675"&gt;MyST Blogsite&lt;/a&gt; infrastructure almost five years now, I certainly sympathize with Roberta.&amp;nbsp; And while I also wonder why some people are driven to such such abusive acts, I have absolutely no doubt that there are lots of such people in the world.&amp;nbsp; Whether its so-called &amp;quot;script kiddies&amp;quot; doing the Internet equivalent of the joy riding, sophisticated criminals executing well-planned schemes, or well-intended (but not so skilled) programmers trying to address legitimate integration requirements, the Internet is teeming with nefarious activity.&lt;/p&gt;&lt;p&gt;Here's a simple rule of thumb:&amp;nbsp; &lt;b&gt;If your site has any significant visibility at all, it will be attacked at some point.&lt;/b&gt;&lt;/p&gt;&lt;p&gt;As I described in my &lt;i&gt;&lt;a title="Compromised WordPress Blogs Become an Army of Hacker Zombies" href="http://faseidl.com/public/item/200919" target="_blank"&gt;FAS Talk&lt;/a&gt;&lt;/i&gt; blog, last month I discovered that a federation of hacked WordPress servers&amp;mdash;over a thousand servers to date&amp;mdash;were (and still are) being used to try to hack into our company web site.&amp;nbsp; At the time I first noticed slower-than-normal server response times, that site was receiving over 50,000 requests per day attempting to gain authoring access.&amp;nbsp; Thankfully, our company web site, like every other advertorial marketing site powered by MyST Blogsite, is protected by multiple security layers and was never actually hacked.&lt;/p&gt;&lt;p&gt;&lt;img style="MARGIN: 0px 10px 3px 0px" alt="Security" src="docs/security-150.jpg" width="150" align="left" border="0" /&gt;MyST SlimeGate&amp;trade; is one of the security layers that protect all commercial sites powered by MyST Blogsite.&amp;nbsp; (There are others; see, for example, &lt;i&gt;&lt;a title="Overly aggressive RSS feed aggregators can cause server performance problems; MyST Blogsite introduces new technology to detect (and reject) egregious offenders." href="public/item/178941"&gt;Fighting Back Against Big, Hungry, Orange Alligators&lt;/a&gt;&lt;/i&gt;.)&amp;nbsp; This layer serves as a blogsite's immune system by killing nefarious requests before they ever reach the blogsite itself and by restricting subsequent access by offending machines through dynamic firewall technology.&amp;nbsp; Once this immune system layer &amp;quot;learned&amp;quot; to recognize requests from compromised WordPress servers, the 50,000 number quickly dropped to about 20 and response times returned to normal.&lt;/p&gt;&lt;p /&gt;&lt;hr /&gt;&lt;em&gt;Do you have&amp;nbsp;a security related story or question? Post a comment below.&lt;/em&gt;&lt;p /&gt;</Description>
        <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
        <ContentType>application/xml</ContentType>
        <ContentDocument>
         <ItemProperties>
               <CommonProperties>
       
                <Keywords>
                 <Keyword>marketing website</Keyword>

                 <Keyword>MyST Blogsite</Keyword>

                 <Keyword>MyST SlimeGate</Keyword>

                 <Keyword>real estate</Keyword>

                 <Keyword>security</Keyword>

                 <Keyword>WordPress</Keyword>

       </Keywords>

                <Links>
                 <Link>
                  <Title>Hacked and Attacked: Why?</Title>

                  <Synopsis>April 18, 2008: San Diego Real Estate Blog</Synopsis>

                  <URL>http://sandiegopreviews.com/2008/04/18/hacked-and-attacked-why/</URL>

        </Link>

                 <Link>
                  <Title>Compromised WordPress Blogs Become an Army of Hacker Zombies</Title>

                  <Synopsis>Somewhere in the shadowy underbelly of the Web, there is an intelligent, and slimy, hacker exploiting WordPress security holes.</Synopsis>

                  <URL>http://faseidl.com/public/item/200919</URL>

        </Link>

                 <Link>
                  <Title>Fighting Back Against Big, Hungry, Orange Alligators</Title>

                  <Synopsis>Overly aggressive RSS feed aggregators can cause server performance problems; MyST Blogsite introduces new technology to detect (and reject) egregious offenders.</Synopsis>

                  <URL>http://blogsite.com/public/item/178941</URL>

        </Link>

       </Links>

               <Hidden>false</Hidden>
        </CommonProperties>

              <ns3:Details xmlns="urn:MyST-Technology.Structured.Details" xmlns:ns3="urn:MyST-Technology.Structured.Details">
               <ns3:Collection name="Quote" type="urn:MyST-Technology.Structured.Collection.Captyx.Quote">
                <ns3:Attribute name="Quote" type="large-text">
                 <ns3:Value>We are just now starting to recover from an attack that has left me stunned...  This was an attack not only on real estate blog sites, but also on reputations, livelihoods and peace of mind.</ns3:Value>

        </ns3:Attribute>

                <ns3:Attribute name="Name" type="text" value="Roberta Murphy"/>

                <ns3:Attribute name="Blog" type="url" value="http://sandiegopreviews.com/2008/04/18/hacked-and-attacked-why/"/>

                <ns3:Attribute name="Title" type="text"/>

                <ns3:Attribute name="Company" type="text" value="San Diego Real Estate Blog"/>

                <ns3:Attribute name="Web" type="url"/>

                <ns3:Attribute name="Icon" type="checkbox" value="true"/>

                <ns3:Attribute name="Frame" type="text" value="bars"/>

                <ns3:Attribute name="HTML" type="checkbox" value="false"/>

                <ns3:Attribute name="Alignment" type="text" value="right"/>

                <ns3:Attribute name="Text Size" type="text" value="medium"/>

                <ns3:Attribute name="Container" type="text" value="div"/>

                <ns3:Attribute name="Container ID" type="text"/>

                <ns3:Attribute name="Container Class" type="text" value="Quote"/>

                <ns3:Attribute name="Container Style" type="text"/>

                <ns3:Attribute name="_captyx.position" type="text" value="_top"/>

                <ns3:Attribute name="_captyx.embargo" type="checkbox" value="false"/>

                <ns3:Attribute name="_captyx.scope" type="text"/>

                <ns3:Attribute name="_captyx.sortkey" type="text"/>

       </ns3:Collection>

      </ns3:Details>

              <RemoteInfo>
               <UserAgent>Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)</UserAgent>

               <RemoteHost>127.0.0.1</RemoteHost>

               <RemoteAddr>127.0.0.1</RemoteAddr>

               <RemoteUser>aseidl</RemoteUser>

               <ForwardedFor>68.40.167.222</ForwardedFor>

      </RemoteInfo>

     </ItemProperties>
       </ContentDocument>
      </Resource>
      <Shares/>
      <Subjects/>
      <UserPermissions>
       <CanDelete>false</CanDelete>
       <CanDiscover>true</CanDiscover>
       <CanEdit>false</CanEdit>
       <CanEditPermissions>false</CanEditPermissions>
       <CanRead>true</CanRead>
      </UserPermissions>
      <CommentInfo>
       <CommentChannelRef AllowAnonymous="true" Inherited="true">
        <ChannelID ObjectClass="Channel" Title="[Public] Public Comments">174050</ChannelID>
        <UserPermissions>
         <CanCreateChannelItem>false</CanCreateChannelItem>
         <CanDelete>false</CanDelete>
         <CanDiscover>true</CanDiscover>
         <CanEdit>false</CanEdit>
         <CanEditPermissions>false</CanEditPermissions>
         <CanPublish>false</CanPublish>
         <CanRead>true</CanRead>
        </UserPermissions>
       </CommentChannelRef>
       <Comments/>
      </CommentInfo>
      <Views>
       <SourceID ObjectClass="Channel" Title="[Weblog] Marketing. Communication. Results.">76407</SourceID>

              <View>
               <Name>blog</Name>

               <Model>blogsite/Blogsite/web</Model>

               <Style/>

               <Scheme/>

       </View>

              <View>
               <Name>edit-item</Name>

               <Model>blogsite/Blogsite/right-content</Model>

               <Style/>

               <Scheme/>

       </View>

              <View>
               <Name>left</Name>

               <Model>blogsite/Blogsite/left-content</Model>

               <Style/>

               <Scheme/>

       </View>

              <View>
               <Name>right</Name>

               <Model>blogsite/Blogsite/right-content</Model>

               <Style/>

               <Scheme/>

       </View>

              <View>
               <Name>wide</Name>

               <Model>blogsite/Blogsite/wide-content</Model>

               <Style/>

               <Scheme/>

       </View>

      </Views>
       <Views>
        <SourceID ObjectClass="Channel" Shared="true" Title="[Public] What's New">102736</SourceID>

               <View>
                <Name>blog</Name>

                <Model>blogsite/Blogsite/my-whatsnew</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>edit-item</Name>

                <Model>blogsite/Blogsite/right-content</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>left</Name>

                <Model>blogsite/Blogsite/left-content</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>right</Name>

                <Model>blogsite/Blogsite/right-content</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>wide</Name>

                <Model>blogsite/Blogsite/wide-content</Model>

                <Style/>

                <Scheme/>

       </View>

      </Views>
       </Item>
      </GetChannelItem_Result>
     </MySmartChannels>
