Challenge Module Redesign: Complete SOC dashboard experience with analytics, charts and improved management #10

New Issue

2026-07-25T18:55:25Z

tech commented

2026-07-25 18:55:25 +00:00

Title:
Challenge Module Redesign: Complete SOC dashboard experience with analytics, charts and improved management

Description:

Objective

Redesign the entire ARGUS Challenge module.

The current Challenge section works functionally, but the user experience is too basic and does not reflect an enterprise web security appliance.

The Challenge system should become a complete security control center similar to modern anti-bot / WAF platforms.

Affected sections:
/challenge

Dashboard
Live Activity
Analytics
Tokens
Trusted Clients
Exceptions
Settings

General Requirements

The complete Challenge module must follow the ARGUS Enterprise SOC design language.

Use the same:

dashboard cards
typography
spacing
dark SOC interface
charts
threat indicators
severity badges
responsive design

Avoid:

large empty areas
simple tables only
unnecessary scrolling
basic progress bars

Prefer:

charts
visual intelligence
drill-down views
threat context
real-time information

1. Challenge Dashboard

Current dashboard should be redesigned into a security overview.

Add:

Overview Cards

Example:

Challenge Overview

24,520

Total Challenges

8,420

Successful Challenges

1,250

Failed Challenges

540

Blocked Clients

98.4%

Protection Rate

LOW

Current Threat Level

Each card should show:

value
trend
previous period comparison
severity status

Challenge Activity Timeline

Add:

Interactive chart:

Challenge Events

Passed
Failed
Blocked
Expired

Features:

1h / 24h / 7d / 30d selector
realtime updates
tooltip details

Challenge Type Distribution

Use donut chart.

Example:

Challenge Types

Browser Check
55%

Proof Of Work
25%

CAPTCHA
15%

Other
5%

Threat Sources

Add:

Top Challenged Sources

🇷🇺 Russia

12,500 requests

Threat:
HIGH

🇨🇳 China

8,200 requests

Threat:
MEDIUM

Must include:

country flag
country name
request count
threat level
blocked percentage

Client Reputation Overview

Add:

Client Reputation

Trusted

65%

Suspicious

25%

Malicious

10%

2. Live Activity

Redesign live activity into a SOC realtime console.

Current:

basic event list.

Improve:

Show live challenge events:

17:42:01

Challenge triggered

IP:
185.xxx.xxx.xxx

Country:
🇺🇸 United States

Reason:
Bot behavior detected

Action:
Browser Challenge

Risk:
HIGH

Each event should include:

timestamp
IP
country flag
ASN
hostname
user agent
challenge type
result
threat score

Add filters:

Severity

Country

Challenge Type

Result

Host

IP

3. Challenge Analytics

Create a complete analytics dashboard.

Add:

Challenge Performance

Charts:

Challenges Over Time

Passed
Failed
Blocked

Success Rate

Donut:

Challenge Results

Passed

82%

Failed

12%

Blocked

6%

Response Time

Chart:

Challenge Latency

Average

320ms

P95

850ms

P99

1.4s

Top Targets

Show:

Most Challenged Hosts

login.example.com

8,500 challenges

api.example.com

4,200 challenges

Bot Intelligence

Add:

Bot Challenge Analysis

Known Bots

45%

Unknown Automation

35%

Human Traffic

20%

4. Tokens

Redesign token management.

Current token list should become enterprise management.

Add:

Cards:

Active Challenge Tokens

12,540

Expired Tokens

420

Revoked Tokens

35

Token table:

Columns:

Token

Client

IP

Country

Created

Expires

Status

Risk

Include:

country flag
threat score
client reputation

Actions:

revoke token
view history
invalidate all tokens

5. Trusted Clients

Redesign trusted clients.

Add:

Overview:

Trusted Clients

5,420

Active

120

Expired

15

Revoked

Client list:

Include:

Client

IP

Country

Device

Last Seen

Trust Level

Show:

country flag
browser
OS
device
reputation

Allow:

add trusted client
remove trust
temporary trust
permanent trust

6. Exceptions

Redesign exception management.

Current:

simple list.

Create security policy view.

Example:

Challenge Exceptions

Allow

192.168.1.0/24

Bypass

Internal Monitoring

Temporary

Expires:
Tomorrow

Add:

Exception types:

IP

CIDR

Country

ASN

Hostname

User Agent

Path

Show:

created by
created date
expiration
reason
security impact

7. Settings

Redesign settings into a guided security policy center.

Current settings should become:

Challenge Policy

Example:

Protection Mode

○ Monitor

○ Challenge Suspicious

● Aggressive Protection

Challenge Types

Each option must explain what it does.

Example:

Browser Verification

Detects automated browsers using JavaScript verification.

Recommended:
Enabled

Proof Of Work

Explain:

Requires computational proof before allowing access.

Useful against:

bots
scraping
automated attacks

CAPTCHA

Explain:

Human verification challenge.

Recommended only for high-risk traffic.

Risk Threshold

Visual slider:

Low
Medium
High
Critical

Country Policies

Add:

Country Based Challenge

🇨🇳 China

Challenge:

🇷🇺 Russia

Block:

Real-Time Integration

Challenge events should integrate with:

Dashboard
Live Logs
Analytics
ANIS Intelligence
WAF events

Example:

Challenge Event

↓

ANIS Reputation Check

↓

Risk Score

↓

Action Decision

API Review

Review Challenge APIs.

Required:

challenge statistics

live events

token management

trusted clients

exceptions

policy configuration

risk scoring

analytics aggregation

Avoid unnecessary raw event loading.

Use pagination.

Final Goal

The Challenge module should become a complete enterprise bot defense platform.

The operator should immediately understand:

How many attacks are being challenged
Who is being challenged
Which countries are involved
Which bots are detected
Challenge effectiveness
Security impact
Current protection level

ARGUS Challenge should look and feel like a commercial enterprise security product, not a basic configuration page.

Labels:

component:challenge
component:soc-dashboard
component:security
type:enhancement
priority:high

Title: Challenge Module Redesign: Complete SOC dashboard experience with analytics, charts and improved management Description: ## Objective Redesign the entire ARGUS Challenge module. The current Challenge section works functionally, but the user experience is too basic and does not reflect an enterprise web security appliance. The Challenge system should become a complete security control center similar to modern anti-bot / WAF platforms. Affected sections: /challenge Dashboard Live Activity Analytics Tokens Trusted Clients Exceptions Settings --- # General Requirements The complete Challenge module must follow the ARGUS Enterprise SOC design language. Use the same: - dashboard cards - typography - spacing - dark SOC interface - charts - threat indicators - severity badges - responsive design Avoid: - large empty areas - simple tables only - unnecessary scrolling - basic progress bars Prefer: - charts - visual intelligence - drill-down views - threat context - real-time information --- # 1. Challenge Dashboard Current dashboard should be redesigned into a security overview. Add: ## Overview Cards Example: Challenge Overview 24,520 Total Challenges 8,420 Successful Challenges 1,250 Failed Challenges 540 Blocked Clients 98.4% Protection Rate LOW Current Threat Level Each card should show: - value - trend - previous period comparison - severity status --- # Challenge Activity Timeline Add: Interactive chart: Challenge Events Passed Failed Blocked Expired Features: - 1h / 24h / 7d / 30d selector - realtime updates - tooltip details --- # Challenge Type Distribution Use donut chart. Example: Challenge Types Browser Check 55% Proof Of Work 25% CAPTCHA 15% Other 5% --- # Threat Sources Add: Top Challenged Sources 🇷🇺 Russia 12,500 requests Threat: HIGH 🇨🇳 China 8,200 requests Threat: MEDIUM Must include: - country flag - country name - request count - threat level - blocked percentage --- # Client Reputation Overview Add: Client Reputation Trusted 65% Suspicious 25% Malicious 10% --- # 2. Live Activity Redesign live activity into a SOC realtime console. Current: basic event list. Improve: Show live challenge events: 17:42:01 Challenge triggered IP: 185.xxx.xxx.xxx Country: 🇺🇸 United States Reason: Bot behavior detected Action: Browser Challenge Risk: HIGH Each event should include: - timestamp - IP - country flag - ASN - hostname - user agent - challenge type - result - threat score --- Add filters: Severity Country Challenge Type Result Host IP --- # 3. Challenge Analytics Create a complete analytics dashboard. Add: ## Challenge Performance Charts: Challenges Over Time Passed Failed Blocked --- ## Success Rate Donut: Challenge Results Passed 82% Failed 12% Blocked 6% --- ## Response Time Chart: Challenge Latency Average 320ms P95 850ms P99 1.4s --- ## Top Targets Show: Most Challenged Hosts login.example.com 8,500 challenges api.example.com 4,200 challenges --- ## Bot Intelligence Add: Bot Challenge Analysis Known Bots 45% Unknown Automation 35% Human Traffic 20% --- # 4. Tokens Redesign token management. Current token list should become enterprise management. Add: Cards: Active Challenge Tokens 12,540 Expired Tokens 420 Revoked Tokens 35 --- Token table: Columns: Token Client IP Country Created Expires Status Risk Include: - country flag - threat score - client reputation --- Actions: - revoke token - view history - invalidate all tokens --- # 5. Trusted Clients Redesign trusted clients. Add: Overview: Trusted Clients 5,420 Active 120 Expired 15 Revoked --- Client list: Include: Client IP Country Device Last Seen Trust Level Show: - country flag - browser - OS - device - reputation --- Allow: - add trusted client - remove trust - temporary trust - permanent trust --- # 6. Exceptions Redesign exception management. Current: simple list. Create security policy view. Example: Challenge Exceptions Allow 192.168.1.0/24 Bypass Internal Monitoring Temporary Expires: Tomorrow --- Add: Exception types: IP CIDR Country ASN Hostname User Agent Path --- Show: - created by - created date - expiration - reason - security impact --- # 7. Settings Redesign settings into a guided security policy center. Current settings should become: ## Challenge Policy Example: Protection Mode ○ Monitor ○ Challenge Suspicious ● Aggressive Protection --- ## Challenge Types Each option must explain what it does. Example: Browser Verification Detects automated browsers using JavaScript verification. Recommended: Enabled --- ## Proof Of Work Explain: Requires computational proof before allowing access. Useful against: bots scraping automated attacks --- ## CAPTCHA Explain: Human verification challenge. Recommended only for high-risk traffic. --- ## Risk Threshold Visual slider: Low Medium High Critical --- ## Country Policies Add: Country Based Challenge 🇨🇳 China Challenge: 🇷🇺 Russia Block: --- # Real-Time Integration Challenge events should integrate with: - Dashboard - Live Logs - Analytics - ANIS Intelligence - WAF events Example: Challenge Event ↓ ANIS Reputation Check ↓ Risk Score ↓ Action Decision --- # API Review Review Challenge APIs. Required: challenge statistics live events token management trusted clients exceptions policy configuration risk scoring analytics aggregation Avoid unnecessary raw event loading. Use pagination. --- # Final Goal The Challenge module should become a complete enterprise bot defense platform. The operator should immediately understand: - How many attacks are being challenged - Who is being challenged - Which countries are involved - Which bots are detected - Challenge effectiveness - Security impact - Current protection level ARGUS Challenge should look and feel like a commercial enterprise security product, not a basic configuration page. Labels: component:challenge component:soc-dashboard component:security type:enhancement priority:high

tech commented

2026-07-25 19:38:14 +00:00

Moved to the correct repository: weboria/argus-appliance#11. argus-installer only tracks customer installer/deployment issues; this is a product feature, so tracking continues there (a private repo). Closing here.

tech closed this issue

2026-07-25 19:38:14 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Weboria/argus-installer#10