This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Profiles
A profile is a collection of security settings that are used to protect specific types of web content or specific parts of your website. In a profile, you determine how the Web App Firewall applies each of its filters (or checks) to requests to your websites, and responses from them. The Web App Firewall supports two types of profile: four built-in (default) profiles that do not require further configuration, and user-defined profiles that do require further configuration.
Built-in profiles
The four Web App Firewall built-in profiles provide simple protection for applications and websites that either do not require protection, or that must not be directly accessed by users at all. These profile types are:
- APPFW_BYPASS: Skips all Web App Firewall filtering and sends the unmodified traffic to the protected application or website, or to the client.
- APPFW_RESET: Resets the connection, requiring that the client re-establish his or her session by visiting a designated start page.
- APPFW_DROP: Drops all traffic to or from the protected application or website, and sends no response of any kind to the client.
- APPFW_BLOCK: Blocks traffic to or from the protected application or website.
- ns-aaa-default-appfw-profile: Protects the authentication virtual servers and ensures that network traffic is secure and compliant with the API specifications.
- ns-aaatm-default-appfw-profile: Protects the traffic management virtual servers and ensures that network traffic is secure and compliant with the API specifications.
- ns-vpn-default-appfw-profile: Protects the VPN virtual servers and ensures that network traffic is secure and compliant with the API specifications.
You use the built-in profiles exactly as you do user-defined profiles, by configuring a policy that selects the traffic to which you want to apply the profile and then associating the profile with your policy. Since you do not have to configure a built-in policy, it provides a quick way to allow or block specified types of traffic or traffic that is sent to specific applications or websites.
User-defined profiles
User-defined profiles are profiles that are build and configured by users. Unlike the default profiles, you must configure a user-defined profile before it will be of use filtering traffic to and from your protected applications.
There are three types of user-defined profile:
- HTML. Protects HTML-based web pages.
- XML. Protects XML-based web services and websites.
- Web 2.0. Protects Web 2.0 content that combines HTML and XML content, such as ATOM feeds, blogs, and RSS feeds.
The Web App Firewall has a number of security checks, all of which can be enabled or disabled, and configured in a number of ways in each profile. Each profile also has a number of settings that control how it handles different types of content. Finally, rather than manually configuring all of the security checks, you can enable and configure the learning feature. This feature observes normal traffic to your protected websites for a period of time, and uses those observations to provide you with a tailored list of recommended exceptions (relaxations) to some security checks, and additional rules for other security checks.
During initial configuration, whether by using the Web App Firewall Wizard or manually, you normally create one general purpose profile to protect all content on your websites that is not covered by a more specific profile. After that, you can create as many specific profiles as you want to protect more specialized content.
The Profiles pane consists of a table that contains the following elements:
Name. Displays all the Web App Firewall profiles configured in the appliance.
Bound signature. Displays the signatures object that is bound to the profile in the previous column, if any.
Policies. Displays the Web App Firewall policy that invokes the profile in the leftmost column of that row, if any.
Comments. Displays the comment associated with the profile in the leftmost column of that row, if any.
Profile Type. Displays the type of profile. Types are Built-In, HTML, XML, and Web 2.0.
Above the table is a row of buttons and a drop-down list that allow you to create, configure, delete, and view information about your profiles:
- Add. Add a new profile to the list.
- Edit. Edit the selected profile.
- Delete. Delete the selected profile from the list.
- Statistics. View the statistics for the selected profile.
- Action. Drop-down list that contains additional commands. Currently allows you to import a profile that was exported from another Web App Firewall configuration.
Share
Share
In this article
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.