Sign in
Sign in
Documentation

Omniper Documentation

Everything you need to know about the Omniper platform, from your first config audit to advanced issue reproduction and compliance.

Getting Started

What is Omniper and how to run your first audit.

Omniper is a network intelligence platform built on a deterministic rule engine. It catches misconfigurations, reproduces outages, and keeps you compliant before they impact your business — with line-level evidence behind every result.

The platform is built around three core tools:

  • Config Analyzer – Instantly scan any network configuration for security gaps, misconfigurations, and compliance violations.
  • Issue Reproducer (OmniLab) – Simulate the exact conditions that caused an outage and pinpoint the root cause.
  • OmniAudit – Run compliance checks against NIST SP 800-53, ISO 27001, or your own custom frameworks.

All scans are processed in-memory and never stored on disk. Privacy by design.

Quick Start (5 minutes)

Run your first security audit right now.

1

Sign up or sign in

Create a free account or log in to your existing Omniper account.

2

Upload a config file

From the dashboard, create a project and drag and drop any configuration file (.cfg, .conf, .txt, .json, .yaml) from any of the 13 supported vendor platforms (Cisco, Juniper, Palo Alto, Fortinet, and more). The vendor is detected automatically.

3

Review the findings

The analysis engine lists all issues by severity (critical, high, medium, low). Each issue includes a description, the exact config line that triggered it, a fix recommendation, and a CVSS score.

4

Export the report

Download the full audit as a PDF for your manager or auditor, or JSON for automation. You can also export YAML for ContainerLab to reproduce issues in your own lab.

Next stepsOnce you are familiar with the Config Analyzer, explore the Issue Reproducer to simulate real-world outages, or the Compliance module to audit against industry standards.

Config Analyzer

How the analysis works and what to expect from the results.

The Config Analyzer is a deterministic rule engine:

  • Deterministic rule engine – A curated set of 2,400+ rules detects specific patterns in the configuration. The same config always produces the same findings.
  • Context-aware suppression – If a prerequisite is missing (e.g., SNMP is disabled globally), related findings are automatically suppressed to avoid false positives.
  • Line-level evidence – Every finding cites the exact config line that triggered it, with a CVSS score and a remediation in the vendor's own CLI.

The result is a comprehensive report that includes line-level evidence, CVSS scoring, and actionable remediation steps.

Supported vendors and devices

Cisco IOSCisco IOS-XRCisco NX-OSCisco ASACisco FTDJuniper JunosPalo Alto PAN-OSFortinet FortiGateCheck PointF5 BIG-IPArista EOSExtreme SLX-OSSophos

13 vendor platforms, one parser. The vendor is detected automatically and the matching ruleset is applied — drop the file, get the right analysis.

Understanding findings

Severity levels

Critical – Immediate risk of compromise or outage.
High – Significant vulnerability that should be addressed soon.
Medium – Best practice violation with moderate risk.
Low – Informational or minor hardening suggestion.

CVSS scoring

Each finding includes a Common Vulnerability Scoring System (CVSS) score (0-10) and a vector string. This helps you prioritize based on industry-standard metrics.

Evidence and fix

Every finding shows the exact line from the original configuration that triggered the alert, plus a concrete remediation command.

Issue Reproducer (OmniLab)

Reproduce intermittent or hard-to-catch network issues with evidence-based diagnosis built from your configs.

Describe the problem in plain English, optionally paste configs or logs, and the system will:

  • Generate a network topology diagram of the affected devices.
  • Identify the root cause with a confidence score.
  • Provide step-by-step reproduction commands (e.g., ping, traceroute, show commands).
  • Suggest a fix and a prevention plan.
  • Export a ContainerLab YAML file to test the fix in your own lab.

Example workflow

1. Describe the issue

Example: "UDP fragmentation causing drops over a VPN tunnel. An application generates large UDP packets (64KB) and fragments with DF set exceed the tunnel MTU."

2. View topology and root cause

Omniper draws a diagram of the involved devices from the configs and pinpoints the misconfiguration (e.g., MTU mismatch or fragmentation policy) with the evidence lines behind it.

3. Apply the fix

You receive the exact commands to apply (e.g., ip tcp adjust-mss 1400) and an Ansible playbook for automation.

4. What-if analysis

Change a parameter (e.g., "What if we increase the MTU to 1500?") and see how the diagnosis and fix evolve, without re-running the whole analysis.

Pro tipOmniLab is especially useful for issues that only occur in production but are hard to reproduce in staging. Export the ContainerLab YAML and run the exact scenario on your laptop.

Compliance (OmniAudit)

Audit your configurations against industry compliance frameworks.

NIST SP 800-53 Rev 5NIST SP 800-171ISO 27001PCI DSS v4.0

You can also upload custom frameworks as JSON files. Each framework defines a set of controls, and Omniper maps your configuration against them.

How to run an audit

  • From the dashboard, go to OmniAudit or select a project.
  • Upload a configuration file or use an existing analysis.
  • Choose a framework (e.g., NIST SP 800-53).
  • Click Run Audit. The system evaluates each control and returns a report with:
    • Pass / Fail status per control.
    • Evidence lines from the config that satisfy or violate each control.
    • Remediation steps for failed controls.

The report can be downloaded as PDF for compliance auditors.

Projects and History

Organize your work across clients, network segments, or compliance initiatives.

Create separate projects for different clients, network segments, or compliance initiatives. Each project keeps its own history and configuration analyses.

On the Overview page of a project you can see:

  • Latest security score and critical issue count.
  • Compliance pass rate from the most recent audit.
  • Top findings across all scans.
  • Security score trend over time.
  • Recent activity including scans and audits.

Use the History tab in OmniScan to browse all previous analyses, load a previous report, or compare scores over time.

Frequently Asked Questions