Compare production Cisco, Nokia, and Juniper configs against active Golden Configuration compliance templates.
Golden Configuration Compliance & Network Security Auditor | NetAI
Loading Configuration health dashboard stats...
Audit logs recorded in database
Top Hardening Drift Violations
New to Configuration Health Checking?
Create a new configuration standard template or reset filters.
Option 2: Build from Configuration File
Highlight text in Monaco Editor to mark as Dynamic or Ignore
No variables automatically recommended.
Highlight text on left editor to convert to placeholders.
No configuration lines ignored.
Configuration Standard GCT Output
Step 1: Choose Configuration Source
Supports multi-file upload (.txt, .cfg, .conf, .log, etc.)
Local NetAI Agent is not installed
✓ Local NetAI Agent connector status online on 127.0.0.1:8088
Step 2: Detect Vendor & Device Characteristics
Step 3: Recommend Configuration Standard template
Step 4: Review Hardening Template Rules
Run Configuration Health Check
Step 5: Running Configuration Health Check Audits
No configuration mismatches found.
Step 7: Download and Export Compliance scorecard reports
Consolidated Reports (All Audited Devices)
Consolidated Details (Violations List)
History of recent device drift checks synchronizing via SSH local agent or manual uploads.
No devices registered or audited yet.
Mark Dynamic Value Placeholder
No violations match the search criteria.
). Forbidden lines verify the absolute absence of hazardous setups (e.g.
); navigator.clipboard.writeText(text); showNotification(
, routing: preset.routing, switching: preset.switching, mpls: preset.mpls, evpn: preset.evpn, bgp: preset.bgp, isis: preset.isis, ospf: preset.ospf, segment_routing: preset.segment_routing, forbidden: preset.rules.forbidden.join(
, tags: Array.isArray(temp.tags) ? temp.tags.join(
) resetCreateForm(); if (tab.id !==
); setWizardStep(1); setActiveTab(
Configuration drift represents the progressive deviation of a device's running configuration from its original standardized golden baseline. It is dangerous because drift often disables security baselines (such as AAA settings or logging traps), leaving devices vulnerable to unauthorized commands or exposing plain-text configuration passwords.
GCT runs an advanced normalization algorithm that strips out volatile elements such as timestamp counters, uptime statistics, dynamic buffers, and comments. This leaves a clean command matrix, preventing false positives and focusing the audit strictly on policy compliance.
Yes. GCT supports variable templates using double-braces. During compliance calculation, these are mapped to specific device properties or local site dictionary maps.
GCT generates specific corrective commands for every detected violation line. These can be downloaded as a script to apply to the device to restore its configuration back to the baseline.