Network Security
Understand the Default Web Access Policies
Table of Contents
Expand All
|
Collapse All
Network Security Docs
-
- Security Policy
-
- Security Profile Groups
- Security Profile: AI Security
- Security Profile: WildFire® Analysis
- Security Profile: Antivirus
- Security Profile: Vulnerability Protection
- Security Profile: Anti-Spyware
- Security Profile: DNS Security
- Security Profile: DoS Protection Profile
- Security Profile: File Blocking
- Security Profile: URL Filtering
- Security Profile: Data Filtering
- Security Profile: Zone Protection
-
- Policy Object: Address Groups
- Policy Object: Regions
- Policy Object: Traffic Objects
- Policy Object: Applications
- Policy Object: Application Groups
- Policy Object: Application Filter
- Policy Object: Services
- Policy Object: Auto-Tag Actions
- Policy Object: Devices
-
- Uses for External Dynamic Lists in Policy
- Formatting Guidelines for an External Dynamic List
- Built-in External Dynamic Lists
- Configure Your Environment to Access an External Dynamic List
- Configure your Environment to Access an External Dynamic List from the EDL Hosting Service
- Retrieve an External Dynamic List from the Web Server
- View External Dynamic List Entries
- Enforce Policy on an External Dynamic List
- Find External Dynamic Lists That Failed Authentication
- Disable Authentication for an External Dynamic List
- Policy Object: HIP Objects
- Policy Object: Schedules
- Policy Object: Quarantine Device Lists
- Policy Object: Dynamic User Groups
- Policy Object: Custom Objects
- Policy Object: Log Forwarding
- Policy Object: Authentication
- Policy Object: Decryption Profile
- Policy Object: Packet Broker Profile
-
-
-
- The Quantum Computing Threat
- How RFC 8784 Resists Quantum Computing Threats
- How RFC 9242 and RFC 9370 Resist Quantum Computing Threats
- Support for Post-Quantum Features
- Post-Quantum Migration Planning and Preparation
- Best Practices for Resisting Post-Quantum Attacks
- Learn More About Post-Quantum Security
-
-
-
- Investigate Reasons for Decryption Failure
- Identify Weak Protocols and Cipher Suites
- Troubleshoot Version Errors
- Troubleshoot Unsupported Cipher Suites
- Identify Untrusted CA Certificates
- Repair Incomplete Certificate Chains
- Troubleshoot Pinned Certificates
- Troubleshoot Expired Certificates
- Troubleshoot Revoked Certificates
Understand the Default Web Access Policies
Understand the Default Web Access Policies
Where Can I Use This? | What Do I Need? |
---|---|
|
|
Web Security policies apply to outbound traffic and web applications. When you enable Web
Security, the following are enabled by default, but you can adjust these settings
later:
- Best Practice Decryption
- Best practice settings for decryption are enabled.
- Global Web Access
- Blocks certain URL categories and allows all others with default Threat Management and DNS Security settings enabled.
- Blocks high-risk web applications and allows all others with default Threat Management and DNS Security settings enabled.
- You can adjust these settings later.
- Global Catch All
- Allows web traffic with default Threat Management and DNS Security settings enabled.
Threat Management and DNS Security settings are based on the following global
defaults, but can be adjusted as needed:
- Vulnerability Protection
- Blocks medium and above criticality threats. Advanced settings let you configure these settings for individual threat categories.
- Wildfire
- Enabled for upload and download of all file types.
- Detect Command-And-Control (C2) Activity
- Blocks medium and above criticality threats. Advanced settings let you configure these settings for individual threat categories
- Malware Protection
- Enabled with default actions for http and http2 decoders.
- DNS Security
- Enabled with default (best-practices) actions for supported threat categories. This is only for outbound DNS traffic.
Override Default Web Security Rules
Security Settings for Web Security come from the WebSecurity Snippet by default, but you can override
those settings with your own custom settings or by using a standard profile. Default
Web Access policies come from the Web Security Snippet and can be overridden at any
scope.
