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
Russian Hackers Pilfered Data from NSA Contractor's Home Computer: Report
Threaded  |  Newest First  |  Oldest First
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
10/6/2017 | 1:59:03 PM
Whose fault?
Contractor --- using a "home" computer without, probable, good security protocols for NSA based high secret work.  What is wrong here?  WHOEVER put the contractor IN there is at fault for not stressing YOU DO NOT DO GOVERMNENT WORK AT HOME!!!  Again, almost Hillary's famous server.  Without at least high end firewalls and such --- well, no wonder it was hacked and HAVING NSA DATA  ON IT is a serious, legal breach indeed.  Do not blame Kapersky on this one. 
Kelly Jackson Higgins
0%
100%
Kelly Jackson Higgins,
User Rank: Strategist
10/6/2017 | 2:36:50 PM
Re: Whose fault?
We just posted an updated report that it was actually an NSA employee, not a contractor. Either way, it's not okay that the nation's spy agency can't keep its classified data safe. Also, if you're going to go back to the email server story, you should also include the recent news about the Kushner & Ivanka Trump personal email accounts being used for White House business, and then being moved to the Trump organization's server. More examples of lax security for sensitive government operations.

Anyway, here's the latest on the NSA:

Russian Hackers Targeted NSA Employee's Home Computer

https://www.darkreading.com/attacks-breaches/russian-hackers-targeted-nsa-employees-home-computer-/d/d-id/1330071?
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
10/6/2017 | 2:46:59 PM
Re: Whose fault?
You are quite right on email - and there are thousands MORE stories like it - plus ancient mainframe systems being unable to do GLOBAL email, only inernal email.  Reminds me of the old IBM PROFS system - internal email only used by IBM ONLY and nobody who used it had resume value OUTSIDE of IBM. 

And the most recent story about a hacker getting into White House email as Jared Kushner tool

AND the legendary, scare the hell out of you story about China hacking the NUCLEAR FOOTBALL once!!!
Kelly Jackson Higgins
0%
100%
Kelly Jackson Higgins,
User Rank: Strategist
10/6/2017 | 2:54:19 PM
Re: Whose fault?
And don't forget John Kelly's pwnd phone: https://www.darkreading.com/vulnerabilities---threats/john-kellys-personal-phone-compromised/d/d-id/1330068?

=O
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
10/6/2017 | 3:21:52 PM
Re: Whose fault?
I suppose we may all be thankful that the USA Nuclear command and control seems to be hosted on 1970s vintage mainframe systems of which NOBODY remembers HOW to hack and invade?   Those old System/370 systems, S/34 - 36 and 38 go on forever.  
Kelly Jackson Higgins
0%
100%
Kelly Jackson Higgins,
User Rank: Strategist
10/6/2017 | 3:25:39 PM
Re: Whose fault?
Mainframes for the win!
jsmwaste
50%
50%
jsmwaste,
User Rank: Apprentice
10/11/2017 | 1:25:34 PM
Re: Whose fault?
Nice infomartion..Thanks for sharing
LouiseMiller
50%
50%
LouiseMiller,
User Rank: Apprentice
10/10/2017 | 9:11:04 AM
Re: Whose fault?
And they are always here - hackers 
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
10/9/2017 | 3:22:22 PM
Re: Whose fault?
> actually an NSA employee, not a contractor.

That's kind of worse, no?

I certainly support work-from-home and telecommuting, but when you're talking about that kind of high-level government work, things need to be vetted for the home office.
rdusek483
50%
50%
rdusek483,
User Rank: Apprentice
10/7/2017 | 8:08:48 AM
Security Corrective Action
Internal-External Airgapping needed . . .
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
10/9/2017 | 2:43:27 PM
Re: Security Corrective Action
The virtue of simplicity.  How about NO GOVERNMENT-PRIVATE DATA EVER EVER EVER on a "home" system particularly if you are dealing with SECURITY CLEARANCE ISSUE!!!    I think conseqiuences such as termination, lawsuit, jail can be persuasive.  A home computer IS NOT secure and most government systems sure are not either.  But to add pain to the pudding through a home system exposure is a violation of every sane security law in the book!!!!  RTFM as they used to say ages ago. 
Joe Stanganelli
0%
100%
Joe Stanganelli,
User Rank: Ninja
10/9/2017 | 3:27:43 PM
Re: Security Corrective Action
>  I think conseqiuences such as termination, lawsuit, jail can be persuasive. 

While I don't disagree with your overall reaction, there are certain problems with immediately going to extreme retributive measures when it comes to this stuff. At the end of the day, it's shadow IT -- and if you unrelentingly flog the peasants every time something like this comes to light, you're going to discourage self-reporting of security incidents for other employees who may be violating IT rules.

Perhaps the employee should be fired, but that shouldn't be the one-size-fits-all insta-solution for every IT violation. Otherwise, you risk not finding out about compromises until it's far too late because employees will fear for their jobs.
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
10/10/2017 | 7:31:02 AM
Re: Security Corrective Action
If the data in question was merely QUARTLERLY ERESULTS for a public company, I would agree.  But this is NATIONAL SECURITY data!!!  We are on a different scale here.  This material HAS to be classified!!!!!  This is not a powerpoint presentation of the 2017 Kick off meeting at Atlanta.  And what about COMMON SENSE for a contract worker?  Or emplooyee for that matter.  No, we are dealling with national secrets!!!  Different ball game. 
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
10/10/2017 | 4:48:33 PM
Re: Security Corrective Action
@REISEN: To clarify: I 100% agree about the severity of the situation, which absolutely must go into account -- as must the role of the particular employee (big difference, for instance, between, say, an IT worker and a public-relations admin).

At the same time, speaking generally and not necessarily on this particular incident, the severity of the situation has to be taken into account the other way too. Some situations do call for extreme measures, but if every reaction is one of draconian you-know-what-to-the-wall maximum punishment, then you greatly risk decreased self-reporting of highly serious situations involving highly sensitive data. Everything is a balancing act.

More on my take here, including insights from another federal agency that deals with highly sensitive data: enterprisenetworkingplanet.com/netsysm/minimize-shadow-it-damage-by-encouraging-self-reporting.html


Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-14905
PUBLISHED: 2020-03-31
A vulnerability was found in Ansible Engine versions 2.9.x before 2.9.3, 2.8.x before 2.8.8, 2.7.x before 2.7.16 and earlier, where in Ansible's nxos_file_copy module can be used to copy files to a flash or bootflash on NXOS devices. Malicious code could craft the filename parameter to perform OS co...
CVE-2020-11441
PUBLISHED: 2020-03-31
phpMyAdmin 5.0.2 allows CRLF injection, as demonstrated by %0D%0Astring%0D%0A inputs to login form fields causing CRLF sequences to be reflected on an error page.
CVE-2020-1712
PUBLISHED: 2020-03-31
A heap use-after-free vulnerability was found in systemd before version v245-rc1, where asynchronous Polkit queries are performed while handling dbus messages. A local unprivileged attacker can abuse this flaw to crash systemd services or potentially execute code and elevate their privileges, by sen...
CVE-2019-10180
PUBLISHED: 2020-03-31
A vulnerability was found in all pki-core 10.x.x version, where the Token Processing Service (TPS) did not properly sanitize several parameters stored for the tokens, possibly resulting in a Stored Cross Site Scripting (XSS) vulnerability. An attacker able to modify the parameters of any token could...
CVE-2019-14880
PUBLISHED: 2020-03-31
A vulnerability was found in Moodle versions 3.7 before 3.7.3, 3.6 before 3.6.7, 3.5 before 3.5.9 and earlier. OAuth 2 providers who do not verify users' email address changes require additional verification during sign-up to reduce the risk of account compromise.