Docs

Set up, run and extend InsightAssure

Everything here matches the product as it ships. Examples use assure.example.com for your InsightAssure host.

Start in four steps

  1. Sign in to your workspace (VerticalServe SaaS) or install InsightAssure in your own environment with ./install.sh.
  2. Run onboarding: adopt the frameworks you report on, create the policy set from the 23 templates, load the 47-risk library and the 83-answer knowledge base.
  3. Connect integrations: your identity provider, HR system, cloud accounts and source control first. The 65 monitors start judging within minutes.
  4. Invite people: employees open My tasks to accept policies, take training and enroll their laptop with the agent.
app.insightassure.com/overview
InsightAssure Overview for Northwind Labs: tiles for controls passing (52%, 57 of 110), monitors failing (30 of 65), open issues (30) and policy acceptance (84%); readiness rings for SOC 2 (18%), SOC 1 (15%), ISO/IEC 27001 (28%) and HIPAA (46%); a control-health bar and a Needs attention list.
The whole program on one screen. Readiness is per framework, from the same 110 controls; Needs attention lists what moves it: 30 failing monitors, 11 controls needing evidence, 18 people with onboarding incomplete and one offboarding with access still open.

Guides

Concepts

TermMeaning
OrganizationYour workspace. Every row carries it; Postgres row-level security on assure.org enforces it underneath the API’s own scoping
FrameworkA standard you report against: SOC 2, SOC 1, ISO/IEC 27001, HIPAA, PCI DSS, NIST CSF, GDPR, ISO/IEC 42001, or your own. Adopting one copies its requirements into your workspace
RequirementA criterion, objective, clause or safeguard of a framework (SOC 2 CC6.1, SOC 1 CO-01, ISO A.8.5). Met when every in-scope control mapped to it is passing or not applicable
ControlOne of 114 unified controls (IAM-02 Multi-factor authentication, CHG-02 Peer review of changes…). Its health is passing, failing, needs evidence, not started or not applicable
MonitorAn automated test over the inventory or the program itself. 65 ship; each feeds named controls and opens an issue when it fails
ResourceOne normalized thing an integration found: an account, an employee, a device, a repository, a bucket, a finding. 20 types
EvidenceA file, link, statement or automated snapshot, linked to controls and, through requests, to audits. Manual controls need evidence inside their frequency window
AuditAn engagement: a framework, a type (Type 1, Type 2, certification…), a period, a firm, and the auditors invited to it

Roles

RoleCan
adminEverything, including users, integrations and settings
complianceRun the program: frameworks, controls, policies, evidence, vendors, risks, audits, trust center
contributorWork the controls, issues, evidence and access-review items assigned to them; read the rest
employeeThe employee portal only: accept policies, take training, enroll a device
auditorOnly the audits they are invited to: requests, the evidence attached to them, populations and findings
viewerRead the program

Want a hand setting it up?

Tell us which frameworks, systems and cloud you run; we will map the integrations and the first audit with you.

Talk to us