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.

Attacks/Breaches

2/21/2018
10:30 AM
Tom Kemp
Tom Kemp
Commentary
Connect Directly
LinkedIn
Twitter
RSS
E-Mail vvv
50%
50%

Takeaways from the Russia-Linked US Senate Phishing Attacks

The Zero Trust Security approach could empower organizations and protect their customers in ways that go far beyond typical security concerns.

On January 12, 2018, cybersecurity firm Trend Micro revealed that Russia-linked hackers tried to infiltrate the US Senate, leveraging phishing attacks to harvest access credentials. These tactics suggest that the hackers were laying the groundwork for a widespread compromise of Senate employees. And while these findings might further bolster the public view that the Kremlin is trying to influence our democracy, security professionals should not get distracted by the media frenzy that these revelations created and instead focus on the real lessons.

By creating fake websites that were mimicking the login page for the Senate's email server, the attackers followed a common blueprint to harvest access credentials that can later be used for lateral attacks and extraction of sensitive information. Taking advantage of Active Directory Federation Services (ADFS), hackers ultimately tried to gain access to systems and applications located across organizational boundaries. It's well known, but often overlooked, that identity is the top attack vector for cybercriminals and state-sponsored attackers alike. According to Verizon's 2017 Data Breach Investigations Report, 81% of hacker-initiated data breaches involved weak, default, or stolen passwords.

These statistics confirm that widely accepted security approaches based on bolstering a trusted network do not work. And they never will. The proof? According to analyst firm Gartner, organizations spent a combined $150 billion on cybersecurity in 2015 and 2016. Meanwhile, we're experiencing a continuous increase in security incidents, which raises doubts about the effectiveness of these investments. During approximately the same period, 66% of organizations surveyed by analyst firm Forrester reported five or more data breaches. When conducting post-mortem analysis of the data breaches that occurred in 2017, it becomes apparent that many of these big breaches can be attributed to a longstanding failure to implement basic cybersecurity measures (e.g., multifactor authentication, or MFA), botched usage of existing security tools to streamline the mitigation of known vulnerabilities, and lack of security measures for protecting sensitive data.

Return to the Essentials of Cybersecurity
Instead of earmarking security investments for bolstering traditional perimeter defenses, which is a futile exercise, organizations must return to the essentials of cybersecurity. In doing so, they can improve their security posture and limit exposure to data breaches.

As the U.S. Senate phishing attack illustrates, weak or stolen user credentials remain the primary entry point for hackers, which is why access control is still the Achilles' heel of many security programs, since practitioners must balance data availability with measures that prevent unauthorized usage (e.g., theft, disclosure, modification, destructions). Meanwhile, hackers often target privileged users because their accounts provide a beachhead into the entire network. Therefore, strict enforcement of well-defined access control policies and continuous monitoring of access paths to ensure they are working as intended are essential for the success of data integrity initiatives.

In this context, MFA plays an essential role in minimizing the risk of falling victim to phishing attacks. When leveraging MFA, knowing someone's user name and password is no longer enough to assume the victim's identity. The likelihood for the hacker to gain access to something their victim knows, something they have, and something they are, is very limited.

Rethink Security: Never Trust, Always Verify
However, MFA is just a first step in securing your organization more effectively. Today's dynamic threat landscape requires a broader shift in an organization's security strategy. Instead of the old adage "trust but verify," the new paradigm is "never trust, always verify." This Zero Trust Security model is championed by many industry leaders including Google, Forrester, and Gartner.

The basic concept of Zero Trust is that users inside a network are no more trustworthy than users outside a network. Therefore, traditional perimeter-based security approaches are inadequate. Zero Trust Security assumes that everything — including users, endpoints, networks, and resources — is always untrusted and must be verified to decrease the chance of a major breach.

Zero Trust Security assumes that untrusted actors already exist both inside and outside the network. Trust must therefore be entirely removed from the equation. Zero Trust Security requires powerful identity services to secure every user's access to apps and infrastructure. Once identity is authenticated and the integrity of the device is proven, authorization and access to resources is granted — but with just enough privilege necessary to perform the task at hand.

Effective Zero Trust Security requires a unified identity platform consisting of four key elements within a single security model. Combined, these elements help to ensure secure access to resources while they significantly reduce the possibility of access by bad actors. The model includes:

  • Verifying the user
  • Validating their device
  • Limiting access and privilege
  • Learning and adapting

This approach must be implemented across the entire organization. Whether giving users access to apps or administrators access to servers, it all comes down to a person, an endpoint, and a protected resource. Users include not only employees but also contractors and business partners who have access to your systems.

Ultimately, it takes Zero Trust Security to trust. But once security professionals embrace this new paradigm, it empowers their organizations and protects their customers in ways that go far beyond typical security concerns, such as enabling digital transformation, increasing data awareness and insights, and reducing existing internal silos between security, IT, DevOps, SecOps, which often lead to the blame game.

Related Content:

 

Black Hat Asia returns to Singapore with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier solutions and service providers in the Business Hall. Click for information on the conference and to register.

Tom Kemp is co-founder and Chief Executive Officer of Centrify Corporation, a software and cloud security provider that delivers solutions that centrally control, secure, and audit access to on-premises and cloud-based systems, applications, and devices for both end and ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
2/25/2018 | 9:43:16 PM
Re: passwords
@Dr.T: The IT departments aren't necessarily more reliable, however...such as when they force you to choose between preset, terrible security questions, like "What was your first pet?" and "Who is your favorite movie star?"
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
2/25/2018 | 11:18:26 AM
Re: Limit access to the instance, not the class
assigned role might need to perform any tas I would be ok granting permissions based on the roles. If it goes below that as tasks that may be managing difficulties.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
2/25/2018 | 11:16:55 AM
Re: Limit access to the instance, not the class
A fundamental error in approach is to grant privileges based on what a person with a given title The title is certainly wrong approach to grant permissions.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
2/25/2018 | 11:15:21 AM
Re: Limit access to the instance, not the class
The salient word is "task" This is a good point. It needs to be related it the tasks users have to perform.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
2/25/2018 | 11:13:48 AM
Re: Limit access to the instance, not the class
enough privilege necessary to perform the task at hand. This is true, least privilege approach is good approach to follow.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
2/25/2018 | 11:11:45 AM
passwords
The passwords are one of the worst things that happen to the technologises we use today, it relies on the individual who are not by nature reliable.
BrianN060
50%
50%
BrianN060,
User Rank: Ninja
2/21/2018 | 9:05:59 PM
Limit access to the instance, not the class
"...access to resources is granted — but with the (sic), just enough privilege necessary to perform the task at hand." 

That's spot on.  The salient word is "task".  The specific task, not job (as in job title or job description), is what should determine access.  A fundamental error in approach is to grant privileges based on what a person with a given title or assigned role might need to perform any task, at any time, that falls within their job description. 
Commentary
How SolarWinds Busted Up Our Assumptions About Code Signing
Dr. Jethro Beekman, Technical Director,  3/3/2021
News
'ObliqueRAT' Now Hides Behind Images on Compromised Websites
Jai Vijayan, Contributing Writer,  3/2/2021
News
Attackers Turn Struggling Software Projects Into Trojan Horses
Robert Lemos, Contributing Writer,  2/26/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: George has not accepted that the technology age has come to an end.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-28466
PUBLISHED: 2021-03-07
This affects all versions of package github.com/nats-io/nats-server/server. Untrusted accounts are able to crash the server using configs that represent a service export/import cycles. Disclaimer from the maintainers: Running a NATS service which is exposed to untrusted users presents a heightened r...
CVE-2021-27364
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. drivers/scsi/scsi_transport_iscsi.c is adversely affected by the ability of an unprivileged user to craft Netlink messages.
CVE-2021-27365
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. Certain iSCSI data structures do not have appropriate length constraints or checks, and can exceed the PAGE_SIZE value. An unprivileged user can send a Netlink message that is associated with iSCSI, and has a length up to the maximum length...
CVE-2021-27363
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. A kernel pointer leak can be used to determine the address of the iscsi_transport structure. When an iSCSI transport is registered with the iSCSI subsystem, the transport's handle is available to unprivileged users via the sysfs file system...
CVE-2021-26294
PUBLISHED: 2021-03-07
An issue was discovered in AfterLogic Aurora through 7.7.9 and WebMail Pro through 7.7.9. They allow directory traversal to read files (such as a data/settings/settings.xml file containing admin panel credentials), as demonstrated by dav/server.php/files/personal/%2e%2e when using the caldav_public_...