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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
Sony Hackers Knew Details Of Sony's Entire IT Infrastructure
Newest First  |  Oldest First  |  Threaded View
Page 1 / 4   >   >>
ODA155
50%
50%
ODA155,
 User Rank: Ninja
12/22/2014 | 9:38:50 AM
Re: Just throwing jet fuel on the fire
@Joe Stanganelli,... First, I love the disclaimer... ad you do make good points too. Whoever, the biggest problem that I see coming out of this is the ONLY point of view is that Sony is the victim, and because that's all the media and "talking heads" seem to be interested in, which I guess is true when you look at it from the view of "who was hacked". But as I have said in other places, Sony has allot to answer for, they've been hacked at lease three times in 5 years, but that hasn't been discussed, which begs the question, "just how easy is it to gain access to that network?".

In my opinion this event, because it involves North Korea, we should be looking at our privately owned (national) infrastructure of public utilities, water, electric... other power generation and banking. It's been proved many times over that some of these critical systems are open to the Internet, if not vulnerable to a dedicated script-kiddy. We (the US) invented STUXNET... Duqu... Flame and possibly others that we haven't heard about (yet). I don't know about you but there is no way that I can believe that America is the only "Nation State" with this capability, we're just the only ones whose been caught using it.  We're wasting time.

 
Joe Stanganelli
50%
50%
Joe Stanganelli,
 User Rank: Ninja
12/22/2014 | 7:02:14 AM
Re: Just throwing jet fuel on the fire
One thing that's often overlooked (of course, it has rarely sought to be enforced except when sexting is involved) when it comes to reporting on hacked/leaked info is the issue of intellectual property.

To report on a few facets, for instance, of Amy Pascal's emails would not be an IP violation, but it would potentially be a copyright infringement to copy the emails wholesale (as the hackers have done).

 

(Disclaimer: The above is provided for informational, educational, and/or entertainment purposes only. Neither this nor other posts here constitute legal advice or the creation, implication, or confirmation of an attorney-client relationship. For actual legal advice, personally consult with an attorney licensed to practice in your jurisdiction.)
Joe Stanganelli
50%
50%
Joe Stanganelli,
 User Rank: Ninja
12/22/2014 | 6:59:12 AM
Re: "Shut it all down"
@ODA: I wasn't endorsing it; I was merely pointing out the fact that it happens.
aws0513
50%
50%
aws0513,
 User Rank: Ninja
12/15/2014 | 12:02:50 PM
Just throwing jet fuel on the fire
Sony is apparently riding on a different rail now.
Sony just issued a cease and desist letter to three different major news media outlets telling them to stop reporting on the content of the hacked information.
(I'm sure you can find the details behind this latest development on several news media outlets by now.)

To me...  this is not a good method for conducting damage control for this kind of situation. 
It will simply call more vultures to the feast.

It does raise the question on what rights the press has with "non-regulatory" exfiltrated content released by hackers and what rights the victims of such attacks may have for the same content.

I know this isn't a 100% IT security concern, but it does feed in to damage control and contingency plans for fluid situations where non-regulatory data is involved.
ODA155
50%
50%
ODA155,
 User Rank: Ninja
12/15/2014 | 9:57:49 AM
Re: "Shut it all down"
So... in affect, it's OK to be mad (as we should) when the NSA breaks the law and it's also OK to ask them to break the law when it suits us?
Joe Stanganelli
50%
50%
Joe Stanganelli,
 User Rank: Ninja
12/14/2014 | 11:44:39 PM
Re: "Shut it all down"
Sure -- but information the NSA garners appears to have been/be being used for law enforcement purposes.  So the semantics/pedantics don't really make much difference here, yes?
ODA155
50%
50%
ODA155,
 User Rank: Ninja
12/13/2014 | 10:57:00 AM
Re: "Shut it all down"
Collaboration and actual enforcement are two separate things... wouldn't you agree?
Joe Stanganelli
50%
50%
Joe Stanganelli,
 User Rank: Ninja
12/12/2014 | 8:52:48 PM
Re: "Shut it all down"
Point of information: The Snowden docs etc. revealed that the NSA does collaborate and give information from their SIGINT ops to other actual domestic law enforcement agencies, like the DEA.
ODA155
50%
50%
ODA155,
 User Rank: Ninja
12/9/2014 | 12:52:22 PM
Re: "Shut it all down"
@Technocrati,... "This is the real truth of it all. It is blatantly evident that most enterprise security is well behind the abilities of serious hackers."

I disagree somewhat to that statement because while it is true that security department are "behind", I don't think it's because of a lack of expertise. In my experience I would argue that security is naturally behind because a) you don't know if it works until it's been tested in the real world, in other words you don't know what the next thing is going to be so you do the usuaul protective things try to plan for what is being reported and react if you need to. Then b), security will always lag behind unless someone can make a really compelling case for spending what it REALLY takes or someone in management understands and gets it. The business makes the money and security spends money, it doesn't make a dime, we're takers and if you haven't tried to convience management to spend money and resources on something that you cannot prove or justify is going to happen tomorrow, fuhgeddaboudit, they'll keep blowing you off until "next quarter", in other words... fuhgeddaboudit.
Technocrati
50%
50%
Technocrati,
 User Rank: Ninja
12/8/2014 | 4:53:43 PM
Re: insider?

"...I wonder if we'll ever find out what really happened here."

 

 

I don't know that that really matters.   The who dun it question really does not address the issue of why supposed "high end security" is constantly being breeched. 

Companies seem to be fooling themselves and "security" is quickly becoming a question of just how much data and sensative information you want to expose to risk, that is if you have the choice.

Page 1 / 4   >   >>


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
How Enterprises Are Assessing Cybersecurity Risk in Today's Environment
The adoption of cloud services spurred by the COVID-19 pandemic has resulted in pressure on cyber-risk professionals to focus on vulnerabilities and new exposures that stem from pandemic-driven changes. Many cybersecurity pros expect fundamental, long-term changes to their organization's computing and data security due to the shift to more remote work and accelerated cloud adoption. Download this report from Dark Reading to learn more about their challenges and concerns.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-0338
PUBLISHED: 2022-01-25
Improper Privilege Management in Conda loguru prior to 0.5.3.
CVE-2022-23935
PUBLISHED: 2022-01-25
lib/Image/ExifTool.pm in ExifTool before 12.38 mishandles a $file =~ /\|$/ check.
CVE-2021-46481
PUBLISHED: 2022-01-25
Jsish v3.5.0 was discovered to contain a memory leak via linenoise at src/linenoise.c.
CVE-2021-46482
PUBLISHED: 2022-01-25
Jsish v3.5.0 was discovered to contain a heap buffer overflow via NumberConstructor at src/jsiNumber.c.
CVE-2021-46483
PUBLISHED: 2022-01-25
Jsish v3.5.0 was discovered to contain a heap buffer overflow via BooleanConstructor at src/jsiBool.c.