+

Top 10 Misconceptions of a Policy-Based Approach

Even for senior software developers, wading into the world of IAM (Identity & Access Management) and access control can be daunting. Making your way through the acronyms is a chore in and of itself — RBAC, ABAC, PBAC, XACML, SAML, etc. Then, you must wrap your head around the complexities of roles, permissions, attributes and so on.

But, at its core, a policy-based access control model (also referred to as Attribute Based Access Control or “ABAC”) is a concept any developer can understand. The phrase “access control” refers to application mechanisms that govern what each user can (or can’t) see and do. And a “policy” is a principle, rule, or guideline formulated or adopted by an organization.

See 10 major misconceptions about a policy-based approach to access control and learn how those myths have been dispelled and why.

Other Resources

White Papers
Why traditional IAM solutions are no longer enough
Identity and Access Management (IAM) solutions are an amazing advancement and have saved countless headaches and work hours for today’s IT professionals. Without these solutions,...
White Papers
Evolving from RBAC to next generation ABAC
Enterprises face a rapid expansion of diverse users alongside an influx of applications, devices, APIs, and microservices. The amount of data created and consumed by...
White Papers
KuppingerCole Report – Market Compass: Dynamic Authorization Management
The KuppingerCole Market Compass on Dynamic Authorization Management provides an overview of the product or service offerings in selected market segments. The report has profiled...