Internal software developer

Last revision (mm/dd/yy): //

Description
Internal software developers are members of the software development team with access to change the software and some aspects of the software configuration. In many organizations, these developers will have the ability to modify any part of the software baseline. Some organizations have strict controls about what internal software developers are allowed to access in production, but others are more lax, allowing developers to make production changes.

A malicious developer is one of the most difficult threats to deal with, as it is extremely difficult to identify malicious code. A talented attacker will make attacks look exactly like an inadvertent error for plausible deniability. In addition, malicious code may be obfuscated to prevent easy detection. Some techniques include spreading an attack throughout a software baseline, using inheritance and class loading tricks to hide calls, and even formatting tricks.

Because internal software developers may have more access to production systems and more knowledge of other internal systems, they are more dangerous than outsourced software developers. However, because their actions can be tracked more closely and their job is on the line, many organizations trust them more than external developers.

Risk Factors
Internal software developers can become a threat when dissatisfied or angry with their employer. Developers commonly have a decent level of access to internal resources, knowledge of internal processes, and an implied trust with their employer, which can allow them opportunities to steal confidential information or plant malicious code.

Examples

 * Java software developer
 * SQL developer
 * Mainframe developer

Related Threat Agents

 * Contractors

Related Attacks

 * Logic/time bomb
 * Backdoor attack
 * Salami attack

Related Vulnerabilities

 * Vulnerability 1
 * Vulnerabiltiy 2