Consultants' GuidesConsultants' Guides
Blog/From BBS to Boardroom: What the Cracking Scene Taught Me About Enterprise IT
PersonalMay 22, 2024

From BBS to Boardroom: What the Cracking Scene Taught Me About Enterprise IT

I ran a BBS at 14, cracked software as SasbenJr, and trained newcomers in Mexelite. Those skills became the foundation of a 20-year enterprise IT career.

From BBS to Boardroom: What the Cracking Scene Taught Me About Enterprise IT
Microsoft Tech:Windows NTMicrosoft DefenderAzure SecurityMicrosoft Sentinel

In 1989, I was running a bulletin board system called Wildcat BBS on a phone line in my bedroom. By day, I was a teenager. By night, I was SasbenJr — a member of the cracking scene, creating intros, patching protection schemes, and training newcomers through Mexelite.

Thirty years later, I sit in boardrooms advising PE firms on cybersecurity posture. The path between those two worlds is shorter than you think.

The Scene

For those who were not there: the cracker scene of the late 1980s and early 1990s was a global underground network of people who reverse-engineered software protection. We communicated through BBS systems, traded techniques on Usenet, and competed to be the first to crack a new release.

It was not about piracy — at least not for me. It was about understanding. How does this protection scheme work? What did the developer assume about the attacker? Where is the elegant bypass? The challenge was intellectual, and the community was meritocratic — your reputation was earned through skill, not credentials.

Mexelite & Teaching

I worked with Mexelite as a trainer for upcoming crackers. The NFO files — those ASCII art text files that accompanied every release — are still in the public domain at Defacto2. The scene had a strong ethic around knowledge sharing. You learned from someone, and you were expected to teach others. Cracking 4 Newbies (C4N) was part of that tradition — structured tutorials that broke down complex protection schemes into teachable steps.

This teaching instinct never left. Today I mentor junior consultants and speak at conferences. The format changed; the impulse did not.

Skills That Transferred

1. Reverse Engineering → Security Assessment

Understanding how software protects itself is identical to understanding how organizations protect themselves. The same pattern — map the system, find the assumptions, test the boundaries — applies whether you are bypassing a dongle or assessing a company's security posture.

Today, Microsoft Defender and Microsoft Sentinel give me the tools to do at enterprise scale what I used to do with a hex editor and a debugger.

2. Assembly Thinking → Performance Optimization

When you have written assembly language to patch a binary, you understand computing at a level that most developers never reach. You know what the CPU is actually doing. This deep-systems thinking translates directly to infrastructure optimization — understanding why a system is slow, where the bottleneck lives, and what the elegant fix is.

3. BBS Culture → Community Building

Running a BBS taught me about building and moderating communities. Managing a team of 200 engineers at a global consulting firm uses the same skills — curate the culture, surface good work, handle conflict directly, and always be learning.

4. The Cracker Ethic → The Consultant's Mindset

The cracker scene valued three things: deep understanding, elegant solutions, and sharing knowledge. That is exactly what good consulting looks like. Understand the problem at its root, find the solution that is both effective and simple, and make sure the client can sustain it without you.

The Transition

In 1997, I joined Unisys Corporation and went professional. The transition was smoother than anyone expected — because the skills were the same, just applied to different targets. Instead of bypassing copy protection on a game, I was hardening Windows NT 3.51 servers. Instead of writing intros for cracked releases, I was writing automation scripts for enterprise deployments.

The Y2K remediation work was particularly ironic. The same attention to byte-level detail that made me good at cracking made me invaluable for finding and fixing date-related bugs in legacy systems.

Why This Matters

The best security professionals I have worked with share one trait: they think like attackers. Not because they are malicious, but because understanding the adversary's perspective is the only way to build effective defenses.

My years as SasbenJr gave me that perspective. And it has been the single most valuable asset in my enterprise career.

*"Once a cracker, always a cracker — just now I am paid to optimize and generate value."*

SecurityCareerHacker CultureReverse Engineering