<< PREVIOUS NEXT >> 

 

CMS CONFIGURATION LIMITS

 

This section provides the CMS configuration limits. The values provided below may not be hard limits in many cases, but exceeding them may lead to an unstable CMS in the deployed environment. Virsec highly recommends staying within these limits. Reach out to the Virsec technical team in case your setup/environment requires scaling beyond these numbers.

 

Configuration

Maximum/Recommended Limit

Number of probes registered with a single CMS instance (Host Only)

2000

Number of probes registered with a single CMS instance (Host+Web/Mem)

1500

Number of Applications on single CMS instance (Web/Mem)

400

Number of Host Profiles per CMS instance

1000

Number of AppControl policies per CMS instance

200

Number of Protection Profiles per CMS instance

200

Number of Protection Actions per CMS instance

200

Number of allowlisted processes in a host profile

5000

Number of allowlisted libraries in a host profile

5000

Number of items in global exclusion list

1000

Number of items in global publisher list

1000

Number of items in global package list

1000

Number of incidents CMS can store at any point

500,000

Number of file events CMS can store at any point

30,000

Number of Users per CMS

100

Number of Roles per CMS

100

Table – CMS Configuration Limits

 

 

<< PREVIOUS NEXT >>