Please use your KuppingerCole account to log in or
create one, if you don't have it yet.
As opposed to traditional monolithic applications, a (micro)service-based architecture comprises multiple loosely coupled modules (“services”) that serve specific business purposes and communicate over lightweight network protocols. Such services can be developed, deployed and scaled independently on different platforms, which greatly reduces the time needed to bring as new product to market and allows for continuous delivery development process, where small changes to the business logic of an individual service can be quickly introduced and deployed.
However, when designing a (micro)-service architecture, dealing with identity and security becomes a much more complicated task than in traditional monolithic applications: each individual component must know which user is interacting with it and which access rights are granted to him. Externalizing and centralizing access management is a natural choice for microservices systems to ensure consistently secure and scalable authorization. Implementing the authorization service itself as a microservice, providing policy-driven access control for other microservices and APIs seems to be just as natural… Or is it?
Language: English • Duration: 53:28 • Resolution: 1280x720
ARCON PAM SaaS
The Role of APIs for Business
OT Discovery & Monitoring
Blockchain & Distributed Ledgers
Privacy Enhancement Technology
Real Time Security Monitoring & Intelligence
Privileged Access Management
Privacy and Consent Management
AI/ML in Cybersecurity