Control testing
Frozen populations, re-derivable samples, independent sign-off, and an Excel workpaper.
SOC 2 Type II testing pack
305 test procedures across 61 criteria, run by the testing workflow.
Recurring evidence collection
Standing requests on a cadence, chased and escalated.
Policy acknowledgement and training
Sign-off pinned to the exact version and its digest. Assign training and keep the attestations auditors ask for.
Policy approvals
An approval chain on the folder that holds your policies: ordered steps, steps that need two of three approvers or open together, one decision for each person, and nobody approves a version they uploaded. Every decision is kept with the file's digest, and the last one files a signed record as evidence.
Trust centre
A public page that shows your posture to prospects. It charts daily page views and report requests, and the request funnel (views, requests, terms accepted, approvals), as counts only, with a CSV export.
Answers on the trust centre
Visitors ask in their own words. The answer comes from the answers you approved, or from your page's own words through your model key, and a reply is shown only when its figures, its addresses and most of its words are on the page. Otherwise the visitor is pointed to a request.
Security questionnaire automation
Upload a prospect's questionnaire and get a drafted answer for each question, with its sources. A person approves every answer.
Personal-data detection
Flags personal data in evidence and makes masked copies for packages.
Privacy requests
Access, deletion and correction requests, with the deadline worked out for the GDPR, the UK GDPR, the CCPA, PIPEDA and Quebec's Law 25, counted with your own holidays, through a public request form you can switch on, and a reply drafted from your own wording. The requester's details are encrypted, and removed a set time after the request closes, leaving the dates and the outcome.
E-signature and contract auto-extract
DocuSign, Dropbox Sign or a manual flow, and the signed copy files itself. Vendor, standards and expiry are proposed from the signed contract.
Assurance report reader
Upload a vendor's SOC 2 report, ISO certificate or penetration test summary. Your model key proposes the period, the opinion, the exceptions and the controls left to you, each with the passage it came from, and nothing is written until a person confirms it.
Board reporting
Reporting packs with the numbers frozen when they are generated.
OSCAL system security plan
Your NIST SP 800-53 or FedRAMP Moderate program as an OSCAL 1.1.3 system security plan in JSON, with the value you set for each parameter and how the system meets each control, checked against NIST's own schema and catalog. A control that does not map is named, never guessed.
Meeting scheduler
Real Teams and Meet invites from the governance calendar.
Notes and mentions
Notes beside any control, risk, vendor or document. Tag a colleague and it reaches their notifications.
People and access
Import your people and the accounts in your other systems, then run the leaver test: every account still active after someone left. Run an access review over the same accounts: one decision per account that cannot be edited afterwards, and a completion report filed as evidence. It never changes an account anywhere.
Personnel compliance
One row for every person in scope: their policies, their training, their device and their background check, each due from the day they started or joined the list, with windows you can set by department and reminders you can switch on. An exemption is a record with a reason, and the report is filed once as evidence.
Vulnerability and remediation
Import scanner findings, set deadlines by severity, accept a risk with an approver and an expiry, and raise Jira Cloud tickets.
AI assistant connection
Give an assistant on your own machine a personal token and it reads your program: controls, risks, vendors and deadlines. It sees what you see and can change nothing. Off until you turn it on.
Outbound webhooks
Events from your program are posted, signed, to your own https endpoints, retried when a delivery fails and logged. Nothing is sent to a host the operator has not named.
Evidence push API
Your own scripts report results against controls with a token you make. Off until you turn it on, and it never connects out. A result never marks a control implemented.
Devices and vendor discovery
Import a device management export and see which devices fail a baseline you confirm. The same page lists the systems in your account imports that are not in the vendor register. It never contacts a device.
Policies, registers, custom frameworks
30 policies and 14 registers, pre-mapped, plus your own frameworks. One register is a library of 120 starting risk scenarios that import into your risk register.