The Insecurity Industry — screenshot of edwardsnowden.substack.com

The Insecurity Industry

This Snowden piece articulates the systemic issues within the cyber 'security' industry, which often creates the very vulnerabilities it claims to protect, rather than solving the root cause of insecure software development.

Visit edwardsnowden.substack.com →

Questions & Answers

What is "The Insecurity Industry" about?
"The Insecurity Industry" is an article by Edward Snowden that critiques the cybersecurity sector, arguing that companies often profit by creating and exploiting vulnerabilities rather than enhancing genuine security. It highlights the systemic problems of insecure software development and the proliferation of offensive cyber capabilities.
Who is the target audience for this article?
This article is intended for individuals interested in cybersecurity, national security, privacy rights, and the ethics of technology development. It particularly resonates with those concerned about government surveillance and the role of private companies in facilitating such activities.
How does Snowden's perspective on cybersecurity differ from mainstream views?
Snowden's perspective differs by asserting that the "insecurity industry" actively contributes to the problem by developing and selling exploits, rather than solely focusing on defensive measures. He criticizes the lack of liability for insecure software, contrasting with the common narrative of an industry solely dedicated to protection.
When is it relevant to read "The Insecurity Industry"?
It is relevant to read this article when examining the broader implications of cybersecurity incidents, understanding the business model of offensive cyber tools like Pegasus, or when considering policy changes related to software liability and state-sponsored hacking. Its arguments remain pertinent in discussions about digital rights and national security.
What technical problem does the article highlight regarding software development?
The article emphasizes that a significant portion of software vulnerabilities, such as memory safety bugs, are introduced during the coding phase due to the continued use of unsafe programming languages. It suggests that choosing safer languages at the outset is a crucial, yet often neglected, protection measure.