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
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
Don't Roll the Dice When Prioritizing Vulnerability Fixes
Ericka Chickowski, Contributing Writer, Dark Reading,  5/15/2018
Why Enterprises Can't Ignore Third-Party IoT-Related Risks
Charlie Miller, Senior Vice President, The Santa Fe Group,  5/14/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: "Security through obscurity"
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11311
PUBLISHED: 2018-05-20
A hardcoded FTP username of myscada and password of Vikuk63 in 'myscadagate.exe' in mySCADA myPRO 7 allows remote attackers to access the FTP server on port 2121, and upload files or list directories, by entering these credentials.
CVE-2018-11319
PUBLISHED: 2018-05-20
Syntastic (aka vim-syntastic) through 3.9.0 does not properly handle searches for configuration files (it searches the current directory up to potentially the root). This improper handling might be exploited for arbitrary code execution via a malicious gcc plugin, if an attacker has write access to ...
CVE-2018-11242
PUBLISHED: 2018-05-20
An issue was discovered in the MakeMyTrip application 7.2.4 for Android. The databases (locally stored) are not encrypted and have cleartext that might lead to sensitive information disclosure, as demonstrated by data/com.makemytrip/databases and data/com.makemytrip/Cache SQLite database files.
CVE-2018-11315
PUBLISHED: 2018-05-20
The Local HTTP API in Radio Thermostat CT50 and CT80 1.04.84 and below products allows unauthorized access via a DNS rebinding attack. This can result in remote device temperature control, as demonstrated by a tstat t_heat request that accesses a device purchased in the Spring of 2018, and sets a ho...
CVE-2018-11239
PUBLISHED: 2018-05-19
An integer overflow in the _transfer function of a smart contract implementation for Hexagon (HXG), an Ethereum ERC20 token, allows attackers to accomplish an unauthorized increase of digital assets by providing a _to argument in conjunction with a large _value argument, as exploited in the wild in ...