Using CASB to Establish User Access, Control of Critical AssetsThomas Likas of Takeda Pharmaceuticals on Deploying a Cloud Access Security Broker
Applying cloud access security broker's three functionalities - API-level integration with managed device transfer for visibility, in-line CASB for proxy and other devices, and its control over cloud and other access points - helps provide better control and the ability to protect and secure user access, says Thomas Likas, global head, security architecture, and engineering, at Takeda Pharmaceuticals.
Likas says, "One of the mistakes I made in deploying CASB technology was to implement it first and then to think of matching with the use business case on protecting the access from managed and unmanaged devices." That approach that doesn't align well he says.
In this interview with Information Security Media Group, Likas discusses:
- Enforcing compliance policies in a CASB environment;
- Risk quantification methods in a CASB model;
- The relevance of SASE in a CASB environment.
Likas is the global head of security architecture and engineering at Takeda Pharmaceuticals in Germany. He has worked in IT for the past 21 years, spending 11+ years in cybersecurity. He has supported several large-scale transformation activities, the latest one being Takeda's journey to 'zero trust' with a strategic move to the AWS platform.