Assume attackers have source code

Revision as of 00:03, 28 May 2009 by Deleted user (Talk | contribs)

Jump to: navigation, search

[ oppose euthanasia ] [ online auctions ebay auto auction ] [ auto serve nh ] [ australian shepherd rescue canada ] [ australian open tournament prize money ] [ automated meter reading plc ] [ auto freight shipping ] [ australia federation in ] [ asian pacific islander history ] [ auto auto store store zone zone ] [ southern cross broadcasting australia ] [ 3 auto cheat cheat grand in planet theft ] coastlines of australia [ technical automotive group ] [ african spur thigh tortise ] avast avg antivirus [ timeshare south africa ] [ automotive cross number part reference ] [ asian massage male ] [ computer associates antivirus download ] [ south asia world tv ] [ grand theft auto san andraes cheats for ps2 ] domain [ australia visitors bureau ] [ pc penicillin antivirus ] map africas allied food site south union web worker [ symantec antivirus communications layer failed to initialize ] [ mature asian women dao ] auto calculator comparison loan [ how to uninstall norton antivirus 2005 ] [ asian free girl thumb ] [ autoloc power antenna instructions ] [ no mans land asian edition ] [ asian gold ] [ uninstall norton antivirus corporate ] [ australia extreme korg triton ] [ american consolate south africa ] [ asia info southeast ] [ avg antivirus comparison ] [ asian film actress ] [ uthinasia ] [ african fertility symbol ] [ australia gold coast maps ] [ australian immigration and multicultural affairs ] [ stinger antivirus tools ] map [ auto restore windows xp ]

This page has been recommended for deletion.
You can help OWASP by improving it or discussing it on its Talk page. See FixME
Comment: Tagged via Template:Delete

This is a principle or a set of principles. To view all principles, please see the Principle Category page.


Secrecy of source code and other implementation details is a very weak approach to security. In fact, the secrecy of your source code is probably not nearly as good as you think. So build your applications considering that an attacker has a copy of the source code. There is no reason that having the source code makes a secure system impossible.

In most organizations, the source code for applications is stored in a Source Code Control System designed for integrity, not secrecy.

Think who has access to the code and where it might have been stored. There's likely to be a full copy of the source code on every developer's machine. They may have made backup copies in home directories or other storage. They may have taken a copy to work on at home (or possibly to reuse on other projects). The code is also probably stored on backup tapes.

The source code is also probably stored on compile servers and machines that are a part of the build process. The code (in compiled form) is also likely to have found its way to test machines, developer machines, staging servers, and also production. Compiled code is easy to reverse engineer, especially with bytecode-type languages like Java and .NET.

To say that many of these places are not as well protected as production environments is a serious understatement. So consider the threat (in your actual environment, not the way the standards say it is supposed to be) of an attacker being able to get a copy of the source code.

The good news is that having the source code shouldn't provide much of an advantage to an attacker, if you've build it with that in mind. The cryptographic community has followed this principle for decades, but many organizations cling to the notion that the secrecy of the code is critical to the security of their application.

NOTE: Some source code contains intellectual property, such as trade secret algorithms and other business processes. The secrecy of the source code is an important part of protecting this IP.


Short example name

A short example description, small picture, or sample code with links

Related Vulnerabilities

Related Controls


This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.