Edition Differences
Currently, CBH provides standard and professional editions. The standard edition provides the following asset specifications: 50, 100, 200, 500, 1,000, 2,000, and 5,000. The professional edition provides the following asset specifications: 50, 100, 200, 500, 1,000, 2,000, and 5,000.
For more details, see What Are Editions Available in CBH?
Differences on Specifications
For details about specifications, see Table 1 Configuration of different specifications.
Asset Quantity |
Max. Concurrent Connections |
CPUs |
Memory |
System Disk |
Data Disk |
---|---|---|---|---|---|
50 |
50 |
4 cores |
8 GB |
100 GB |
500 GB |
100 |
100 |
4 cores |
8 GB |
100 GB |
1000 GB |
200 |
200 |
4 cores |
8 GB |
100 GB |
1000 GB |
500 |
500 |
8 cores |
16 GB |
100 GB |
2,000 GB |
1,000 |
1,000 |
8 cores |
16 GB |
100 GB |
2,000 GB |
2,000 |
1,500 |
8 cores |
16 GB |
100 GB |
2,000 GB |
5,000 |
2,000 |
16 cores |
32 GB |
100 GB |
3,000 GB |
The number of concurrent connections in Table 1 includes only connections established by O&M clients that use character-based protocols (such as SSH or MySQL client). Connections established by O&M clients that use graphic-based protocols (such as H5 web and RDP client) is not included, which is only one third of this number.
Edition Difference
Both editions provide identity authentication, permission control, account management, and operation audit. Apart from those functions, the enhanced edition also provides automatic O&M and database O&M audit.
For details about functions supported by different editions, see Table 2 Functions of different editions.
Function |
Description |
Standard edition |
Professional edition |
---|---|---|---|
Identity authentication |
Two-factor authentication for user accounts CBH allows you to configure multi-factor authentication, such as mobile phone one-time passwords (OTPs), mobile phone SMS messages, USB keys, and dynamic OTP tokens to authenticate user identities. |
Supported |
Supported |
Remote authentication for user accounts CBH also allows you to authenticate user identities through AD, RADIUS, LDAP, and Azure AD remote authentication. |
Supported |
Supported |
|
Permission control |
System access permission CBH allows you to configure department- and role-based permission control so that you can allow a specific system user to access a specific module in a given CBH system. |
Supported |
Supported |
Resource access permission CBH allows you to configure resource access control policies based on users, user groups, managed accounts, and account groups to limit what resources can be assessed. You can also configure two-person authorization policies and command control policies to limit what operations are allowed on a certain resource. |
Supported |
Supported |
|
Two-person authorization CBH allows you to configure two- or multi-person authorization for core sensitive resources. |
Supported |
Supported |
|
Character command interception CBH allows you to configure command control policies to dynamically authorize key operations on character protocol resources. |
Supported |
Supported |
|
Database command interception CBH allows you to configure database control policies to precisely restrict and re-review sensitive and risky database operations.
NOTE:
This function applies to cloud databases as well as self-built databases. |
Not supported |
Supported |
|
Account management |
User lifecycle management
|
Supported |
Supported |
Resource account lifecycle management
|
Supported |
Supported |
|
Host resource management
|
Supported |
Supported |
|
Application resource management
|
Supported |
Supported |
|
Database resource management
|
Not supported |
Supported |
|
Automatic password change for managed accounts
|
Supported |
Supported |
|
Automatic synchronization of managed resource accounts
|
Not supported |
Supported |
|
Operation audit |
System login and operation logging
|
Supported |
Supported |
Resource O&M audit
|
Supported |
Supported |
|
Database operation audit
|
Not supported |
Supported |
|
Efficient O&M |
One-stop web browser O&M
|
Supported |
Supported |
Third-party client O&M
|
Supported |
Supported |
|
Database O&M
|
Not supported |
Supported |
|
Automatic O&M
|
Not supported |
Supported |
|
Ticket application |
Access and command authorization ticket application
|
Supported |
Supported |
Database authorization ticket application
|
Not supported |
Supported |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.