QNET HTTP


Security Level

Definition

Estimated Value

Rationale

SL-C Component

Intrinsic security capability of the QNET webserver

SL1

Fails the fundamental requirements for Confidentiality (FR4) and Authentication (FR1) for SL2. Transmitting credentials in clear-text exposes administration to compromise by any attacker with network access.

SL-T 

Target System

Security level achieved by the Zone/Conduit

SL2

It can achieve SL2 if the Conduit implements mandatory cryptographic protection (VPN/IPsec) to secure the Web Server traffic and DPI management filters. Without network-level encryption, the SL-T is limited to SL1.


Optional webserver for remote supervision, can achieve a target security level (SL-T) of SL2 if it operates in a segregated network, restricted access to authorized personnel only.


Foundational

Requirement

SL-C
Component Capability

Network Measures

SL-T
Target Level Achieved

FR1 - IAC

Identification and Authentication Control 

Basic Authentication is vulnerable to credential sniffing on the network.

VPN/IPsec for remote access  or TLS Proxy on the network path.

SL2

Authentication relies on VPN credentials rather than the weak Basic Auth

FR2 - UC

Use Control

Lack of granular roles/privileges in WS; access grants full management control.

DPI/Layer 7 Firewall Rules: Filters specific HTTP management commands (POST) and restricts actions.

SL2

Control over actions is enforced by network inspection, mitigating the risk of intentional misuse by authorized but malicious local user

FR3 - SI

System Integrity

No integrity check

HTTP commands are vulnerable to on-path tampering.

VPN/IPsec: Provides cryptographic integrity checks for all transmitted management commands and data.

SL2

Protects against command alteration, even if the attacker is an internal employee on the network

FR4 - DC

Data Confidentiality

Transmission of credentials and configuration data in clear-text.

VPN/IPsec: Essential to encrypt internal traffic, preventing credential theft via network sniffers used by internal personnel.

SL2

Confidentiality is guaranteed by the cryptographic tunnel, protecting data from compromise

FR5 - RDF

Restricted Data Flow

Introduces a management flow (HTTP port 80) that must be controlled.

Strict Firewall Rules: Limits access to port 80 only to specifically authorized administrative hosts.

SL2/3

The Trusted Environment Assumption is formalized by the strict access control list.

FR6 - TRE

Timely Response to Events

Entering the wrong password causes a controlled lockout, and the event is recorded in non-volatile memory.  

None

SL3

Requirement for attack detection and logging are satisfied.

FR7 - RA

Resource Availability

Protection against DoS attacks is strengthened by the controlled lockout function.

None

SL3

Attack results in a controlled suspension, not a chaotic failure.


Integrated webserver meets or exceeds SL2 security levels across all analyzed Fundamental Requirements.

The use of the Web Server depends on the network perimeter in which it is deployed:

  • Segregated Industrial Environment: It can remain active without additional measures.
  • External Network Access: The webserver can remain active provided that the system is protected by a Conduit that fulfills the necessary security requirements (VPN/IPsec, DPI).
  • Maximum Protection (Hardening): If an adequate Conduit cannot be guaranteed, or for high-criticality applications, the webserver can be completely disabled. This action eliminates the attack vector at its source, neutralizing the risk of unauthorized access via the web interface.