Skip to content
Tech News
← Back to articles

Security through obscurity is not bad

read original get Cybersecurity Obfuscation Guide → more articles
Why This Matters

This article emphasizes that security through obscurity remains a valuable supplementary strategy in cybersecurity, countering the misconception that it is inherently flawed. It highlights the importance of layered security approaches, especially in protecting APIs and sensitive data from automated scraping and reverse engineering. Recognizing the role of obscurity can help developers better safeguard their applications against evolving threats.

Key Takeaways

Escaping the crowded echo chamber

I was recently reading a post by a user on a web development forum. This user, whom we’ll call Mini, was asking the community whether it was worth using JavaScript obfuscation for some of the scripts running on their website. Their main goal was to make it harder for data-scraping bots to reverse engineer and replicate the API requests powering the page.

Then I saw it: like a solo LGTM comment on a +4,156/-1,640 line PR, a comment from another user whom we'll call Echo:

Security through obscurity is bad

What was worse was that this comment had many upvotes, likely from others who had heard the phrase once and simply channelled their inner parrot to repeat it forever.

I decided to reply to Echo's comment and share my thoughts:

Security through obscurity is NOT bad.

Security ONLY through obscurity is bad (Kerckhoffs's Principle).

Security through obscurity, as an additional layer, is good!

At first, I thought this was what Echo actually meant, but to my surprise, Echo believed that all forms of obscurity were redundant and should not be used at all. They also specifically argued that, in the modern day, AI had made getting around any sort of obscurity trivial.

... continue reading