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.

Endpoint Security

09:15 AM
Joe Stanganelli
Joe Stanganelli
Joe Stanganelli

Should All IAM Be CIAM?

CIAM vendors are right that traditional IAM isn't going to cut it for customer-facing solutions - but their sound premises have led to the perverse conclusion of keeping in-house IAM systems suboptimal. What if the power of CIAM could help employees realize better usability and security too?

Identity-management vendors are increasingly sounding the alarm that it's not enough for businesses to purchase identity access management (IAM) solutions; they also have to invest in specialized consumer identity access management (CIAM) solutions for their customers. The reasoning goes like this: customers behave differently from internal business users; they are identified on systems differently, have different needs, are more unpredictable and demand more.

In particular, CIAM vendors urge that it is wrong to extend the same traditional IAM systems to consumer-facing portals because the latter lack the usability that consumers have come to demand.

Employees as second-class identities? "Workplace IAM benefits from having a captive audience -- employees will tolerate poor performance from their authentication systems. However disruptive it may be, they have little recourse but to cope with the system," blogs Sven Dummer, a product-marketing director at CIAM vendor Janrain, in pitching CIAM as a complement to traditional in-house IAM. "Customers are not so forgiving and are likely to stop using a brand app or software platform if it doesn't meet their expectations for easy, fast and reliable access."

Dummer goes on to argue that CIAM scales better, profiles user behavior better and requires IT-security teams to be ready for anything on the open Internet -- and he is not alone in making this argument. To wit, it makes no sense for the IT and security teams to treat customers or other external users in the same semi-lackluster way that they treat employees and other internal users.

This argument, while founded on some solid premises, misses the bigger picture -- that enterprise IT security is falling short of the mark when it comes to meeting in-house security and usability demands. If the justification for CIAM deployment is to improve the customer's user experience anyway, then rather than ensuring that the organization doesn't treat customers as poorly as they do their own employees, the focus should instead be on ensuring that the organization treats its employees at least approximately as well as it treats its customers.

Overlapping CIAM with IAM After all, in a March 2018 report, Gartner identified the "increasing overlap" of CIAM features with traditional in-house IAM features as the top trend driving CIAM design -- particularly as:

  1. B2C IAM deployments approach 70%
  2. Effective CIAM deployment requires a ground-up security architecture that can support it
  3. Customer-facing mobile CIAM interfaces frequently have to access company data commonly managed by an in-house IAM system

Forrester, for its part, has pointed out that -- counter to Dummer's assessment -- poor and unintuitive usability in enterprise IAM solutions will lead to employees quietly thumbing their nose at security controls -- instead constructing and exploiting risky and subversive workarounds (to say nothing of the other risks of poor employee morale). (See: IAM Heads to the Mobile Cloud.) Report after report and headline after headline in cybersecurity agree that, at the end of the day, users -- whether internal or external -- just want their stuff to work, even if it means sacrificing security and data protection. (See: iOS 12: How Apple Keeps Getting Mobile Security Wrong and Uber Loses Customer Data: Customers Yawn & Keep Riding.)

Consequently, if CIAM's flexibility, usability and security are deemed superior for wild-card consumer use cases, why not apply CIAM systems or principles in-house? Why not make things better for everybody?

Reconciling CIAM with in-house demands This proposition bears a wrinkle, however. Andras Cser, one of the co-authors of the aforementioned Forrester report, has previously pointed out that CIAM lacksthe endpoint controls of traditional in-house IAM, where every user and every device are known and approved.

At first glance, this appears to be a huge weakness in CIAM because of the increasing proliferation of endpoint-focused attacks. (See: DHS: Millions of Smartphones Infected With Severe Embedded Vulnerabilities.) Nonetheless, it is a bit of a red herring. As Verizon Business pointed out in its annual Data Breach Investigation Report last year, web-application attacks targeting endpoint devices (including attacks that do not rely upon stolen credentials) have represented the most common attack vector leveraged against enterprise data. Indeed, in 2017, malicious web applications were more than five times more likely to be the cause of a data breach than a physically lost or stolen endpoint device. (See: Data Breach Increase Shows Endpoints Are Under Attack.) Therefore, absent those few attacks that rely upon physical access to an endpoint device (and, in some cases, even then), the loss of strict endpoint control that comes with CIAM implementations can potentially be more than made up for by the focus on controlling access to web applications themselves -- a focus that IT security teams need to have anyway. (See: Unknown Document 742114.)

To be sure, CIAM is not mutually exclusive with the enterprise-security strategies that typically ought accompany traditional in-house IAM. And there are yet further ways to firm up CIAM deployments -- while keeping them flexible enough for common usability.

  • IAM vendors themselves espouse the need for multifactor authentication (MFA) as "industry standard."
  • By the same token (pun unintended), single sign-on (SSO) with federated access can improve usability while relieving employees of having to remember too many ever-changing passwords.
  • Web-app attacks on endpoints can be further avoided or mitigated with basic anti-malware software, improved firewalls and more attentive IP-address lookup and filtering.
  • Regardless of identity-management strategy, common endpoint vulnerabilities can be resolved by pushing out automated software updates, upgrading legacy devices and improving both security training and security culture throughout the organization. (See: Endpoint Security: 3 Big Obstacles to Overcome and Personal Security Begets Enterprise Security.)
  • Most importantly (yet often overlooked), security teams should work with the business side to identify top usability concerns, map out user system interactions from start to finish and identify time periods when systems may be under the most strain from given departments.

Related posts:

— Joe Stanganelli is managing director at research and consulting firm Blackwood King LC. In addition to being an attorney and consultant, he has spent several years analyzing and writing about business and technology trends. Follow him on Twitter at @JoeStanganelli.


Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...