Cisco Cisco Web Security Appliance S170 사용자 가이드
A-10
AsyncOS 9.1 for Cisco Web Security Appliances User Guide
Appendix A Troubleshooting
Policy Problems
If some Access and Routing Policy group memberships are defined by HTTPS and if some Access
Policies block HTTPS, then when you enable the HTTPS Proxy, those Access and Routing Policy groups
become disabled. You can choose to enable the policies at any time, but all HTTPS related configurations
are removed.
Policies block HTTPS, then when you enable the HTTPS Proxy, those Access and Routing Policy groups
become disabled. You can choose to enable the policies at any time, but all HTTPS related configurations
are removed.
Blocked Object Problems
•
•
Some Microsoft Office Files Not Blocked
When you block Microsoft Office files in the Block Object Type section, it is possible that some
Microsoft Office files will not be blocked.
Microsoft Office files will not be blocked.
If you need to block all Microsoft Office files, add
application/x-ole
in the Block Custom MIME
Types field. However, blocking this custom MIME type also blocks all Microsoft Compound Object
format types, such as Visio files and some third-party applications.
format types, such as Visio files and some third-party applications.
Blocking DOS Executable Object Types Blocks Updates for Windows OneCare
When you configure the Web Security appliance to block DOS executable object types, the appliance
also blocks updates for Windows OneCare.
also blocks updates for Windows OneCare.
Identification Profile Disappeared from Policy
Disabling an Identification Profile removes it from associated policies. Verify that the Identification
Profile is enabled and then add it to the policy again.
Profile is enabled and then add it to the policy again.
Policy Match Failures
•
•
•
•
Policy is Never Applied
If multiple Identification Profiles have identical criteria, AsyncOS assigns the transactions to the first
Identification Profile that matches. Therefore, transactions never match the additional, identical
Identification Profiles, and any policies that apply to those subsequent, identical Identification Profiles
are never matched or applied.
Identification Profile that matches. Therefore, transactions never match the additional, identical
Identification Profiles, and any policies that apply to those subsequent, identical Identification Profiles
are never matched or applied.