What you carry
Annualized loss expectancy across the register, before any mitigation is credited.
Lanterna Tech helps you put an annual figure on your IT/OT exposure, on the share your plan already covers, and on what the next investment actually buys.
Personalised onboarding included
Illustrative example — seeded Monte-Carlo simulation.
The gap
A critical IT device, a controller that goes end-of-support next quarter, is obvious to the people who run it but abstract to the people who fund it. Roadmap tools describe the work. They rarely say what happens if it doesn't get done — so the ask competes on conviction instead of arithmetic.
Lanterna Tech was built the other way around: every initiative carries the loss it prevents, and every view rolls that up. The plan and the business case are the same artifact.
Quantification FAIR-based
Each initiative carries a loss magnitude range and an event frequency. From those, two engines run: a deterministic annualized loss expectancy for a figure you can defend line by line, and a seeded Monte-Carlo simulation for the distribution behind it.
Annualized loss expectancy across the register, before any mitigation is credited.
The same figure after each initiative's mitigation, so the roadmap's value is stated rather than asserted.
Exposure removed per dollar spent, ranked — the efficient frontier of your own backlog.
Execution
The remediation program groups active initiatives into waves from their dependencies, so the order of execution comes out of the plan instead of a meeting. Give it a budget ceiling and it returns the executable set — greedy on return, closed over prerequisites, so nothing lands before what it depends on.
Waves, critical path, and a Gantt on real dates with dependency arrows.
What is on fire right now — blast radius, residual exposure, deadline countdowns.
Industrial
Where an IT incident costs data, an OT incident can move something physical. Lanterna Tech carries the model industry already reasons in: six Purdue levels from the process itself up to enterprise IT, with IEC 62443 zones and conduits attached — so a blind spot between levels is visible rather than inferred.
Assets and initiatives from level 0 to level 4, with the industrial DMZ sitting at 3.5.
Run an IEC 62443 assessment campaign with your suppliers: each one answers via their own private link, you review requirement by requirement, and you approve or reject each response.
Pull findings from Claroty, Nozomi Networks, or a generic scanner on a schedule, and get told what changed. If a single connector fails, no vendor finding is declared resolved that round — an outage never reads as a fix.
Third parties
Link assets to the suppliers behind them and criticality propagates upward: a vendor inherits the highest criticality of anything it touches, computed from Purdue level, loss expectancy, and blast radius.
You keep the last word — a criticality set by hand on an asset always overrides the computed one.
Suppliers against the assets they touch, criticality derived from the assets themselves.
Frameworks
Each catalogue is held at its real granularity, scored, and turned into initiatives that inherit the exposure model like anything else on the roadmap.
Cyber & OT frameworks
These are self-assessment and prioritization tools. They tell you where you stand and what to tackle first — they certify nothing and replace no auditor.
For whom
Built-in Purdue model, IEC 62443 by zone, NIST CSF 2.0 self-assessment, SL gap analysis on every device.
NIST CSF 2.0 + IEC 62443 assessment, with timestamped, tamper-evident attestations. No files to reconstruct for the auditor.
Automatic EOL lookup via endoflife.date, alerts six months out, replacement plan included.
At-rest encryption (KMS envelope), per-tenant IP allow-lists, SSO, TOTP 2FA, SHA-256 audit trail. Documentation ready for the board.
The surface
One register. Every view reads the same initiatives and the same assets — nothing is re-entered to appear somewhere else. The board, the Gantt, the exposure curve and the executive page are the same data seen from different chairs.
Clickable metrics, tabbed widgets, multiple personas available (CISO, CTO, CFO, DG).
Underneath
An asset register plus an OT topology is the map an attacker is looking for. So the platform is built around a precise question — not “how do we defend ourselves?” but “what could someone read who has already taken our servers?” The answer is in how the keys are split below: the most sensitive one never reaches us.
Every organization has its own data key, never stored in the clear: it is wrapped by a key living in a cloud KMS vault, separate from the database. The server asks for it when needed, keeps it in memory for five minutes, and every request is logged. Revoking that key ends access — immediately, and for the whole organization.
Asset names and descriptions — what identifies your equipment — are encrypted in your browser before they are sent, with AES-256-GCM. The key that seals them is derived from your passphrase by PBKDF2-SHA256 at 600,000 iterations and never leaves the tab. All we receive is an opaque string. This is not a promise about our conduct: we do not hold the key, so there is no other way for us to behave.
Microsoft Entra ID SSO, passkeys, or a password with mandatory TOTP. No account is ever created with a password chosen by someone else: creation issues a one-hour activation link, and the invitee sets their own password and second factor.
Each audit entry carries the fingerprint of the one before it, in SHA-256. Removing or altering a line breaks the chain instead of making it vanish — tampering becomes visible rather than undetectable.
Quick overview
4-step wizard: title, domain, status, horizon. 30 seconds. You can also import from CSV with column mapping.
Define your Purdue zones and target SLs, then assess against IEC 62443 and NIST CSF 2.0. Lanterna Tech detects SL gaps and vulnerable assets.
Drag to reorganize dates, computed dependencies, highlighted critical path. Cascade preview on hover to see impact.
Sandbox mode to simulate a delay, migration or replacement without touching the live plan. Compare scored scenarios before deciding.
Board-ready PDF in one click. KPIs, top risks, deadlines, maturity per domain. Schedulable weekly.
Decision log per initiative: who, when, on what basis, with what trade-offs. Integrity-verifiable SHA-256 chain.
And you are not on your own: we set up your first assets with you.
Pricing
SMB, first structured roadmap
Mid-market, structured IT
Large enterprise
Industry, critical infrastructure
Questions
Each initiative carries a loss range (minimum and maximum) and an annual event frequency, following the FAIR approach. Two engines run on that: a deterministic annualized loss expectancy (ALE) you can defend line by line, and a Monte Carlo simulation for the distribution behind it. The simulation is seeded: the same data gives the same result, so two versions of the plan can be compared without random noise.
Gross exposure is the annualized expected loss across the whole register before any mitigation credit — what you carry today. Residual exposure is the same calculation after each initiative in the plan applies its mitigation. The difference, avoided exposure, is what the roadmap takes off the table: its value is stated in dollars per year rather than claimed.
It is the 90th percentile of simulated annual losses. Lanterna Tech states it in plain words: “there is a 10% chance that annual losses exceed X.” The median (P50) describes an ordinary year, the P90 a plausible bad one; the loss exceedance curve sets both against your risk appetite threshold.
Yes. The Enterprise OT tier adds the Purdue model, from the physical process (level 0) up to the enterprise (level 4) with the industrial DMZ at 3.5, plus IEC 62443 zones and conduits with their target security levels. You can import findings from Claroty or Nozomi Networks and track what changed week to week, and run IEC 62443 assessment campaigns with your suppliers.
No. The IEC 62443 and NIST CSF 2.0 assessments are self-assessment and prioritization tools: they show where you stand and where to start, then turn the gaps into costed initiatives. They certify nothing and do not replace an auditor.
Partly, and we say so plainly. All of your organization's data is encrypted at rest with a key unique to your organization, wrapped by a KMS vault kept apart from the database: a stolen database or backup yields nothing readable, but our server can decrypt the data to run the application. Once your administrator turns on the vault, the most sensitive fields (asset names and descriptions, the OT register, supplier contact details, assessment notes) are encrypted in your browser with a key derived from your passphrase, which we never hold: those we cannot open. The limit of any in-browser encryption applies: it does not protect against a compromised server delivering modified code.
Starter $100, Professional $350 and Enterprise $650 per month, in US dollars; Enterprise OT is quoted. Annual billing takes −25% off. Each tier lists its user, initiative and asset limits in the Pricing section.
Creating an initiative takes about thirty seconds, and both initiatives and assets can be imported from CSV. You are not on your own either: we set up your first assets with you, and the Enterprise OT tier includes dedicated OT onboarding.
Next
We reply within one business day. No sales funnel, no bot — someone who knows the subject.