How It Works

Context-Aware Security:
We Understand Your Website.That’s Why We Are Best At Protecting It.

Endless logs and alerts, ongoing patching and hardening, deployments that last forever, hackers repeatedly getting through…
Protecting websites has become unmanageable and ineffective, but it does not have to be this way.
Sentrix redefines the way companies protect their websites. It bases its approach on understanding the website’s functionality and structure. This method, referred to as context-aware defense, creates the simplest, most manageable and cost-effective environment for protecting websites against all threat types while addressing the rigorous security requirements of the enterprise.

 

The Context-Aware Security Lifecycle:

img-1

 

1. WEBSITE PRE-SCANNING

Sentrix analyzes the customer’s website and identifies its deterministic components and business-logic components.

Deterministic Components: have predictable responses that can be pre-generated, replicated and served from the cloud without accessing the customer’s backend. Sentrix can predict and replicate on average 80% of a customer’s website. Our advanced scanning techniques predict and replicate not only static website assets like text and images, but also CMS-generated content, database generated content and complex, dynamic forms.

Business Logic Components comprise the remaining non-deterministic elements of the website, like search boxes and user name input fields. Requests to these components require back end processing.

For business logic components Sentrix generates an automated, Smart Whitelist. A robust set of rules based on the functionality of each defended resource.

 

img-2

 

2. FRONT END REPLICATION

Sentrix decouples the Deterministic Component from the Business Logic Component and creates a replica of the Deterministic Components in the cloud.

 

img-3

 

3. CONTEXT-AWARE DEFENSE

Sentrix inspects incoming traffic and treats each request based on its context:
Legitimate Requests to the Deterministic Component are served by the cloud-based Replica without accessing the customer backend.
Illegitimate Requests to the Deterministic Component are not served at all as there is no corresponding legitimate response. Therefore they are blocked without generating alerts and log entries, keeping maintenance under control. This initial process dramatically reduces the attack , leaving only a handful of specific business transactions to be inspected and validated. Since the organization focuses on protecting these transactions, the probability of attacks is greatly minimized.
The requests to the Non-Deterministic, Business Logic Component are then inspected by the context-aware security policy. Illegal requests are blocked, and only clean requests which have been validated by the series of contextual security measures are forwarded on to the origin site.

 

img-4

Scroll to Top