From c0de6e1b17c564e00985c53dbd7a6cb2d0da58ca Mon Sep 17 00:00:00 2001
From: gorhill <rhill@raymondhill.net>
Date: Mon, 6 Oct 2014 11:50:51 -0700
Subject: [PATCH] Created Dynamic filtering (markdown)

---
 Dynamic-filtering.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)
 create mode 100644 Dynamic-filtering.md

diff --git a/Dynamic-filtering.md b/Dynamic-filtering.md
new file mode 100644
index 0000000..d81001a
--- /dev/null
+++ b/Dynamic-filtering.md
@@ -0,0 +1,13 @@
+Dynamic filtering, introduced in version 0.7.0.0, allows a user to filter dynamically certain classes of requests. Currently, `script` and `iframe` objects can be dynamically filtered, i.e. filtered on or off without having to create a custom filter.
+
+Dynamic filtering is a useful feature security-wise. For example, blocking 3rd-party `<iframe>` by default would have protected users in the case of the [jQuery.com malware attack](http://www.riskiq.com/resources/blog/jquerycom-malware-attack-puts-privileged-enterprise-it-accounts-risk).
+
+Of course, blocking portion of a page may cause page breakage, sometimes benign, sometimes crippling. It is up to the user to choose how to make use of this feature.
+
+
+
+1. to block inline `<script>` tags, i.e. javascript code which is embedded directly in the main document.
+2. to block 1st-party `<script>` tags.
+3. to block 3rd-party `<script>` tags.
+4. to block 1st-party `<iframe>` tags.
+5. to block 3rd-party `<iframe>` tags.
\ No newline at end of file