Cloud

1/17/2018
04:00 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Google Rolls Out Security Center for G Suite Enterprise

New dashboards give admins a look at data such as suspicious device activity and spam email delivery across the business.

Google is integrating a new security center into G Suite to give administrators a more granular view of security metrics for employees' devices, and guidance for managing them.

The idea behind this update is to give admins a single place to see their enterprise security posture. In one dashboard, a series of individual windows presents data including suspicious device activity and how spam and malware emails are targeting users across the business.

"It basically helps administrators by providing them a single comprehensive view into the security posture of the organization," says Chad Tyler, product manager for the Security Center.

Admins can click on individual graphs to learn more about specific types of data and act on them. If you want to learn more about phishing attacks, you can view what types of phishing emails users are seeing, and who receives the most malicious messages. If someone is often targeted, you know to ensure they have additional precautions like two-factor authentication.

In another example, admins can also view which files are triggering data loss prevention alerts. Based on this data, they can take action to see which users are sharing information. The data in Security Center is collected from devices logged into their corporate Google accounts.

"A lot of this information is based on usage logs we have around auditing within the administrator console," says Tyler. "When a user is using Gmail, there are logs associated with the different things sent and received. This is the organization's view of what's going on."

In a separate window, the Security Center has a list of security guidance recommendations. Admins can see their current settings and read up on Google's recommended settings to reduce risk. Tyler points out that all best practices will look the same in each admin's Security Center so it's worth considering individual settings to determine which is best for your organization.

This component of Security Center is less of a notification systems and more of a management tool, says Tyler. Google will update them based on new security information or new settings.

The Security Center is solely for admins and won't present alerts or best practices to end users, he adds, noting that Gmail already has measures in place to prevent successful attacks.

"There's already a lot of protection for the end users, to keep them from clicking what's known to be spam," Tyler says. "This is just giving information to administrators to better understand what's going on and make those higher-level decisions."

Security Center is part of G Suite Enterprise and will automatically appear in admin consoles 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
Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Data Privacy Careers Are Helping to Close the IT Gender Gap
Dana Simberkoff, Chief Compliance and Risk Management Officer, AvePoint, Inc,  8/20/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-15601
PUBLISHED: 2018-08-21
apps/filemanager/handlers/upload/drop.php in Elefant CMS 2.0.3 performs a urldecode step too late in the "Cannot upload executable files" protection mechanism.
CVE-2018-15603
PUBLISHED: 2018-08-21
An issue was discovered in Victor CMS through 2018-05-10. There is XSS via the Author field of the "Leave a Comment" screen.
CVE-2018-15598
PUBLISHED: 2018-08-21
Containous Traefik 1.6.x before 1.6.6, when --api is used, exposes the configuration and secret if authentication is missing and the API's port is publicly reachable.
CVE-2018-15599
PUBLISHED: 2018-08-21
The recv_msg_userauth_request function in svr-auth.c in Dropbear through 2018.76 is prone to a user enumeration vulnerability because username validity affects how fields in SSH_MSG_USERAUTH messages are handled, a similar issue to CVE-2018-15473 in an unrelated codebase.
CVE-2018-0501
PUBLISHED: 2018-08-21
The mirror:// method implementation in Advanced Package Tool (APT) 1.6.x before 1.6.4 and 1.7.x before 1.7.0~alpha3 mishandles gpg signature verification for the InRelease file of a fallback mirror, aka mirrorfail.