Skip to main content

SHIELD Web FAQ

Product Overview​

Q. What is SHIELD Web?​

SHIELD Web is an RBI (Remote Browser Isolation) solution designed to protect legacy web services. It safeguards against external attacks without modifying existing web services by simply changing the DNS.

Unlike traditional ASM (Attack Surface Management) that only discovers and reports vulnerabilities,SHIELD Web blocks direct attacksto provide practical protection.

Q. What is the difference between ASM and SHIELD Web?​

Existing ASM (Attack Surface Management)

  • Role: Vulnerability Scanning and Reporting
  • Customer Action: Must directly improve vulnerabilities
  • If improvement is not possible: Vulnerabilities continue to be exposed.

SHIELD Web

  • Role: Direct Attack Prevention
  • Customer Action: No Improvement Work Needed
  • Effect: Immediate protection, safe without improvement

→ SHIELD Web isPractical Solutions for ASMis.

Q. What web services can it be applied to?​

  • Aging web service that is difficult to improve due to the end of outsourcing
  • Web services with exposed Open API
  • A site where a security vulnerability has been discovered but is difficult to fix
  • Sites that are likely to be targeted due to public service
  • Services that are difficult to improve after the introduction of ASM

Q. What are the main effects of SHIELD Web?​

Strengthening Security

  • Blocking Web Vulnerabilities (SQL Injection, XSS, etc.)
  • API Unauthorized Access Block
  • Zero-Day Attack Defense
  • Minimizing Attack Surface

Cost Reduction

  • Approximately 80% economical compared to redevelopment
  • No additional equipment required
  • Monthly subscription fee based

Quick Application

  • Applicable within 1~2 days
  • No service interruption

Application Method​

Q. How do I apply SHIELD Web?​

It is applied simply in 3 steps.

Step 1: Change DNS

  • Change the A record of the existing web service domain to the SHIELD Web IP.

Step 2: Provide Certificate

  • Register the SSL/TLS certificate of the existing web service with SHIELD Web

Step 3: Firewall Configuration

  • Allow only SHIELD Web IP in the web server firewall
  • Blocking External Direct Access

→ Applied on the same day

Q. Is changing the DNS sufficient?​

No. In addition to DNS changes,Firewall ConfigurationThis is required.

If only the DNS has been changed:

External → SHIELD Web → Web Server (O)  
External → Direct Access to Web Server (O) ← Still Possible

In the case where the firewall has been configured:

External → SHIELD Web → Web Server (O)  
External → Direct Access to Web Server (X) ← Blocked

If there is no firewall configuration, the protective effect is halved.

Q. Why is a certificate necessary?​

userhttps://www.company.comUpon connection:

  1. Connected to SHIELD Web due to DNS change
  2. SHIELD Web requires proof of "I am company.com".
  3. SSL certificate is required at this time

If there is no certificate, the browser will display a "Not Secure" warning.

Q. Who provides the certificate?​

Provided by the domain owner (customer).

  • www.company.comThe certificate can only be issued to the owner of company.com.
  • SHIELD Web provides services using the provided certificate.
  • Wildcard certificate (*.company.com) recommended

Q. Do I need to modify the existing web service?​

No. The existing web service isI will not modify it at all..

  • No source code modification needed
  • No need to change server settings
  • No need to modify the database
  • Only change DNS and firewall settings

Q. How does server-side rendering work?​

Traditional Method

User Browser → Web Server Direct Access → Execution in Browser  
Risk: Vulnerability Exposure, API Structure Exposure

SHIELD Web Method

User Browser → SHIELD Web → Web Server  
                ↓  
         Executed in an Isolated Environment  
                ↓  
         Only the Screen is Sent to the User  
         
Safety: Vulnerabilities Not Exposed, API Structure Not Exposed

Q. What types of attacks can be blocked?​

  • Parameter Manipulation: API structure not exposed, manipulation not possible
  • API Unauthorized Access: Allow only SHIELD Web through the firewall
  • Zero-Day Attack: Blocking unknown vulnerabilities with isolation methods

Q. How do you protect the Open API?​

General Web Service

Open Developer Tools (F12)  
→ Check API calls in the Network tab  
→ GET /api/users/123  
→ POST /api/payment {"amount": 1000}  
→ Can be called directly with Postman

SHIELD Web

Open Developer Tools (F12)  
→ Only SHIELD Web Streaming Protocol is visible  
→ Actual API URL cannot be confirmed  
→ Parameter structure cannot be confirmed  
→ Direct calls are not possible

Additionally, the firewall settings allow access to the web server only from SHIELD Web, blocking any bypass access.

Q. Does it affect the performance of the web service?​

The WebJet™ protocol of SHIELD Web provides low latency.

Performance Indicators

  • Screen transmission delay: < 50ms
  • Frame rate: 30~60 FPS
  • Experience similar to existing browsers

Optimization Techniques

  • Efficient Screen Compression
  • Send only the changed area
  • Network Bandwidth Optimization

Q. What is the SaaS model?​

It is provided as a service without separate installation.

Advantages

  • No server preparation needed
  • No equipment introduction necessary
  • Minimize management burden
  • Monthly subscription fee for operation
  • Immediately applicable

Customer Responsibility

  • DNS Settings
  • Certificate Provision
  • Firewall Configuration

Q. Is it applicable to various web services?​

Yes, it can be applied independently by domain.

Multi-Domain Operation

  • Certificate required for each domain
  • Providing isolated environments independent by domain
  • Data Isolation Guarantee

When using a wildcard certificate

  • Multiple subdomains available
  • For example: *.company.com → api.company.com, shop.company.com, etc.

Q. Is there a limit on the number of users?​

Automatically responds with auto scaling.

Automatic Scaling

  • When the number of visitors increases: Automatic server scaling
  • When traffic decreases: automatic server scaling
  • No simultaneous connection limit

Caution

  • PoC Stage: Testing with Limited Concurrent Access
  • Live Service: Prior Consultation on Expected Concurrent Users

Q. What happens in case of a failure?​

Minimize service interruptions with a high availability (HA) configuration.

Securing Stability

  • Distributed processing of multiple instances
  • Automatic Switch on Failure
  • 24/7 Monitoring
  • Automatic Backup and Recovery

SLA (Service Level Agreement)

  • Operating rate target: 99.9% or higher
  • Regular Inspection Advance Notice

Q. Is the data safe?​

Protects data with various security technologies.

Transmission Security

  • TLS 1.3 Encryption
  • Send only screen data
  • Source Code Non-Disclosure
  • API Structure Non-Exposure

Storage Security

  • Independent environment per session
  • Complete deletion upon session termination
  • Delete all data including cookies and cache
  • Data Residual Prevention

Q. Do you comply with the Personal Information Protection Act?​

Yes, SHIELD Web helps comply with the Personal Information Protection Act.

Compliance Requirements

  • Safety Measures Obligations: Encrypted Transmission, Access Control
  • Access Log: All access log records
  • Unauthorized Access Blocking: Firewall Integration

Customer Responsibility

  • The handling of personal information in actual web services is the customer's responsibility.
  • SHIELD Web provides transmission segment security