Skip to content

Guide: Getting Started

This guide helps you complete a stable first setup in one session and verify that protection is actually running.

Outcome

At the end, you should have:

  • certificate installed and trusted,
  • monitor and proxy running,
  • live events visible,
  • baseline filters enabled.

Prerequisites

  • administrator permission on your device,
  • internet access,
  • 5 to 10 minutes.

Step 1: Launch the app

Install from the latest release:

After launch, confirm that the top area and status strip are visible.

Overview top bar after launch

What this image shows: the main header and first status row that confirm the app loaded correctly.

Overview quick status strip with primary controls

What to verify now: core status controls are visible and the app is responsive.

Step 2: Complete certificate setup

If this step is incomplete, HTTPS pages cannot be inspected correctly.

Certificate and proxy setup flow

What this flow means: install certificate, enable monitor/proxy, validate traffic, then confirm counters.

In-app path:

  1. Open Settings.
  2. Open Certificate.
  3. Install and trust the local certificate.
  4. Confirm status is healthy.
Certificate section in settings

What to verify now: certificate status indicates installed/trusted.

Step 3: Enable monitoring

Go to Live Threats and turn Monitor + Proxy ON.

Live Threats controls with monitor and proxy

What this image shows: the exact controls that must be ON before traffic inspection starts.

Live Threats top controls focus

What to verify now: both controls stay ON after a few seconds (no quick fallback to OFF).

Step 4: Validate with real browsing

Browse normal sites for 30 to 60 seconds and check data movement.

Live counters during traffic

What this image shows: counters rising while traffic is being inspected.

Live alert stream during browsing

What this image shows: a real-time event stream with allowed/blocked entries.

Live alert stream with recent events and counters

What to verify now: new rows appear continuously while you browse.

Live incident cards with blocked and secret detections

What this image shows: incident cards with context for triage decisions.

Step 5: Optional terminal validation

Use terminal checks when you want hard confirmation beyond the UI.

Terminal checks for certificate and proxy state

What this image shows: certificate files, listener on port 8080, and system proxy values.

Terminal live stream validation output

What to verify now: logs show live events and counters consistent with Live Threats.

Step 6: Apply baseline security toggles

In Settings, keep these enabled:

  • phishing protection,
  • ad/tracker filtering,
  • security notifications.
Security toggles baseline
Settings security cards and filter controls
Settings toggle block details

What to verify now: toggles reflect your desired policy and remain enabled.

If something fails

  • Browser warning persists: repeat certificate trust step.
  • Monitor ON but no traffic: verify proxy remains ON.
  • Too many false blocks: update filters and review allowlist.

  • How-To: Certificate and Proxy Diagnostics

Continue

  1. Guide: UI Overview
  2. Guide: Filter Center and Whitelist
  3. Guide: Daily Operations and Troubleshooting
  4. Tutorial: From Zero