Everything you need to run Perimeter yourself — written so you never have to email support. Start at the top, or jump to a topic. Each page has numbered steps, tables, and plain-English explanations.
New here? Read Getting started first, then Findings & de-noising — those two cover 90% of day-to-day use. In a hurry? Jump to the “How do I…?” recipe index or the Troubleshooting & FAQ.
| Guide | What it covers |
|---|---|
| Getting started | What Perimeter is, local-first vs cloud, first run, the demo tenant, the eight tabs, sample findings. |
| Assets, scopes & scan authorization | The attack-surface inventory, scope seeds, ownership proof (DNS-TXT / file challenge), the SSRF/abuse guard, why scanning needs verification. |
| Findings & de-noising | Severity vs exploit-first ranking, EPSS + CISA KEV, the act-now / prioritize / schedule / watch tiers, false-positive verdicts, “hide noise”, multi-engine confirmation. |
| False-positive feedback loop | Mark false positive / confirm real, suppression memory, how human verdicts override the heuristics. |
| Compliance evidence | Per-finding evidence records, control mapping (PCI / HIPAA / SOC 2 / CMMC / NIST / ISO), the signed evidence pack / audit binder, signatures & tamper-evidence. |
| Feeds & scheduling | The daily EPSS/KEV refresh job, what’s live vs deferred to the hosted runner/agent, the scan ingest shape, reports & exports. |
| Cloud / Pro sign-in & entitlements | Signing in with your DosanjhLabs account, the three Pro entitlements, syncing state, publishing evidence to the shared graph. |
| Security & privacy | Local-first guarantees, what leaves the browser and what never does, the scan guard, AI data minimization, evidence signing keys. |
| Troubleshooting & FAQ | Scan won’t run / not authorized, no live data, a real finding got suppressed, evidence signature problems, scheduling, plus a full FAQ. |
| Error reference | Every error/blocked message you can see, what it means, and how to fix it. |
| “How do I…?” recipe index | One-line answers with deep links to the exact step for the most common tasks. |
Perimeter ships as a local-first, no-account console seeded with realistic sample data so the whole workflow — inventory → prioritized findings → remediation → control mapping → signed evidence — runs in your browser right now. The parts that need a server or an agent (the live scan engines, live EPSS/KEV pulls, the ownership-verification challenge, and scheduling) are built as clean seams and are labeled Deferred / hosted throughout these docs. Where you see that badge, the interface exists and is exercised, but the live engine behind it is part of the hosted/Pro tier.
If a page here didn’t answer your question, the Troubleshooting & FAQ and Error reference are the catch-alls. Perimeter is a DosanjhLabs product; account, billing and suite-wide questions live on the DosanjhLabs hub.