Computerworld - Security through obscurity is probably one of the oldest tricks in the security book.
The basic premise stems from the fact that people are trying to ensure security by hiding certain facts of their software or architecture design from regular users. This is equivalent to someone hiding a house key under a pot of plants in front of his house.
However, Auguste Kerckhoffs, a 19th century Flemish cryptographer, said it should be assumed that attackers know the design of the entire security system, except for the keys. This concept, known as Kerckhoffs' law, basically rejected the notion of security through obscurity (your key hidden under your potted plant) and suggested that a system should be secure even if everything's public knowledge, except the key.
Most administrators and developers these days are somewhat familiar with the various security concepts such as virus, worm, buffer or heap overflow, cross-site scripting and SQL injection. Since these concepts are fresh in their minds, they try to take explicit precaution to avoid these traps.
However, they continue to develop software and products that rely on hiding certain trivial information, such as URL, username or other session information, and hope that users won't find them. They also try to hide this information in obvious places, such as hidden fields of a Web page or a different directory on a Web server.
A case in point: Last March, Harvard Business School, along with a few other top business schools, suffered a huge embarrassment because its admission portal had a "break-in," as university officials called it (see story). ApplyYourself.com, a company that handles applications for Harvard and other elite institutions, had a Web portal where applicants could check on the status of their applications. Generally, Harvard's decisions go out on March 30. However, one applicant had figured out a way to obtain the status before that date. This applicant then posted it on a Web site for others to try. In the end, a total of 119 applicants tried this method. After finding out, Harvard decided to reject these 119 applicants regardless of their admission status (see story). Stanford University had made similar decisions recently, rejecting 41 applicants who tried this method.
We are not here to argue whether Harvard and Stanford made the right decision or whether the action taken by the 119 applicants was ethical. However, there are some lessons to be learned here.
First of all, ApplyYourself.com's method of hiding the admission status from the applicants was a great example of security through obscurity. In order to obtain the status early,
- Warning: Cloud Data at Risk Experts agree that relying on SaaS vendors to backup and restore your data is dangerous. Yet that's exactly what huge portions of the...
- The Opportunities and Challenges of the Cloud In this report F5 poses questions to IDC analysts, Sally Hudson and Phil Hochmuth, on behalf of F5's customers to better understand the...
- Mobile First: Securing Information Sprawl Learn how the partnership between Box and MobileIron can help you execute a "mobile first" strategy that manages and secures both mobile apps...
- The Truth About Cloud Security "Security" is the number one issue holding business leaders back from the cloud. But does the reality match the perception?
- What should I look for in a Next Generation Firewall? SANS Provides Guidance With so many vendors claiming to have a Next Generation Firewall (NGFW), it can be difficult to tell what makes each one different....
- Responding to New SSL Cybersecurity Threat The featured Gartner research examines current strategies to address new SSL cybersecurity threats and vulnerabilities. All Security White Papers | Webcasts
Our new bimonthly Internet of Things newsletter helps you keep pace with the rapidly evolving technologies, trends and developments related to the IoT. Subscribe now and stay up to date!