0%

Book Description

As stories continue to mount about security breaches in organizations and government agencies—such as the 2016 US Department of Justice hack—many people believe there’s really nothing they can do about it. Fact is, you can do quite a bit. In this report, security professional Andrew Peterson addresses several widespread misconceptions about the hacking world so that you can be better prepared to join the fight.

You may believe hackers today are too clever and attacks are too sophisticated for you to do anything, or that your organization isn’t worth a hacker’s time. But that isn’t the case.

All organizations—from small, owner-operated businesses to large, multinational corporations—own data worth stealing and are potential, and even likely, targets for an attack. If you’re ready to take security seriously, you need to involve everyone in the company, including security and non-security professionals alike. This report provides you with an accurate picture, rather than conjecture or half-truths propagated by the media.

Table of Contents

  1. Cracking Security Misconceptions
    1. Introduction
    2. Misconception #1: Hackers Are Criminals
      1. White Hat
      2. Black Hat
      3. Gray Hat
      4. Wrap-up
    3. Misconception #2: Hackers Must Be Geniuses
      1. United States Department of Justice
      2. Target
    4. Misconception #3: Hacks Are Sophisticated and Complex
      1. Social Engineering
      2. Network Attacks
      3. Web Application Attacks
      4. Endpoint Attacks
      5. Wrap-up
    5. Misconception #4: Hackers Have No Reason to Attack Me
      1. Motivated by Knowledge
      2. Motivated by Money
      3. Motivated by Politics
      4. Motivated by Revenge (Insider Threat)
      5. Wrap-up
    6. Misconception #5: There’s No Money in Hacking
    7. Misconception #6: Big Organizations Are the Most Secure
    8. Misconception #7: If I’m Compliant, I’m Secure
    9. Misconception #8: There’s Nothing I Can Do to Stop Hackers
      1. Flaw #1: The Gray Scale
      2. Flaw #2: No Knowledge of a Hack
    10. A Way Forward
    11. Conclusion
18.209.209.246