LogoLogo
  • ShieldsGuard - User Guide
  • Installation Steps
    • Shields Guard Installation
    • Shields Guard SEG Installation
  • Getting Started
    • 1. General Welcome and Site Management Panel
    • 2. Overview
      • 2.1 Today's Data
      • 2.2 Country Statistics
      • 2.3 URL Statistics
      • 2.4 IP Statistics
      • 2.5 HTTP Status Statistics
    • 3. Protection
      • 3.1 DDoS Protection
        • 3.1.1 Google Recaptcha Setup
        • 3.1.2 Friendly Captcha Setup
      • 3.2 WAF – Web Application Firewall
    • 4. Security Rules
      • 4.1 BlackList & WhiteList
      • 4.2 User Agent Filtering
      • 4.3 Query String Filtering
      • 4.4 HTTP Header Filtering
      • 4.5 Block POST Values
      • 4.6 Custom Headers
      • 4.7 Block URL Requests
      • 4.8 URL Path Blocking
      • 4.9 Encrypt Path
      • 4.10 Remove Request Value
      • 4.11 Exclude Directories from Protection
    • 5. Logs
      • 5.1 Access Log
      • 5.2 Security Log
    • 6. Asset Management
      • 6.1 Asset Management
      • 6.2 Network Topology
      • 6.3 Vulnerability Scan
    • 7. Access
  • 8. DNS
  • 9. SSL
  • 10. Subdomain Manage
  • 11. Edit Page
  • ShieldsGuard SEG
    • 1. SEG Dashboard
    • 2. Reporting
    • 3. Analyzed
      • 3.1 Files
      • 3.2 URL
      • 3.3 Mail
      • 3.4 Domain
    • 4. Mail Settings
      • 4.1 File
      • 4.2 Mail Body
      • 4.3 Sender Domain
Powered by GitBook
On this page
Export as PDF
  1. Getting Started
  2. 6. Asset Management

6.3 Vulnerability Scan

Previous6.2 Network TopologyNext7. Access

Last updated 9 days ago

📖 Overview

The Vulnerability Scan module provides real-time detection, classification, and visibility into the known and potential security weaknesses across your entire digital surface.

This system continuously analyzes exposed services, technologies, protocols, and configurations to identify vulnerabilities — then ranks them by severity so you know exactly what to fix, and where.

🚨 ShieldsGuard helps you stay ahead of attackers by showing what they see before they exploit it.


🔍 What It Scans

  • Web application stack (WordPress, PHP, Plesk, etc.)

  • SSL/TLS configuration and certificate health

  • HTTP headers and content security policies

  • Open ports and exposed services

  • Publicly accessible endpoints

  • CMS plugin versions

  • Protocol vulnerabilities and misconfigurations

  • Missing or misconfigured DNS and email security


🎯 Severity Levels

All findings are categorized using a clear, color-coded system:

Severity
Meaning

🔴 Critical

Exploitable vulnerabilities with high impact

🟠 High

Major misconfigurations or outdated technologies

🟡 Medium

Weaknesses requiring mitigation

🔵 Low

Minor risks or hygiene issues

⚪ Info

Informational or best practice observations

Each severity level helps prioritize remediation based on real-world impact.


📋 Vulnerability Detail

Every finding includes:

  • Affected domain and URL

  • Risk level (color and label)

  • Vulnerability type or CVE (if applicable)

  • Description of the issue

  • Discovery method

  • Exact URL or port

  • Suggested resolution

  • Timestamp

  • Quick access to “View” for more details


🧠 Example Findings

Vulnerability
Risk Level
Affected Component

CVE-2020-24778 (GSAP)

High

JavaScript library

Missing HSTS Header

Medium

HTTP response headers

Misconfigured CORS

Medium

API endpoints

SSL Certificate Near Expiry

Medium

TLS

Missing HttpOnly on Cookies

Low

Set-Cookie directive

No DKIM or SPF Records

Info

Email configuration

WordPress XML-RPC Brute Force Exposure

Medium

WP login subsystem

REST API Enumeration

Info

WP-JSON endpoint


📈 Dashboard Features

  • 📊 Risk Score Gauge — Visual snapshot of risk posture

  • 📑 Security Findings Table — Fully filterable by severity or domain

  • 🧮 Vulnerability Histogram — Severity-wise chart

  • 🔍 Domain Filter — Narrow scope by subdomain or asset

  • 📤 Export Capabilities — Download reports for audits or incident response


⚙️ How to Use It Effectively

Goal
Action

Patch critical exposures quickly

Sort by severity and act on 🔴/🟠 first

Track remediation over time

Re-scan after fixes and compare findings

Improve compliance posture

Export finding logs with timestamps

Investigate patterns

Correlate vulnerabilities across domains

Confirm system health after deploy

Run scan post-update to detect regressions


🔐 Best Practices

  • Integrate scans into your change and release cycle.

  • Treat HIGH and CRITICAL findings as blockers in CI/CD.

  • Review LOW/INFO items regularly for hygiene improvements.

  • Use scan results to update your WAF, IP filters, and rules.


🎯 ShieldsGuard Vulnerability Scan is your early warning system — detecting what could be exploited before attackers do, and giving you a prioritized, actionable plan to fix it.