GajShield - Data Security Firewall
WAAP + ZTNA · Web Application & API Protection with Zero-Trust Access

One Inline Layer for Every App, API and User

GajWAF is a WAAP (Web Application & API Protection) platform with built-in zero-trust access. It inspects every request and response in line — blocking injection, bots, account takeover, API abuse and data leaks — while its zero-trust access gateway verifies users on every request, and adaptive identity risk can follow a person across your apps. Run it from a browser console, on-premises, in the cloud or in a container.

Request a Demo See Capabilities
Also on: Microsoft Azure Marketplace AWS Marketplace
~0.2 ms
Added latency per request
Agentless
Nothing to install on your servers
6
Compliance report packs
Active-passive
Built-in HA: floating VIP, state sync
Complete WAAP + ZTNA
WAF · API Security · Bots · Zero-Trust Access
Deployment
On-Premises · Cloud · Container
Compliance Evidence
PCI DSS · HIPAA · GDPR · DPDP · CERT-In · ISO 27001
The Patchwork Problem

Five Tools, Five Consoles. Gaps In Between.

Most organisations stitch together a web firewall, an API gateway, a bot tool, a zero-trust access broker and a reporting pipeline — each bought, integrated and operated on its own. The result is more to run, more to tune, and blind spots where the products don't overlap. That is why industry analysts now treat these as one category: Web Application and API Protection, or WAAP.

Gap 1 · Watching, Not Blocking

Many tools are alert-only or inspect sampled traffic. Attacks that aren't sampled — or are only alerted on — still reach the application.
Gap 2 · Signatures Only

Signature matching misses attacks it has never seen. Zero-days and novel API abuse pass straight through until a rule is written.
Gap 3 · Data Leaves Your Control

Cloud-hosted WAF services route your traffic and logs outside your environment — and hand auditors raw logs someone has to interpret.
The Solution

GajWAF Is a Complete WAAP + ZTNA Platform in One Layer You Own

GajWAF combines web application protection, API security, bot defence, zero-trust access, adaptive identity risk and data-leak prevention in a single inline layer — one that you run, tune and own.

Built to block, simple to run, yours to own — here are the four reasons security and IT teams choose GajWAF to protect their web applications and APIs.

Inline, Not Sampled

Full request and response inspection in the traffic path with about 0.2 ms of overhead — it blocks attacks, it doesn't just alert.

Run It From a Browser

Certificates, rules, schemas, sites, bans and reports are all managed in the console — no command line, no files to hand-edit.

Deploy Anywhere

Your own servers, the cloud or a container. No endpoint agents, no cloud dependency, works fully offline.

Audit & Compliance Ready

Branded, scheduled reports and evidence mappings for HIPAA, PCI DSS, GDPR, India DPDP/CERT-In and ISO 27001.
The Platform

One Inline Layer for Every App, API and User

GajWAF sits in the traffic path, inspects every request and response, and forwards only clean traffic to your applications.

Users, bots & API clients All inbound web and API traffic GajWAF Verifies who sent each request, inspects it, and blocks attacks, abuse and data leaks Your web apps & APIs Receive only clean traffic; no agents installed

Ten capabilities, one console

Web Application FirewallAPI SecurityBot ManagementLayer-7 DoS ProtectionData-Leak PreventionMalware ProtectionMachine LearningZero-Trust AccessAccount TakeoverClient-Side Protection
Detection engine: signatures, behaviour and machine learning together Signature rules catch known attacks, behavioural analysis spots abnormal sessions and clients, and machine learning with per-endpoint baselines flags attack-like requests even when no signature matches.
The Console

Your Protection at a Glance

The GajWAF dashboard shows what's being blocked, which sites are protected and what needs your attention — all in the browser, with no command line.

GajWAF WAAP dashboard showing a health banner, requests over the last 7 days, attacks blocked, sites protected, and counts for policy blocks, rate-limited requests, bans, browser checks and security events
Health at the top, detail below. Attacks blocked, rate-limited traffic, bans and policy blocks are counted separately, and anything that needs action — like expiring certificates — is flagged first.
Global Threat View

See Where Attacks Come From

Attacks on your web applications and APIs arrive from every continent. The GajWAF attack map shows each origin country and its volume — and with country rules, IP reputation and threat-intelligence feeds, you decide what gets through.

GajWAF WAAP attack map showing attacks from North and South America, Europe, Africa, the Middle East, Asia and Australia converging on protected servers in India
Every attack, traced to its origin. Dot size shows attack volume per country. In the console, hover for the country and count, or click a dot to open those events.
The Difference

Why GajWAF Is Different

How GajWAF as a single WAAP + ZTNA layer compares with the typical stitched-together approach.

Typical ApproachGajWAF
One layer, not manySeparate products for web attacks, APIs, bots and access — each run on its ownWeb apps, APIs, bots, zero-trust access and data-leak prevention in a single layer
Attack and access, one engineSeparate WAF and access broker: one sees the attack, the other the personAttack and access share one context: an attack raises that user's risk
Risk follows the personEach request on each app judged in isolationOne risk picture per person drives step-up or lock-out across apps
Enforce, don't just watchOften alert-only or inspecting sampled traffic, leaving gapsInline on every request and response — it blocks, with negligible added latency
Anyone can run itSpecialists, command-line tooling and risky manual rule editsGuided browser console, watch-only mode, one-click undo and one-click fixes for false alarms
Catches the unknownSignature matching only — misses attacks it has never seenSignatures plus behaviour, machine learning and a model that learns each site's normal traffic
Your data stays yoursCloud service where your traffic and logs leave your controlRuns in your own environment — on-premises, cloud or offline — so data never leaves it
Proof, not just logsRaw logs that someone has to collect and interpretBoard-ready and compliance-mapped reports, generated on demand or scheduled and emailed
Zero-Trust Access · Adaptive Identity Risk

Protect Every App. Recognise Every User Across Them.

GajWAF works in two layers in one inline engine: attack protection tuned to each application, and adaptive security that follows the person to every app they touch.

Per-application protection, per-person risk

GajWAF two-layer model: one person reaches App A, App B and App C, each with its own attack protection. Every app sends signals into one adaptive risk picture per identity, which drives step-up or lock-out on each app. LAYER 1 per application, below One person one identity, any app ATTACK PROTECTION App A Own mode and security level Own rules and thresholds ATTACK PROTECTION App B Own mode and security level Own rules and thresholds ATTACK PROTECTION App C Own mode and security level Own rules and thresholds signals in step-up / lock-out LAYER 2 per person Adaptive security: one risk picture per identity New device New country Impossible travel Sign-in velocity Failed sign-ins Denied access + attacks seen on their sessions GajWAF two-layer model: one person reaches App A, App B and App C, each with its own attack protection. Every app sends signals into one adaptive risk picture per identity, which drives step-up or lock-out on each app. LAYER 1 per application One person one identity, any app App A Attack protection Own mode, level, rules, thresholds App B Attack protection Own mode, level, rules, thresholds App C Attack protection Own mode, level, rules, thresholds LAYER 2 per person Adaptive security: one risk picture per identity New device New country Impossible travel Sign-in velocity Failed sign-ins Denied access + attacks seen on their sessions signals in step-up / lock-out
Layer 1 protects each app; layer 2 follows the person. Every app sends signals into one risk picture per identity, and that picture drives step-up or lock-out wherever the user goes next.
WAAP · Per Application

Attack protection

  • Evaluated per site and application, by design
  • Each app has its own mode, security level, rules and thresholds
  • Run a payments app strict and a marketing site relaxed, without one affecting the other
Identity Risk · Per Person

Adaptive security

  • Risk is scored per person, not per app
  • New device, new country, impossible travel, sign-in velocity, failed sign-ins, denied access and attacks seen on their sessions roll up to one risk picture
  • That picture drives MFA step-up or lock-out on any app the user touches

In practice: apps in one shared risk domain

On App A Failed sign-ins from a new country raise the user's risk. On App B An attack seen on the same user's session raises it further. At App C The user arrives already elevated, and must pass MFA step-up or is locked out.

You decide how far risk travels

Every risk picture is keyed to domain · identity provider · user. One setting on the authentication gateway — the identity-risk security domain — decides which applications share it.

Default · Left Blank

Per-application, isolated

  • Each site keeps its own risk
  • Risk built up on App A does not affect App B
  • The safe default: risk never bleeds between unrelated apps or tenants by accident
Shared Risk Domain

Cross-application adaptive

  • Give apps that share a directory the same risk domain
  • A user who trips risk on App A arrives at App B already elevated
  • A step-up or revocation reflects their behaviour everywhere in that domain
ExplainableEvery risk-triggered step-up names the factors behind it, so operators act instead of guess. Self-healingRisk decays over time and persists across restarts, so users are not penalised forever. Tamper-resistantManipulation is bounded: an attacker cannot push a score up or wash it down.
Two guarantees, always on Tenant and identity-provider isolation is always enforced: the identity provider is part of the key, so one customer's user can never inherit another customer's user's risk, even with correlation on. And in a high-availability cluster, identity risk, revocations and trusted devices sync across nodes, so correlation holds across the whole fleet, not just one box.

Zero-trust access: every request proves who it is

GajWAF puts an identity-aware sign-in gateway in front of each application. No request reaches the backend until GajWAF knows who sent it, and access is decided again on every request, using the person's current risk.

SSO · Directories

Identity-aware sign-in gateway

  • LDAP / Active Directory, RADIUS and OpenID Connect (e.g. Microsoft Entra ID, Google, Okta, Keycloak)
  • Verified identity passed to the backend for single sign-on
  • No change to the application
Least Privilege

Authorization on every request

  • Allow or deny by path and HTTP method for each user or group
  • Deny rules override allow rules
  • Deny by default: anything not explicitly allowed is blocked
Context · Device

Continuous verification

  • Conditions on country, Tor, hosting / datacenter networks, IP reputation and known device
  • Sessions bound to the country and device they started on
  • Time- and risk-based step-up during the session
MFA · Revocation

Step-up and instant revocation

  • Assurance-aware MFA step-up: forces a fresh OpenID Connect sign-in and enforces the required acr
  • Trusted-device registry for lower friction on known devices
  • Revoke one user's sessions, or the whole fleet's, instantly
Replace VPN accessGive staff and contractors access to specific applications, not your whole network. Contain compromised accountsA valid login used by the wrong person is caught by its behaviour and forced to re-authenticate. Serve many tenants safelyIdentity and risk stay isolated per tenant and identity provider, ideal for MSPs and hosting.
One engine for attack and access Most stacks bolt a separate ZTNA product in front of a separate WAF. GajWAF makes the same inline proxy do both, so attack detection and the access decision share one context, with no integration to wire up.
Capabilities

Six WAAP Pillars: Web, API, Bot & Data Protection

Threat detection, API security, bot and abuse defence, data protection, access control and operations — in a single firewall.

01

Threat Protection & Machine Learning

Signature, anomaly-scoring and machine-learning detection work together — with per-endpoint baselines that flag requests that don't look like a site's normal traffic, even when no signature matches.

  • OWASP Top 10 and OWASP API Security Top 10 coverage
  • SQL injection, XSS, remote code execution, path traversal, SSRF and more
  • Anomaly scoring with a configurable blocking threshold and custom rules
  • Virtual patching for zero-days via signed, verified rule updates
  • Successful-attack detection — flags responses that prove a compromise
  • Machine-learning detection of attack-like requests (monitor or enforce)
  • Positive-security learning — per-endpoint baselines flag deviations
  • Behavioural analysis of request, session and client activity
  • Technology fingerprinting with auto-applied protection packs
  • Known-vulnerability & end-of-life software detection; import existing IPS rulesets
02

API Security

Enforce each API's contract, verify tokens and keys, and stop abuse, scraping and malformed requests before they reach the service.

  • OpenAPI / Swagger schema validation (report or enforce)
  • XML / SOAP validation against XSD & WSDL
  • Automatic API discovery from observed traffic
  • JWT verification and API-key enforcement with per-key limits
  • GraphQL guards: depth, aliases, batch limits, introspection block
03

Bots, Layer-7 DoS & Account Takeover

Challenge automated traffic, absorb application-layer floods and defeat credential abuse on login and checkout — without storing passwords.

Bots & DoS

  • Browser challenge & emergency mode; verified search crawlers are exempt
  • Bot traps and security-scanner detection
  • Country rules, IP reputation / threat-intelligence feeds and hosting-network scoring
  • Absorbs Layer-7 request floods
  • Adaptive rate limiting per site, stricter on sign-in endpoints
  • One-click emergency mode during a targeted attack
  • Automatic bans for floods, brute force and scanning
  • Request size, count and timing limits against resource exhaustion

Account takeover

  • Credential stuffing — one client failing across many accounts
  • Password spraying — one password tried across many accounts
  • Protects an account under attack from many clients
  • Flags suspicious successful sign-ins (e.g. from a new country)
  • Passwords are never stored or logged
Bot defence in depth: automated traffic is filtered in layers Obvious scanners and bots are caught early by detection and traps. Reputation, country and hosting-network scoring narrow the field, and browser challenges and adaptive rate limits handle the rest. Under a targeted campaign, one-click emergency mode makes every visitor pass a quick check until the storm passes.
04

Data-Leak, Client-Side & Malware Protection

Stop sensitive data leaving in responses, watch the scripts running on your pages, and block infected uploads before they reach the application.

  • Data-leak prevention — mask or block card numbers, database errors, stack traces, keys, cloud credentials & custom patterns
  • Security response headers, content-security policy and backend-fingerprint stripping
  • Anti-defacement monitoring with serve-last-good-copy
  • Hidden-field tampering & page-flow (forced-browsing) protection
  • Detects formjacking and card skimming (Magecart) via third-party script monitoring
  • Supports PCI DSS 4.0 client-side requirements (6.4.3 / 11.6.1)
  • Antivirus scanning of form uploads and raw file bodies
  • Fail-open or fail-closed when the scanner is unavailable; full scan audit trail
05

Zero-Trust Access & Authentication

Put an identity-aware gateway in front of internal or legacy applications using your existing directory — with access decided on every request and no change to the application. See zero-trust access in detail

  • Sign-in gateway (SSO) in front of any app — LDAP / Active Directory, RADIUS and OpenID Connect, the base of zero-trust access
  • Least-privilege authorization by path and method on every request
  • Adaptive identity risk drives MFA step-up or lock-out
  • Console two-factor authentication, users-only mode and enforced 2FA
  • Role-based access (admin / analyst / viewer), site-scoped accounts, full activity audit
06

Operations, Availability & Reporting

A guided browser console, live changes with no dropped connections, built-in high availability and reports your auditors and board can actually read.

  • Console with Simple & Advanced modes, security presets and a setup wizard
  • One-click configuration undo with full version history
  • One-click false-alarm tuning from any event
  • Built-in connectivity tests (backend, sign-in, antivirus, alerts)
  • TLS termination with automatic certificate issuance & renewal and HSTS
  • Load balancing, health checks, session persistence & graceful draining
  • High availability — active-passive clustering, floating virtual IPs, encrypted state sync
  • Live configuration changes with no dropped connections
  • Live dashboards, per-site policies and site-scoped operator accounts
  • Searchable event store, CSV export and audit stream for SIEM
  • Alerts (email / webhook) for attack spikes, bans, outages, certificate expiry & config changes
  • Branded PDF / HTML / CSV reports, scheduled & emailed, for management, security or developers
Simple & AdvancedConsole modes for every skill level One-click undoFull configuration version history One-click tuningFix false alarms fast, from any event Watch-onlyObserve before you enforce
Technology Fingerprinting

Protection Packs Matched to the Stack Behind Each Site

GajWAF fingerprints the technologies behind every protected site, automatically applies the relevant protection packs, and flags known-vulnerable or end-of-life software — across widely used platforms such as:

WordPressPHPJava.NET / IISNode.jsPythonRailsApachenginxDrupalJoomlaLaravelMagentoConfluenceJenkinsGraphQL
Account Takeover Patterns

Three Ways Attackers Abuse Logins — All Detected

Login and checkout pages are where stolen and guessed credentials get tested. GajWAF recognises each pattern of credential abuse — without ever storing or logging a password.

Pattern 1
One client → many accounts

Credential Stuffing

A single client works through stolen username-and-password pairs, failing across many different accounts as it hunts for the ones that still work.

✓ Detected: one client failing across many accounts
Pattern 2
One password → many accounts

Password Spraying

One common password is tried once against many accounts — a slow, quiet approach meant to stay under per-account lockout limits.

✓ Detected: one password tried across many accounts
Pattern 3
Many clients → one account

Distributed Account Attack

Attempts on a single account are spread across many clients, so no one source looks suspicious on its own.

✓ Detected: one account under attack from many clients
And when a login does succeed: GajWAF flags suspicious successful sign-ins — for example, from a new country. Passwords are never stored or logged.
Coverage

What GajWAF Stops

The attack and abuse classes GajWAF detects and blocks across web applications and APIs.

Injection & Exploitation

11 attack classes

SQL injection, cross-site scripting (XSS), remote code execution, command injection, path traversal / LFI, SSRF, XXE, template injection (SSTI), insecure deserialization, open redirect and remote file inclusion.

Bots & Abuse

9 attack classes

Automated bots & crawlers, content scraping, credential stuffing, password spraying, account takeover, brute force, Layer-7 request floods, vulnerability scanners and carding / fraud probes.

API, Data & Integrity

8 attack classes

API schema / contract violations, unauthorized API access, GraphQL abuse, sensitive-data exposure, malware uploads, web defacement, client-side script injection (Magecart), and known-CVE & end-of-life software.
Aligned to OWASP Coverage spans the OWASP Top 10 and the OWASP API Security Top 10, with machine-learning detection and per-endpoint baselines to catch attacks that have no matching signature.
Use Cases

Where Teams Put GajWAF to Work

Six common reasons organisations deploy GajWAF in front of their applications.

Protect Apps You Can't Patch

Shield legacy, third-party or unpatched applications from known and zero-day exploits with virtual patching — without touching the code.

Secure Your APIs

Enforce each API's contract, verify tokens and keys, and stop abuse, scraping and malformed requests before they reach the service.

Stop Account Takeover

Defeat credential stuffing, password spraying and bots on login and checkout, and flag suspicious sign-ins — without storing passwords.

Meet Compliance

Satisfy the web-application control in PCI DSS, HIPAA, GDPR and India's DPDP, and hand auditors mapped evidence reports on demand.

Replace VPN with Zero-Trust Access

Put an identity-aware gateway in front of internal or legacy apps using your existing directory, with access decided on every request.

Ride Out an Attack

Turn on emergency mode in one click during a flood or targeted campaign — every visitor passes a quick check until the storm passes.
Virtual patching: protect what you can't patch yet GajWAF spots known-vulnerable and end-of-life software behind each site and applies virtual patches through signed, verified rule updates — closing the exposure window without code changes.
Deployment

Deploy the Way You Run

GajWAF sits inline in front of your applications and runs wherever they do — a self-hosted WAAP with one layer, no agents and no cloud dependency.

On-Premises

On a GajShield Firewall Appliance, your own server or a virtual machine — in front of your servers, fully inside your network.

Public or Private Cloud

Launch from Azure Marketplace or AWS Marketplace, or run the same software in any other cloud or region — no vendor lock-in.

Container

Run it alongside your containerised applications and services.

High-Availability Pair

Active-passive with a floating address and automatic failover for zero-downtime protection.
Zero-downtime protection with an active-passive pair Clients reach GajWAF through a floating virtual IP. If the active node fails, the passive node takes over automatically, with configuration, bans, users, identity risk, revocations and trusted devices already in sync.

Launch from your cloud marketplace

GajWAF runs as a virtual machine in your own Azure subscription or AWS account, so your traffic and logs stay in your environment.

Microsoft Azure

GajWAF on Azure Marketplace

Deploy GajWAF as a virtual machine in your Azure subscription and put WAAP and zero-trust access in front of the apps and APIs you run in Azure.

View on Azure Marketplace
AWS

GajWAF on AWS Marketplace

  • Delivered as an Amazon Machine Image (64-bit x86, Ubuntu 22.04 LTS)
  • Protect as many sites as you need on a single instance
  • Pay as you go by the instance-hour on your AWS bill, or save with an annual contract
  • 15-day free trial
View on AWS Marketplace
Specifications

Technical Specifications

Form factorInline software appliance. Installs on your own servers, as a container, or through the included installer.
PlatformsGajShield Firewall Appliances, standard 64-bit Linux servers, virtual machines, and public cloud on Microsoft Azure and AWS. No endpoint agents and no separate database to run.
DeploymentOn-premises, private or public cloud, or container; available on Microsoft Azure Marketplace and AWS Marketplace. Air-gap and offline updates supported.
PerformanceAbout 0.2 ms added inspection latency per request; configuration changes apply live with no downtime.
ProtocolsHTTP/1.1, HTTP/2 and HTTPS; TLS 1.2–1.3; WebSocket pass-through. Multiple sites / virtual hosts per instance.
TLS & certificatesPer-site certificates (upload in the console or automatic issuance & renewal), HSTS, HTTP→HTTPS redirect, private-CA trust for backends.
High availabilityActive-passive clustering with floating virtual IPs and encrypted state sync (configuration, bans, users, identity risk, revocations and trusted devices).
Protection modesPer site: block, watch-only or off; relaxed / balanced / strict security presets.
Zero-trust accessIdentity-aware sign-in gateway per app; least-privilege authorization on every request (path / method × user / group, deny by default); context and device conditions; session binding; MFA step-up (OIDC acr); per-user and fleet-wide revocation.
Adaptive identity riskRisk scored per identity (domain · identity provider · user). Per application by default; cross-application when apps share an identity-risk security domain. Tenant / IdP isolation always enforced; synced across HA nodes.
ManagementHTTPS web console (light/dark), API for automation, role-based access and two-factor authentication.
IntegrationsLDAP / Active Directory, RADIUS and OpenID Connect sign-in (e.g. Microsoft Entra ID, Google, Okta, Keycloak); antivirus for upload scanning; location (GeoIP) data; email & webhook alerting; import of existing IPS rulesets.
LoggingBuilt-in searchable event store with configurable retention, CSV export, and an audit log for SIEM forwarding.
Standards

Compliance Evidence Your Auditors Can Use

Generate audience-specific and compliance-mapped reports that document GajWAF's active controls as evidence toward each framework.

HIPAASecurity Rule
PCI DSS v4.0Req 6.4.2
GDPRArticle 32
India DPDP Act2023
CERT-In Directions2022
ISO/IEC 270012022

Compliance reports map GajWAF's technical controls — encryption in transit, data-leak prevention, access control, logging & retention, malware protection and authentication — to each framework's requirements, with a clear assessment for every control:

MetControl is in place and evidenced PartialControl partly addressed by GajWAF GapNeeds attention or other controls

Reports for every audience

ManagementBoard-ready summaries SecurityAttacks, bans and trends DeveloperEvents to fix at the source ComplianceSix mapped evidence packs

Branded PDF / HTML / CSV reports, generated on demand or scheduled and emailed.

Reports are supporting evidence, not a certification, and do not cover organisational, physical or application-level controls outside GajWAF.
Next Step

See GajWAF Protect Your Applications

Web application firewall, API security, bot management, Layer-7 DoS, data-leak, malware, account-takeover and client-side protection, machine learning, zero-trust access and adaptive identity risk — in one inline layer you run, tune and own.

Request a Demo or Proof of Concept See Capabilities See the Full Firewall
Or launch it today from Azure Marketplace AWS Marketplace (15-day free trial)

Important notes

Performance figures. Latency and other performance figures are from GajShield's own test environments and are not independent benchmarks. Actual detection efficacy, throughput, latency and behaviour vary with traffic, hardware, applications, policy configuration and deployment conditions.

WAAP and DoS terminology. GajWAF is a Web Application & API Protection (WAAP) platform. DoS and flood protection described here refers to application-layer (Layer 7) controls and does not imply a volumetric network DDoS scrubbing service.

Compliance reporting. Compliance reports map GajWAF technical controls to framework requirements as supporting evidence. They are not a certification or attestation of compliance and do not cover organisational, physical or application-level controls outside GajWAF.

Adaptive identity risk scope. By default, identity risk is kept per application. Cross-application correlation applies only to applications configured with a shared identity-risk security domain on the authentication gateway. Tenant and identity-provider isolation is always enforced.

Product claims. Features may vary by version, edition, deployment mode, licence or configuration and may change without notice. Illustrations and screenshots are representative. References to typical or traditional approaches are general market descriptions, not claims about any specific vendor.

Trademarks. GajShield, GajWAF and related names and logos are product names and/or trademarks of GajShield Infotech (I) Pvt. Ltd. All third-party company, product, service and standard names referenced are the property of their respective owners and are used for identification only; their use does not imply affiliation, sponsorship, certification or endorsement.

 

Get In Touch With Us

Subscribe to our Newsletter
Please fill the required field.

Stay Connected

Privacy PolicyDisclaimerWarranty Policy
2026 © GajShield Infotech (I) Pvt. Ltd. All rights reserved.