LogoLogo
SupportFeedbackLogin
  • WELCOME
    • Welcome to Veriam docs
    • Admin Portal
    • Customer Portal
  • FOR PROVIDERS
    • Customer accounts
    • Customer users
    • CIAM
      • Getting started
      • Connect your application
        • Application settings
      • Set up access controls
      • Role based access
        • Configuring roles
        • Adding permissions to roles
      • Policy based access
        • Configuring policies
      • Attribute based access
      • Resource based access
      • Filters
      • Provide access to customers
    • Subscription Management
      • Merchant of Record
      • Getting started
      • Setup access rules for subscriptions
      • Configure your plans
      • Set up your pricing page
      • Pricing models
      • Billing & invoicing
      • Managing subscriptions
        • Create subscriptions
        • Cancel subscriptions
        • View payments & invoices
  • Contracting
  • FOR CUSTOMERS
    • Manage your organization
      • Set up your organization
      • Add your users
      • Manage users
      • Manage employee access
      • Provide access to my application for my own employees
    • Manage your account
      • Create account
      • Join your organization
      • Manage my own profile
      • Account security
      • Forgot password
    • Manage your subscriptions
      • Get a new subscription
      • Cancel subscriptions
      • Manage users of subscriptions
      • View subscription details
      • Billing contact
Powered by GitBook
LogoLogo

Product

  • CIAM
  • Subscription Management
  • Contracting

Company

  • About Us
  • Contact
  • Foundation

Support

  • Log a ticket
  • Give us Feedback

2024 Veriam

On this page
  • Why Use PBAC?
  • PBAC on Veriam

Was this helpful?

  1. FOR PROVIDERS
  2. CIAM

Policy based access

Policy-Based Access Control (PBAC) is a security framework that governs access to resources based on defined policies. Unlike traditional role-based models, PBAC evaluates contextual attributes, such as user identity, device type, location, and time, to dynamically enforce access decisions. This approach allows for greater flexibility and security, ensuring that access is granted based on real-time conditions rather than static roles.

Why Use PBAC?

1. Enhanced Security

PBAC enforces strict access policies by considering multiple factors beyond just user roles. By incorporating attributes such as risk levels, device security posture, and contextual information, PBAC reduces unauthorized access and minimizes security threats.

2. Fine-Grained Access Control

Unlike Role-Based Access Control (RBAC), which assigns users predefined roles, PBAC enables organizations to define precise access conditions. Policies can be tailored to specific tasks, ensuring that users only have the necessary permissions based on their current situation.

3. Adaptive and Dynamic Access

PBAC allows organizations to implement real-time access decisions. Policies can dynamically adjust based on changing risk factors, ensuring that access permissions evolve in response to security needs and regulatory requirements.

4. Compliance and Audit Readiness

Regulatory frameworks such as GDPR, HIPAA, and ISO 27001 require stringent access control mechanisms. PBAC facilitates compliance by ensuring that access is granted based on defined policies and monitored in real time. This improves audit readiness and helps organizations meet regulatory obligations.

5. Scalability and Maintainability

Managing access in large organizations with thousands of users can be complex. PBAC simplifies access management by centralizing policies that apply across multiple systems and users. This reduces administrative overhead and makes it easier to update access rules without modifying individual user permissions.

PBAC on Veriam

Veriam supports PBAC out for the box, fully integrated into the CIAM solution. You don't need any additional external integrations to provide access to your applications or resources based on policyies. You can even combine the flexibility of policy based access with the more traditional role based access.

Because of the flexibility of our policies, our policy based access can also be used to setup Attribute Based Access Control (ABAC) and Resource Based Access Control (RBAC).

PreviousAdding permissions to rolesNextConfiguring policies

Last updated 3 months ago

Was this helpful?