Imperva Cyber Community

Hi All,

I'm currently looking into the benefits of segmenting our onboarded sites using sub accounts. From what I've read so far, the main use case is when you need to only allow certain admins to manage certain sites instead of all onboarded sites. Outside of this, I would love to hear about some other benefits and if there is any best practice around using sub accounts.

Hi Malen,

You are correct, RBAC is the main use case for subaccounts. 

• Strong Tenant & Environment Isolation
  
  • Subaccounts create hard logical separation between environments, teams, or customers.
• Least‑Privilege Access & Delegated Administration
  • Subaccounts let you safely delegate control without giving away the keys.
• Safer Change Management
  • Changes inside one subaccount cannot impact others.
• Clean Organizational Structure at Scale
  
  • Subaccounts bring structure and clarity to large Imperva deployments.
• Operational Efficiency for Security Teams
  • Subaccounts reduce noise and context‑switching.
• Simplified Compliance & Audit Readiness
  • Subaccounts align well with compliance and audit frameworks.
• MSSP & Multi‑Customer Enablement
  • For service providers, subaccounts are non‑negotiable.
• Centralized Governance Without Centralized Risk
  • The parent account retains oversight without operational risk.
    
    

Hi All,

I'm currently looking into the benefits of segmenting our onboarded sites using sub accounts. From what I've read so far, the main use case is when you need to only allow certain admins to manage certain sites instead of all onboarded sites. Outside of this, I would love to hear about some other benefits and if there is any best practice around using sub accounts.