Comments
Newest First | Oldest First | Threaded View
Target Data Breach - Fazio
For all that I have read here, I have not heard anyone mention that Target may have given Fazio access to an RDP server to run necessary applications for billing and PM. It sounds too easy, but definitley plausible. In this case once the Fazio machine(s) was comprimised with maybe a key logger, the hackers identified the "link" when sifting thorugh their catch. At that point the liability is on Target for allowing systems used for POS, etc to be exposed and vulnerable to systems that are external/clinet/contractor facing. Fazio owns part of this, but Target has a the bulk of the responsiblity.
Could they have targeted Target exclusivley... YES. There is tons of public info about contracts and... they also placed info on a public facing server / webpage. Its my opinion that this is going to get real real messy for Fazio. Target may recover, but will never be the same. This on is just too big.
Could they have targeted Target exclusivley... YES. There is tons of public info about contracts and... they also placed info on a public facing server / webpage. Its my opinion that this is going to get real real messy for Fazio. Target may recover, but will never be the same. This on is just too big.
Re: Thanks for updating
rradina, you raise some interesting possibilities here. I don't have enough information to comment on them, but one thing's for sure, it would be a great service to the community if forensics investigators shared what they learned and what steps companies should take, and should have taken. True hackers will just find another way to exploit the IT ecosystem. But if companies do more to take a "neighborhood watch" approach, rather than minding their own "house's" security, hackers at least might look elswhere.
Re: Thanks for updating
I missed that. However, that raises new concerns. If by "data connection", they mean some kind of private link with Target so they can perform these duties, it's not difficult to envision lax firewall rules or an unpatched "Intranet" server that was vulnerable. Hackers owned Fazio's PC(s) so they could attack any system Fazio was capable of reaching through that data link. Billing and project management servers are probably "Intranet" servers. They could have easily been running a dated and unsupported version of Windows because the software suite was not compatible with later versions. Once compromised, it was behind the firewall on a VLAN that probably had broad access to many corporate data center resources (backup servers, file servers, database servers, etc.). From there they could have hacked any number of systems until they found one that could talk to the retail POS systems.
Re: Thanks for updating
The point was, it does not appear that the hackers got to Target through the HVAC control systems, but rather...the contractor's access to Target's network was limited to business-related administrative purposes. As he was quoted here: "Our data connection with Target was exclusively for electronic billing, contract submission, and project management, and Target is the only customer for whom we manage these processes on a remote basis. No other [Fazio] customers have been affected by the breach."
How the hackers used that information to get to the credit card files is an important questions, still to be determined.
How the hackers used that information to get to the credit card files is an important questions, still to be determined.
Re: Thanks for updating
It's not the first occurrence of hackers attacking a climate control system vulnerability to gain greater access to sensitive company data.
Thanks, IoT! :p
Thanks, IoT! :p
Re: Random or targeted
I have to think this was not random. At least to the point that they knew they were going to get into more by hacking Fazio. They must have known they had contracts with Target and others. What else did they hack and maybe no one has discovered it yet?
I have to think this was not random. At least to the point that they knew they were going to get into more by hacking Fazio. They must have known they had contracts with Target and others. What else did they hack and maybe no one has discovered it yet?
Who will be made responsible?
This will be interesting to see if the HVAC contractors are found to be liable in any way. I'm sure their security will be looked at closely.
Re: Thanks for updating
"What's still not clear, however, is how attackers might have parlayed Fazio's access credentials for Target's electronic billing, contracts, or project management system into full-blown access to the retailer's IT network and payment processing systems."
From the statement above, how do we know it was the accounting system? The quote is a "theory" because it uses the terms "might have". Am I missing another story?
Until someone comes clean with incredible detail, we're all throwing mud at the wall. Granted, the more that comes out the closer our mud gets but we're still just guessing. We don't even know if the credentials stolen via Fazio were instrumental before or after an initial breach. We may never know unless we catch the perpetrators and they spill the beans.
From the statement above, how do we know it was the accounting system? The quote is a "theory" because it uses the terms "might have". Am I missing another story?
Until someone comes clean with incredible detail, we're all throwing mud at the wall. Granted, the more that comes out the closer our mud gets but we're still just guessing. We don't even know if the credentials stolen via Fazio were instrumental before or after an initial breach. We may never know unless we catch the perpetrators and they spill the beans.
Thanks for updating
Thanks for continuing to follow this story and set the record straight about the HVAC contractor implicated in the Target breach. In particular: For making it clear, based on what now seems to be known, that the hackers used an accounting system, not the HVAC system to break in and that the contractor likely was unwittingly caught in a very large phish net. As the number of companies granting network exchange privileges to one another continues to grow, so will the collateral damage as hackers continue to perfect their skills.
White Papers
Video
0 Comments
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Security Vulnerabilities: The Next WaveJust when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
The Dark Reading Security Spending Survey
Enterprises are spending an unprecedented amount of money on IT security — where does it all go? In this survey, Dark Reading polled senior IT management on security budgets and spending plans, and their priorities for the coming year. Download the report and find out what they had to say.
Twitter Feed
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...
CVE-2016-10369NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).
CVE-2016-8202unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...
CVE-2016-8209A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.
CVE-2017-0890Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.
- Terms of Service
- Privacy Statement
- Legal Entities
- Copyright © 2017 UBM, All rights reserved
Tweet This
User Rank: Apprentice
3/11/2014 | 10:32:47 AM
Even as a small IT Service company we have to go through PCI compliance. Are these big companies too big that they dont have anyone who can see the big picutre? Do they perform 3rd party security audits? If so - why wasnt this found. If not - wow - they hold millions of credit card numbers and probably lots of Personal Information which must be protected - and they did nothing to think about security? Wow!