Tribe of Hackers

Cybersecurity Advice from the Best Hackers in the World

Marcus J. Carey, Jennifer Jin

• Publisher: Wiley
• Year: 2019
• Print ISBN:
  9781119643371
• eBook ISBN:
  9781119643388
• Edition: 1
• Topic: Informatique
• Subtopic: Cryptographie

Tribe of Hackers: Cybersecurity Advice from the Best Hackers in the World (9781119643371) was previously published as Tribe of Hackers: Cybersecurity Advice from the Best Hackers in the World (9781793464187). While this version features a new cover design and introduction, the remaining content is the same as the prior release and should not be considered a new or updated product.

Looking for real-world advice from leading cybersecurity experts? You've found your tribe.

Tribe of Hackers: Cybersecurity Advice from the Best Hackers in the World is your guide to joining the ranks of hundreds of thousands of cybersecurity professionals around the world. Whether you're just joining the industry, climbing the corporate ladder, or considering consulting, Tribe of Hackers offers the practical know-how, industry perspectives, and technical insight you need to succeed in the rapidly growing information security market. This unique guide includes inspiring interviews from 70 security experts, including Lesley Carhart, Ming Chow, Bruce Potter, Robert M. Lee, and Jayson E. Street.

• Get the scoop on the biggest cybersecurity myths and misconceptions about security
• Learn what qualities and credentials you need to advance in the cybersecurity field
• Uncover which life hacks are worth your while
• Understand how social media and the Internet of Things has changed cybersecurity
• Discover what it takes to make the move from the corporate world to your own cybersecurity venture
• Find your favorite hackers online and continue the conversation

Tribe of Hackers is a must-have resource for security professionals who are looking to advance their careers, gain a fresh perspective, and get serious about cybersecurity with thought-provoking insights from the world's most noteworthy hackers and influential security specialists.

1
Marcus J. Carey

“Even if an organization is compromised by a zero-day attack, the lateral movement, registry manipulation, network communications, and so on, will be apparent to a mature cybersecurity practitioner and program.”

Twitter: @marcusjcarey • Website: https://www.linkedin.com/in/marcuscarey/

Marcus J. Carey is a cybersecurity community advocate and startup founder with more than 25 years of protecting government and commercial sensitive data. He started his cybersecurity career in U.S. Navy cryptology with further service in the National Security Agency (NSA).

If there is one myth that you could debunk in cybersecurity, what would it be?

The biggest myth that I hear is how attackers are always changing up their tactics. While it is true that new exploits come out over time, the initial exploit is just the tip of the iceberg when it comes to attacker movement on a system or network.

Even if an organization is compromised by a zero-day attack, the lateral movement, registry manipulation, network communications, and so on, will be apparent to a mature cybersecurity practitioner and program. So, their tactics don’t really change a lot.

What is one of the biggest bang-for-the-buck actions that an organization can take to improve its cybersecurity posture?

The easiest thing an organization can do to prevent massive compromise is to limit administrative accounts on systems. In the military, we obeyed the “least privilege principle” when it came to information access. Organizations should do the same when it comes to their own administrative access. If attackers are able to compromise a user with administrative credentials, it’s essentially game-over; they now have all the keys to the castle.

How is it that cybersecurity spending is increasing but breaches are still happening?

Unfortunately, I believe that we are spending too much money on cybersecurity products that bill themselves as silver bullets. Another thing is that there will always be breaches. Anything connected to a network can be compromised and the information pilfered. What really matters is can an organization detect and defend the attacks?

I recommend that organizations get the basics down really well before they blow money on a lot of products. Instead, organizations should hire and train people to defend their networks. In most cases, I’ve found that there isn’t enough investment in the personnel responsible for securing networks.

Do you need a college degree or certification to be a cybersecurity professional?

Years ago, the answer would certainly have been “Yes, you need a college degree.” When I was growing up, I was told that I needed to go to college. All of the “successful people” I knew had some form of higher education. Luckily, I went to the military and was able to eventually earn a master’s in network security. I still believe I needed it back then and surely do not regret anything.

However, this is 2019, and I do not feel this way anymore. My son has been working as a software developer for a cybersecurity company since he was 16 years old. In technology, especially software development, you can prove your knowledge through blogging, podcasting, and working on open source projects. GitHub is the new résumé for software developers.

I understand that college degrees or certifications are still valid because they show minimal mastery of a subject matter. But nowadays, there are so many more ways to show actual experience. So, in short, my answer to this question is yes, no, maybe, and it depends.

How did you get started in the cybersecurity field, and what advice would you give to a beginner pursuing a career in cybersecurity?

I remember being fascinated by computers ever since I saw the movie WarGames. I never had a computer growing up, but I did take a few classes on coding in middle school and high school. Since I couldn’t afford to go to college and really wanted to, I joined the U.S. Navy for the Montgomery G.I. Bill.

I scored pretty well on my ASVAB (military aptitude test). At the military processing center, I told them that I didn’t care what job I got as long as it had to do with computers. I was told I would be training at a school for cryptologic technical communications. It ended up being awesome. It allowed me to work for the Naval Security Group and the National Security Agency for the first eight years of my adulthood. I learned a lot about cryptography, telecommunications, system administration, basic programming, and internetworking.

The military isn’t for everyone, but it definitely helped me. I always tell anyone considering the military route to demand from their recruiter a career field and skills that are applicable to the civilian world.

What is your specialty in cybersecurity, and how can others gain expertise in your specialty?

I’d say my specialty is understanding internetworking really well. I gained these skills while working in the Navy and at the NSA. A big part of gaining expertise in that subject was reading a lot of books and taking several Cisco Systems certifications. After getting the certifications, I was in a better position to practice related skills and gain even more experience.

My advice is to try as hard as you can to validate your knowledge so that others will give you a chance. This is extremely important. Every time I acquired a certification, I was given so many more opportunities. Eventually, I was the first military service member to become part of the NSA’s global network engineering team. That was a big deal, and I learned a lot from my time there.

What is your advice for career success when it comes to getting hired, climbing the corporate ladder, or starting a company in cybersecurity?

I’ll take a swing at a couple of these. First, my advice for getting hired is to look at job postings and reverse engineer them. Create a résumé that mirrors what they are asking for if you already have the skills. If you don’t have the skills, I recommend using your free time to learn those missing skills by reading, using open source software, and consuming any free training you can find. I’ve found that even if you don’t have the necessary degree, years of experience, or certifications, there is still hope. Don’t limit yourself and think that you aren’t good enough for a job based solely on those requirements. If you believe that you have the skills to do a job, you should always apply.

Starting a company in cybersecurity has been one of the most grueling processes I have ever been through. There are typically two types of companies: those that sell products and those that ...

Table of contents

• Cover
• Title Page
• Copyright
• Acknowledgments
• Introduction
• Chapter 1. Marcus J. Carey
• Chapter 2. Ian Anderson
• Chapter 3. Andrew Bagrin
• Chapter 4. Zate Berg
• Chapter 5. Cheryl Biswas
• Chapter 6. Keirsten Brager
• Chapter 7. Evan Booth
• Chapter 8. Kyle Bubp
• Chapter 9. Lesley Carhart
• Chapter 10. Lee Carsten
• Chapter 11. Whitney Champion
• Chapter 12. Ming Chow
• Chapter 13. Jim Christy
• Chapter 14. Ian Coldwater
• Chapter 15. Dan Cornell
• Chapter 16. Kim Crawley
• Chapter 17. Emily Crose
• Chapter 18. Daniel Crowley
• Chapter 19. Winnona DeSombre
• Chapter 20. Ryan Dewhurst
• Chapter 21. Deidre Diamond
• Chapter 22. Ben Donnelly
• Chapter 23. Kimber Dowsett
• Chapter 24. Ronald Eddings
• Chapter 25. Justin Elze
• Chapter 26. Robert Graham
• Chapter 27. Claudio Guarnieri
• Chapter 28. Ron Gula
• Chapter 29. Jennifer Havermann
• Chapter 30. Teuta Hyseni
• Chapter 31. Terence Jackson
• Chapter 32. Ken Johnson
• Chapter 33. David Kennedy
• Chapter 34. Michelle Klinger
• Chapter 35. Marina Krotofil
• Chapter 36. Sami Laiho
• Chapter 37. Robert M. Lee
• Chapter 38. Kelly Lum
• Chapter 39. Tracy Z. Maleeff
• Chapter 40. Andy Malone
• Chapter 41. Jeffrey Man
• Chapter 42. Jim Manico
• Chapter 43. Kylie Martonik
• Chapter 44. Christina Morillo
• Chapter 45. Kent Nabors
• Chapter 46. Wendy Nather
• Chapter 47. Charles Nwatu
• Chapter 48. Davi Ottenheimer
• Chapter 49. Brandon Perry
• Chapter 50. Bruce Potter
• Chapter 51. Edward Prevost
• Chapter 52. Steve Ragan
• Chapter 53. Stephen A. Ridley
• Chapter 54. Tony Robinson
• Chapter 55. David Rook
• Chapter 56. Guillaume Ross
• Chapter 57. Brad Schaufenbuel
• Chapter 58. Chinyere Schwartz
• Chapter 59. Khalil Sehnaoui
• Chapter 60. Astha Singhal
• Chapter 61. Dug Song
• Chapter 62. Jayson E. Street
• Chapter 63. Ben Ten
• Chapter 64. Dan Tentler
• Chapter 65. Ben Tomhave
• Chapter 66. Robert “TProphet” Walker
• Chapter 67. Georgia Weidman
• Chapter 68. Jake Williams
• Chapter 69. Robert Willis
• Chapter 70. Robin Wood
• Epilogue
• Bibliography
• End User License Agreement