<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>hellbannedguy</author><text>And let&amp;#x27;s not discount the moral of low paid, overworked employees, and companies that let low level managers run roughshod over lower level employees.  My point is don&amp;#x27;t discount inside corporate espionage by disgruntled any level employees.&lt;p&gt;Thank goodness I didn&amp;#x27;t have access to a script that would lock up at least two of my past employers when coming up years ago?  Then again, I personally haven&amp;#x27;t been that mad, but boy do I know employees who were.&lt;p&gt;I could say that we are all choir boys, but you piss on an employee, especially during a recession, well let&amp;#x27;s just say I have seen unpstanding guys rub magnets over hard drives over pure apathy.  (The guy didn&amp;#x27;t know about strength of magnents, and it did not hurt anything.)&lt;p&gt;Plugging in a usb, or downloading a suspicious email is something I can see happening, especially to &amp;quot;those&amp;quot; companies.&lt;p&gt;I imagine Xfinity employees dream about it?</text><parent_chain><item><author>SV_BubbleTime</author><text>Most of these start as phishes to lower level employees. It makes sense to me that’ll happen again and I’m not sure I can say the solution is better backups.&lt;p&gt;Another issue with backups, is are you restoring to an already infected &amp;#x2F; immediately infectable state?&lt;p&gt;I think the better closer is “The certainly will begin to take security, training, and best practices seriously”.</text></item><item><author>diego_moita</author><text>What I suspect: the first ransom was paid by insurance, therefore it didn&amp;#x27;t hurt them, therefore they didn&amp;#x27;t bother protect themselves for the second.&lt;p&gt;Now just wait to see what will happen to your insurance rate after you pay the third ransom.&lt;p&gt;They certainly will begin to understand the need for backups.</text></item></parent_chain></comment><story><title>80% of orgs that paid the ransom were hit again</title><url>https://venturebeat.com/2021/06/16/cybereason-80-of-orgs-that-paid-the-ransom-were-hit-again/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ajsnigrutin</author><text>&amp;gt;  Most of these start as phishes to lower level employees. It makes sense to me that’ll happen again and I’m not sure I can say the solution is better backups.&lt;p&gt;Why? Secretary gets a call from a nigerian prince, starts that letter.exe she gets in her e-mail, her computer gets fscked, IT takes her drive, restores a clean image, and she gets back to work.&lt;p&gt;If the only copy of some important document is on his&amp;#x2F;her pc, or that pc can overwrite&amp;#x2F;delete the only copy, then they&amp;#x27;ve fscked up by design... and yes, now better backups would help.</text><parent_chain><item><author>SV_BubbleTime</author><text>Most of these start as phishes to lower level employees. It makes sense to me that’ll happen again and I’m not sure I can say the solution is better backups.&lt;p&gt;Another issue with backups, is are you restoring to an already infected &amp;#x2F; immediately infectable state?&lt;p&gt;I think the better closer is “The certainly will begin to take security, training, and best practices seriously”.</text></item><item><author>diego_moita</author><text>What I suspect: the first ransom was paid by insurance, therefore it didn&amp;#x27;t hurt them, therefore they didn&amp;#x27;t bother protect themselves for the second.&lt;p&gt;Now just wait to see what will happen to your insurance rate after you pay the third ransom.&lt;p&gt;They certainly will begin to understand the need for backups.</text></item></parent_chain></comment><story><title>80% of orgs that paid the ransom were hit again</title><url>https://venturebeat.com/2021/06/16/cybereason-80-of-orgs-that-paid-the-ransom-were-hit-again/</url></story>