Sizing is based on total named users that were tested with certain traffic profile. You can exceed the limit but you will most likely experience performance degradtion as exceeding the recommended sizing numbers is not recommended.
Notes below from http://www.cisco.com/c/en/us/products/collateral/security/adaptive-security-appliance-asa-software/whitepaper_C11-715169.pdf
Note on sizing: a. Sizing for Cloud Web Security (CWS) is based on named users. This isn’t concurrent users but total number of users who may browse the internet b. Tests used HTTP traffic with 32K object size—every single HTTP GET was answered by an object 32K in size c. Peak bandwidth per seat is 20 Kbps (measured on a 95th percentile basis) d. Traffic profile: HTTP—88% and HTTPS—12% e. Tests were run with authentication using IDFW and the test setup designed such that every GET request would make the ASA apply a header to each request f. Actual internet traffic profile may vary based on usage, but Cisco strongly recommends that customers adhere to the sizing guidelines above
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...