Features Description
WAF as a Sensor Barrier1 treats the WAF as a sensor. When the WAF identifies some form of cyber activity it will block it and alert on it.Next, the very attributes used on all other components are captured and stored in the onboard dBase and used by the AARE Engine with its layered Algorithms.
Proxy Encryption Proxies allow for visibility as clear text. Without it, attacks can be hidden via encryption.
Types of WAF There are 3 styles of Application Firewalls; Positive, Negative, and Learning. With Barrier1, you have all 3 in Real Time. If any aspect has been changed, Barrier1 will identify it and is part of the Analytics.
Application Layer Barrier1 has always had the ability to inspect key attributes within layer 7. Well written scripts, definitions, and rules are a good way to search for the very attributes in all Cyber Attack classifications. In a True WAF, there is a reverse proxy. A reverse proxy tears down the encrypted files and streams. At this point it is clear text. That is where the inspection happens. Once the inpection/analytics is done, the packet is encrypted gain and sent on.
Bandwidth Mgmt. Barrier1 can hard code bandwidth for specific applications and traffic.
Digital Rights Mgmt. Barrier1 has always had this function built into it.
Granular Access Control Barrier1 independently or through the use of some AD delivers granular control.
Policy Setting Policy setting capability is extensive.
  • Disable, EXE, and .vbs email attachments
  • Allow only certain browser
  • Allow outbound by keywords
  • Customizable and NO boundary limits
Application objects Component example: Match a file content application object with transmission. Ie: FTP
Actions Examples: FTP Notification Reply, HTTP Block Page, HTTP Redirect
Global Setting Yes
Hosted Email Yes
Scan Encrypted Files Yes, You have to utilize a proxy to do this
ActiveX Control Yes
Blocking Outbound Files Yes
By Pass DPI Yes
Custom Signatures Yes
Visibility into Hidden Fields Yes
Communications Strings Yes