NetBridge Terminal Examples
NetBridge Terminal Screens
These terminal screen examples demonstrate the key features and interfaces of the NetBridge SSH key management system.
Dashboard
NETBRIDGE SSH KEY MANAGEMENT DASHBOARD
System Status: Healthy ●
┌─ SECURITY OVERVIEW ────────────────────┐ ┌─ RECENT ACTIVITY ────────────────────┐
│ │ │ 17:45:22 Policy applied to web01.lan │
│ Active Keys: 37 ██████████ 92.5% │ │ 17:30:45 Key authorized for web01.lan │
│ Compliant Keys: 34 █████████░ 85.0% │ │ 17:25:30 User login: admin1 │
│ Protected Keys: 31 ████████░░ 77.5% │ │ 17:05:12 Key usage: developer2 │
│ Policy Coverage: 40 ███████████ 100% │ │ 17:03:45 Key usage: developer1 │
│ Active Servers: 40 ███████████ 100% │ │ 17:01:45 User login: developer1 │
│ │ │ 16:45:25 Policy assigned to db01.lan │
└────────────────────────────────────────┘ └────────────────────────────────────────┘
┌─ ALERTS & SECURITY INCIDENTS ───────────────────────────────────────────────────┐
│ ⚠ POLICY_VIOLATION: 4 keys violating StrongKeyEncryption policy │
│ ⚠ SECURITY_ALERT: Suspicious access pattern detected (16:24:30) │
│ ✓ INCIDENT_RESOLVED: False alarm, access restored (16:26:30) │
│ ⚠ POLICY_VIOLATION: Unauthorized access attempt outside allowed hours │
└────────────────────────────────────────────────────────────────────────────────┘
┌─ KEY EXPIRATION ──────────────────────┐ ┌─ SERVER ACCESS ────────────────────────┐
│ │ │ │
│ Valid: 28 ███████░░░ 70.0% │ │ web01.lan: 23 accesses ████████░░ │
│ Expiring Soon: 6 ██░░░░░░░░ 15.0% │ │ db01.lan: 18 accesses ██████░░░░ │
│ Expired: 3 █░░░░░░░░░ 7.5% │ │ app01.lan: 12 accesses ████░░░░░░ │
│ No Expiration: 3 █░░░░░░░░░ 7.5% │ │ dev01.lan: 31 accesses ███████████ │
│ │ │ cicd.devops: 8 accesses ███░░░░░░░ │
└───────────────────────────────────────┘ └─────────────────────────────────────────┘
Commands: [U]sers [K]eys [S]ervers [P]olicies [R]eports [H]elp [Q]uit
SSH Key Management
NETBRIDGE SSH KEY MANAGEMENT
40 Total SSH Keys
┌─ KEY FILTERS ───────────────────┐ ┌─ KEY ACTIONS ────────────────────────────┐
│ [A] All Keys │ │ [G] Generate New Key │
│ [C] Compliant Only │ │ [I] Import Existing Key │
│ [V] Violations Only │ │ [R] Rotate Selected Key │
│ [E] Expiring Soon │ │ [U] Authorize for Server │
│ [O] By Owner │ │ [K] Revoke Selected Key │
│ [T] By Type │ │ [M] Mass Operations │
└─────────────────────────────────┘ └──────────────────────────────────────────┘
ID | Name | Type | Owner | Status | Protected | Expires | Servers
----+---------------------+----------+------------+--------+-----------+----------------+--------
309 | admin1-macbook | ed25519 | admin1 | ● Active | ✓ Yes | 2023-11-13 | 1
308 | jsmith-laptop-new | ed25519 | jsmith | ● Active | ✓ Yes | 2024-02-11 | 3
307 | apatterson-laptop-.. | ed25519 | apatterson | ● Active | ✓ Yes | 2024-02-11 | 1
306 | jsmith-laptop-rotat.. | ed25519 | jsmith | ● Active | ✓ Yes | 2024-02-11 | 0
305 | dev2-laptop | ed25519 | developer2 | ● Active | ✓ Yes | 2024-02-11 | 2
304 | dev1-laptop | ed25519 | developer1 | ● Active | ✓ Yes | 2024-02-11 | 2
303 | webdeploy-key | ed25519 | webdeploy | ● Active | ✗ No | 2023-11-13 | 4 ⚠
301 | mjohnson-laptop | rsa-2048 | mjohnson | ● Active | ✗ No | 2023-11-13 | 2 ⚠
300 | apatterson-laptop | ed25519 | apatterson | ✗ Inactive | ✓ Yes | 2024-02-11 | 0
299 | jsmith-laptop | ed25519 | jsmith | ✗ Inactive | ✓ Yes | 2024-02-11 | 0
298 | jsmith-desktop | rsa-4096 | jsmith | ● Active | ✓ Yes | 2024-02-11 | 2
297 | weak-test-key | rsa-2048 | jsmith | ✗ Inactive | ✗ No | Never | 0 ⚠
┌─ KEY DETAILS ─────────────────────────────────────────────────────────────────┐
│ Selected: admin1-macbook (ID: 309) │
│ Owner: admin1 (Admin User) │
│ Type: ed25519 │
│ Fingerprint: SHA256:AdMiN1mAcBoOkPrO123456789abcdefghij │
│ Created: 2023-08-15T17:20:45.123456 Expires: 2023-11-13T17:20:45.123456 │
│ Status: Active Protected: Yes │
│ │
│ Server Authorizations: │
│ - web01.lan (192.168.1.101) - Authorized by admin1 on 2023-08-15T17:30:45 │
└────────────────────────────────────────────────────────────────────────────────┘
Commands: [F]ilter [P]age [S]ort [V]iew [B]ack [H]elp [Q]uit
Policy Compliance
NETBRIDGE POLICY COMPLIANCE
7 Policies • 40 Servers
┌─ POLICY COMPLIANCE SUMMARY ───────────────────────────────────────────────────┐
│ │
│ StrongKeyEncryption [████████░░] 89.5% (Policy ID: 101) │
│ 90DayKeyRotation [█████████░] 92.3% (Policy ID: 102) │
│ NoRootKeyAccess [██████████] 100.0% (Policy ID: 103) │
│ JustInTimeAccess [███████░░░] 75.0% (Policy ID: 104) │
│ RequireMFA [█████░░░░░] 50.0% (Policy ID: 106) │
│ DevOpsKeyPolicy [██████████] 100.0% (Policy ID: 201) │
│ RestrictedAccessHours [██████████] 100.0% (Policy ID: 107) │
│ │
└────────────────────────────────────────────────────────────────────────────────┘
┌─ NON-COMPLIANT ITEMS ─────────────────────────────────────────────────────────┐
│ │
│ 1. Key ID 301 (mjohnson-laptop): No passphrase protection │
│ Violates: StrongKeyEncryption (Policy ID: 101) │
│ │
│ 2. Key ID 303 (webdeploy-key): No passphrase protection │
│ Violates: StrongKeyEncryption (Policy ID: 101) │
│ │
│ 3. Key ID 301 (mjohnson-laptop): Using weaker RSA-2048 encryption │
│ Violates: StrongKeyEncryption (Policy ID: 101) │
│ │
│ 4. Server ID 3 (db01.lan): JIT access policy violations detected │
│ Violates: JustInTimeAccess (Policy ID: 104) │
│ │
│ 5. Server ID 4 (db02.lan): No MFA setup despite policy requirement │
│ Violates: RequireMFA (Policy ID: 106) │
│ │
└────────────────────────────────────────────────────────────────────────────────┘
┌─ SUGGESTED REMEDIATION ──────────────────────────────────────────────────────┐
│ │
│ 1-3. Rotate non-compliant keys: │
│ netbridge-cli key rotate 301 │
│ netbridge-cli key rotate 303 │
│ │
│ 4. Configure JIT access on db01.lan: │
│ netbridge-cli server policy configure 3 104 │
│ │
│ 5. Enable MFA on db02.lan: │
│ netbridge-cli server mfa enable 4 │
│ │
└──────────────────────────────────────────────────────────────────────────────┘
Commands: [D]etails [R]emediate [E]xport Report [B]ack [H]elp [Q]uit
Server Access Monitor
NETBRIDGE SERVER ACCESS MONITOR
40 Active Servers
┌─ ACCESS ACTIVITY (LAST 24 HOURS) ────────────────────────────────────────────┐
│ │
│ 12AM 2AM 4AM 6AM 8AM 10AM 12PM 2PM 4PM 6PM 8PM 10PM │
│ ┌────┬────┬────┬────┬────┬────┬────┬────┬────┬────┬────┬────┐ │
│ Web │ │ │ │ │▄▄▄▄│████│████│████│████│▄▄▄▄│▄▄ │ │ │
│ └────┴────┴────┴────┴────┴────┴────┴────┴────┴────┴────┴────┘ │
│ ┌────┬────┬────┬────┬────┬────┬────┬────┬────┬────┬────┬────┐ │
│ DB │ │ │ │ │▄▄ │████│▄▄▄▄│████│▄▄▄▄│▄▄ │ │ │ │
│ └────┴────┴────┴────┴────┴────┴────┴────┴────┴────┴────┴────┘ │
│ ┌────┬────┬────┬────┬────┬────┬────┬────┬────┬────┬────┬────┐ │
│ App │ │ │ │ │▄▄ │▄▄▄▄│▄▄▄▄│▄▄▄▄│▄▄▄▄│▄▄ │ │ │ │
│ └────┴────┴────┴────┴────┴────┴────┴────┴────┴────┴────┴────┘ │
│ ┌────┬────┬────┬────┬────┬────┬────┬────┬────┬────┬────┬────┐ │
│ Dev │ │ │ │ │▄▄▄▄│████│████│████│████│████│▄▄▄▄│ │ │
│ └────┴────┴────┴────┴────┴────┴────┴────┴────┴────┴────┴────┘ │
│ │
└───────────────────────────────────────────────────────────────────────────────┘
┌─ TOP SERVERS BY ACCESS ────────────┐ ┌─ TOP USERS BY ACCESS ──────────────────┐
│ │ │ │
│ 1. dev01.lan 31 ███████████ │ │ 1. jsmith 18 ███████░░░ │
│ 2. web01.lan 23 ████████░░ │ │ 2. webdeploy 16 ██████░░░░ │
│ 3. db01.lan 18 ██████░░░░ │ │ 3. developer1 12 ████░░░░░░ │
│ 4. web02.lan 15 █████░░░░░ │ │ 4. mjohnson 12 ████░░░░░░ │
│ 5. app01.lan 12 ████░░░░░░ │ │ 5. developer2 8 ███░░░░░░░ │
│ │ │ │
└────────────────────────────────────┘ └─────────────────────────────────────────┘
┌─ RECENT ACCESS EVENTS ─────────────────────────────────────────────────────────┐
│ 17:30:22 | SUCCESS | jsmith | web01.lan | 192.168.1.20 | SSH │
│ 17:25:45 | SUCCESS | admin1 | db01.lan | 192.168.1.10 | SSH │
│ 17:15:12 | SUCCESS | webdeploy | app01.lan | 192.168.1.30 | SCP │
│ 17:10:05 | SUCCESS | developer2 | dev01.lan | 192.168.2.101 | SSH │
│ 17:05:30 | FAILED | mjohnson | db02.lan | 192.168.1.22 | SSH │
│ 17:03:22 | SUCCESS | developer1 | cicd.devops.lan | 192.168.2.100 | SSH │
│ 16:55:15 | SUCCESS | webdeploy | web02.lan | 192.168.1.30 | SFTP │
└───────────────────────────────────────────────────────────────────────────────┘
┌─ ACCESS ALERTS ───────────────────────────────────────────────────────────────┐
│ ⚠ Unusual access time detected: mjohnson accessed db01.lan at 04:22 AM │
│ ⚠ Multiple failed login attempts: unknown user tried to access web01.lan │
│ ⚠ Access from unusual location: jsmith accessed web02.lan from 203.0.113.42 │
└───────────────────────────────────────────────────────────────────────────────┘
Commands: [F]ilter [T]ime Range [D]etails [A]lerts [B]ack [H]elp [Q]uit
Key Rotation Workflow
NETBRIDGE KEY ROTATION WORKFLOW
Maintaining Zero Trust SSH Access
┌─ PHASE 1: KEY SELECTION ──────────────────────────────────────────────────────┐
│ │
│ Selected Key: apatterson-laptop (ID: 300) │
│ Owner: apatterson (Alice Patterson) │
│ Type: ed25519 │
│ Fingerprint: SHA256:vF45dKw9TzGHjsUuCvMnXZz3fEt9Dfga5RbCJxLY │
│ Status: Active │
│ Protection: With passphrase │
│ Created: 2023-02-15T14:38:45.234567 │
│ Expires: 2023-08-15T14:38:45.234567 (EXPIRED) │
│ │
│ Current Server Authorizations: │
│ - dev01.lan (192.168.1.50) │
│ │
└────────────────────────────────────────────────────────────────────────────────┘
┌─ PHASE 2: NEW KEY CONFIGURATION ─────────────────────────────────────────────┐
│ │
│ New Key Name: apatterson-laptop-rotated │
│ │
│ Key Type: │
│ ● ed25519 (current, recommended) │
│ ○ rsa-4096 │
│ ○ rsa-2048 │
│ │
│ Passphrase Protected: │
│ ● Yes (required by StrongKeyEncryption policy) │
│ ○ No │
│ │
│ Key Expiration: 180 days (2024-02-11) │
│ │
└──────────────────────────────────────────────────────────────────────────────┘
┌─ PHASE 3: TRANSITION PLAN ──────────────────────────────────────────────────┐
│ │
│ Old Key Deactivation: │
│ ○ Immediate (after new key deployment) │
│ ● Delayed (7 days) │
│ ○ Manual (require explicit deactivation) │
│ │
│ Access Migration: │
│ ● Automatic (transfer all server authorizations) │
│ ○ Selective (choose servers to migrate) │
│ │
│ Notification: │
│ ☑ Notify key owner via email │
│ ☑ Notify security team │
│ ☐ Notify server administrators │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
┌─ PHASE 4: EXECUTION & VERIFICATION ─────────────────────────────────────────┐
│ │
│ ● Generate new key pair │
│ ● Install on authorized servers │
│ ● Verify key functionality │
│ ● Schedule old key deactivation │
│ ● Update audit logs │
│ ● Send notifications │
│ │
│ Progress: ██████████████████████████████████░░░░░░ 80% │
│ │
│ Status: Installing new key on dev01.lan... │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
Commands: [C]ontinue [P]ause [A]bort [S]ettings [L]og [H]elp [Q]uit
Usage in the Marketing Page
These terminal screens can be used throughout the marketing materials on the NetBridge website to demonstrate the system's capabilities visually. Each screen highlights a key feature of the NetBridge system:
- Dashboard - Provides an overview of system status, security events, and compliance metrics
- SSH Key Management - Shows how keys are managed, filtered, and inspected
- Policy Compliance - Demonstrates policy enforcement and remediation capabilities
- Server Access Monitor - Illustrates real-time monitoring of server access activities
- Key Rotation Workflow - Shows the step-by-step process for secure key rotation
To include these on the website, you can wrap them in terminal-style frames with optional annotations highlighting key features.
Integration with Org Website
To integrate these screens with your existing org-mode website structure, these examples will be automatically tangled to `/ssh:pi:/home/aygp-dr/projects/defrecord/netbridge.defrecord.com/www/examples/screens/` when you tangle this file.
You can reference them from other org files using code like:
#+INCLUDE: "./examples/screens/dashboard.txt" src text
Or create a custom HTML template to display them with proper styling.