DOCSLIB.ORG

BIG-IP Acceleration

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
BIG-IP Acceleration BIG-IP® Acceleration: Concepts Version 13.0.0 Table of Contents Table of Contents Introducing Acceleration............................................................................................................9 Overview: Introduction to acceleration............................................................................... 9 Origin web server load balancing............................................................................9 About data centers.................................................................................................. 9 Data compression................................................................................................. 10 Data deduplication.................................................................................................10 Optimization of TCP connections..........................................................................10 Caching objects.....................................................................................................11 Optimization of HTTP protocol and web applications............................................11 Overview: BIG-IP Acceleration.........................................................................................11 Application management.......................................................................................12 Application monitoring...........................................................................................12 Deployment of Distributed BIG-IP Application Acceleration..................................12 Management of requests to origin web servers.................................................... 12 Management of responses to clients.....................................................................13 Flow of requests and responses........................................................................... 14 About symmetric optimization using iSession on BIG-IP systems........................ 15 Accelerating Traffic with Acceleration Profiles......................................................................17 About HTTP compression profiles................................................................................... 17 HTTP Compression profile options....................................................................... 17 About Web Acceleration profiles...................................................................................... 17 Web Acceleration profile settings.......................................................................... 18 Meta characters.....................................................................................................19 Web Acceleration Profile statistics description......................................................21 About iSession profiles.....................................................................................................22 Screen capture showing compression settings..................................................... 22 About CIFS traffic optimization.........................................................................................23 About MAPI optimization..................................................................................................23 About TCP profiles...........................................................................................................24 TCP Profiles for LAN traffic optimization............................................................... 24 TCP Profiles for WAN traffic optimization..............................................................24 About tcp-mobile-optimized profile settings...........................................................25 About mptcp-mobile-optimized profile settings......................................................26 About HTTP2 profiles.......................................................................................................26 About HTTP/2 profiles...........................................................................................27 HTTP/2 profile settings..........................................................................................28 About NTLM profiles........................................................................................................ 29 About OneConnect profiles..............................................................................................29 OneConnect and HTTP profiles............................................................................ 31 OneConnect and SNATs.......................................................................................31 OneConnect and NTLM profiles............................................................................31 Managing Traffic with Bandwidth Controllers........................................................................33 Overview: Bandwidth control management......................................................................33 Bandwidth controllers vs. rate shaping............................................................................ 33 About static bandwidth control policies............................................................................ 33 About dynamic bandwidth control policies....................................................................... 33 3 Table of Contents Example of a dynamic bandwidth control policy.............................................................. 34 Managing Traffic with Rate Shaping....................................................................................... 37 Introduction to rate shaping..............................................................................................37 About rate classes............................................................................................................37 Rate class name.............................................................................................................. 38 Base rate..........................................................................................................................38 Ceiling rate.......................................................................................................................38 Burst size......................................................................................................................... 38 Depleting the burst reservoir............................................................................................39 Replenishing a burst reservoir......................................................................................... 39 About specifying a non-zero burst size ........................................................................... 39 About the direction setting............................................................................................... 40 About the parent class..................................................................................................... 40 About shaping policy........................................................................................................41 About queue method........................................................................................................41 About drop policy............................................................................................................. 41 Using Acceleration Policies to Manage and Respond to HTTP Requests.......................... 43 Overview: Acceleration policies....................................................................................... 43 Policies screen access.......................................................................................... 43 Types of acceleration policies................................................................................44 BIG-IP acceleration policies options......................................................................44 Acceleration policy selection................................................................................. 45 Customization of acceleration policies.................................................................. 45 Creation of user-defined policies...........................................................................46 Publication of acceleration policies....................................................................... 46 About the Acceleration Policy Editor role.............................................................. 46 Acceleration policies exported to XML files...........................................................46 Overview: Policy Matching............................................................................................... 46 Resolution rules when multiple nodes match........................................................47 Unmatched requests............................................................................................. 49 An example matching rule................................................................................................49 Overview: Policy Editor screen.........................................................................................49 Policy Editor screen parts......................................................................................50 Policy Tree.............................................................................................................51 Acceleration policy rule inheritance.......................................................................51 Inheritance rule parameters.................................................................................
Load more

Recommended publications
  • Application Profile Avi Networks — Technical Reference (16.3)
    Page 1 of 12 Application Profile Avi Networks — Technical Reference (16.3) Application Profile view online Application profiles determine the behavior of virtual services, based on application type. The application profile types and their options are described in the following sections: HTTP Profile DNS Profile Layer 4 Profile Syslog Profile Dependency on TCP/UDP Profile The application profile associated with a virtual service may have a dependency on an underlying TCP/UDP profile. For example, an HTTP application profile may be used only if the TCP/UDP profile type used by the virtual service is set to type TCP Proxy. The application profile associated with a virtual service instructs the Service Engine (SE) to proxy the service's application protocol, such as HTTP, and to perform functionality appropriate for that protocol. Application Profile Tab Select Templates > Profiles > Applications to open the Application Profiles tab, which includes the following functions: Search: Search against the name of the profile. Create: Opens the Create Application Profile popup. Edit: Opens the Edit Application Profile popup. Delete: Removes an application profile if it is not currently assigned to a virtual service.Note: If the profile is still associated with any virtual services, the profile cannot be removed. In this case, an error message lists the virtual service that still is referencing the application profile. The table on this tab provides the following information for each application profile: Name: Name of the Profile. Type: Type of application profile, which will be either: DNS: Default for processing DNS traffic. HTTP: Default for processing Layer 7 HTTP traffic.
    [Show full text]
  • SSL/TLS Implementation CIO-IT Security-14-69
    DocuSign Envelope ID: BE043513-5C38-4412-A2D5-93679CF7A69A IT Security Procedural Guide: SSL/TLS Implementation CIO-IT Security-14-69 Revision 6 April 6, 2021 Office of the Chief Information Security Officer DocuSign Envelope ID: BE043513-5C38-4412-A2D5-93679CF7A69A CIO-IT Security-14-69, Revision 6 SSL/TLS Implementation VERSION HISTORY/CHANGE RECORD Person Page Change Posting Change Reason for Change Number of Number Change Change Initial Version – December 24, 2014 N/A ISE New guide created Revision 1 – March 15, 2016 1 Salamon Administrative updates to Clarify relationship between this 2-4 align/reference to the current guide and CIO-IT Security-09-43 version of the GSA IT Security Policy and to CIO-IT Security-09-43, IT Security Procedural Guide: Key Management 2 Berlas / Updated recommendation for Clarification of requirements 7 Salamon obtaining and using certificates 3 Salamon Integrated with OMB M-15-13 and New OMB Policy 9 related TLS implementation guidance 4 Berlas / Updates to clarify TLS protocol Clarification of guidance 11-12 Salamon recommendations 5 Berlas / Updated based on stakeholder Stakeholder review / input Throughout Salamon review / input 6 Klemens/ Formatting, editing, review revisions Update to current format and Throughout Cozart- style Ramos Revision 2 – October 11, 2016 1 Berlas / Allow use of TLS 1.0 for certain Clarification of guidance Throughout Salamon server through June 2018 Revision 3 – April 30, 2018 1 Berlas / Remove RSA ciphers from approved ROBOT vulnerability affected 4-6 Salamon cipher stack
    [Show full text]
  • Protecting Encrypted Cookies from Compression Side-Channel Attacks
    Protecting encrypted cookies from compression side-channel attacks Janaka Alawatugoda1, Douglas Stebila1;2, and Colin Boyd3 1 School of Electrical Engineering and Computer Science, 2 School of Mathematical Sciences 1;2 Queensland University of Technology, Brisbane, Australia [email protected],[email protected] 3 Department of Telematics, Norwegian University of Science and Technology, Trondheim, Norway [email protected] December 28, 2014 Abstract Compression is desirable for network applications as it saves bandwidth; however, when data is compressed before being encrypted, the amount of compression leaks information about the amount of redundancy in the plaintext. This side channel has led to successful CRIME and BREACH attacks on web traffic protected by the Transport Layer Security (TLS) protocol. The general guidance in light of these attacks has been to disable compression, preserving confidentiality but sacrificing bandwidth. In this paper, we examine two techniques|heuristic separation of secrets and fixed-dictionary compression|for enabling compression while protecting high-value secrets, such as cookies, from attack. We model the security offered by these techniques and report on the amount of compressibility that they can achieve. 1This is the full version of a paper published in the Proceedings of the 19th International Conference on Financial Cryptography and Data Security (FC 2015) in San Juan, Puerto Rico, USA, January 26{30, 2015, organized by the International Financial Cryptography Association in cooperation with IACR. 1 Contents 1 Introduction 3 2 Definitions 6 2.1 Encryption and compression schemes.........................6 2.2 Existing security notions................................7 2.3 New security notions..................................7 2.4 Relations and separations between security notions.................8 3 Technique 1: Separating secrets from user inputs9 3.1 The scheme.......................................9 3.2 CCI security of basic separating-secrets technique.................
    [Show full text]
  • A Comprehensive Study of the BREACH A8ack Against HTTPS
    A Comprehensive Study of the BREACH A8ack Against HTTPS Esam Alzahrani, JusCn Nonaka, and Thai Truong 12/03/13 BREACH Overview Browser Reconnaissance and Exfiltraon via AdapCve Compression of Hypertext Demonstrated at BlackHat 2013 by Angelo Prado, Neal Harris, and Yoel Gluck • Chosen plaintext aack against HTTP compression • Client requests a webpage, the web server’s response is compressed • The HTTP compression may leak informaon that will reveal encrypted secrets about the user Network Intrusion DetecCon System Edge Firewall Switch Router DMZ Clients A8acker (Vicm) 2 BREACH Requirements Requirements for chosen plain text (side channel) aack • The web server should support HTTP compression • The web server should support HTTPS sessions • The web server reflects the user’s request • The reflected response must be in the HTML Body • The aacker must be able to measure the size of the encrypted response • The aacker can force the vicCm’s computer to send HTTP requests • The HTTP response contains secret informaon that is encrypted § Cross Site Request Forgery token – browser redirecCon § SessionID (uniquely idenCfies HTTP session) § VIEWSTATE (handles mulCple requests to the same ASP, usually hidden base64 encoded) § Oath tokens (Open AuthenCcaon - one Cme password) § Email address, Date of Birth, etc (PII) SSL/TLS protocol structure • X.509 cerCficaon authority • Secure Socket Layer (SSL) • Transport Layer Security (TLS) • Asymmetric cryptography for authenCcaon – IniCalize on OSI layer 5 (Session Layer) – Use server public key to encrypt pre-master
    [Show full text]
  • A Perfect CRIME?
    AA PerfectPerfect CRIME?CRIME? OnlyOnly TIMETIME WillWill TellTell Tal Be'ery, Amichai Shulman i ii Table of Contents 1. Abstract ................................................................................................................ 4 2. Introduction to HTTP Compression ................................................................. 5 2.1 HTTP compression and the web .............................................................................................. 5 2.2 GZIP ........................................................................................................................................ 6 2.2.1 LZ77 ................................................................................................................................ 6 2.2.2 Huffman coding ............................................................................................................... 6 3. CRIME attack ..................................................................................................... 8 3.1 Compression data leaks ........................................................................................................... 8 3.2 Attack outline ........................................................................................................................... 8 3.3 Attack example ........................................................................................................................ 9 4. Extending CRIME ............................................................................................
    [Show full text]
  • Randomized Lempel-Ziv Compression for Anti-Compression Side-Channel Attacks
    Randomized Lempel-Ziv Compression for Anti-Compression Side-Channel Attacks by Meng Yang A thesis presented to the University of Waterloo in fulfillment of the thesis requirement for the degree of Master of Applied Science in Electrical and Computer Engineering Waterloo, Ontario, Canada, 2018 c Meng Yang 2018 I hereby declare that I am the sole author of this thesis. This is a true copy of the thesis, including any required final revisions, as accepted by my examiners. I understand that my thesis may be made electronically available to the public. ii Abstract Security experts confront new attacks on TLS/SSL every year. Ever since the compres- sion side-channel attacks CRIME and BREACH were presented during security conferences in 2012 and 2013, online users connecting to HTTP servers that run TLS version 1.2 are susceptible of being impersonated. We set up three Randomized Lempel-Ziv Models, which are built on Lempel-Ziv77, to confront this attack. Our three models change the determin- istic characteristic of the compression algorithm: each compression with the same input gives output of different lengths. We implemented SSL/TLS protocol and the Lempel- Ziv77 compression algorithm, and used them as a base for our simulations of compression side-channel attack. After performing the simulations, all three models successfully pre- vented the attack. However, we demonstrate that our randomized models can still be broken by a stronger version of compression side-channel attack that we created. But this latter attack has a greater time complexity and is easily detectable. Finally, from the results, we conclude that our models couldn't compress as well as Lempel-Ziv77, but they can be used against compression side-channel attacks.
    [Show full text]
  • Development and Implementation of an Adaptive HTTP Streaming Framework for H.264/MVC Coded Media
    POLITECNICO DI TORINO III Facoltà di Ingegneria Laurea Specialistica in Ingegneria delle Telecomunicazioni Development and Implementation of an Adaptive HTTP Streaming Framework for H.264/MVC Coded Media Adviser: Prof. Gabriella OLMO – Politecnico di Torino Co-Adviser: Ing. Emanuele QUACCHIO – STMicroelectronics Candidate: Juan Esteban HURTADO GUZMÁN November 2010 Acknowledgments I would like to express my deepest gratitude to Emanuele Quacchio, my supervisor at STMicroelectronics, for the patient guidance and all the intuitions provided. Without his expert support, carrying through this study would have been much harder and taken longer. I’m indebted to him for effective team work, and encouraging through the whole process. I would also like to thank Prof.ssa Gabriella Olmo, for providing this thesis opportunity and constant guidance. Many thanks to all my friends who have been around all these years, who have been helping me at different occasions and in one way or another have influenced this thesis I must acknowledge my girlfriend and best friend, Paula, without her love, patient, encouragement and editing assistance, I would not have finished this thesis. Lately, and most importantly I wish to thanks my family. Victoria Eugenia, Juan Martin and Alejandro. They have always supported and encourage me to do my best in all matters of life. To them I dedicate this thesis. ii Abstract 3-D/MVC video streaming refers to the continuous, interactive and real-time delivery of 3-D/Multi-view media content over networks that allows user interactions
    [Show full text]
  • Categorizing Efficient XML Compression Schemes
    John N. Dyer Categorizing Efficient XML Compression Schemes John N. Dyer, Department of Information Systems, College of Business Administration, Georgia Southern University, P.O. Box 7998, Statesboro, GA 30459 Abstract Web services are Extensible Markup Language (XML) applications mapped to programs, objects, databases, and comprehensive business functions. In essence, Web services transform XML documents into and out of information technology systems. As more businesses turn to web services data transfer, XML has become the language of web services. Unfortunately, the structure of XML results in extremely verbose documents, often 3 times larger than ordinary content files. As XML becomes more common through Web services applications, its large file sizes increasingly burden the systems that must utilize it. This paper provides a qualitative overview of existing and proposed schemes for efficient XML compression, proposes three categories for relating XML compression scheme efficiency for Web services, and makes recommendations relating to efficient XML compression based on the proposed categories of XML documents. The goal of this paper is to aid the practitioner and Web services manager in understanding the impact of XML document size on Web services, and to aid them in selecting the most appropriate schemes for applications of XML compression for Web services. Keywords: Compression, Web services, XML Introduction XML is the foundation upon which Web services are built, and provides the description of data, as well as the storage and transmission format of data exchanged via Web services (Newcomer, 2002). XML is similar to Hypertext Markup Language (HTML), and well-formed XML documents can even be displayed in Web browsers.
    [Show full text]
  • CLI Book 3: Cisco ASA Series VPN CLI Configuration Guide, 9.8 Americas Headquarters Cisco Systems, Inc
    CLI Book 3: Cisco ASA Series VPN CLI Configuration Guide, 9.8 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Session Overhead Reduction in Adaptive Streaming
    Session Overhead Reduction in Adaptive Streaming A Technical Paper prepared for SCTE•ISBE by Alexander Giladi Fellow Comcast 1899 Wynkoop St., Denver CO +1 (215) 581-7118 [email protected] © 2020 SCTE•ISBE and NCTA. All rights reserved. 1 Table of Contents Title Page Number 1. Introduction .......................................................................................................................................... 3 2. Session overhead and HTTP compression ........................................................................................ 4 3. Reducing traffic overhead ................................................................................................................... 5 3.1. MPD patch .............................................................................................................................. 6 3.2. Segment Gap Signaling ......................................................................................................... 7 3.3. Efficient multi-DRM signaling ................................................................................................. 8 4. Reducing the number of HTTP requests ............................................................................................ 9 4.1. Asynchronous MPD updates.................................................................................................. 9 4.2. Predictive templates ............................................................................................................. 10 4.3. Timeline extension ..............................................................................................................
    [Show full text]
  • Protecting Encrypted Cookies from Compression Side-Channel Attacks Douglas Stebila
    Protecting encrypted cookies from compression side-channel attacks Douglas Stebila Joint work with Janaka Alawatugoda (QUT) and Colin Boyd (NTNU) Supported by ARC Discovery Project DP130104304. Financial Crypto 2015 • IACR eprint 2014/724 Royal Holloway, University of London • January 22, 2015 Royal Holloway • 2015/01/22 Protecting encrypted cookies from compression side-channel attacks • Stebila 2 Introduction Encryption and compression Royal Holloway • 2015/01/22 Protecting encrypted cookies from compression side-channel attacks • Stebila 3 Symmetric key encryption A symmetric key Main security goal: encryption scheme • indistinguishability is a triple of algorithms: Attacker cannot tell apart • KeyGen() –> k encryptions of two messages • Enck(m) –> c of the same length: • Deck(c) –> m Enck(m0) looks like Enck(m1) KeyGen and Enc when |m0|=|m1| can be probabilistic Royal Holloway • 2015/01/22 Protecting encrypted cookies from compression side-channel attacks • Stebila 4 Symmetric key encryption I voted for Bush. Enck 8jv0cKErN3aafBc6i len = 17 I voted for Gore. Enck WpmuUzU581bgOvMLZ len = 17 same length input => same length output Royal Holloway • 2015/01/22 Protecting encrypted cookies from compression side-channel attacks • Stebila 5 Compression A compression Main security goal: scheme is a pair of • none algorithms: • Comp(m) –> o Main functionality goal: • Decomp(o) –> m • |Comp(m)| << |m| for common distribution of m Comp may be • Can’t be true for all m due probabilistic (but to Shannon’s theorem usually isn’t) Royal Holloway •
    [Show full text]
  • Publication 5258, Affordable Care Act (ACA) Information Returns (AIR)
    Publication 5258 Affordable Care Act (ACA) Information Returns (AIR) Submission Composition and Reference Guide Processing Year 2021 Publication 5258 (Rev. 11-2020) Catalog Number 69127G Department of the Treasury Internal Revenue Service www.irs.gov Last updated 1/12/2020 Change/Document History It will be assured that this document is current. Printed documents and locally copied files may become obsolete due to changes to the master document. Date Summary of Changes Changes Marked 9/10/2020 Updated Table 5-2 -- update No Indentrust ACES information 9/10/2020 Updated Figure 5-3 No 9/10/2020 Updated Table 12-1 information for No TPE1101, 1122 and 1123,1131, 1133 9/22/2020 Updated text in section 6.5.5 No 9/22/2020 Renumbered Table 7.8 No 9/22/2020 Updated Table 7.10 with new element No Age of Employee (AgeNum) 9/22/2020 Updated Table 7.10 with new element No Plan Start Month. 9/22/2020 Updated Table 7.10 added offer of No coverage codes 1K 1L 1M 1N 10 1P 1Q 1R 1S 1T 1U 1V 1W 1X 1Y 1Z 9/22/2020 Updated Table 7.10 added Employee No Share of Lowest Cost Monthly Premium, for Self-Only Minimum Value Coverage codes 1K 1L 1M 1N 10 1P 1Q 9/22/2020 Updated Table 7.10 ICHRA – Individual No Coverage Health Reimbursement Agreement 1/12/2021 Added Change/Document History table No Table of Contents 1 Introduction ............................................................................................................................................. 1 1.1 Identification ............................................................................................................................... 1 1.2 Scope ......................................................................................................................................... 1 1.3 Purpose ...................................................................................................................................... 2 1.4 Document Organization ............................................................................................................
    [Show full text]