Why End User Accounts Appear Inactive in CloudSOC — and Why That’s Okay

Products

• CASB Gateway Advanced
• CASB Advanced Threat Protection
• CASB Audit
• CASB Gateway
• CASB Security Advanced
• CASB Security Advanced IAAS
• CASB Security Premium
• CASB Security Premium IAAS
• CASB Security Standard
• CASB Securlet IAAS
• CASB Securlet SAAS
• CASB Securlet SAAS With DLP-CDS

Issue/Introduction

As part of the recent migration to Broadcom Login and the deployment of AuthHub, customers may observe that some end user accounts imported from Active Directory appear in an "Inactive" state within the CloudSOC platform. This change is expected and reflects updates to how user roles and access permissions are managed in the new infrastructure. The following explains why this behavior occurs and what it means for your organization.

Resolution

As part of our ongoing infrastructure enhancements, including the migration to Broadcom Login and the deployment of AuthHub, you may notice a change in how end user accounts appear within the CloudSOC platform.

 

What’s Changing?

Following the migration:

Only administrator accounts (System Admins or Limited Access Admins) require an "Active" status to access the CloudSOC Console.
End user accounts imported from Windows Active Directory will now appear as "Inactive" by default.

This is expected behavior and does not indicate an issue with your configuration.

 

Why This Matters
The account status only affects console access.
End user traffic—whether through Gatelets, Securlets, or Audit—is not impacted by the account status.
This change helps streamline access control and aligns with Broadcom’s zero trust security model.
How It Works

 

With the new AuthHub integration:

When a user account is synced from Active Directory, it is checked against Broadcom Login.
If the user has any administrator role in Broadcom Login, their account is marked Active.
If not, the account is set to Inactive, as it does not require console access.