On the Cisco Web Security Appliance, the default global Identification Profile that AsyncOS creates does not require authentication by default — it passively matches all client requests that no other, more specific profile has already claimed, and an administrator must deliberately enable authentication or reposition a guest/authenticating profile ahead of it. Identification Profiles are processed sequentially in the order they are listed (top to bottom), not alphabetically, and a profile can be associated with more than one user group when multiple realms/groups are included in its membership definition, so those other statements about defaults are incorrect.
Community Discussion