Web application security system with automated business logic analysis
A multi-layered traffic inspection system blocks a wide range of attacks targeting web applications and prevents database theft, malware placement on websites and unauthorized changes to website content.
Artificial intelligence analyzes application behavior models, significantly simplifying the creation of a security policy. As such, implementing Continent WAF requires only minimum time.
The system records user access privileges and can be used as an already certified superimposed means of web application protection against unauthorized access
The integrated use of Continent WAF and Continent TLS facilitates strengthened protection and – without affecting the performance of either device – checks even encrypted application traffic as it enters the corporate network.
HTTP validation
SSL tunnel data analysis
Parsing requests and responses
User behavior deviation analysis
Traffic mirroring
Real-time protection
Audit of web server activity logs
The Continent WAF model range offers virtual and software-hardware versions and a choice of hardware platforms with a set of interfaces tailored to your needs.
| Operating system | Ubuntu 20.04 Server Astra Linux Special Edition 1.6 «Smolensk» |
| Processor | x86_64 with 4 cores, at least 2.2 GHz |
| RAM | Minimum - 16 GB |
| HD | Minimum - 500 GB |
| Network adapter | at least 2x Gigabit Ethernet for active mode; 1x Gigabit Ethernet for passive mode |
| Web-browser | Google Chrome 88 or later; Mozilla Firefox 85 or later |
Information contained in these documents may be changed by the developer without special notice; such changes do not violate the developer’s obligations to the user.
Continent WAF installation, configuration and operation.
Continent WAF maintenance and fine-tuning.
Hardware Appliance |
A set of hardware platforms with installed Continent WAF software. |
Virtual appliance |
Virtual machine with Continent WAF software. |
| Professional | Corporate | |
|---|---|---|
No limit on the number of protected applications. |
 |
|
Standard model for parsing transaction data (or optimized for a specific framework within the package). |
|
|
Creation of proprietary verification settings for checking HTTP protocol. |
|
|
ModSecurity open signature format-based Signature detection method, automatic suppression of false positives on signatures. |
|
|
The ability to create individual parsing models for transaction data. |
|
|
Customizable business logic models (actions and sessions). |
|
|
False positive suppression based on transaction data parsing models and business logic. |
|
|
Creation of distributed fault-tolerant configurations with centralized management. |
|
|
Possible integration with external systems (SIEM, IDM, analytical systems, etc.). |
|
|
Database high availability. |
|
|
Hosting all WAF components on one node. |
|
|
Performance of the node up to 1000 RPS. |
|
|
Performance of the node up to 3000 RPS. |
|
|
Performance of the node up to 5000 RPS (Virtual appliance only). |
 |
|
Automatic construction of request routing models, business logic, and application activity parameters. |
|
|
Integration into SDLC processes (dedicated API, licenses for the test zone – free-of-charge). |
|
|
Active-Active balancing. |
|
|
Multitenancy. |
|
|
