Skip to content

Unsecurity Episode 225: Hacks & Hops Panel Discussion

MichaelMeganBradOscarBrian KrebsAlex HoldenPeter Foy

Engineers explore architecture and security mechanisms for Unsecurity Episode 225: Hacks & Hops Panel Discussion.

Summary

### Overview In this panel discussion from the Hacks & Hops event (featured on Unsecurity Episode 225), cybersecurity professionals explore the human, ethical, and operational realities of the information security industry. Rather than focusing purely on technical exploit mechanics, the discussion centers on navigating ethical dilemmas in consulting and sales, responding to complex incident response scenarios, and confronting the high levels of stress and mental health challenges facing practitioners and leadership across the sector.

### Key Topics - **Ethical Dilemmas and Industry Truthfulness**: The panelists address ethics within infosec, pointing out vendor sales practices that overpromise, herd mentality in purchasing tools organizations cannot properly configure, and pressure from clients or legal teams to omit unfavorable findings from assessment and incident response reports. Panelists emphasize telling the truth—differentiating lies of commission from lies of omission—and establishing firm personal and organizational boundaries. - **Emerging Tech, Buzzwords, and AI**: The conversation touches on how new developments like AI, deepfakes, and recycled buzzwords (such as zero trust) complicate ethical boundaries and risk management, noting that while the fundamental ethical questions remain similar, technology alters how easily unethical acts can be executed, hidden, or detected. - **Incident Response Complexities**: The speakers reflect on real-world incidents, emphasizing that poor organizational response, denial, and lack of containment often cause more difficulty than the technical breach itself. Key challenges include internal embezzlement, employee policy violations, clients failing to prioritize active compromises, and chaotic multi-agency responses lacking clear coordination. - **Organizational Preparedness and Blame Culture**: Discussion focuses on the critical need for business impact analyses (BIAs) and pre-established communication channels. The panel highlights how victim-shaming employees for clicking malicious links creates concealment behaviors that delay triage and remediation. - **Mental Health, Burnout, and Leadership**: The session delves deeply into mental health strains within cybersecurity, discussing impostor syndrome, anxiety, depression, neurodiversity (such as managing ADHD), and suicide. Panelists discuss ways leaders can foster safe, honest cultures through open communication, leading by example, destigmatizing mental health, and supporting colleagues in crisis.

### Technical Details - **Incident Response & Containment Realities**: Panelists share specific case scenarios, including investigating a distressed bank takeover that uncovered a 12-year embezzlement scheme exceeding one million dollars, handling an internal help desk technician pirating content over a Cisco VoIP phone network, and an early web defacement via SQL injection against a Jasc Software server. - **Coordinating Multi-Party Breach Events**: One speaker recounted a ransomware incident at a large health system where on-site responders included CISA, the FBI, local sheriff deputies, insurance representatives, and multiple incident response teams. Responders discovered an uncontained site-to-site VPN link connecting into another health system customer, requiring immediate secondary threat hunting while navigating external media inquiries and claims from Russian threat forums alleging coordinated attacks. - **Operational Resistance**: Another scenario highlighted a compromised law firm where IT technicians spent two months actively uninstalling security monitoring tools because they felt the tools were slowing down endpoint machines, blinding security teams to ongoing outbound malicious traffic.

### Takeaways - **Prioritize Integrity Over Revenue**: Security practitioners must commit to transparent reporting and resist pressures from clients or internal sales teams to gloss over critical vulnerabilities or breach details. - **Build Preparedness Before the Breach**: Organizations must establish clear incident response plans and define command structures in advance to avoid panic, uncoordinated external escalations, and neglected containment. - **Eliminate Victim Shaming**: Fostering an open reporting culture encourages users and staff to report suspected compromises or credential disclosures immediately without fear of reprimand. - **Actively Support Mental Health**: Leaders must normalize conversations around stress, burnout, and mental health, model vulnerability, respect individual work-life balance needs, and directly check in on peers and team members.

Related talks