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.

Cloud

10/11/2018
02:30 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Google Adds New Identity, Security Tools to Cloud Platform

A wave of cloud news includes new tools for identity and access management and policies for stronger controls on cloud resources.

Google this week announced tools and updates related to cloud security and identity access management (IAM), most of which aim to make identity management simpler and more secure.

"How do we rethink security? How do we rethink identity in this cloud-based world?" asked Karthik Lakshminarayanan, director of product management, in a press briefing. Google's latest updates build on Cloud Identity, which it released in March, and context-aware access, announced in July.

The updates also incorporate elements of BeyondCorp, an enterprise security model Google launched in 2011 after years of building zero-trust networks. Its idea was to shift access controls from the perimeter to users' devices as people become more mobile and want to access data from anywhere. Indeed, it became challenging for businesses to manage who should be able to access what.

"We need a new trust model; we need a new security perimeter," Lakshminarayanan explained. "We look at the state of who the employee is and what they are trying to access."

Three of Google's announcements aim to simplify and strengthen IAM in the cloud, while two focus on securing cloud-based data and organizing alerts.

CICP: Identity Management On Prem, In the Cloud
The first announcement is Cloud Identity for Customers and Partners (CICP), a customer IAM platform developers can use to add IAM functionality to their apps. The idea is to let developers focus on development while CICP takes care of authentication and security.

Capabilities include an authentication service that manages UI flows for user sign-up and sign-in. "Google says CICP is customizable according to an organization's preferred authentication method (email/password, phone, social, SAML, OIDC, and anonymous), client SDKs (Web, iOS, Android), and server SDKs (Node.js, Java, Python, and more). It's also integrated with Google's threat and intelligence signals to detect compromise.

CICP is still being finalized. Google is working to enable two-factor authentication for its general rollout, and says it will also be released with an enterprise-grade availability SLA and technical support. The tool will be ready for public beta in the coming weeks, Google reports.

Google is also bringing secure LDAP to Cloud Identity, acknowledging that even though SaaS adoption is growing, many businesses still depend on traditional LDAP-based applications and IT infrastructure. Letting users access SaaS and traditional apps often requires multiple identity management systems, a challenge it hopes to solve with this offering.

"A mantra Google has is, 'Let's meet customers where they are,'" Lakshminarayanan said. "They're in the cloud, but they also have a massive, massive footprint of traditional applications. We can't ignore that."

Secure LDAP in Cloud Identity will let organizations manage access to both SaaS apps and LDAP-based apps and infrastructure, hosted on-premises or in the cloud, with a single IAM platform. Employees can use the same credentials to access SaaS tools and traditional applications.

The last bit of identity news: Google is bringing context-aware access capabilities for customers using Cloud Identity-Aware Proxy (IAP). Context-aware access lets admins define granular access to cloud resources based on the user's identity and the context of the request. For example, someone using Cloud IAP can dictate a Web app for employees and contractors may only be opened by a device running the latest version of Windows, macOS, or ChromeOS.

Cloud Resource Control
Google is introducing a couple of new tools to protect cloud-based resources with new policies and restrictions. Google Cloud Platform's (GCP) organization policy service mandates admins set restrictions on how resources like virtual machines and images can be configured.

Now it has two new organization policies: location restriction and domain-restricted sharing. Location restriction, coming soon to beta, will let admins limit where GCP resources are created based on geographical region. They can also limit the domains that can access GCP resources, meaning dev teams can work while security teams ensure the right controls are in place.

A new alert center for G Suite will provide a unified view of security alerts so admins can decide which ones to prioritize, along with insights to help gauge the company's exposure to threats.

The alert center includes information on problems that might affect G Suite services – for example, increases in phishing activity and data on which devices are showing suspicious behavior. G Suite enterprise edition domains can use the G Suite security center to remediate these issues.

Related Content:

 

 

 

Black Hat Europe returns to London Dec 3-6 2018  with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

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
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Look Beyond the 'Big 5' in Cyberattacks
Robert Lemos, Contributing Writer,  11/25/2020
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: We are really excited about our new two tone authentication system!
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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-4126
PUBLISHED: 2020-12-01
HCL iNotes is susceptible to a sensitive cookie exposure vulnerability. This can allow an unauthenticated remote attacker to capture the cookie by intercepting its transmission within an http session. Fixes are available in HCL Domino and iNotes versions 10.0.1 FP6 and 11.0.1 FP2 and later.
CVE-2020-4129
PUBLISHED: 2020-12-01
HCL Domino is susceptible to a lockout policy bypass vulnerability in the LDAP service. An unauthenticated attacker could use this vulnerability to mount a brute force attack against the LDAP service. Fixes are available in HCL Domino versions 9.0.1 FP10 IF6, 10.0.1 FP6 and 11.0.1 FP1 and later.
CVE-2020-9115
PUBLISHED: 2020-12-01
ManageOne versions 6.5.1.1.B010, 6.5.1.1.B020, 6.5.1.1.B030, 6.5.1.1.B040, ,6.5.1.1.B050, 8.0.0 and 8.0.1 have a command injection vulnerability. An attacker with high privileges may exploit this vulnerability through some operations on the plug-in component. Due to insufficient input validation of ...
CVE-2020-9116
PUBLISHED: 2020-12-01
Huawei FusionCompute versions 6.5.1 and 8.0.0 have a command injection vulnerability. An authenticated, remote attacker can craft specific request to exploit this vulnerability. Due to insufficient verification, this could be exploited to cause the attackers to obtain higher privilege.
CVE-2020-14193
PUBLISHED: 2020-11-30
Affected versions of Automation for Jira - Server allowed remote attackers to read and render files as mustache templates in files inside the WEB-INF/classes & <jira-installation>/jira/bin directories via a template injection vulnerability in Jira smart values using mustache partials. The ...