Information Security
Thoropass
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Thoropass (formerly Laika), Inc. · thoropass.com
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Thoropass (formerly Laika) is a US cybersecurity and compliance firm selling an audit platform alongside audit, pentesting and scanning services. The judges score it highest on framework coverage, 4 to 5, on nine named regimes — SOC 1, SOC 2, HIPAA, HITRUST, Cyber Essentials, GDPR, CMMC Level 1, NIST CSF 2.0 and PCI DSS — though no public information shows one control answer mapping across frameworks. Information security management scores 1 to 2, tied with sovereignty: the ISMS claim is a single sentence, with no public information on risk methodology, asset inventory, treatment tracking or incident workflows; sovereignty's range reflects US-incorporated entities and no public information on hosting locations, an EU region or a subprocessor list. Controls and statement-of-applicability scored a uniform 3 on a real-time view of SOC 2 controls and progress. Audit readiness runs 3 to 4 — higher scores credit audits by the vendor's own AICPA-registered CPA firm, lower ones cite no public information on revision-safe history or evidence packs. Integrations and automation sits at 2 to 3; no prices are published.
Speaks for it
- Framework coverage scored 4 to 5, the highest range awarded, on nine named regimes from SOC 1 and SOC 2 to CMMC Level 1 and PCI DSS
- Audits are performed by the vendor's own AICPA-registered CPA firm, Laika Compliance, LLC dba Thoropass Assurance, putting platform and report under one roof
- A real-time view of SOC 2 controls, progress and audit readiness evidences control status tracking
- Penetration testing, certified ASV scans, vulnerability scanning and Thoropass AI are listed alongside the software
- More than 1,000 organizations are named as customers, with an on-page rating of 4.8/5
Held against it
- The ISMS claim is one sentence, with no public information on risk methodology, asset inventory, treatment tracking or incident workflows with statutory reporting clocks (scored 1 to 2)
- The "Integrations and APIs" line carries no public information on named connectors, directory import or API documentation (scored 2 to 3)
- Control evidence stops at status tracking, with no public information on statement-of-applicability generation, measure ownership with due dates, or internal audit workflows (scored a uniform 3)
- The entities are US-incorporated with a DPA listed, and we found no public information on hosting locations, an EU region or a subprocessor list (scored 1 to 2)
- No prices, editions, modules or billing periods appear in the captured pages
Best for
- You are a US-market buyer needing SOC 1, SOC 2, HIPAA, HITRUST, CMMC Level 1 or PCI DSS coverage, where framework coverage scored highest
- You want the audit delivered by the vendor's own AICPA-registered CPA firm instead of sourcing an external auditor
- You are a one-person security function starting from a real-time view of SOC 2 control status and progress
- You want pentesting and certified ASV scans available alongside the compliance software under one vendor
Avoid if
- You need an evidenced ISMS backbone — risk methodology, asset inventory, incident workflows with statutory reporting clocks — when the public claim is a single sentence
- You need named connectors, directory import or documented APIs so you are not re-keying your estate by hand; the captured pages show an offering label with no named connectors
- You require published hosting locations, an EU region or a subprocessor list for the system holding your risk register — the entities on record are US-incorporated and we found no public information on hosting or subprocessors
- You need NIS2, DORA, TISAX or a certifiable ISO 27001 regime — ask the vendor: the public pages we read do not show it
The scores
Asset & risk management depth
Show reasoningHide reasoning
How this is scored
The ISMS core: asset inventory, risk methodology (identification, assessment, treatment), protection-needs inheritance, incident handling with statutory clocks.
0 — No ISMS substance; "information security" is a chapter in the marketing site.
3 — A flat risk list and an asset spreadsheet import; no treatment tracking, no inheritance, incidents live in the ticket system.
5 — Asset and risk management with configurable matrices and treatment tracking; basic incident handling; inheritance and aggregation need manual work.
8 — A real risk backbone: documented methodology (ISO 27005 or equivalent), inherited protection needs across asset relations, incident workflows with statutory reporting clocks (NIS2 24h/72h), risk acceptance with ownership.
10 — Risk management a certifier works inside: complete asset-risk-treatment chain with inheritance, continuity planning, incident reporting with authority export, and risk reporting the executive level actually reads.
The CISO
The captured page carries exactly one sentence on ISMS management in a consolidated platform, with nothing behind it. I found no public information on risk methodology, asset inventory, protection-needs inheritance, risk acceptance with ownership, or incident handling with statutory reporting clocks — for a company carrying NIS2 exposure this reads as a marketing chapter, not a risk backbone. 1
The GRC Consultant
The single line about maintaining your ISMS in one consolidated audit platform is a promise, not a method: we found no public information on asset inventory, risk methodology, treatment tracking, protection-needs inheritance, or incident workflows with statutory clocks. I run a dozen ISMSs, and nothing captured lets me judge whether client twelve inherits anything from client one. 1
The Drafted IT Officer
The pitch is one line — "maintain your ISMS in one consolidated audit platform" — with nothing behind it. We found no public information on asset inventory, a risk methodology, treatment tracking, protection-needs inheritance or incident workflows with statutory reporting clocks, and as the person who would own a 24-hour report, a tagline is not an ISMS. 1
The Lead Auditor
The captured pages reduce the ISMS story to a single sentence — "Maintain your ISMS in one consolidated audit platform or compliance suite" — with nothing on asset inventory, risk methodology, treatment tracking, protection-needs inheritance, or incident workflows with statutory clocks. I found no public information on any part of the risk backbone, so this sits at the bottom of the scale. 1
The Evidence Integrator
A single sentence claims the ISMS can be maintained in one consolidated audit platform, and beyond that we found no public information on asset inventory, a risk methodology, treatment tracking, inherited protection needs, or incident handling with statutory reporting clocks. Without any feed from the live estate this reads as a typed risk register waiting to go stale. 1
The Skeptic
The whole ISMS claim is one sentence — "Maintain your ISMS in one consolidated audit platform or compliance suite" — and we found no public information on asset inventory, risk methodology, treatment tracking, protection-needs inheritance, or incident handling with statutory reporting clocks. That is a marketing chapter, not an evidenced risk backbone. 1
Controls, SoA & measures
Show reasoningHide reasoning
How this is scored
Control catalogs, statement of applicability, measure tracking and internal audit — whether the control side of the ISMS is operable or a checklist.
0 — A static control checklist; applicability, implementation status and evidence are the consultant's spreadsheet.
3 — Control catalogs with status fields, but no SoA generation, no measure ownership, no link between controls and risks.
5 — Controls linked to risks and measures with owners and due dates; SoA producible with manual assembly; internal audit supported by checklists.
8 — SoA on demand from live control status, measure tracking with delegation and escalation, internal audit workflows with findings management, controls carrying their own evidence.
10 — The control fabric as a living system: catalog updates versioned, SoA always current, audit programs with recurring schedules, and every control answerable with linked evidence at any moment.
The CISO
A real-time view of SOC 2 controls, progress and audit readiness is control status tracking, which is where the evidence stops. I found no public information on a statement of applicability generated from live status, measure ownership with due dates, or internal audit workflows with findings management — the SoA I sign and defend is not in evidence. 1
The GRC Consultant
A real-time view of SOC 2 controls, progress and audit readiness is genuine status tracking, which sits above a static checklist. But we found no public information on statement-of-applicability generation, measure ownership with due dates, escalation, or controls linked to risks and carrying their own evidence — without that, it is still the consultant's spreadsheet wearing a UI. 1
The Drafted IT Officer
A "real-time view of your SOC 2 controls, progress, and audit readiness" tells me controls carry status fields, which is genuinely where a solo security officer starts. We found no public information on statement-of-applicability generation, measure ownership with due dates, or how controls connect to risks, so the control side reads as tracking rather than an operable system. 1
The Lead Auditor
A "real-time view of your SOC 2 controls, progress, and audit readiness" evidences control status tracking, which puts the control side above a static checklist. I found no public information on statement-of-applicability generation, measure ownership with delegation, internal audit workflows, or any link between controls and risks. 1
The Evidence Integrator
The captured page promises a real-time view of SOC 2 controls, progress, and audit readiness, which implies status fields on the control side. We found no public information on statement-of-applicability generation, measure ownership with due dates, or internal audit workflows, so the evidence stops at control catalogs with status. 1
The Skeptic
The strongest capture is "a real-time view of your SOC 2 controls, progress, and audit readiness", which reads as control status tracking; we found no public information on SoA generation, measure ownership and delegation, or internal audit workflows. Status fields on a control list, with the rest left to the buyer's imagination. 1
Framework & standard coverage
Show reasoningHide reasoning
How this is scored
Which regimes the product actually operationalizes — ISO 27001, NIS2, TISAX/VDA ISA, DORA, BSI IT-Grundschutz, SOC 2 — and whether one control maps across them or each framework is a fresh island.
0 — One framework, hard-coded; anything else is "on the roadmap".
3 — Two or three frameworks as separate checklists; the same control is answered once per framework.
5 — The major regimes for its market with partial cross-mapping; newer regimes (NIS2, DORA) present as content packs of varying depth.
8 — Broad current coverage including NIS2/TISAX/DORA where relevant, one-control-many-frameworks mapping, and visible maintenance as regimes evolve.
10 — Framework coverage as a living product: dozens of regimes, genuine multi-compliance mapping on one data basis, per-industry profiles, and documented update cadence when the standard moves.
The CISO
Nine regimes are named — SOC 1 and SOC 2, HIPAA, HITRUST, Cyber Essentials, GDPR, CMMC Level 1, NIST CSF 2.0 and PCI DSS — a broad but US-weighted list. ISO 27001 appears only as an ISMS marketing phrase rather than in the framework list, NIS2, TISAX and DORA are absent, and I found no public information on one-control-many-frameworks mapping, so the same control may be answered once per regime. 1
The GRC Consultant
Nine regimes are named — SOC 1, SOC 2, HIPAA, HITRUST, Cyber Essentials, GDPR, CMMC Level 1, NIST CSF 2.0 and PCI DSS — which is broad coverage of the major US regimes for its market. We found no public information on NIS2, DORA, TISAX or BSI IT-Grundschutz, and nothing showing one control answer mapping across frameworks instead of being re-answered per regime — my whole reason to buy a platform. 1
The Drafted IT Officer
Nine named regimes — SOC 1, SOC 2, HIPAA, HITRUST, Cyber Essentials, GDPR, CMMC Level 1, NIST CSF 2.0 and PCI DSS — plus an "Other Frameworks" line and an ISO 27001 ISMS pitch is real breadth for a US-facing buyer. We found no public information on one-control-many-frameworks mapping, or on NIS2, DORA, TISAX or BSI IT-Grundschutz, which are the regimes a European operator gets asked about. 1
The Lead Auditor
Nine regimes are named — SOC 1, SOC 2, HIPAA, HITRUST, Cyber Essentials, GDPR, CMMC Level 1, NIST CSF 2.0, PCI DSS — which are the major regimes for a US-market buyer, plus an "Other Frameworks" bucket. I found no public information on one-control-many-frameworks mapping or update cadence, and the captured list names none of ISO 27001 as a certifiable regime, NIS2, DORA, TISAX, or BSI IT-Grundschutz despite the ISMS language. 1
The Evidence Integrator
Nine regimes are named — SOC 1, SOC 2, HIPAA, HITRUST, Cyber Essentials, GDPR, CMMC Level 1, NIST CSF 2.0, PCI DSS — plus a pointer to other frameworks, covering the major regimes for a US-market buyer. We found no public information on mapping one control across frameworks onto a single data basis, or on NIS2, DORA, TISAX, or BSI IT-Grundschutz content. 1
The Skeptic
The footer names nine regimes — SOC 1, SOC 2, HIPAA, HITRUST, Cyber Essentials, GDPR, CMMC Level 1, NIST CSF 2.0, PCI DSS — plus an unexplained "Other Frameworks", well past a two-or-three-regime offering. But we found no public information on whether one control maps across frameworks, and the named list includes no ISO 27001, NIS2, DORA or TISAX even though an ISMS is claimed. 1
Audit readiness & evidence
Show reasoningHide reasoning
How this is scored
Whether the system produces defensible proof: revision-safe history, evidence collection, reports for auditors, authorities and management.
0 — Exports are screenshots; history is overwritten in place.
3 — PDF reports exist but evidence is attached ad hoc and changes leave no reliable trail.
5 — Versioned records, standard report generators, evidence attachments per control; assembling a full audit file still takes days.
8 — Revision-safe change history, audit-scoped evidence packs on demand, management reports current at a click, auditor access roles.
10 — Audit readiness as a standing state: continuous evidence status per framework and scope, exportable proof packs an external auditor accepts as-is, and a defensible answer to "show me the state on date X".
The CISO
Real-time audit readiness for SOC 2 combined with an in-house CPA firm registered with the AICPA performing the audits means the audit file is born inside the platform — a structural advantage over platform-plus-external-auditor setups. But I found no public information on revision-safe change history, audit-scoped evidence packs on demand, or an answer to "show me the state on date X", so defensible proof is asserted rather than shown. 1
The GRC Consultant
Audit readiness is sold as a real-time view and the vendor performs audits through its own AICPA-registered CPA firm, which is more audit-facing than most compliance software. But we found no public information on revision-safe change history, auditor access roles, or evidence packs an external auditor accepts as-is. 1
The Drafted IT Officer
Real-time audit readiness on screen, with audits performed by the vendor's own AICPA-registered CPA firm, is a coherent story for a one-person security function. We found no public information on revision-safe history, exportable evidence packs, auditor access roles or reproducing the state of a past date — and that is the part an auditor actually tests. 1
The Lead Auditor
The page promises a real-time audit-readiness view and the vendor's own AICPA-registered assurance arm performs the audits, so the path from platform to report is tightly coupled. I found no public information on revision-safe change history, auditor-scoped evidence packs on demand, or any capability to show the state of controls on a given date — exactly the proof I would demand as a certifier. 1
The Evidence Integrator
Audits themselves are performed by an in-house licensed CPA firm registered with the AICPA, so the audit producer and the platform sit under one roof, and real-time audit readiness for SOC 2 is claimed. We found no public information on revision-safe change history, on-demand evidence packs, auditor access roles, or reconstructing the state at a given date. 1
The Skeptic
"Audit readiness" appears as a real-time view tied to SOC 2 controls, and the vendor runs its own AICPA-registered CPA firm (Laika Compliance, LLC dba Thoropass Assurance) — audit and platform under one roof. We found no public information on revision-safe change history, audit-scoped evidence packs, auditor access roles, or a state-of-record answer for any past date. 1
Integrations & automation
Show reasoningHide reasoning
How this is scored
Whether the platform feeds from the real IT estate — directory import, CMDB, ticketing, scanners, API — and automates evidence collection instead of re-typing it.
0 — A closed island: manual entry in, PDF out, no API.
3 — CSV/Excel import and export; no live connections, no API worth the name.
5 — Directory import (AD/Entra), a documented REST API for core objects, a handful of native connectors (ticketing, CMDB or SSO); automation is reminders and recurrence.
8 — Real connector set (Jira/ServiceNow-class ticketing, CMDB, cloud and endpoint sources), webhooks, SSO/SCIM, automated evidence tests with human review.
10 — The platform behaves like infrastructure: API parity for the data model, event streams, continuous control monitoring against the live estate, and automation that measurably removes the recurring toil rather than renaming it.
The CISO
Integrations and APIs is named as a product area, alongside vulnerability scanning and certified ASV scans as services, but the captured page names no connectors, no directory import and no API documentation. I found no public information on automated evidence collection from the live estate; what is visible is the label, not the wiring. 1
The GRC Consultant
Integrations and APIs are explicitly named as part of the offering, so this is not a closed island, but we found no public information on specific connectors, API scope for core objects, SSO or automated evidence collection. Directory import, CMDB, ticketing and scanner feeds are all open questions from these pages. 1
The Drafted IT Officer
"Integrations and APIs" appears as a footer service line and nothing more; we found no public information on named connectors, directory import or API documentation. Re-keying my estate by hand is exactly what I cannot sustain next to the day job, so a label without detail scores like a label. 1
The Lead Auditor
An "Integrations and APIs" product area appears in the footer, so connectivity is claimed, but the captured page names no connectors, no directory import, no CMDB, ticketing, or scanner sources, and no API scope or documentation. That is a label rather than a capability in evidence; I found no public information on what actually connects or what automation removes. 1
The Evidence Integrator
Integrations and APIs, Thoropass AI, and vulnerability scanning appear as footer line items, so the category exists in name. We found no public information on a documented REST API, directory import, ticketing or CMDB connectors, webhooks, SSO/SCIM, or automated control tests against the live estate — a navigation label is not a connector set, and this is the capability I weigh most. 1
The Skeptic
The offering list includes a line called "Integrations and APIs", but the captured pages name no connector, no API object, and no automation; we found no public information on directory import, ticketing, CMDB, scanners, SSO or SCIM. A section heading alone gives a buyer nothing to evaluate. 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the security posture of the whole company actually lives and under whose law — entity, hosting, subprocessors, DPA. The risk register is itself a target.
0 — Non-EU entity, non-EU-default hosting, no public DPA or subprocessor list — for the system holding your risk register.
3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad or undocumented.
5 — EU hosting is the default, DPA and subprocessor list published; the vendor or a critical subprocessor is still within non-European jurisdictional reach.
8 — EU entity, EU hosting with named data centers, published subprocessor list free of content-touching non-EU processors, DPA and TOMs public.
10 — Jurisdictionally clean end to end: European ownership, EU-only hosting and subprocessors, on-premises or sovereign-cloud options, and the whole chain documented publicly.
The CISO
Both entities are American — Thoropass, Inc. and a licensed CPA firm registered with the AICPA — with a DPA listed among the legal documents but nothing more on record. I found no public information on hosting locations, a subprocessor list, or any EU hosting option; for the system that would hold my risk register, that leaves the whole chain within non-European jurisdictional reach by default. 1
The GRC Consultant
Thoropass, Inc. is a US entity and the assurance arm is an AICPA-registered CPA firm, with a DPA listed among the legal documents — but we found no public information on hosting locations, an EU region, or subprocessors. For a system holding the risk register itself, that is undocumented jurisdictional exposure I would not sign for. 1
The Drafted IT Officer
Thoropass, Inc. is a US firm and audits run through Laika Compliance, LLC dba Thoropass Assurance registered with the AICPA; an MSA and DPA are listed, but we found no public information on EU hosting options, data-center locations or a subprocessor list. For a system that would hold my risk register, US jurisdiction end to end as far as the captured pages go is a real consideration. 1
The Lead Auditor
The main entity and the assurance arm are US-incorporated, with the assurance firm registered with the AICPA, and a DPA is listed among the legal pages; that is the sum of what is published. I found no public information on EU hosting, named data centers, or a subprocessor list, so a European buyer's risk register and audit file would sit under US jurisdiction with nothing published to bound that exposure. 1
The Evidence Integrator
The operating entity is US-incorporated with an AICPA-registered audit arm, and a DPA is among the published legal documents. We found no public information on hosting location, an EU region, or a subprocessor list, so the risk register itself would live under non-European jurisdictional reach — my standing concern for this category of system. 1
The Skeptic
Thoropass, Inc. is a US firm whose assurance arm is an AICPA-registered CPA entity, and a DPA is among the listed legal documents; beyond that we found no public information on hosting location, named data centers, or subprocessors. The system meant to hold your risk register would live with a non-EU company whose processing arrangements are not shown publicly. 1
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real invoice — per module, per entity, per year, with consulting unbundled — from public pages alone. Unpublished pricing is the B2B norm in this market, so this criterion describes rather than condemns; the benches weight it accordingly.
0 — No public prices at all; every configuration is a sales conversation.
3 — An entry price exists, but module add-ons, scale steps or bundled consulting make the real total incomputable.
5 — Most editions carry real numbers with billing period stated and software separated from services; at least one commonly needed module or scale step is unpriced.
8 — Every edition and module priced publicly with entity/user boundaries and setup fees stated; only genuine corporate-group contracts are custom.
10 — Complete price computability: modules, scale steps, service packages and renewal rules public, so the invoice for a 100-employee company and a certification project is a two-minute exercise.
The CISO
I found no public pricing information in the captured pages — no edition prices, no billing period, nothing stated per module or per service. With the audit delivered by the vendor's own assurance firm and pentesting sold alongside the software, the real invoice comes from a sales conversation, which is the market norm here and worth stating plainly. 1
The GRC Consultant
No prices appear anywhere on the captured pages: no editions, modules, per-user or per-entity terms, and no separation of software from the pentesting, scanning and audit services. A buyer cannot compute any part of the invoice from public information; every configuration is a sales conversation. 1
The Drafted IT Officer
We found no public pricing information: no edition numbers, no module prices, no separation of software from consulting services. That is normal in this market, but it means a drafted IT officer cannot build a budget before a sales conversation. 1
The Lead Auditor
No price figure of any kind appears on the captured page — no editions, no modules, no billing periods, no separation of software from audit services such as the named pentesting and ASV scanning. Unpublished pricing is the norm in this market, but the criterion describes it at its floor, and I found no public information from which any part of an invoice could be computed. 1
The Evidence Integrator
We found no public pricing of any kind on the captured page — no edition prices, module rates, scale steps, or billing periods. Unpublished pricing is the norm in this market; I record only that no numbers were visible. 1
The Skeptic
No price, edition, module, user or entity boundary, or billing period appears anywhere in the captured material, and software sits alongside unpriced services like penetration testing, ASV scans and audits. We found no public information on pricing; every configuration is a sales conversation. 1
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data residency, Subprocessors. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on pricing on the pages we read (thoropass.com, thoropass.com/privacy-policy, thoropass.com/data-processing-addendum, help.thoropass.com/en/articles/11887300-asset-intelligence, help.thoropass.com/en/collections/14300359-asset-inventory, help.thoropass.com/en/collections/3334200-controls and 7 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- We could not confirm any compliance information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- 13 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 8 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page thoropass.com Checked 22 Sep 2026 Details →
- 2 Privacy policy — found from the homepage www.thoropass.com Checked 30 Sep 2026 Details →
- 3 Data processing agreement (dpa) — found from the homepage www.thoropass.com Checked 30 Sep 2026 Details →
- 4 Asset & risk management depth — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →
- 5 Asset & risk management depth — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →
- 6 Controls, SoA & measures — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →
- 7 Controls, SoA & measures — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →
- 8 Framework & standard coverage — found from sitemap www.thoropass.com Checked 1 Oct 2026 Details →
- 9 Framework & standard coverage — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →
- 10 Audit readiness & evidence — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →
- 11 Audit readiness & evidence — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →
- 12 Integrations & automation — found from sitemap www.thoropass.com Checked 1 Oct 2026 Details →
- 13 Integrations & automation — found from sitemap help.thoropass.com Checked 1 Oct 2026 Details →