STE WILLIAMS

Third-Party Breaches – and the Number of Records Exposed

Each breach exposed an average of 13 million records, Risk Based Security found.

Third-party risks are quickly mounting for enterprise organizations if the number of data breaches and total number of records exposed as a result are any indication.

In a recent analysis of data pertaining to security breaches in 2019, Risk Based Security uncovered a sharp increase in incidents involving companies handling sensitive data for business partners and other clients. The total number of such third-party breaches hit 368 in 2019, up from 328 in 2018 and 273 in 2017 — a 35% increase in two years.

In addition, the number of records exposed in these breaches skyrocketed 273% last year, from just over 1.7 billion in 2018 to 4.8 billion in 2019. On average, some 13 million records were exposed in each third-party breach in 2019, making it easily the worst year ever on record, according to the analysis. Data exposed in these breaches ran the gamut, including names, addresses, dates of birth, Social Security Numbers, credit card numbers, email addresses, and financial data.

Risk Based Security counted a total of 7,098 data breaches in 2019 — a relatively modest increase of 1% over 2018’s 7,035 publicly disclosed data breaches. The breaches in total exposed a staggering 15.1 billion records, which included everything from relatively innocuous transaction logs to PII, financial data, and health records.

“The security landscape is just as challenging as ever,” says Inga Goddijn, executive vice president at Risk Based Security. “Given the trend over the past few years now, expect the number of events to continue to grow while the number of records exposed will be driven in large part by the number of leaky databases and services uncovered.”   

Though the overall number of breaches increased only slightly year-over-year, the number of records exposed in 2019 was some 284% greater than in 2018. But that was largely due to four incidents that alone accounted for some 8.5 billion of the 15.1 billion records in total that were exposed.

Risk Based Security identified the four breaches as involving smart home product company Orvibo; Chinese e-commerce merchant LightInTheBox; email marketing company Verifications.io; and an unknown company managing data for data aggregators including Oxydata and People Data Labs.

All four breaches resulted from data being put into open, misconfigured databases that were then made publicly accessible over the Internet to anyone. Excluding these data breaches, the total number of records exposed last year would still have been higher than the number in 2018, but by a relatively small 1.3 billion records.

Karen Bruner, technical evangelist at container security firm StackRox, says the increase in breaches involving cloud databases and services is the result of poor security hygiene. “All the major cloud providers offer the controls needed to keep the data in their cloud buckets private, but customers need to use them,” Bruner says.

Inexperienced cloud users will sometimes remove all protections when they have trouble accessing the data from applications. That inexperience often goes hand-in-hand with not doing best practices, like scanning their cloud infrastructure for security misconfigurations, she says. “And when security is set up correctly initially, it takes just one customer change to wipe it out and make the bucket contents public,” Bruner adds.

Web Breaches Exposed Most Records
As in previous years, breaches involving external hackers, malicious insiders, and from accidents and negligence outnumbered breaches stemming from other causes. However, Web breaches caused by misconfigured services and failure to follow basic hardening practices resulted in a far greater number of exposed records. For instance, though nearly 5,200 data breaches resulted from hacking, they exposed only about 1.5 billion records as compared to nearly 13.6 billion records from a mere 343 Web breaches.

Sam Rubin, vice president at incident response and risk management firm Crypsis Group, says the Risk Based Security report highlights the challenges posed by the growing complexity and attack surface of modern IT environments.

“The cloud is highly enabling, yet with so many cloud providers in the typical enterprise mix, most IT teams have multiple shared responsibility models to manage,” he says.

Smaller organizations are as likely as enterprises to use cloud providers, yet they are more challenged with the staffing needed to manage cloud security best practices. Large enterprises have more qualified staff but tend to have a more expansive multicloud terrain to navigate, he says. “And unfortunately, cloud is only one challenge companies must address,” Rubin says.

Related Content:

Check out The Edge, Dark Reading’s new section for features, threat data, and in-depth perspectives. Today’s top story: “Chaos Order: The Keys to Quantum-Proof Encryption

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year … View Full Bio

Article source: https://www.darkreading.com/attacks-breaches/third-party-breaches---and-the-number-of-records-exposed---increased-sharply-in-2019/d/d-id/1337037?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Mozilla issues final warning to websites using TLS 1.0

Sometime this March, the Firefox, Chrome, Safari and Edge browsers will start throwing up warnings when users visit websites that only support Transport Layer Security (TLS) versions 1.0 or 1.1.

Announced in October 2018 as part of a joint plan to phase out support, the implications for any holdout sites are stark – enable the later TLS 1.2 or, ideally, 1.3, or face having no traffic.

According to the latest Mozilla reminder, visitors using Firefox will start seeing a ‘Secure Connection Failed’ message with accompanying SSL_ERROR_UNSUPPORTED_VERSION for anyone in doubt.

Initially, it will be possible to override this but only for so long. Sooner rather than later, Mozilla says that too will disappear:

We’re committed to completely eradicating weak versions of TLS because at Mozilla we believe that user security should not be treated as optional.

Other browsers will follow suit, with the Chrome browser having adopted ‘Your connection to this site is not fully secure’ messages last month with full blocking due to begin in March.

Netscape Navigator

But why the need to ditch TLS 1.0 and 1.1?

Although not exactly a household name, TLS is the encryption protocol that makes several types of secure connection possible, including secure versions of SMTP, POP3, FTP and of, course, HTTP.

For example, when a browser visits a site using HTTPS, TLS sets up authentication, the exchange of session keys, and agreement on cipher suites.

To make all this work, both ends must also agree which version of TLS they will use, which is where the problems start for older versions.

Issue number one is the age of TLS 1.0 and 1.1.

As far as the IETF is concerned, TLS 1.0 has been around since 1999, building on technology invented years before that to work with Netscape’s famous but ancient Navigator browser.

TLS 1.1 arrived in 2006 but was quickly improved upon by TLS 1.2 two years later. We’re now up to TLS 1.3, support for which is appearing now.

Going from TLS 1.0 to 1.3 might not sound like a huge jump but TLS 1.3 is vastly more secure and more optimised for the speed of today’s internet – both valid reasons to ask sites to get rid of older versions.

It’s not clear how many sites still use TLS 1.0 and 1.1 – Google estimates around 0.75% of page loads – but even a small sliver of sites is now too many.

Judging from the sites cited by Google, most appear to be smaller domains which are either unmanaged or managed passively.

From March, for the want of an upgrade, these sites will start to suffer the consequences of that.


Latest Naked Security podcast

LISTEN NOW

Click-and-drag on the soundwaves below to skip to any point in the podcast. You can also listen directly on Soundcloud.

Article source: http://feedproxy.google.com/~r/nakedsecurity/~3/3oMQ9dp5jKA/

What Are Some Basic Ways to Protect My Global Supply Chain?

Assessing supply chains is one of the more challenging third-party risk management endeavors organizations can take on.

Question: What are some foundational ways to protect my global supply chain?  

Rick Holland, CISO, Digital Shadows: Assessing supply chains is one of the more challenging third-party risk management endeavors organizations can take on. A global company can easily have more than 1,000 firms in its supply chain. In the age of digital transformation, much of the supply chain consists of SaaS providers that are easier to replace than the traditional on-premises vendor. The result is a transient supply chain that continually evolves. To add even more complexity, the more mergers and acquisitions activity a firm undertakes, the more complicated its supply chain becomes. All of these factors make supply chain risk management a daunting task.

Two common deficiencies of cybersecurity supply chain programs are a lack of understanding of the types of data and access the third party possesses, as well as a prioritized list of suppliers. This is why security teams need to have robust processes in place that include both the lines of business that leverage supply chain providers and the procurement teams that handle the logistics of assessing and onboarding the vendors. The security and privacy teams must have questions that can be inserted into assessments. They should include items that give insights into what data a third party has access to, where that data resides, and who has access to it. Once an organization understands the criticality of the data a third party has access to, it can then prioritize the risk around a supplier based on the classification of that data.

With today’s technology and complexity, it isn’t pragmatic for a cybersecurity supply chain program to monitor “all the things.” However, it becomes more feasible with a prioritized list of vendors that have data or access to data that could represent a material risk to the business if stolen or abused.  

The Edge is Dark Reading’s home for features, threat data and in-depth perspectives on cybersecurity. View Full Bio

Article source: https://www.darkreading.com/edge/theedge/what-are-some-basic-ways-to-protect-my-global-supply-chain/b/d-id/1337015?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

5 Common Errors That Allow Attackers to Go Undetected

Make these mistakes and invaders might linger in your systems for years.

Although cybersecurity technologies continue evolving to address current threats, many data breaches remain undiscovered for months or even years. For instance, in one of the biggest data breaches discovered in 2018, which affected 500 million customers of the Marriott Hotel Group, hackers went undetected for four years.

How can your organization detect threats faster and reduce the chances of a breach? Unfortunately, there isn’t one solution. But we can analyze the root causes of known breaches and learn from them. In this column, we’ll examine five common errors that make it easier for attackers to linger in an IT network undiscovered and advice on how to mitigate the risks.

Error 1: Siloed security systems
During their evolution, large companies often undergo multiple mergers and acquisitions. This strategy can boost stock prices, but it can also increase both IT system complexity and data security risks. Notably, the Marriott data breach originally occurred in the reservation system of Starwood, a chain that the hotel giant acquired in 2016. Rather than unifying security controls and improving the detection capabilities of its newly acquired business right after the deal, Marriott appears to have neglected to take action, wasting two years until it discovered the data leak in November 2018.

To avoid this error, organizations should regularly review their IT systems and IT risks, especially during and after a merger or acquisition. In particular, they should discover and classify all sensitive data across their on-premises and cloud storage and take steps to ensure that those files are not overexposed and that they reside only in dedicated safe locations with proper access controls. Organizations should also update their security policies, unify them, and apply them across the entire IT infrastructure. Cross-system software solutions can make this security monitoring easier.

Error 2: Lack of accountability
Many corporations have a complex management structure that leads to poor accountability and lack of visibility into IT security policy development and execution. The infamous Equifax data breach, which remained undetected for 76 days, was made possible by an expired security certificate. A Congressional investigation found that the absence of clear lines of responsibility in Equifax’s IT management structure had kept the company from implementing security initiatives in a timely manner, which had led to more than 300 security certificates expiring.

The best way to avoid this error is to have one person responsible for the development and implementation of information security policies. In most cases, it is the chief information security officer (CISO). The CISO should develop clear policies with zones of responsibility and provide IT teams with clear workflows for the security issues for which they are accountable. Another tip is to automate patching, which mitigates the risk that overburdened IT teams will fail to make manual updates promptly. Many experts believe this strategy could have prevented the Equifax data breach.

Error 3: Lack of support from the CEO
If a company’s leader does not consider security to be a business goal, IT security teams will likely lack vital strategic direction and resources, including both adequate staffing and modern technologies. As a result, they cannot prioritize security efforts and proactively respond to evolving threats; instead, they are overwhelmed with routine troubleshooting.

Every CEO should recognize that data protection is a crucial business goal and establish a leadership-driven security approach. Regular meetings with the CISO are a must, as are metrics that evaluate the effectiveness of the cybersecurity strategy. Equally important is enabling the IT team to focus on issues that are critical to the safety of the business by investing in modern solutions that automate most security processes and can be scaled up easily as the business grows.

Error 4: Inefficient cybersecurity strategy
Some organizations spend vast sums of money on technologies in an effort to cover all IT risks. However, unless they conduct a thorough risk assessment, they might well have spent their money in vain. For example, a company might spend a lot of money to store and protect its data, including stale data, but miss an unauthorized access to its customer database.

Security efforts should be prioritized. Start with an IT asset inventory that will help to you identify and classify your most crucial information assets, such as data that falls under the General Data Protection Regulation (GDPR). Using that information, develop security policies to appropriately protect data with each level of sensitivity and an effective incident response plan. Last but not least, it’s important to set up alerts so you can respond quickly to suspicious activity.

Error 5: No actionable incident response plan
A recent Netwrix study shows that only 17% of organizations test their incident response plans. The remaining 83% have no guarantee that their plan will work out in real life; in case of an incident, they might waste precious time and fail to notify customers and authorities properly.

Initiating a pseudo-cyberattack as a part of penetration testing is a good idea. This will help to determine if your draft plan is effective and ensure that everyone knows exactly what to do if an incident occurs. The results of the test should be used to improve the plan and develop regular practice runs for employees.

Conclusion
The only way for organizations to avoid long-lasting data breaches is to ensure that their cybersecurity strategy is an ongoing focus rather than a one-off exercise that’s soon forgotten. A forward-thinking business leader should manage cybersecurity risks on an equal footing with all other business risks and treat cybersecurity as an organizationwide issue. Creating a security-centric culture requires a joint effort by various departments that involves technology, processes, and people. With centralized IT governance and a bird’s-eye view of the IT infrastructure, businesses can be far more confident that unauthorized activity will be detected and terminated quickly.

Related Content:

Check out The Edge, Dark Reading’s new section for features, threat data, and in-depth perspectives. Today’s top story: “From 1s 0s to Wobbly Lines: The Radio Frequency (RF) Security Starter Guide

Matt Middleton-Leal is General Manager and Chief Security Strategist is at Netwrix, a software company that enables information security and governance professionals to reclaim control over sensitive, regulated and business-critical data, regardless of where it resides. Matt … View Full Bio

Article source: https://www.darkreading.com/attacks-breaches/5-common-errors-that-allow-attackers-to-go-undetected/a/d-id/1336955?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

5G Adoption Should Change How Organizations Approach Security

With 5G adoption, businesses will be able to power more IoT devices and perform tasks more quickly, but there will be security ramifications.

Last year, all four wireless carriers began offering 5G, and people couldn’t be happier. While some may have to wait until devices and infrastructure fully catch up with demand, the promise of being able to communicate and download at speeds of up to 10Gbps has users and companies eagerly anticipating a very speedy future.

5G promises super-high bandwidth and throughput and ultra low-level latency communication that are up to 20 times faster than 4G LTE. 5G can reach speeds of 20GB per second, while 4G LTE maxes out at 1GB per second. While this is a nice-to-have in many situations, businesses are looking forward to 5G adoption to power more Internet of Things (IoT) devices and enable their employees to perform tasks very quickly.

“This is the first time we’ve had this type of functionality all at once,” said Dmitry Kurbatov, chief technology officer at Positive Technologies, a security solutions provider. “LTE provided huge bandwidth, but the modems used for LTE consumed too much power to be used for more powerful IoT devices. The same is true of 2G: It provided great covering for the network and was accessible everywhere, but the connection speed wasn’t good enough for a satisfactory experience.”

With the increased spectrum and ability to segment networks, enterprises are likely to start using 5G more and more. Not only will it provide opportunities for coverage that WiFi may not have provided, but it could potentially replace WiFi or Bluetooth in some situations.

While all of this sounds great, it’s important to stop and consider the security ramifications. Done right, 5G can actually be the most secure cellular technology to date. 5G encrypts more data, and because it’s based on software and runs in the cloud, it’s easier to monitor.

But it’s not that simple. There is a greater risk of attacks on both IoT and mobile devices, simply because there will be so many more of them. With such fast speeds, employees are likely to choose 5G for their mobile devices instead of WiFi, and employers will use 5G for their IoT sensors.

Read the full article here on Data Center Knowledge.

Dark Reading’s Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Article source: https://www.darkreading.com/cloud/5g-adoption-should-change-how-organizations-approach-security/d/d-id/1337030?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Stop Defending Everything

Instead, try prioritizing with the aid of a thorough asset inventory.

What is your information security program defending?

This is a deceivingly difficult question for most. When I ask this at typical organizations, the answer is often disheartening. The standard response is “everything.” The word everything causes my skepticism radar to start chirping like a Chernobyl Geiger counter.

The claim being made here is that all of the systems and all of the data created and stored by the organization are defended. These companies, and the “everything” claim, do not make distinctions between high and low levels of protection. To lump all systems and data into one category causes equality across the board, which is a recipe for inefficiency at best and disaster at worst.

Fredrick the Great said, “He who attempts to defend everything, defends nothing.” If we attempt to defend everything, this means that we are not prioritizing. In this scenario, the same security controls and effort to defend a critical system storing the organization’s crown jewels are going to also apply on a noncritical system. This would lead to either underprotecting a critical system, overprotecting a noncritical system, or potentially both.

The concept of opportunity costs is important here since we all have limited resources. No department is given a blank check for all the tools, training, and expert staff that one could desire. The opposite is more likely to be the case, where departments are being asked to do more with less.

In a reality with limited resources, every dollar spent on a tool also represents a dollar that could have been spent on a different one. Every staff member hired with a particular skill represents a candidate that got passed on who had a different expertise. Every hour spent researching a solution is an hour that could have been dedicated to various other projects.

Opportunity costs are why prioritization needs to occur. Without it, an organization is guessing as to what to protect and how best to defend assets. This prioritization begins with an asset inventory.

Collect Everything
What constitutes an effective asset inventory from which to prioritize information security? In a word, details. “No details” means no value. An inventory is a listing of detailed attributes that can serve as an authoritative and consolidated resource. It is the one-stop shop for everything that is relevant to information security regarding an asset.

It must also be detailed in the sense that it must be all-inclusive. It’s every system that touches your network or handles sensitive information. It’s everything that’s wired, wireless, or even capable of either of those. It’s printers, IP phones, kiosks, marquees, and Internet of Things devices. It’s bare-metal hypervisors like ESXi. It’s firewalls, routers, wireless access points, and switches. It’s everything.

Understand Everything
Once all the assets are inventoried and information about them is collected, we begin to understand the big picture. Most of the asset details in an inventory play a supporting role to the system’s criticality ranking. This ranking is derived from attributes, such as the purpose of the system, type of data it generates and stores, user community, and business function it supports. From this criticality attribute, the security controls to protect it can be determined in order to bring the risks in line with the business’s risk tolerance.

Integration
Now we return to the asset inventory to reconcile those determined controls and provide assurances that they are in place and working as expected. Confidence in the functioning of a security program cannot exist without a complete asset inventory.

The various tools in the environment are typically tuned to determine what is working. Asset management, on the other hand, is used to determine what is not working. Assurance is a significant function of information security. Move past the assumptions that something should be working as advertised to a place of objective confidence that it is working.

A quality asset inventory allows a reconciliation process to occur. Comparing each tool’s list of registered systems with an authoritative and all-inclusive inventory provides a clear and objective list of discrepancies. One can, at that point, put aside assumptions and actually know which systems are being protected or monitored by a tool — also, more importantly, which systems are missing and thus unprotected.

A Neglected Control
It is very rare that I see an organization with an accurate inventory. Why is this foundational control so often ignored?

For one, there isn’t a tool to automate the process. We’re conditioned to searching for a tool to solve our problems. A nail needs a hammer and a squeaky wheel needs oil. Asset inventory tools are basically repackaged spreadsheets. None readily automates a method to collect the type of information needed to understand the security posture of an asset and to ensure that each one has the controls that it should have.

It’s also an indirect control. While firewalls and anti-malware tools can directly show the bad that they protect you from, asset management is a control that provides the assurances that your other controls are actually functioning as expected. It’s not just a “helper” control, though, but more of a foundational control on which to build the entire program.

Asset management isn’t sexy. It doesn’t result in pretty graphs or quality filler for PowerPoint slides. Quite the opposite — it highlights the gaps in a security program. Asset management presents information that can be difficult to swallow. However, it will also help you achieve the next maturity level in your security program.

Related Content:

Check out The Edge, Dark Reading’s new section for features, threat data, and in-depth perspectives. Today’s top story: “From 1s 0s to Wobbly Lines: The Radio Frequency (RF) Security Starter Guide

Kevin Kurzawa has a background in a variety of environments, with each having its own unique business drivers. His experiences in IT and information security have ranged from Department of Defense contractors large and small (including Lockheed and Harris) to traditional … View Full Bio

Article source: https://www.darkreading.com/risk/stop-defending-everything/a/d-id/1336973?_mc=rss_x_drr_edt_aud_dr_x_x-rss-simple

Data about inmates and jail staff spilled by leaky prison app

Inmates’ and correctional facilities employees’ data has been sloshed onto the web, unencrypted and unsecured, in yet another instance of a misconfigured cloud storage bucket.

Security researchers at vpnMentor came across the leak on 3 January during a web-mapping project that was scanning a range of Amazon S3 addresses to look for open holes in systems.

The leaky bucket belongs to JailCore, a cloud-based app meant to manage correctional facilities, including by helping to ensure better compliance with insurance standards by doing things like tracking inmates’ medications and activities. That means that the app handles personally identifiable information (PII) that includes detainees’ names, mugshots, medication names, and behaviors: going to the lavatory, sleeping, pacing, or cursing, for example.

JailCore also tracks correctional officers’ names, sometimes their signatures, and their personally filled out observational reports on the detainees.

Some of the PII is meant to be freely available to the public: details such as detainee names, dates of birth and mugshots are already publicly available from most state or county websites within rosters of current inmates. But another portion of the data is not: that portion includes specific medication information and additional sensitive data, vpnMentor says, such as the PII of correctional officers.

JailCore closed down the data leak between 15 and 16 January: 10 or 11 days after vpnMentor notified it about the breach (and about the same time that the security firm reached out to the Pentagon about it). The company initially refused to accept vpnMentor’s disclosure findings, the firm said.

Risk of identity theft

The leaky bucket held 36,077 PDFs of data from an Amazon server belonging to JailCore. The security researchers didn’t open each file, but the records that they did open pertained to correctional facilities in Florida, Kentucky, Missouri, Tennessee and West Virginia.

JailCore says that it’s a startup that’s currently working with six jails, totaling 1,200 inmates. It thinks that a tiny portion of real people’s information was involved in the breach. From one of its comments cited by vpnMentor:

Of those 6 jails, only 1 is using the application to track medication compliance in a 35 inmate jail and only 5 of those 35 inmates in that jail has a prescribed medication. Meaning all other reports with any mention of medication were all used for demonstration purposes only.

JailCore asked vpnMentor to bear in mind that detainees aren’t free citizens, and that’s a whole ‘nuther can of worms when it comes to privacy rights:

These are incarcerated individuals, not free citizens. Meaning, the same privacy laws that you and I enjoy, they do not.

[…] You cannot look at this like an example of a private citizen getting certain private information hacked from the cloud. These are incarcerated individuals who are PROPERTY OF THE COUNTY (this is even printed on their uniforms) … they don’t enjoy our same liberties.

Does that mean that it’s OK to expose prison inmates to the risk of identity theft? vpnMentor’s take on that risk:

Knowing the full name, birthdate, and, yes, even the incarceration record of an individual can provide criminals with enough information to steal that person’s identity. Considering that the person whose identity is stolen is in jail, cut off from normal access to a cellphone or their email, the damage could be even greater, as it will take longer to discover.

When Vice’s Motherboard contacted JailCore, a representative acknowledged that the records were in fact generated by its app and confirmed that JailCore had sealed up the hole. The JailCore rep also told the publication that the company doesn’t think that any of the compromised PII is personally sensitive or compromising in any way.

A tub full of leaky buckets

And thus does JailCore join the Who’s Who list of organizations that have misconfigured their Amazon S3 buckets and thereby inadvertently regurgitated their private data across the world: Dow Jones; a bipartisan duo including the Democratic National Committee (DNC) and the Republican National Committee (RNC); and Time Warner Cable – to name just a few.

In fact, back in 2017, security vendor Threat Stack conducted a survey of 200 AWS users in early 2017 and found that 73% left SSH open to the public, and 62% weren’t using two-factor authentication (2FA) to secure access to their data.

Amazon took a proactive step by scanning its customers’ S3 buckets and sending warnings when it found spillage, reaching out to customers with bad security before crooks had a chance to.

It doesn’t have to be this way. There’s help out there for organizations that can take a deep breath, step away from their servers, and plunge in to learn how to better secure them: Amazon has an FAQ about how to access AWS Simple Storage Service (S3) controls and encryption.

Article source: http://feedproxy.google.com/~r/nakedsecurity/~3/ypFJWLIWMOE/

US charges four Chinese military members with Equifax hack

The US has charged the Chinese military with plundering Equifax in 2017.

The Justice Department (DOJ) on Monday released a nine-count indictment that accused four members of the People’s Liberation Army (PLA) of being hackers behind the breach, which was one of the largest in US history.

The breach exposed millions of names and dates of birth, taxpayer ID numbers, physical addresses, and other personal information that could lead to identity theft and fraud. Besides the original estimate of 145.5 million Americans who were affected, the breach also hit 15.2 million Brits and some 100,000 Canadians.

The indictment charged the four with a three-month campaign during which they allegedly hacked into computers of the credit-reporting agency and siphoned off the sensitive financial data and other personally identifiable information (PII) from all those people.

The accused are Wu Zhiyong, Wang Qian, Xu Ke, and Liu Lei: all members of the PLA’s 54th Research Institute, which is part of the Chinese military.

How they allegedly pulled it off

According to the indictment, the four allegedly pried open Equifax by exploiting a vulnerability in the Apache Struts Web Framework software used by the credit reporting agency’s online dispute portal.

We already knew it was done via a web app vulnerability and that it was a months-old Struts vulnerability: specifically, a nasty server-side remote code execution (RCE) bug made known to the public in March 2017.

The indictment says that the Chinese military staffers used that access to conduct reconnaissance of Equifax’s online dispute portal and to obtain login credentials that could be used to further poke around in Equifax’s network.

The defendants allegedly spent weeks running queries to identify Equifax’s database structure and searching for sensitive PII within its system. Once they found files that they could exploit, they allegedly stored the stolen information in temporary output files, compressed and divided the files, and were ultimately able to download and exfiltrate the data from Equifax’s network to computers outside the US, the indictment charges.

Make that a whole lot of queries against Equifax’s system: the alleged attackers ran about 9,000 queries, which returned names, birth dates and taxpayer IDs for nearly half of all American citizens.

The indictment also charges the defendants with stealing trade secret information, namely Equifax’s data compilations and database designs.

Attorney General William P. Barr, who announced the indictments, called it “a deliberate and sweeping intrusion into the private information of the American people.”

In short, this was an organized and remarkably brazen criminal heist of sensitive information of nearly half of all Americans, as well as the hard work and intellectual property of an American company, by a unit of the Chinese military.

Today, we hold PLA hackers accountable for their criminal actions, and we remind the Chinese government that we have the capability to remove the Internet’s cloak of anonymity and find the hackers that nation repeatedly deploys against us.

The indictment says that the defendants tried to cover their tracks by routing traffic through some 34 servers, located in nearly 20 countries, to obfuscate their true location; that they used encrypted communication channels within Equifax’s network to blend in with normal network activity; and that they allegedly deleted compressed files and wiped log files on a daily basis in an effort to eliminate records of their activity.

Each of the defendants is charged with three counts of conspiracy to commit computer fraud, conspiracy to commit economic espionage, and conspiracy to commit wire fraud. They’ve also been charged with two counts of unauthorized access and intentional damage to a protected computer, one count of economic espionage, and three counts of wire fraud.

Credit monitoring

In July 2019, the Federal Trade Commission (FTC) announced that Equifax had agreed to pay $675 million – up to possibly $700 million – as part of a settlement for failing to secure the huge amount of personal information stored on its network.

The settlement included $300 million paid into a fund for credit monitoring services, for compensation to those who forked over money to Equifax to buy credit or identity monitoring services or who had other out-of-pocket expenses as a result of the breach.

Starting this year, it will also provide affected US consumers with six free credit reports per year for seven years (on top of the one free one they get every year from Equifax and the two other credit reporting agencies, Experian and TransUnion).

Finally, Equifax agreed to pay $175 million to 48 states, the District of Columbia and Puerto Rico, as well as $100 million to the Consumer Financial Protection Bureau (CFPB) in civil penalties.

In August 2019, the FTC said that affected consumers would be eligible for a $125 cash payout, or more, as part of its settlement with Equifax. A week later, the FTC was rapidly blinking its eyes at how many people were actually interested in receiving payback. Well, that’s “unexpected,” it said, and, well, “overwhelming.”

How about instead of cash, you take the free-credit-reporting offer instead? the FTC suggested. Because of the “high interest in the alternative cash payment under the settlement,” consumers who expect to take the FTC up on the offer might end up getting “far less than $125.”


Latest Naked Security podcast

LISTEN NOW

Click-and-drag on the soundwaves below to skip to any point in the podcast. You can also listen directly on Soundcloud.

Article source: http://feedproxy.google.com/~r/nakedsecurity/~3/2euIheG1QVA/

Netgear’s routerlogin.com HTTPS cert snafu now has a live proof of concept

An infosec researcher has published a JavaScript-based proof of concept for the Netgear routerlogin.com vulnerability revealed at the end of January.

Through service workers, scripts that browsers run as background processes, Rashid Saleem reckons he can exploit Netgear routers to successfully compromise admin panel credentials.

There’s just one catch: for Saleem’s method to work, the target has to try to log into their home router after connecting to a compromised Wi-Fi point and downloading malware.

By loading a malicious service worker for the domain routerlogin.com – the default admin panel address for Netgear consumer routers – Saleem said it is possible for a bad actor to capture and read the login credentials by executing a classic man-in-the-middle attack.

As we reported in January, Netgear was bundling valid, signed TLS certificates along with private keys embedded in firmware that anyone could freely download. Working on the basis that routerlogin.com is easier to communicate to non-techie users instead of a unique IP address on the local subnet, Netgear included HTTPS certificates in its firmware so customers didn’t get scared off as browsers unable to connect to the internet threw up error messages and warnings when they couldn’t authenticate the HTTPS connection to routerlogin.com.

Saleem described his findings in a blog post along with a downloadable proof-of-concept package.

“Even if the user were using DNS-over-TLS or DNS-over-HTTPS, the malicious Wi-Fi network could intercept packets to the IP address behind routerlogin.com and perform the same attack,” he posted.

Jake Moore of infosec biz ESET mused that the probability of this being a viable attack in the wild was low, telling The Register: “To me, it seems crazy that you would want to access your home router so desperately that you need to do it remotely – unless, of course, you’ve just realised that your username and password are still the defaults whilst at work.”

Echoing UK calls for mandatory security standards enforced on industry, he continued: “Scammers exploit wherever they can so manufacturers need to do their utmost to help protect their users with best practice in place. Few people play around with the settings after the initial set up so it’s best to reduce the entry points altogether to reduce the risk of attack.”

It appeared from his blogpost that Saleem had not contacted Netgear in advance, on the grounds that the HTTPS certificates it issued have all now been revoked.

Netgear did not answer when The Register called for comment. ®

Sponsored:
Detecting cyber attacks as a small to medium business

Article source: https://go.theregister.co.uk/feed/www.theregister.co.uk/2020/02/12/netgear_router_https_cert_poc/

If you’re running Windows, I feel bad for you, son. Microsoft’s got 99 problems, better fix each one

Patch Tuesday It’s going to be a busy month for IT administrators as Microsoft, Intel, Adobe, and SAP have teamed up to deliver a bumper crop of security fixes for Patch Tuesday.

Redmond weighs in just under the century mark

Microsoft had one of its largest patch bundles in recent memory, as the Windows giant released fixes for 99 CVE-listed vulnerabilities.

These included CVE-2020-0674, a remote code execution flaw in Internet Explorer’s Trident rendering engine that is already being exploited in the wild. This hole would typically be exploited by a malicious webpage or the like to infect a visiting vulnerable computer.

“Even if you don’t use IE, you could still be affected by this bug though embedded objects in Office documents,” noted Dustin Childs of the Trend Micro Zero Day Initiative.

“Considering the listed workaround – disabling jscript.dll – breaks a fair amount of functionality, you should prioritize the testing and deployment of this patch.”

Four of this month’s other bugs have also been publicly disclosed, though none have been targeted in the wild yet. These include two elevation of privilege bugs in Windows Installer (CVE-2020-0683 and CVE-2020-0686), a security bypass in Secure Boot (CVE-2020-0689), and an information disclosure vulnerability in Edge and IE (CVE-2020-0706.)

Once again, Remote Desktop was cause for alarm as patches for two remote code execution flaws (CVE-2020-0681, CVE-2020-0734) in the administration tool will need to be tested and installed ASAP.

Exchange admins will want to pay close attention this month, as Microsoft has posted a fix for CVE-2020-0688, a flaw that allows remote code execution by way of poisoned e-mails.

“An attacker could gain code execution on affected Exchange servers by sending a specially crafted e-mail. No other user interaction is required,” noted Childs. “The code execution occurs at System-level permissions, so the attacker could completely take control of an Exchange server through a single e-mail.”

A remote code execution flaw (CVE-2020-0618) was also addressed in SQL Server’s Reporting Services component.

The browser scripting engine received its usual bundle of patches (CVE-2020-0673, CVE-2020-0767, CVE-2020-0710, CVE-2020-0712, CVE-2020-0713, CVE-2020-0711) for remote code execution bugs that can be exploited by a malicious website.

For Office, patches were doled out for an Excel remote code execution bug (CVE-2020-0759), an Outlook security bypass (CVE-2020-0696), an Office Online spoofing bug (CVE-2020-0695), and Office tampering flaw (CVE-2020-0697), and two cross-site scripting bugs in SharePoint (CVE-2020-0693, CVE-2020-0694.)

Finally, if you’re still using Windows 7 and/or Windows Server 2008 R2 and you haven’t paid Microsoft for extended security support, there’s trouble brewing. There are five critical holes among 42 vulns in the end-of-life operating systems that need fixing. Bear in mind that criminals will already be hard at work reverse engineering the patches, and finding out how to write exploit code for them, so upgrade to a newer platform or start paying coin to Redmond.

Security folks joke at Exploit Wednesday, the day after Patch Tuesday when the latest round of exploit code is deployed, but there’s a grain of truth to this.

Adobe mends hole in the internet’s screen door with Flash fix

This month Adobe is rolling out fixes for two of its most popular widely used offerings: Flash and Acrobat/Reader.

For Flash Player, the patch addresses a single arbitrary code execution flaw, CVE-2020-3757, that would allow arbitrary code execution. Windows, macOS, Linux, and Chrome OS versions of the plug-in will all get the fix.

With Acrobat and Reader, a total of 17 bugs are addressed on Windows and macOS. The most serious will allow for arbitrary code execution, though no exploits have been reported in the wild.

The heaviest patch load was for Adobe Framemaker, where a list of 21 CVE-listed bugs were cleaned up. Arbitrary code execution would be the biggest risk here, with no active exploits reported.

CMSE flaw highlight half-dozen Intel updates

Of the six Intel bulletins, the lone ‘high’ risk classification was for CVE-2019-14598. According to Intel, a flaw related to improper authentication in Converged Security and Manageability Engine (CSME) allows for denial of service or, more importantly, information disclosure and elevation of privilege.

EoP bugs made up the remaining five bulletins. Those included issues in RWC2 and RWC3 as well as the Manycore Platform Software Stack (MPSS). Another EoP issue, in SGX, was considered less of a risk and given a low severity label.

One flaw that will not be getting a fix is CVE-2020-0560. That elevation of privilege error, found in the outdated Renesas Electronics USB 3.0 driver, has prompted Chipzilla to simply discontinue the component and drop support. That’s certainly one way to get rid of buggy software.

SAP posts a baker’s dozen

Finally, there is enterprise software giant SAP, who posted 13 fixes headlined by an update for the Chromium plugin in SAP Business Client.

Also patched were flaws in Host Agent (CVE-2010-6186) and Landscape Management (CVE-2020-6191, CVE-2020-6192) that were considered high-risk flaws. ®

Sponsored:
Detecting cyber attacks as a small to medium business

Article source: https://go.theregister.co.uk/feed/www.theregister.co.uk/2020/02/11/patch_tuesday_february_2020/