Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
Taking Steps To Stop Software Sabotage
Newest First  |  Oldest First  |  Threaded View
AgtX
AgtX,
User Rank: Apprentice
4/24/2013 | 8:25:07 PM
re: Taking Steps To Stop Software Sabotage
You can trend employees. Rigorous background checks won't happen in many infrastructure key corporations. If an employee behaves suspiciously with security vulnerabilities found in their code, that can be an indicator. If they consistently have security vulnerabilities in code, that can be an indicator. If they had a full blown back door, that can be an indicator.

But indicators are just indicators. Only chance where this indicator could be used is when there can be a counterintelligence investigation. For regular law enforcement situations, this kind of detection is out of the question unless the employee puts in something very obvious or talks about it to a potential witness.

PJS880
PJS880,
User Rank: Ninja
4/23/2013 | 5:38:06 PM
re: Taking Steps To Stop Software Sabotage




Is this even
possible?- Even with a system of checks
and balances there is bind to be vulnerabilities that rogue employees will
exploit. The bottom line is to trust yourself and your companies hiring an background
check measures. There is no viable solution, other than having one administrator
with all the keys, which is unrealistic. It also brings up the question what if
the administrator goes rogue. I agree that rigorous separation of departments
with multiple levels of security imposed would help reduce software sabotage,
but never eliminate it. Keep in mind there is many measure to catch it once it
has happened but to avoid it all together is obviously a challenge.

Paul Sprague

InformationWeek Contributor
-

nannasin28
nannasin28,
User Rank: Apprentice
4/16/2013 | 3:01:22 AM
re: Taking Steps To Stop Software Sabotage
Custom code is used to glue the components together.-- 78M05
marktroester
marktroester,
User Rank: Apprentice
4/12/2013 | 7:20:45 PM
re: Taking Steps To Stop Software Sabotage
Hello Ericka - thanks for the interesting article. The other angle to consider is the move to component based development and agile practices. Modern day development is dominated by components - applications are now constructed from components, many of them open source. Custom code is used to glue the components together. -It is possible that an insider could attempt to malign the application by replacing a trusted component - so it's important that organizations have the ability to maintain the integrity of the components that they use. This should be done as part of a larger component management strategy.

Mark Troester
http://www.sonatype.com/people...
Twitter:-@mtroester:twitter-
AgtX
AgtX,
User Rank: Apprentice
4/11/2013 | 1:45:38 PM
re: Taking Steps To Stop Software Sabotage
A nation based or very smart inside attacker would likely simply inject a security vulnerability which is difficult to find and even if caught would be considered to be an accidental vulnerability. That does not take much logic to figure out and the tactic is strong for them.

For web applications and the like they would also want a vulnerability which would plausibly be found by an outsider. It is routine to rate any vulnerabilities found using the factor of ease of finding as part of the threat ratio.

Proving a developer did this is next to impossible, however.

I do not think company background checks would discover someone in a dual employ of a foreign nation. And that is the most likely suspect. Because this is one of the most effective ways for nations to steal information from other nations.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Improving Enterprise Cybersecurity With XDR
Enterprises are looking at eXtended Detection and Response technologies to improve their abilities to detect, and respond to, threats. While endpoint detection and response is not new to enterprise security, organizations have to improve network visibility, expand data collection and expand threat hunting capabilites if they want their XDR deployments to succeed. This issue of Tech Insights also includes: a market overview for XDR from Omdia, questions to ask before deploying XDR, and an XDR primer.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-20109
PUBLISHED: 2022-06-29
A vulnerability classified as problematic was found in Teleopti WFM up to 7.1.0. Affected by this vulnerability is an unknown functionality of the file /TeleoptiWFM/Administration/GetOneTenant of the component Administration. The manipulation leads to information disclosure (Credentials). The attack...
CVE-2017-20110
PUBLISHED: 2022-06-29
A vulnerability, which was classified as problematic, has been found in Teleopti WFM up to 7.1.0. Affected by this issue is some unknown functionality of the component Administration. The manipulation as part of JSON leads to information disclosure (Credentials). The attack may be launched remotely....
CVE-2017-20111
PUBLISHED: 2022-06-29
A vulnerability, which was classified as critical, was found in Teleopti WFM 7.1.0. This affects an unknown part of the component Administration. The manipulation leads to improper privilege management. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and ...
CVE-2017-20112
PUBLISHED: 2022-06-29
A vulnerability has been found in IVPN Client 2.6.6120.33863 and classified as critical. Affected by this vulnerability is an unknown functionality. The manipulation of the argument --up cmd leads to improper privilege management. The attack needs to be approached locally. The exploit has been discl...
CVE-2017-20108
PUBLISHED: 2022-06-29
A vulnerability classified as problematic has been found in Easy Table Plugin 1.6. This affects an unknown part of the file /wordpress/wp-admin/options-general.php. The manipulation with the input "><script>alert(1)</script> leads to basic cross site scripting. It is possible to ...