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.

Operations

7/6/2017
02:35 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

New Google Security Controls Tighten Third-Party Data Access

Google adds OAuth app whitelisting to G Suite so admins can vet third-party applications before users can grant them authorized data access.

Google is updating its G Suite with OAuth apps whitelisting, a new security measure created to help administrators buckle down on data access control and see how third-party applications are using information.

The new controls are designed to give admins more detailed visibility into which third-party apps are accessing G Suite data, limit access to vetted OAuth apps, and protect G Suite app data by preventing unauthorized app installation, decreasing the risks associated with shadow IT.

Administrators will be able to use OAuth app whitelisting to select which third-party applications are allowed access to users' G Suite data, and see the data they can access. They can also disable OAuth access at a granular level, for the whole organization or specific groups.

Once an app is on the whitelist, users will be able to grant it authorized access to their G Suite apps data. This will protect employees from unauthorized, and potentially malicious, applications based on the settings that admins select.

"Unauthorized data access by external apps can be a major concern for organizations," says Rishi Dhand, product manager at G Suite. "The risks vary based on the kind of data that an unauthorized app may have accessed."

Admins have a powerful and important role in ensuring the security of third-party apps that can access employees' data. Dhand advises asking the following questions when vetting applications:

  • Is my organization's data access policy in sync with the access being requested by the third-party app?
  • Is the third-party app functionality correlated to the access the app is requesting? For example, he says, a calendar app requesting access to Drive data could be a red flag.
  • What is the app developer's approach to security? Have the developers published information that highlights the steps they take to protect user data?

This update addresses the risk of malicious apps tricking users into accidentally sharing sensitive data with threat actors. A new type of credential phishing technique, or "OAuth phishing," abuses the OAuth standard to trick users into granting persistent account access.

In OAuth phishing attacks, hackers send potential victims an OAuth permission request for an approved application. Once the target grants access, the hacker can maintain access to the account after multiple password resets. These attacks exploit users' trust in online service providers, and the trust between service providers and third-party applications.

We recently saw this technique play out in the May 3 Google Docs phishing scam. More than one million users were tricked into clicking a link, which led to a page requesting access to the user's Gmail account. If granted permission, the attacker could access victims' Google Drive through OAuth authentication connections used among third-party applications.

OAuth phishing attacks are dangerous because they bypass many of the red flags that typically alert users to email phishing. The Google attack was tough to detect as malicious because the icons and messaging were familiar to users.

By giving admins greater control over which apps can access user data, this G Suite update lessens the risk of employees granting access to malicious applications that could steal their information and cause further damage.

The G Suite updates will roll out in phases, the company reports. It will be made available within the admin console over the next few days.

Related Content:

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Stop Defending Everything
Kevin Kurzawa, Senior Information Security Auditor,  2/12/2020
Small Business Security: 5 Tips on How and Where to Start
Mike Puglia, Chief Strategy Officer at Kaseya,  2/13/2020
Architectural Analysis IDs 78 Specific Risks in Machine-Learning Systems
Jai Vijayan, Contributing Writer,  2/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. 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-2020-4230
PUBLISHED: 2020-02-19
IBM DB2 for Linux, UNIX and Windows (includes DB2 Connect Server) 11.1 and 11.5 is vulnerable to an escalation of privilege when an authenticated local attacker with special permissions executes specially crafted Db2 commands. IBM X-Force ID: 175212.
CVE-2019-4429
PUBLISHED: 2020-02-19
IBM Maximo Asset Management 7.6.0 and 7.6.1 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 162886.
CVE-2019-4457
PUBLISHED: 2020-02-19
IBM Jazz Foundation 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.0.6, and 6.0.6.1 could allow an authenticated user to obtain sensitive information that could be used in further attacks against the system. IBM X-Force ID: 163654.
CVE-2019-4640
PUBLISHED: 2020-02-19
IBM Security Secret Server 10.7 processes patches, image backups and other updates without sufficiently verifying the origin and integrity of the code which could result in an attacker executing malicious code. IBM X-Force ID: 170046.
CVE-2020-4135
PUBLISHED: 2020-02-19
IBM DB2 for Linux, UNIX and Windows (includes DB2 Connect Server) 9.7, 10.1, 10.5, 11.1, and 11.5 could allow an unauthenticated user to send specially crafted packets to cause a denial of service from excessive memory usage.