DOCSLIB.ORG

Websense Content Gateway Online Help Version

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Websense Content Gateway Online Help Version Online Help Websense Content Gateway v7.6 Websense Content Gateway Online Help April, 2011 R033011760 Copyright © 1996-2011 Yahoo, Inc., and Websense, Inc. All rights reserved. This document contains proprietary and confidential information of Yahoo, Inc and Websense, Inc. The contents of this document may not be disclosed to third parties, copied, or duplicated in any form, in whole or in part, without prior written permission of Websense, Inc. Websense, the Websense Logo, ThreatSeeker and the YES! Logo are registered trademarks of Websense, Inc. in the United States and/or other countries. Websense has numerous other unregistered trademarks in the United States and internationally. All other trademarks are the property of their respective owners. Every effort has been made to ensure the accuracy of this manual. However, Websense Inc., and Yahoo, Inc. make no warranties with respect to this documentation and disclaim any implied warranties of merchantability and fitness for a particular purpose. Websense Inc. shall not be liable for any error or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual or the examples herein. The information in this documentation is subject to change without notice. Traffic Server is a trademark or registered trademark of Yahoo! Inc. in the United States and other countries. Red Hat is a registered trademark of Red Hat Software, Inc. Linux is a registered trademark of Linus Torvalds. Microsoft, Windows, Windows NT, and Active Directory are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Mozilla and Firefox are registered trademarks of the Mozilla Foundation. Netscape and Netscape Navigator are registered trademarks of Netscape Communications Corporation in the United States and in other countries. UNIX is a registered trademark of AT&T. All other trademarks are property of their respective owners. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure of the technical data contained in this document by the Government is subject to restrictions as set forth in subdivision (c) (1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227-7013 and/or in similar or successor clauses in the FAR, or in the DOD or NASA FAR Supplement. Unpublished rights reserved under the Copyright Laws of the United States. Contractor/manufacturer is Websense, Inc, 10240 Sorrento Valley Parkway, San Diego, CA 92121. Portions of Websense Content Gateway include third-party technology used under license. Notices and attribution are included elsewhere in this manual. Contents Contents Topic 1 Overview . 1 TRITON Unified Security Center . 2 Deployment options . 3 As a Web proxy cache. 3 In a cache hierarchy. 3 In a managed cluster . 3 As an SSL server. 4 As a DNS proxy cache . 4 Components . 5 Cache. 5 RAM cache . 5 Adaptive Redirection Module . 5 Host database. 5 DNS resolver. 6 Processes . 6 Administration tools . 7 Proxy traffic analysis features . 7 Online Help . 8 Technical Support. 8 Topic 2 Getting Started . 11 Starting Content Gateway Manager . 11 Entering your subscription key. 12 Providing system information . 13 Verifying that the proxy is processing Internet requests . 14 Using the command-line interface . 14 Starting and stopping Content Gateway on the Command Line . 15 Topic 3 Web Proxy Caching . 17 Cache requests . 17 Ensuring cached object freshness . 18 HTTP object freshness . 18 FTP object freshness . 22 Scheduling updates to local cache content . 22 Configuring the Scheduled Update option . 23 Forcing an immediate update . 24 Pinning content in the cache. 24 Setting cache pinning rules . 25 Enabling cache pinning . 25 To cache or not to cache? . 25 Online Help i Contents Caching HTTP objects . 25 Client directives . 26 Origin server directives . 27 Configuration directives . 29 Forcing object caching . 31 Caching HTTP alternates . 31 Configuring how Content Gateway caches alternates. 31 Limiting the number of alternates for an object . 32 Caching FTP objects. 32 Disabling FTP over HTTP caching. 33 Topic 4 Explicit Proxy Caching . 35 Manual browser configuration . 35 Using a PAC file. 36 Sample PAC file . 37 Using WPAD . 38 Configuring FTP clients in an explicit proxy environment . 39 Topic 5 Transparent Proxy and ARM . 43 Enabling the ARM . 44 Transparent interception strategies . 45 Transparent interception with a Layer 4 switch . 45 Transparent interception with WCCP v2 devices . 46 Transparent interception and multicast mode . 59 Transparent interception with policy-based routing . 60 Transparent interception with software-based routing . 60 Interception bypass . 61 Dynamic bypass rules . 62 Static bypass rules . 63 Viewing the current set of bypass rules . 64 Connection load shedding . 64 Reducing DNS lookups . 65 IP spoofing . 66 IP spoofing and the flow of traffic . 66 Enabling IP spoofing: . 68 Topic 6 Clusters. 69 Management clustering . 70 SSL Manager clustering . 70 Configuring SSL Manager clustering: . 71 Changing clustering configuration . 72 Adding nodes to a cluster . 72 Deleting nodes from a cluster . 74 ii Websense Content Gateway Contents Virtual IP failover. 74 What are virtual IP addresses? . 75 Enabling and disabling virtual IP addressing . 75 Adding and editing virtual IP addresses . 76 Topic 7 Hierarchical Caching . 77 HTTP cache hierarchies . ..
Load more

Recommended publications
  • Elastic Load Balancing Application Load Balancers Elastic Load Balancing Application Load Balancers
    Elastic Load Balancing Application Load Balancers Elastic Load Balancing Application Load Balancers Elastic Load Balancing: Application Load Balancers Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Elastic Load Balancing Application Load Balancers Table of Contents What is an Application Load Balancer? .................................................................................................. 1 Application Load Balancer components ......................................................................................... 1 Application Load Balancer overview ............................................................................................. 2 Benefits of migrating from a Classic Load Balancer ........................................................................ 2 Related services ......................................................................................................................... 3 Pricing ...................................................................................................................................... 3 Getting started .................................................................................................................................
    [Show full text]
  • The TAXII HTTP Protocol Binding Specification Version 1.0 (Draft)
    THE MITRE CORPORATION The TAXII HTTP Protocol Binding Specification Version 1.0 (draft) Mark Davidson, Charles Schmidt 11/16/2012 The Trusted Automated eXchange of Indicator Information (TAXII™) specifies mechanisms for exchanging structured cyber threat information between parties over the network. This document describes how to use HTTP to convey TAXII messages. The TAXII HTTP Binding Date: 11-16-2012 Trademark Information TAXII and STIX are trademarks of The MITRE Corporation. This technical data was produced for the U. S. Government under Contract No. HSHQDC-11-J-00221, and is subject to the Rights in Technical Data-Noncommercial Items clause at DFARS 252.227-7013 (NOV 1995) ©2012 The MITRE Corporation. All Rights Reserved. Feedback Community input is necessary for the success of TAXII. Feedback on this or any of the other TAXII Specifications is welcome and can be sent to [email protected]. Comments, questions, suggestions, and concerns are all appreciated. Open Issues Sections 8 and 9 of this document require significant development. 1 Copyright © 2012, The MITRE Corporation. All rights reserved. The TAXII HTTP Binding Date: 11-16-2012 Table of Contents Trademark Information ................................................................................................................................. 1 Feedback ....................................................................................................................................................... 1 Open Issues ..................................................................................................................................................
    [Show full text]
  • Taxii-V2.1-Cs01.Pdf
    TAXII™ Version 2.1 Committee Specification 01 27 January 2020 This stage: https://docs.oasis-open.org/cti/taxii/v2.1/cs01/taxii-v2.1-cs01.docx (Authoritative) https://docs.oasis-open.org/cti/taxii/v2.1/cs01/taxii-v2.1-cs01.html https://docs.oasis-open.org/cti/taxii/v2.1/cs01/taxii-v2.1-cs01.pdf Previous stage: https://docs.oasis-open.org/cti/taxii/v2.1/csprd02/taxii-v2.1-csprd02.docx (Authoritative) https://docs.oasis-open.org/cti/taxii/v2.1/csprd02/taxii-v2.1-csprd02.html https://docs.oasis-open.org/cti/taxii/v2.1/csprd02/taxii-v2.1-csprd02.pdf Latest stage: https://docs.oasis-open.org/cti/taxii/v2.1/taxii-v2.1.docx (Authoritative) https://docs.oasis-open.org/cti/taxii/v2.1/taxii-v2.1.html https://docs.oasis-open.org/cti/taxii/v2.1/taxii-v2.1.pdf Technical Committee: OASIS Cyber Threat Intelligence (CTI) TC Chairs: Richard Struse ([email protected]), MITRE Corporation Trey Darley ([email protected]), CCB/CERT.be Editors: Bret Jordan ([email protected]), Broadcom Drew Varner ([email protected]), NineFX, Inc. Related work: This specification replaces or supersedes: ● TAXII™ Version 2.0. Edited by John Wunder, Mark Davidson, and Bret Jordan. Latest stage: http://docs.oasis-open.org/cti/taxii/v2.0/taxii-v2.0.html. ● TAXII™ Version 1.1.1. Part 1: Overview. Edited by Mark Davidson, Charles Schmidt, and Bret Jordan. Latest stage: http://docs.oasis-open.org/cti/taxii/v1.1.1/taxii-v1.1.1-part1-overview.html.
    [Show full text]
  • Mobile Device Management Protocol Reference
    Mobile Device Management Protocol Reference Developer Contents 1 About Mobile Device Management 7 At a Glance ................................................ 8 The MDM Check-in Protocol Lets a Device Contact Your Server ................... 8 The MDM Protocol Sends Management Commands to the Device .................. 8 The Way You Design Your Payload Matters .............................. 8 The Device Enrollment Program Lets You Configure Devices with the Setup Assistant ........ 8 The Volume Purchase Program Lets You Assign App Licenses to Users and Devices ......... 9 Apple Push Notification Certificates Can Be Generated Through the Apple Push Certificates Portal .. 9 See Also ................................................. 9 2 MDM Check-in Protocol 10 Structure of a Check-in Request ...................................... 10 Supported Check-in Commands ..................................... 11 Authenticate Message ........................................ 11 TokenUpdate Message ........................................ 12 CheckOut .............................................. 13 3 Mobile Device Management Protocol 14 Structure of MDM Payloads ........................................ 16 Structure of MDM Messages ....................................... 18 MDM Command Payloads ......................................... 20 MDM Result Payloads ........................................... 20 MDM Protocol Extensions ......................................... 21 macOS Extensions .......................................... 21 Network User Authentication
    [Show full text]
  • 403 Forbidden: a Global View of CDN Geoblocking
    403 Forbidden: A Global View of CDN Geoblocking Allison McDonald Matthew Bernhard Luke Valenta University of Michigan University of Michigan University of Pennsylvania∗ [email protected] [email protected] [email protected] Benjamin VanderSloot Will Scott Nick Sullivan University of Michigan University of Michigan Cloudflare [email protected] [email protected] [email protected] J. Alex Halderman Roya Ensafi University of Michigan University of Michigan [email protected] [email protected] ABSTRACT 1 INTRODUCTION We report the first wide-scale measurement study of server- Researchers have devoted significant effort to measuring side geographic restriction, or geoblocking, a phenomenon and circumventing nation-state Internet censorship (e.g., [23, in which server operators intentionally deny access to users 39, 49]). However, censorship is not the only reason why from particular countries or regions. Many sites practice online content may be unavailable in particular countries. geoblocking due to legal requirements or other business Service operators and publishers sometimes deny access reasons, but excessive blocking can needlessly deny valuable themselves, server-side, to clients from certain locations. content and services to entire national populations. This style of geographic restriction, termed geoblocking [45], To help researchers and policymakers understand this may be applied to comply with international regulations, phenomenon, we develop a semi-automated system to detect local legal requirements, or licensing restrictions, to enforce instances where whole websites were rendered inaccessible market segmentation, or to prevent abuse. due to geoblocking. By focusing on detecting geoblocking Geoblocking has drawn increasing scrutiny from policy- capabilities offered by large CDNs and cloud providers, we makers. A 2013 study by the Australian parliament concluded can reliably distinguish the practice from dynamic anti-abuse that geoblocking forces Australians to pay higher prices and mechanisms and network-based censorship.
    [Show full text]
  • Webdav) Protocol: Microsoft Extensions
    [MS-WDVME]: Web Distributed Authoring and Versioning (WebDAV) Protocol: Microsoft Extensions Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL’s, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft Open Specification Promise or the Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected]. Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights.
    [Show full text]
  • Warning. This Thread Contains Spoilers. Please Note That Alpha Cannot Be Included in Your Lab Report
    09/01/2018 Offensive Security's Complete Guide to Alpha Welcome, OS­26810 Notifications My Profile Settings Log Out What's New? Forum New Posts Private Messages FAQ Calendar Community Forum Actions Quick Links Forum Pentesting With Kali Lab Machines Public Network 10.11.1.71 Offensive Security's Complete Guide to Alpha Results 1 to 10 of 125 Page 1 of 13 1 2 3 11 ... Last Reply to Thread Thread: Offensive Security's Complete Guide to Alpha Thread Tools Search Thread 05­12­2016, 03:58 PM #1 g0tmi1k Join Date: Jun 2011 Offsec Staff Posts: 538 Offensive Security's Complete Guide to Alpha Welcome to Offensive Security's complete guide to "Alpha". Warning. This thread contains spoilers. Please note that Alpha cannot be included in your Lab Report Table of Contents: Introduction Abstract/Overview Reconnaissance DNS Lab Notes/Existing Machines Offsec­Ninja/IRC Bot Hint Information Gathering Port Scanning Services (Part 1 ­ SSH) Services (Part 2 ­ HTTP) Web Application (Part 1 ­ Main) Web Application (Part 2 ­ Hidden) Vulnerabilities vs Exploits vs CVEs SearchSploit (Part 1) Web Application (Part 3 ­ [SPOILER]) SearchSploit (Part 2) [SPOILER] Web Scanners Limited Shell Exploit #1 ­ Manually (Part 1 ­ PoC) Exploit #1 ­ Manually (Part 2 ­ Remote Shell) Exploit #1 ­ Manually (Part 3 ­ Bash Trick) Exploit #2 ­ Exploit­DB Exploit #3 ­ Metasploit Privilege Escalation Information Gathering (Part 1 ­ OS) Information Gathering (Part 2 ­ Running Processes) Information Gathering (Part 3 ­ Installed Packages) Information Gathering (Part 4 ­ Installed Programs) Information Gathering (Part 5 ­ Config files) Method #1 ­ [SPOILER] (Part 1 ­ Setup) Method #1 ­ [SPOILER] (Part 2 ­ Exploiting) Method #2 ­ [SPOILER] (Part 1 ­ SSH) Method #2 ­ [SPOILER] (Part 2 ­ SU) Post Exploitation Last updated: 2017­Sept­12 Last edited by g0tmi1k; 09­12­2017 at 12:13 PM.
    [Show full text]
  • Webdav) Protocol: Microsoft Extensions
    [MS-WDVME]: Web Distributed Authoring and Versioning (WebDAV) Protocol: Microsoft Extensions Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected].
    [Show full text]
  • Amazon Simple Storage Service API Reference API Version 2006-03-01 Amazon Simple Storage Service API Reference
    Amazon Simple Storage Service API Reference API Version 2006-03-01 Amazon Simple Storage Service API Reference Amazon Simple Storage Service: API Reference Copyright © 2014 Amazon Web Services, Inc. and/or its affiliates. All rights reserved. The following are trademarks of Amazon Web Services, Inc.: Amazon, Amazon Web Services Design, AWS, Amazon CloudFront, Cloudfront, Amazon DevPay, DynamoDB, ElastiCache, Amazon EC2, Amazon Elastic Compute Cloud, Amazon Glacier, Kindle, Kindle Fire, AWS Marketplace Design, Mechanical Turk, Amazon Redshift, Amazon Route 53, Amazon S3, Amazon VPC. In addition, Amazon.com graphics, logos, page headers, button icons, scripts, and service names are trademarks, or trade dress of Amazon in the U.S. and/or other countries. Amazon©s trademarks and trade dress may not be used in connection with any product or service that is not Amazon©s, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Amazon Simple Storage Service API Reference Table of Contents Welcome to Amazon S3 ................................................................................................................. 1 How Do I...? ......................................................................................................................... 1 Introduction .................................................................................................................................
    [Show full text]
  • Joyn Implementation Guidelines V3.1
    GSM Association Non Confidential Official Document. joyn Implementation Guidelines v3.1 joyn Implementation Guidelines Version 3.1 15 February 2017 . Security Classification – NON CONFIDENTIAL GSMA MATERIAL Copyright Notice Copyright © 2017 GSM Association Antitrust Notice The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy. 3.1 Page 1 of 86 GSM Association Non Confidential Official Document. joyn Implementation Guidelines v3.1 Table of Contents 1 Introduction 5 1.1 Scope 5 1.2 Future queries and clarifications 5 1.3 Definition of Terms 5 1.4 Document Cross-References 7 2 joyn implementation clarifications 10 2.1 General issues 10 ID_1_1 Reject_btn parameter 10 ID_1_2 Blushing emotions 10 ID_1_3 HTTP Content server URL prefixes 10 ID_1_4 File Transfer over HTTP: sender upload retries in error cases 11 ID_1_5 Resize video files before transferring 11 ID_1_6 Support for the FTvHTTP download resume by network 12 ID_1_7 Cipher suites support policy for RCS 12 2.2 Configuration issues 13 ID_2_1 FQDN resolution 13 ID_2_2 P-CSCF redundancy 14 ID_2_3 Domain prefixes for provisioning 15 ID_2_4 MSISDN format in configuration request 16 ID_2_5 HTTP request during Wi-Fi Provisioning 16 ID_2_6 Configuration mechanism over PS without Header Enrichment 17 ID_2_7 Provisioning for high service availability 17 ID_2_8 Clarification on usage of the FT CAP ALWAYS ON parameter 18 ID_2_9 Clarification on expected client behaviour when validity period has expired 18 ID_2_10 Clarification on format of the
    [Show full text]
  • Fortiadc D-Series Handbook 4.3.2, Revision 1
    FortiADC™ Handbook - D Series VERSION 4.3.2 FORTINET DOCUMENT LIBRARY http://docs.fortinet.com FORTINET VIDEO GUIDE http://video.fortinet.com FORTINET BLOG https://blog.fortinet.com CUSTOMER SERVICE & SUPPORT https://support.fortinet.com FORTIGATE COOKBOOK http://cookbook.fortinet.com FORTINET TRAINING SERVICES http://www.fortinet.com/training FORTIGUARD CENTER http://www.fortiguard.com END USER LICENSE AGREEMENT http://www.fortinet.com/doc/legal/EULA.pdf FEEDBACK Email: [email protected] December 1, 2015 FortiADC™ Handbook - D Series TABLE OF CONTENTS Introduction .................................................................................................... 10 Features................................................................................................................. 10 Basic network topology.......................................................................................... 10 Scope..................................................................................................................... 11 What’s New ..................................................................................................... 12 Key Concepts and Features.......................................................................... 17 Server load balancing ............................................................................................ 17 Feature Summary ............................................................................................ 17 Authentication and authorization.....................................................................
    [Show full text]
  • IPP Authentication Methods V1.0
    August 16, 2019 Best Practice 5199.10-2019 The Printer Working Group IPP Authentication Methods (IPPAUTH) Status: Approved Abstract: This Best Practice document provides implementation guidance on how to best integrate various authentication mechanisms used over IPP's HTTP and HTTPS transports into IPP protocol exchanges when printer access or print feature policy requires authorization. This is a PWG Best Practice document. For the definition of "PWG Best Practices", see: http://ftp.pwg.org/pub/pwg/general/pwg-process30.pdf This document is available electronically at: https://ftp.pwg.org/pub/pwg/ipp/informational/bp-ippauth10-20190816-5199.10.odt https://ftp.pwg.org/pub/pwg/ipp/informational/bp-ippauth10-20190816-5199.10.pdf Copyright © 2017-2019 The Printer Working Group. All rights reserved. PWG 5199.10-2019 – IPP Authentication Methods (IPPAUTH) August 16, 2019 Copyright © 2017-2019 The Printer Working Group. All rights reserved. Title: IPP Authentication Methods (IPPAUTH) The material contained herein is not a license, either expressed or implied, to any IPR owned or controlled by any of the authors or developers of this material or the Printer Working Group. The material contained herein is provided on an “AS IS” basis and to the maximum extent permitted by applicable law, this material is provided AS IS AND WITH ALL FAULTS, and the authors and developers of this material and the Printer Working Group and its members hereby disclaim all warranties and conditions, either expressed, implied or statutory, including, but not limited to, any (if any) implied warranties that the use of the information herein will not infringe any rights or any implied warranties of merchantability or fitness for a particular purpose.
    [Show full text]