# 1. SEG Dashboard
#### ๐ Overview
The **SEG Dashboard** (Secure Email Gateway Dashboard) provides a centralized view of your email security posture. It displays **live analytics**, **user activities**, and **threat intelligence** associated with the inbound and outbound email traffic passing through ShieldsGuardโs filtering infrastructure.
This dashboard acts as the **command center** for monitoring phishing, malware, spam, and content policy enforcement in real time.
***
#### ๐ Threat Metrics Overview
The top panel offers real-time summaries of four core threat categories:
| Category | Description |
| ------------------ | ----------------------------------------------------------------------------------------------- |
| **Phishing** | Attempts to trick users into revealing sensitive information via email (e.g., fake login pages) |
| **Malware** | Emails containing malicious attachments or links |
| **Spam** | Unsolicited or bulk email categorized as junk |
| **Content Filter** | Violations of configured content policies (e.g., blocked file types, sensitive keywords) |
Each box shows:
* Total blocked emails
* Percentage of total filtered emails
* Color-coded risk indicator (blue/green/red/orange)
***
#### ๐ Security Events Panel
This table displays detailed forensic records of any detected threat.
| Field | Description |
| ----------------- | --------------------------------------------- |
| **Analysis Time** | Timestamp when email was scanned |
| **Verdict** | Result of the analysis (e.g., Blocked, Clean) |
| **Reason** | Detected threat type or violated rule |
If no threats are detected, the table will indicate an empty status with a success message.
***
#### ๐งโ๐ผ User Activities Panel
Tracks end-user interactions with the email system.
| Field | Description |
| ---------- | -------------------------------------------------- |
| **User** | Email address of the user |
| **Action** | Login activity or message interaction (e.g., read) |
| **Date** | Timestamp of the action |
> ๐ง Useful for security auditing, behavior analysis, and insider threat monitoring.
***
#### ๐ Email Threat Map
Displays geolocated sources of email-based threats on a global map.
* Real-time pinpointing of phishing or malware origins
* Helps identify targeted attack regions or patterns
* Color-coded intensity by threat type and frequency
***
#### ๐ Email Statistics Graph
A timeline-based chart showing categorized email security trends such as:
| Legend Category | Meaning |
| -------------------- | ---------------------------------- |
| ๐ต Blocked Words | Detected keywords in content |
| โซ No Threat Found | Safe emails |
| ๐ Suspicious | Suspicious but not blocked content |
| ๐ด Phishing, Spam | Confirmed threats |
| ๐ค Maximum File Size | Exceeds allowed attachment limit |
The graph provides a **historical overview** and trends for daily/weekly security metrics.
***
#### โ Use Cases
| Scenario | Dashboard Benefit |
| --------------------------- | --------------------------------------------- |
| SOC visibility | Real-time monitoring of email threat flow |
| End-user auditing | Track user access and interactions |
| Threat landscape awareness | Map-based geointel of where threats originate |
| Incident response readiness | Quickly identify and isolate infected users |
***
#### ๐ก๏ธ Why It Matters
Email is still the #1 vector for:
* Ransomware
* Credential theft
* Business email compromise (BEC)
* Insider abuse
The SEG Dashboard ensures you're not blind to any of it.
***
> ๐ฏ The SEG Dashboard gives you clarity, visibility, and control over the most exploited attack surface in cybersecurity: email. Know whatโs being blocked, whatโs being delivered, and whoโs interacting with it.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.shieldsguard.com/shieldsguard-seg/1.-seg-dashboard.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.