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

12/10/2019
10:45 AM
50%
50%

Only 53% of Security Pros Have Ownership of Workforce IAM

Most practitioners report an increase in identities, but many don't have control over how those identities are protected from a range of attacks.

At the core of many data breaches are compromised credentials. Over the past 10 years, companies have invested billions in security tools and identity access management (IAM) technology to secure them. However, many security teams lack power to mitigate identity risks.

A new survey of 511 IT security professionals, conducted by Dimensional Research and commissioned by the Identity Defined Security Alliance, found 52% of respondents saw a fivefold increase in identities over the past decade. The rise is primarily driven by technological changes including mobile devices (76%), enterprise connected devices (60%), and cloud apps (59%). Workforce growth (57%) and an increase in employees using tech (66%) have also contributed.

Security teams are increasingly worried about a range of identity-related attacks. Phishing (83%) was the most common concern, followed by social engineering (70%) and compromise of privileged identities (64%). All respondents say a lack of strong IAM policies introduces risk.

Despite the growth of identities and concern for their security, only 53% of respondents report security has any level of ownership for workforce IAM. While 99% say security is involved with IAM activities, only 24% say the security team has "excellent" awareness of IAM. They attribute this to lack of goal alignment between security and the organization (33%), reporting structure (30%), history of security not being involved (30%), and resistance from other teams (24%). Budget ownership (40%) is the top reason for companies holding back on IAM investment.

Read more details in the full report here.

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "Criminals Hide Fraud Behind the Green Lock Icon."

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.